I think lack of disk space is a poor excuse for an organization
distributing an OS. This isn't the 90's. 500GB drives are $99.00 at
newegg and that's enough to hold the OS, ports, and packages for 50
releases (at least). Surely the decision not to keep older releases
where pkg_add() can find
Processes that access a share from a remote machine hang if the connection
goes away. I'm using FBSD V5.4 and mount_smbfs. This can be replicated
by the following sequence:
1) Share a file system from a remote Windows machine.
2) Mount the share using mount_smbfs
3) Start a tar() command to
Thanks for responding.
Do you see the problem if you only use mkisofs?
Yes. I just tried it and got the same problem with an iso image using
mkisofs. This is starting to look like a timezone issue. The date/time
difference between the date displayed via ISO and the date displayed via
FFS
Hello,
I've got a curious problem using growisofs on FBSD 5.2.1-RELEASE #0.
I'm using the following hardware (from dmesg):
acd0: DVDR HP DVD Writer 530 at ata1-slave PIO4
cd0: HP DVD Writer 530r VPS8 Removable CD-ROM SCSI-0 device
Using the cd0 device (through atapicam) I can write to
I'm looking for a way to build an indicator light that shows when
the OS is booted and ready on a headless system. Is there a way
to do this and do you know of any documentation that explains how
to do something like this?
Jon
___
[EMAIL PROTECTED]