Re: Accessing FreeBSD 3.4-STABLE filesystems from 4.0-STABLE...
Thus spake Brad Knowles ([EMAIL PROTECTED]): upgraded it to 4.0-STABLE on a second hard drive, and I likewise can't access the 4.0-STABLE filesystems from 3.4-STABLE. If you don't tell us where it fails (and how), we can't help you. Alex To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Accessing FreeBSD 3.4-STABLE filesystems from 4.0-STABLE...
-On [2325 03:05], Brad Knowles ([EMAIL PROTECTED]) wrote: I gotta be doing something stupid here. I haven't been able to access the existing 3.4-STABLE filesystems on this machine since I upgraded it to 4.0-STABLE on a second hard drive, and I likewise can't access the 4.0-STABLE filesystems from 3.4-STABLE. Block/character device collapsing breaking you up now? /dev/ Should only be character devices now. -- Jeroen Ruigrok van der Werven Network- and systemadministrator [EMAIL PROTECTED] VIA NET.WORKS The Netherlands BSD: Technical excellence at its best http://www.bart.nl Like cures like... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Accessing FreeBSD 3.4-STABLE filesystems from 4.0-STABLE...
In message [EMAIL PROTECTED] Jeroen Ruigrok van der Werven writes: : Block/character device collapsing breaking you up now? : : /dev/ Should only be character devices now. I was surprised how many block devices were in my /dev when I did a ls -l /dev | grep ^b. Maybe we should put something in /etc/daily in -current to whine about all block devices in /dev :-) Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Accessing FreeBSD 3.4-STABLE filesystems from 4.0-STABLE...
Warner Losh wrote: In message [EMAIL PROTECTED] Jeroen Ruigrok van der Werven writes: : Block/character device collapsing breaking you up now? : : /dev/ Should only be character devices now. I was surprised how many block devices were in my /dev when I did a ls -l /dev | grep ^b. Maybe we should put something in /etc/daily in -current to whine about all block devices in /dev :-) Well, there is a message in the boot scroll, but if you use a splash screen you'll miss it (like I did until I started doing some boot debugging recently). I was also pretty shocked at how much cruft I had. I took the extreme route of 'rm *' and started from the beginning again. Doug -- "So, the cows were part of a dream that dreamed itself into existence? Is that possible?" asked the student incredulously. The master simply replied, "Mu." To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Accessing FreeBSD 3.4-STABLE filesystems from 4.0-STABLE...
On Sat, Mar 25, 2000 at 01:40:05PM -0700, Warner Losh wrote: In message [EMAIL PROTECTED] Jeroen Ruigrok van der Werven writes: : Block/character device collapsing breaking you up now? : : /dev/ Should only be character devices now. I was surprised how many block devices were in my /dev when I did a ls -l /dev | grep ^b. Maybe we should put something in /etc/daily in -current to whine about all block devices in /dev :-) At a slight tangent; could removal of block devices be the cause of this message when starting the ddd debugger? gdb: warning: cannot set file to non-blocking mode: Resource temporarily unavailable and when exiting: gdb: warning: cannot restore file mode: Resource temporarily unavailable Possibly trying to set a device (the pipe?) to non-blocking when it already is? Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message -- Seminars, n.: From "semi" and "arse", hence, any half-assed discussion. FreeBSD - The Power To Serve http://www.freebsd.org My Webpage http://ukug.uk.freebsd.org/~mark/ mailto:[EMAIL PROTECTED] http://www.radan.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Accessing FreeBSD 3.4-STABLE filesystems from 4.0-STABLE...
Folks, I gotta be doing something stupid here. I haven't been able to access the existing 3.4-STABLE filesystems on this machine since I upgraded it to 4.0-STABLE on a second hard drive, and I likewise can't access the 4.0-STABLE filesystems from 3.4-STABLE. Anybody got any ideas what I might have done wrong, and what parts of the archives I should go searching in (and what I should be searching for ;-), in order to find the answers? Thanks! -- These are my opinions -- not to be taken as official Skynet policy == Brad Knowles, [EMAIL PROTECTED]|| Belgacom Skynet SA/NV Systems Architect, Mail/News/FTP/Proxy Admin || Rue Colonel Bourg, 124 Phone/Fax: +32-2-706.13.11/12.49 || B-1140 Brussels http://www.skynet.be || Belgium To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
