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...:-(

Re: php5 port compile problem

Hi Xander, Thanks for the info, but do you mean the bind9 port? I'm not excited about installing a port for bind when it is in the base distro already, but... joel > I know this problem! I encountered it a few months ago when php5 was this > beta. > > What I found was that you need bind9 for ph

Re: freebsd 5.3 have any problem with vinum ?

Hi Greg, Greg 'groggy' Lehey wrote: On Monday, 25 October 2004 at 14:21:33 -0600, secmgr wrote: It's beginning to look like that's a bad idea. Lukas is (understandably) working only on gvinum, and since I know it's nearly there, I'm not going to do any further work on Vinum in FreeBSD 5. Given

Re: TFTPD timeout

Dear Folks, Could the timeouts be caused by the tftpd running with -l (and therefore trying a gethotbyaddress() on the booting workstation) ? This caused me near disasters with tftp loads on small Cisco router (2500 series that need to boot to download the image). Yours sincerely. -- St

Re: msdosfs - support for large disks?

Torfinn Ingolfsen wrote: Hello, I was trying to find out the current status of support for large MS-DOS disks (well, filesystems, perhaps) in -stable (and 5.3). I checked mount_msdosfs(8), msdosfs(5), fsck_msdosfs(8), newfs_msdos(8), the Handbook and the FAQ. Nowhere could I find any statement as t

msdosfs - support for large disks?

Hello, I was trying to find out the current status of support for large MS-DOS disks (well, filesystems, perhaps) in -stable (and 5.3). I checked mount_msdosfs(8), msdosfs(5), fsck_msdosfs(8), newfs_msdos(8), the Handbook and the FAQ. Nowhere could I find any statement as to what size disk / files

usb printer problems

Hello, I'm having difficulty with usb devices, specifically a camera and a printer - I'm starting to tear my hair out! Problem ONE is that they are not always detected. Sometimes everything goes fine: ugen0: Eastman Kodak Company KODAK

Sound keeps dying

Running 4-STABLE. Sound on my system works after boot, but then later stops. Here's what I see in /var/log/messages... Oct 30 17:11:19 catbert /kernel: pcm0: port 0xe400-0xe43f irq 10 at device 11.0 on pci0 Oct 30 17:11:19 catbert /kernel: pcm0: Oct 30 17:17:04 catbert /kernel: pcm0:play:0: p

Re[2]: TFTPD timeout

R> Maxim V Tretjyakov wrote: >> >>>Do you have an entry for tftpd in /etc/hosts.allow ? >> >> >> Yes, there is: >> ALL : ALL : allow >> >> I never changed this file. R> I have a tftp server running on a master PC for a cluster of R> diskless PCs (though this is a 5.3 system). When using the R>

Re: freebsd 5.3 have any problem with vinum ?

On Friday, 29 October 2004 at 14:20:40 -0600, secmgr wrote: > Greg 'groggy' Lehey wrote: > >> A bit of background: we know that 'gvinum' will replace Vinum; the >> original intention had been to do it seamlessly, but for various >> reasons that did happen. Then we decided that we should leave them

Re: TFTPD timeout

Maxim V Tretjyakov wrote: Do you have an entry for tftpd in /etc/hosts.allow ? Yes, there is: ALL : ALL : allow I never changed this file. I have a tftp server running on a master PC for a cluster of diskless PCs (though this is a 5.3 system). When using the proper hostnames or IP numbers with tf