<div dir="ltr"><div>you may also want to inspect the bios to see which drive it wants to boot from. also didn't say whether you're using uefi or not.</div><div><br></div><div>Does it boot? Try and see.</div><div><br></div><div>Yes Rick is correct, use a UUID.<br></div><div><br></div><div>-C<br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, Mar 5, 2019 at 9:46 PM Stephen Potter <<a href="mailto:spp@unixsa.net">spp@unixsa.net</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><br>
On 3/5/2019 2:36 PM, Stephen P. Molnar wrote:<br>
> 1. Will the boot proceed to completion?<br>
> 2. Will users have read/write permission?<br>
<br>
Presuming your bootblock is installed properly on /dev/sda and your <br>
kernel is properly in /boot on /dev/sda1, your boot should work. Of <br>
course, this is all dependent on your other services and such being <br>
properly setup and there not being corruption on /dev/sda1 that requires <br>
an fsck.<br>
<br>
fstab has nothing to do with user level permissions. I assume you mean <br>
read/write permission to /hdb1 and /hdc1. It will depend on how you <br>
created the mount points as well as the filesystems on /dev/sdb1 and <br>
/dev/sdc1.<br>
<br>
-spp<br>
<br>
_______________________________________________<br>
colug-432 mailing list<br>
<a href="mailto:colug-432@colug.net" target="_blank">colug-432@colug.net</a><br>
<a href="http://lists.colug.net/mailman/listinfo/colug-432" rel="noreferrer" target="_blank">http://lists.colug.net/mailman/listinfo/colug-432</a><br>
</blockquote></div>