Why the mode of /dev/null is changed after system reboot?
I have a gateway running FreeBSD 4.10-p3. Normally, the mode of /dev/null should be 666, but recently, I find that its mode is changed to 600 automatically after reboot, I have checked all /etc/rc* and /usr/local/etc/rc.d/*, but I can't get anything that led to it...:-( ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Why the mode of /dev/null is changed after system reboot?
> It could be a port doing this at startup, but we still need more > debugging.. > > Kris > > I think that sshd2 does this. because I installed it only recently... ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Why the mode of /dev/null is changed after system reboot?
No, it just happened after system reboot...:-) If I chmod it to 666ïit will re-chmod it to 600 after system reboot. On Tue, 2 Nov 2004 09:08:15 +0300 (MSK), Dmitry Morozovsky <[EMAIL PROTECTED]> wrote: > I remember I stepped into this once or twice in the past. Bad umask at > mergemaster/MAKEDEV time possibly? > > Sincerely, > D.Marck [DM5020, MCK-RIPE, DM3-RIPN] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Why my RELENG_5 box auto reboot after compiling kernel without console support?
I have ever compiled kernel without console, keyboard, and VGA in RELENG_4, it is no problem, and works fine, but I can't do so in RELENG_5 now...:-( ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Why I can't disable ACPI?
I'm running a RELENG_6 (Beta2) as my desktop now. When I add "hint.acpi.0.disabled=1" to /boot/loader.conf and reboot, system can't find my ATA disks and can't boot sucessfully... ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Too short ethernet frame...
OS: RELENG_6 (Beta2) NIC: vr0: # tcpdump -penv -i vr0 less 32 16:15:42.512701 [|ether] 16:15:44.523102 [|ether] 16:15:46.522495 [|ether] 16:16:00.540387 [|ether] 16:16:02.541834 [|ether] 16:16:08.550068 [|ether] 16:16:10.570483 [|ether] # snort -pev -i vr0 less 32 Captured data length < Ethernet header length! (0 bytes) Captured data length < Ethernet header length! (0 bytes) Captured data length < Ethernet header length! (0 bytes) When I run rdesktop, more invalid ethernet frame was sniffered... ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Too short ethernet frame...
On 8/12/05, Brooks Davis <[EMAIL PROTECTED]> wrote: > > Most likely, your cabling, duplex configuraion, nic, switch are > misconfigured and a high traffic ap like rdesktop is pushing them over > the edge. I'd check the duplex settings on each end and try another > cable first. Then try a different nic and switch if possible. It's > possible the problem is a driver bug, but it's more likely you've for > some sort of physical network problem. > > -- Brooks > Thanks a lot for your reply. I have try another NIC (RealTek 8029), and the same things happens. But when I run 6.0 Beta1 kernel or a LiveCD Linux, I can't see any too short ethernet frames... BTW: It happens not only when I run rdesktop... ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Too short ethernet frame...
Just now, I add "date=2005.07.31.03.00.00" to my src cvsup sup-file and make kernel, too short ethernet frames are still sniffered. But when I add "date=2005.07.22.03.00.00" to sup-file and cvsup and make kernel, the damn datagrams gone!!! ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Too short ethernet frame...
On 8/16/05, Brooks Davis <[EMAIL PROTECTED]> wrote: > > Sounds like someone introduced a bug in the nic driver or the ethernet > code, but I'm not seeing anything obvious between those dates. If you > could narrow the date range further that would help. > > -- Brooks OK, now, I get the result: "tag=RELENG_6 date=2005.07.30.22.00.00" works fine, "tag=RELENG_6 date=2005.07.31.03.00.00" makes noise, many many ethernet frames can be sniffered. the cvsup log: Updating collection src-all/cvs Edit src/sys/dev/mlx/mlx_pci.c Add delta 1.23.2.1 2005.07.31.00.41.53 csjp Edit src/sys/net/bpf.c Add delta 1.153.2.1 2005.07.31.00.48.18 csjp Edit src/sys/net/bpfdesc.h Add delta 1.29.2.1 2005.07.31.00.48.18 csjp Shutting down connection to server Finished successfully I guess it should be bpf.c... ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Too short ethernet frame...
On 8/18/05, Ian Dowse <[EMAIL PROTECTED]> wrote: > > There appear to be some braces missed in that revision of bpf.c. Does > the following patch help? > > Ian > Thank you very much, your patch works fine for me... ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 6.0-BETA3: 'kldunload linux' --> panic
On 8/23/05, Rene Ladan <[EMAIL PROTECTED]> wrote: > The following panic can reliably be reproduced on a GENERIC 6.0-BETA3 > kernel when loading linux support via /etc/rc.conf (linux_enable="YES") > and then issuing "kldunload linux". > No, I have a BETA3 box too, and can unload linux kernel module after booting with linux_enable="YES"... ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 6.0-BETA3: 'kldunload linux' --> panic
On 8/23/05, Rene Ladan <[EMAIL PROTECTED]> wrote: > > On a i386 UP ? > CFLAGS=-O2 -pipe (should be safe) > Yes, my box is a x86 UP system, my CFLAGS=-O -pipe ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
