feisty upgrade fstab

[kramerjm-Re5JQEeQqe8AvxtiuMwx3w at public.gmane.org (James Kramer)]

>
> In my case what is returned from vol_id doesn't match fstab, so that
> seems to be a good explanation. I'd recommend playing around with the
> mount command using the UUID identifier and see what it reports.
>
> A possibly related issue is that when Feisty switched to udev, there
> were race conditions in the start up scripts, which triggered a variety
> of problems, such as mdadm managed RAID arrays not getting fully
> assembled after a reboot (I mentioned that on this list a month or so
> ago). Maybe a scan for file systems based on UUID fails because the
> devices aren't ready yet, but when the mount is actually performed they are.
>
>   -Tom
>
This sounds like the issue.  When I boot the computer is is hanging
somewhere but I haven't had the time to check it out.  I will look
into it further in the future.  At least I will learn the new file
system in the  process.
jay
> Tom Metro
> Venture Logic, Newton, MA, USA
> "Enterprise solutions through open source."
> Professional Profile: http://tmetro.venturelogic.com/
>
> --
> This message has been scanned for viruses and
> dangerous content by MailScanner, and is
> believed to be clean.
>
> _______________________________________________
> Discuss mailing list
> Discuss-mNDKBlG2WHs at public.gmane.org
> http://lists.blu.org/mailman/listinfo/discuss
>

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.