This has been going on for awhile, and I've looked everywhere for a
solution. When I boot single user, the / filesystem gets mounted on
wd0s4a even though /dev does not even have such an entry nor does
/etc/fstab, since these have all been updated.
This is not really such a problem until I try
Original Message
On 3/10/00, 9:51:06 AM, R Joseph Wright [EMAIL PROTECTED] wrote
regarding single user mode problem:
This has been going on for awhile, and I've looked everywhere for a
solution. When I boot single user, the / filesystem gets mounted on
wd0s4a even though /dev does
This has been going on for awhile, and I've looked everywhere for a
solution. When I boot single user, the / filesystem gets mounted on
wd0s4a even though /dev does not even have such an entry nor does
/etc/fstab, since these have all been updated.
This is not really such a problem
This has been going on for awhile, and I've looked everywhere for a
solution. When I boot single user, the / filesystem gets mounted on
wd0s4a even though /dev does not even have such an entry nor does
/etc/fstab, since these have all been updated.
This is not really such a problem until I
Regardless, this is typically syptomatic of either a very old
/boot/loader, non-use of the loader eg. through a /boot.config file, or
an error in the entry for / in /etc/fstab.
Isn't /boot/loader updated upon making a new world? If so, it ought to be
current. I don't know any way of
On Fri, Mar 10, 2000 at 11:21:15AM -0800, R Joseph Wright wrote:
Regardless, this is typically syptomatic of either a very old
/boot/loader, non-use of the loader eg. through a /boot.config file, or
an error in the entry for / in /etc/fstab.
Isn't /boot/loader updated upon making
On Fri, 10 Mar 2000, in a never-ending search for enlightenment, R Joseph Wright wrote:
Regardless, this is typically syptomatic of either a very old
/boot/loader, non-use of the loader eg. through a /boot.config file, or
an error in the entry for / in /etc/fstab.
Isn't
On Fri, 10 Mar 2000, Walter Brameld wrote:
On Fri, 10 Mar 2000, in a never-ending search for enlightenment, R Joseph Wright
wrote:
Regardless, this is typically syptomatic of either a very old
/boot/loader, non-use of the loader eg. through a /boot.config file, or
an error in the
