On 08/08/2014 02:55 PM, Gordan Bobic wrote:
On 08/08/2014 04:44 PM, Robert Moskowitz wrote:
So I am looking at the fstabs for f19 and in particular f19 has its boot
in a separate (uboot) partition:
# more /etc/fstab
UUID=33de6a91-2289-4ec7-9703-2b03a9d51725 / ext4 defaults,noatime 0 0
UUID=2cb94397-dc57-4276-bd81-0f30170f8cc1 /boot ext3
defaults,noatime 0 0
UUID=762e6e34-142b-49fe-9e8b-fb8a8a8cddab swap swap defaults,noatime
0 0
devpts /dev/pts devpts gid=5,mode=620 0 0
tmpfs /dev/shm tmpfs defaults 0 0
proc /proc proc defaults 0 0
sysfs /sys sysfs defaults 0 0
Where as the Redsleeve does not:
# more /run/media/rgm/rootfs/etc/fstab
/dev/mmcblk1p3 / ext4 defaults,noatime 1 1
devpts /dev/pts devpts gid=5,mode=620 0 0
tmpfs /dev/shm tmpfs defaults 0 0
proc /proc proc defaults 0 0
sysfs /sys sysfs defaults 0 0
#tmpfs /tmp tmpfs defaults 0 0
#tmpfs /var/tmp tmpfs defaults 0 0
#tmpfs /var/cache/yum tmpfs defaults 0 0
#tmpfs /var/lib/yum tmpfs defaults 0 0
=================================================
It does not look like there is any content in the uboot partition that
is needed after boot, so do I not mount it at all?
The common practice is to mount it. In reality, you only need it
mounted if you intend to update the kernel at some point.
Of course I have to figure out the right UUIDs for swap and rootfs to
get them to mount properly.
Or can I 'just use' /dev/mmcblk1p2 and /dev/mmcblk1p3?
You can use the /dev/ device nodes or UUIDs. As long as you make sure
you are using the correct ones.
The boot did not like using /dev/, I changed to UUIDs and it worked.
Grumble.
You can always mkswap the swap partition again, that will report the
uuid, which you can then put into your fstab. For formatted ext* file
systems you can get the uuid from dumpe2fs, e.g.
dumpe2fs /path/to/device/node | grep UUID
I found them with:
blkid /dev/sdb*
_______________________________________________
users mailing list
[email protected]
http://lists.redsleeve.org/mailman/listinfo/users
