Article 5RY4D FSTAB file keeps getting changed

FSTAB file keeps getting changed

by
jr_bob_dobbs
from LinuxQuestions.org on (#5RY4D)
I discovered an unexpected thing in Bedrock and was wondering if anyone could clue me in.

Here is the /etc/fstab as it is in my bedrock OS:
Code:# /etc/fstab for bedrocked Void on vindi
#device point fs options dmp order
/dev/azura/vindi / ext4 defaults,noatime 1 0
tmpfs /tmp tmpfs size=4G,nodev,nosuid 0 0
tmpfs /dev/shm tmpfs nosuid,nodev,noexec 0 0
devpts /dev/pts devpts gid=5,mode=620 0 0
proc /proc proc defaults 0 0
/dev/azura/swappy none swap sw 0 0

/dev/azura/homie /other_home ext4 defaults,noatime 1 0
/dev/azura/sloppy /hsc ext4 defaults,noatime 1 0
/dev/azura/dawn /dawn_slash ext4 ro,defaults,noatime 1 0
/dev/azura/dusk /dusk_slash ext4 ro,defaults,noatime 1 0
/dev/azura/moon /fallback_slash ext4 ro,defaults,noatime 1 0

/dev/sr0 /mnt/cdrom0 auto noauto,user,ro 0 0
/dev/sr1 /mnt/cdrom1 auto noauto,user,ro 0 0
# actual end of this fileCompare this against the fstab in another OS on the same computer:
Code:# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
# breaks initrd: /dev/azura/dawn / ext4 noatime 1 1
/dev/mapper/azura-dawn / ext4 noatime 1 1
/dev/azura/swappy none swap sw 0 0

#/dev/fd0 /mnt/floppy auto noauto,owner 0 0
/dev/fd0 /mnt/floppy auto noauto,owner 0 0
devpts /dev/pts devpts gid=5,mode=620 0 0
proc /proc proc defaults 0 0
tmpfs /dev/shm tmpfs nosuid,nodev,noexec 0 0
tmpfs /tmp tmpfs size=4G,nodev,nosuid 0 0

/dev/sr0 /mnt/cdrom0 auto noauto,user,ro 0 0
/dev/sr1 /mnt/cdrom1 auto noauto,user,ro 0 0
/dev/sr2 /mnt/cdrom2 auto noauto,user,ro 0 0
/dev/sr3 /mnt/cdrom3 auto noauto,user,ro 0 0

/dev/azura/moon /fallback_slash ext4 defaults,ro 1 5
/dev/sda2 /fallback_boot ext2 defaults,ro 1 6
/dev/azura/dusk /dusk_slash ext4 defaults,ro,noatime 1 3
/dev/azura/homie /home ext4 defaults,noatime 1 2
/dev/azura/sloppy /hsc ext4 defaults,noatime 1 4
/dev/azura/vindi /vindi_slash ext4 defaults,noatime 1 7
/dev/sda1 /toy_os auto defaults,ro,noatime 1 5

# usb sticks, so that user can mount & unmount them...
/dev/sdb1 /mnt/sdb1 auto noauto,user 0 0
/dev/sdb5 /mnt/sdb5 auto noauto,user 0 0
/dev/sdc1 /mnt/sdc1 auto noauto,user 0 0

# actual end of this fileTwo point of interest. One: note how, aside from longer device names, I try to keep everything in clearly visible columns. Two: drives set to be checked at boot time by dump column being set to 1 and then the last ("pass") column set with numbers specifying the order of disk checking.

When I edit the bedrock fstab and then reboot, the spacing is reduced to single spaces, dump values are set to zero and pass set to 0 as well.

This seems to only happen on partitions that are mounted at boot time. Note the "noauto" mount point lines are not changed. Also, commented lines are left alone.

I've tried editing the /etc/hosts file to change things back but the edits get reverted on reboot.

I couldn't find any mention of this on the (bedrock) web site and I was wondering if someone could clue me in? Thank you.latest?d=yIl2AUoC8zA latest?i=xAkJ88RB9wM:5holwpaaCRo:F7zBnMy latest?i=xAkJ88RB9wM:5holwpaaCRo:V_sGLiP latest?d=qj6IDK7rITs latest?i=xAkJ88RB9wM:5holwpaaCRo:gIN9vFw
External Content
Source RSS or Atom Feed
Feed Location https://feeds.feedburner.com/linuxquestions/latest
Feed Title LinuxQuestions.org
Feed Link https://www.linuxquestions.org/questions/
Reply 0 comments