Siduction Forum
Siduction Forum => Siduction News => Topic started by: devil on 2014/11/02, 21:36:17
-
Wir hatten heute ein Core Meeting: http://bugs.siduction.org/projects/siduction/wiki/2014-11_01_Core_Meeting (http://bugs.siduction.org/projects/siduction/wiki/2014-11_01_Core_Meeting)
-
Thanks for posting this.
FWIW, I like the idea of the installer only offering to mount / and /home partitions. Users who don't know how to customize /etc/fstab to mount their additional selected partitions, or can't find instructions with a google search, really have no business trying to use siduction. Not being a snob --- but they need to learn more linux system administration before they strap on sid.
-
Not being a snob --- but they need to learn more linux system administration before they strap on sid.
A snob and prettier than me :o and more hair >:(
:)
I wasn't sure at first which way would be better, with more time to think about it, I agree with mounting / and /home partitions.
I prefer the cli installer myself, but, I was thinking of newer users, but I think KISS is needed here.
-
Nice to have a ETA now for a new release.
I also prefer to mount / and /home only, by default, at least since we have systemd at work and its strange behaviour when not finding an uuid anymore even if its not the one of / or /home...
greets ayla
-
Little clarification:
one can create several mounts with the installer, not only / and /home - this was possible before. The only thing is to make the installer more streamlined and easier to use.
-
What really would add value to the fstab is to create mountpoints on basis of the labels ***if*** a lable is defined.
The whole ugliness and in part uselessness of the fstab or at least big part of it comes from those uninformative mountpoints in media like "disk1part1, disk1part2...." which doesn't give a clue what's the content of say disk2part3.
At sidux time Kelmo did make half a step in the right direction (guess who suggested it). Each entry in fstab had a comment line above stating the label of the partition below. This gave some orientation, but "solved" the problem only half way.
A really helpfull solution would be to have a means which walks through the partitons, looks for a label and if available creates the respective mount point (and I am convinced that's what user gave up to look for because all attempts to solve this mess tanked). I think we can assume that an user selected a reasonable lable. And having this feature would encourage people even more to actually lable their partitions.
I am not saying "we must have this". I'm saying if somehow possible this feature would *add value* to fstab for users (who otherwise need to do this work manually).
-
Many systems here for testing on different partitions, fstab is different in kde compared to cinnamon, e17, gnome, and I just had to install windows 7 as a request from one of my grandchildren :(
fstab on my production box (kde)
# /etc/fstab: static file system information.
#
# <file system> <mount point> <type> <options> <dump> <pass>
#Entry for /dev/sda3 :
UUID=d214e821-0d19-45be-8770-dfdba028ba1f / ext4 defaults,relatime,errors=remount-ro 0 1
#Entry for /dev/sda2 :
UUID=4182AD3F3349D507 /media/sda2 ntfs-3g defaults,locale=en_US.utf8 0 0
#Entry for /dev/sda5 :
UUID=1495E70670ADDCA3 /media/sda5 ntfs-3g defaults,locale=en_US.utf8 0 0
#Entry for /dev/sdb1
UUID=192108a8-601e-4868-882d-97ad3042b5ee /media/sdb1 ext4 auto,users,rw,exec,relatime 0 0
#Entry for /dev/sdc1
UUID=0236d812-1bda-4b81-846a-19dff5d663b0 /media/sdc1 ext4 auto,users,rw,exec,relatime 0 0
#Entry for /dev/sda1 :
UUID=258e380d-f937-4179-89fa-ecd87628c789 none swap sw 0 0
#Entry for /dev/sda6
UUID=b4885921-86d7-4f8e-ae2c-d15bd2db48fe /media/sda6 ext4 auto,users,rw,exec,relatime 0 0
#Entry for /dev/sda7
UUID=0f242206-e2dc-4993-8c8e-f4e9cc3bef68 /media/sda7 ext4 auto,users,rw,exec,relatime 0 0
#Entry for /dev/sda8
UUID=804466e8-5bcc-47ff-82e7-9e042a4a4050 /media/sda8 ext4 auto,users,rw,exec,relatime 0 0
#Entry for /dev/sda9
UUID=155ea5b4-1744-4936-ab31-5c043c1a314f /media/sda9 ext4 auto,users,rw,exec,relatime 0 0
#Entry for /dev/sda10
UUID=0da9b51a-dcf1-4c69-b4ed-622d00cc4560 /media/sda10 ext4 auto,users,rw,exec,relatime 0 0
This is fstab from cinnamon, e17, gnome (basically all 3 are the same, just different / partition)
UUID=258e380d-f937-4179-89fa-ecd87628c789 none swap sw 0 0
UUID=0da9b51a-dcf1-4c69-b4ed-622d00cc4560 /disks/disk1part10 ext4 auto,users,rw,exec,relatime 0 0
UUID=4182AD3F3349D507 /disks/disk1part2 ntfs auto,users,ro,dmask=0022,fmask=0133,nls=utf8 0 0
UUID=d214e821-0d19-45be-8770-dfdba028ba1f /disks/disk1part3 ext4 auto,users,rw,exec,relatime 0 0
UUID=1495E70670ADDCA3 /disks/disk1part5 ntfs auto,users,ro,dmask=0022,fmask=0133,nls=utf8 0 0
UUID=b4885921-86d7-4f8e-ae2c-d15bd2db48fe /disks/disk1part6 ext4 auto,users,rw,exec,relatime 0 0
UUID=0f242206-e2dc-4993-8c8e-f4e9cc3bef68 /disks/disk1part7 ext4 auto,users,rw,exec,relatime 0 0
UUID=804466e8-5bcc-47ff-82e7-9e042a4a4050 / ext4 defaults,relatime,errors=remount-ro 0 1
UUID=155ea5b4-1744-4936-ab31-5c043c1a314f /disks/disk1part9 ext4 auto,users,rw,exec,relatime 0 0
UUID=192108a8-601e-4868-882d-97ad3042b5ee /disks/disk2part1 ext4 auto,users,rw,exec,relatime 0 0
UUID=0236d812-1bda-4b81-846a-19dff5d663b0 /disks/disk3part1 ext4 auto,users,rw,exec,relatime 0 0
3 of the systems use diskxpartx while one uses sxx, weird, I know what is what but others might not.
-
A really helpfull solution would be to have a means which walks through the partitons, looks for a label and if available creates the respective mount point ...
One could argue we already have this -- the OS does provide a unique identification (i.e. label) for each partition on the computer.
root@imerabox:/# blkid -c /dev/null -o list
device fs_type label mount point UUID
----------------------------------------------------------------------------------------------
/dev/sdb1 ext4 revodata /mnt/REVODATA ec21f5b3-7fd4-4f4b-af8d-cf787b147ae8
/dev/sdc1 ext2 /boot 5b98d884-97ae-45ae-b44d-a9bc998e67cb
/dev/sdc2 swap <swap> 3a63113d-ae25-4a4c-a083-9e6172492a19
/dev/sdc3 ext4 /mnt/HITACHI e8de505f-5d7e-4183-a9a2-042efafa50f1
/dev/sda1 ext4 / bea3a748-3411-4024-acd0-39f3882ddaf9
/dev/sda2 ext4 SDA2 /mnt/SDA2 8cfe2acc-7572-4b45-b25f-ed021bb1d78b
/dev/sde btrfs (in use) 2bbc4079-e05d-43a3-865b-5b3d3f4af0f5
/dev/sdd btrfs (in use) 2bbc4079-e05d-43a3-865b-5b3d3f4af0f5
But the nearly infinite number of possibilities, and the likelihood of hitting bugs of one kind or another, makes me think piper and his pretty hair are correct -- KISS is the way to avoid such problems. I really don't expect an installer to find my 2-drive BTRFS filesystem and understand how to make the mount line correctly -- it will never know whether or not I want compression, and which algorithm I prefer.
-
...
One could argue we already have this -- the OS does provide a unique identification
which you daily try eagerly but unsuccessfully to learn by heard to be able to mount -u ????????-????-????-????-???????????? them manually in case you need to.
Yeah, KISS, and the remainder is for nerds.