Hi,
> On Sun, 26 Feb 2006 22:56:32 +0200
> Rostislav Krasny <[EMAIL PROTECTED]> said:
rosti> Could you please suggest a good
rosti> comprehensive article on the Web about IPv4-mapped IPv6 addresses and
rosti> their usage?
You can find some documents by googling with `IPv4-mapped IPv6
add
On Sun, Feb 26, 2006 at 09:19:35PM +0100, Dimitry Andric wrote:
> > comconsole_speed= in /boot/loader.conf
> > existing speed, if comconsole is already set by previous stage
> > BOOT_COMCONSOLE_SPEED compile time default
>
> Well, the last item will simply never be hit, since there is ALWAYS a
>
Uwe Laverenz wrote:
Hi,
there seems to be a problem with RELENG_6 in environments where nss_ldap
is used for user- and group-lookups. The problem affects different ports
that don't have very much in common, so I guess there might be a bug in
FreeBSD's libc, because that's the place, where the na
On Mon, 27 Feb 2006 02:49:15 +0900
Hajimu UMEMOTO <[EMAIL PROTECTED]> wrote:
> Hi,
>
> > On Sun, 26 Feb 2006 17:40:19 +0200
> > Rostislav Krasny <[EMAIL PROTECTED]> said:
>
> rosti> It will require to specify a virtual host for each address or to use
> rosti> hostname with multiple addre
Ed Maste wrote:
> So I suspect that the following happens when you boot:
>
> - your BIOS sets the serial port to 9600
Yes.
> - boot0 does nothing with the serial pot
I'm using 'dangerously dedicated' disks, so it's only boot[12] that is used.
> - boot1/2 reads the -P in /boot.config and detect
Ian Dowse wrote:
> The problem may be that your boot blocks were compiled with
> BOOT_COMCONSOLE_SPEED set to 9600. Try reinstalling them with e.g.
> `disklabel -B ad0s1' (make sure you get the right device name -
> it should be the slice that you boot from).
Argh, shouldn't have done this without
Ed Maste wrote:
>> Okay, but why did 4.x through 5.x through 6.x (these have all been on
>> this particular machine) always boot with 115200 until now? :)
> Because now the loader has new behaviour of using the existing speed
> if the previous stage indicates a serial port is in use, instead
> of
Ian Dowse wrote:
>> Okay, but why did 4.x through 5.x through 6.x (these have all been on
>> this particular machine) always boot with 115200 until now? :)
> They probably used 9600 for the boot blocks, and then switched to
> 115200 when /boot/loader started, so you didn't notice. Now the
> settin
On 10 feb 2006, at 07.15, Johan Ström wrote:
Hi list!
I've been experiencing problems earlier with gmirror (thread "Page
fault, GEOM problem??"). My gmirror crashed, and the box compleatly
froze.
Now I got a new mobo, and it has been working great since (no
crashes, and i get decent 40-5
My video card spits out rather weird messages to the kernel message
buffer. This is only an annoyance, except it causes dmesg to seg fault.
I have some very simple possible fixes at
http://www.freebsd.org/cgi/query-pr.cgi?pr=93841
It is nothing crucial but it would be nice if a fix was submit
Hi,
> On Sun, 26 Feb 2006 17:40:19 +0200
> Rostislav Krasny <[EMAIL PROTECTED]> said:
rosti> It will require to specify a virtual host for each address or to use
rosti> hostname with multiple addresses only once. Specifying a virtual host by
rosti> a hostname and registering multiple host
On Sun, 26 Feb 2006 09:45:34 +0900
Hajimu UMEMOTO <[EMAIL PROTECTED]> wrote:
> Hi,
>
> > On Sun, 26 Feb 2006 01:46:30 +0200
> > Rostislav Krasny <[EMAIL PROTECTED]> said:
>
> rosti.bsd> As far as I understand the code of selecthost() it walks through
> linked
> rosti.bsd> lists of known
Problem: Bogus modification dates cause tar/bsdtar 1.02.023 failure,
gnutar works
The files were created from old Macintosh files using netatalk. One file
has a bogus modification date of Nov 16, 1913, which appears to cause
"bsdtar" to fail:
newserv# tar cvf /tmp/test.tar hpLaserJet456Ins
Darren,
On Sun, Feb 26, 2006 at 12:16:05PM +, Darren Reed wrote:
D> > Root of the problem is inside ipfilter - if driver use 'partial' (i.e.
without
D> > pseudo header) rx checksum offloading ipfilter fails to calculate checksum
D> > correctly (it's using ip packet length (ip_fil_freebsd.c:
On Tue, Jan 31, 2006 at 12:09:13PM +0300, Oleg Bulyzhin wrote:
> > > Btw, until recent changes bge had txcsum (not rxcsum) only.
> > >
> > > As i can see there is no problem with checksum's at all (at least inside
> > > bge driver). tcpdump reports bad checksum on outgoing packets due to
> > > nat
On Sun, Feb 26, 2006 at 03:55:56AM -0600, Nikolas Britton wrote..
> Nevermind, I followed my own advice, everything's working perfect now.
>
> 1. Removed promise and highpoint cards.
> 2. Connected the primary drive to the onboard SATA controllor.
> 3. Installed BETA2.
> 4. cvsup'd new src, checke
Nevermind, I followed my own advice, everything's working perfect now.
1. Removed promise and highpoint cards.
2. Connected the primary drive to the onboard SATA controllor.
3. Installed BETA2.
4. cvsup'd new src, checked if sos's patches were in there, it was. so
he missed BETA2.
5. rebuilt kerne
On Sun, Feb 26, 2006 at 12:32:05AM +, Gary Palmer wrote:
> Mathieu Prevot wrote:
>
> >Hello,
> >
> >I remarked something I don't understand. I have a usb mouse, and if I
> >just have usbd_enable="YES" and moused_enable="NO" in rc.conf I can have a
> >functionnal mouse after boot. If I go to si
I use nss_ldap-1.239 and nss_ldap-1.244 on 5.4 and 6.0
I have a problem -- login success only if {CRYPT} mechanism used in
ldap database. Other services, authenticated in ldap, work fine
(pam_ldap, apache auth for example).
My configs:
/etc/pam.d/system
# auth
authsufficient pam_o
19 matches
Mail list logo
