Please wrap your messages to 72 columns like other civilised authors.
>>>> No, I do not talking about /etc/fstab, I'm talking about what device
>>>> kernel is using to mount root *before* starting /sbin/init (e.g.
>>>> "changing root device to ..." in dmesg).
>>>
>>> Hmm, the bootblock or the loader might be responsible....
>>
>> This is -current. If the message is "changing root device to..." you
>> are out of date and must update before we can help you.
>>
>> The root mount code has changed quite a lot just recently, and
>> debugging the 'old' code isn't practical anymore.
>
> You are not right - I'm usually rebuilding kernel in one-three days,
> and world in a week. My current kernel built from sources sup'ed
> (cvsup.freebsd.org) yesterday.
There is no room for me to be "not right"; the "changing root device
to" message has been gone for quite some time now. If you are seeing
it, you are "not right" and are running code built from old sources.
To cover your original point; an up-to-date -current kernel correctly
booted will mount the device listed in /etc/fstab as the root device
"*before* starting /sbin/init". The re-mount of the root filesystem
subsequently performed will actually re-use the device that's already
mounted there, _not_ the entry from /etc/fstab (this is an enhancement
designed to make life easier when /etc/fstab is not quite right, eg.
when the kernel has had to guess about the root filesystem, or when
it's been moved maually).
--
\\ Give a man a fish, and you feed him for a day. \\ Mike Smith
\\ Tell him he should learn how to fish himself, \\ [EMAIL PROTECTED]
\\ and he'll hate you for a lifetime. \\ [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
