Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#31438 - [arch-install-scripts] Separate genfstab from AIS and make it a separate [core] package

Attached to Project: Arch Linux
Opened by Andrew (DSpider) - Thursday, 06 September 2012, 11:39 GMT
Last edited by Dave Reisner (falconindy) - Thursday, 06 September 2012, 13:20 GMT
Task Type Feature Request
Category Packages: Core
Status Closed
Assigned To Dave Reisner (falconindy)
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

I have tried my best to describe it here: https://bbs.archlinux.org/viewtopic.php?id=147829

Having them both into a single "Install the base system and chroot into it" section would be easier to follow:

# pacstrap /mnt base base-devel
# arch-chroot /mnt

Done.

Then, if you would like to automatically generate an /etc/fstab file:

# pacman -S genfstab
# genfstab

Notice that this way, you don't really need to specify a root or a destination file (it's /etc/fstab, ffs). Easier to type too, than the ogreish "genfstab -p /mnt >> /mnt/etc/fstab". The user can choose to generate them by appending "-L" or "-U" flags (by label or by UUID).


PS: This way the script could also be called "fstab-gen", to match the "locale-gen" command. It would be easier to remember and give the install process some congruency.
This task depends upon

Closed by  Dave Reisner (falconindy)
Thursday, 06 September 2012, 13:20 GMT
Reason for closing:  Won't implement
Additional comments about closing:  Too many drawbacks to suggested approach.
Comment by Dave Reisner (falconindy) - Thursday, 06 September 2012, 13:20 GMT
So you want genfstab not only in [core], but in the base group. This will not happen. The installation process should not be about golfing it into as few keystrokes as possible.

> Notice that this way, you don't really need to specify a root or a destination file (it's /etc/fstab, ffs)
A laughable exclamation. You have 3 options:

1) blindly overwrite /etc/fstab. This leads to bug reports when some user foolishly runs it without arguments, sees zero feedback, and then has trouble booting.
2) append to /etc/fstab. This only conditionally makes sense based on the current contents of fstab.
3) write to stdout. Hey, this might seem sane. This acts as a _dry_ _run_ before you clobber, or append (ooooh, now its your choice!!!) to /etc/fstab.

No, this isn't about "its /etc/fstab, ffs", it's about building a set of flexible tools which might have a place outside the installation environment on the liveCD.

Loading...