SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Would it be possible to mount {/dev, /dev/pts, /dev/input} with "atime" rather than "relatime"? These are ram-based filesystems, so there should not be a performance penalty, but this would allow a super easy way of detecting whether a computer is in use interactively.
I need edit fstab , when plug or unplug some devices sdX changing positions, only i fix, rebuilding kernel , and change yes to module under BLK_DEV_FD option.
setup in the -current installer should be modified to use UUID instead of devices names in /etc/fstab, as done in Slint and most other Linux distributions. No need to change the kernel configuration (even if doing that doesn't hurt).
Last edited by Didier Spaier; 03-30-2020 at 04:27 AM.
It's a bad idea, because UUID's change more frequently than sdX numbers.
If you have two removable devices, their sdX name will change every time you plug them in a different order. The UUID (aka file system UUID) will change every time you create a new file system in the partition. How frequently do you issue a command like "mkfs.<fileystem type> /dev/<name>"?
You can also name the partition by its own UUID (PARTUUID) regardless of the file system. This will change if you delete then recreate the partition, or resize it. FWIW, I attach the default /etc/default/grub currently shipped in Slint (for grub-2.04+git365e0cc3e7_20201227), renamed grub.txt
Last edited by Didier Spaier; 03-30-2020 at 05:33 AM.
Reason: Paragraph added.
I change my HDD less often than I change partitions.
For removable usb sticks what you're saying is correct, but I don't think that removable drives is the main point of an installer.
Or rather I (personally) would be more likely to rsync an installed Slackware root onto a usb partition and edit the fstab file rather than install directly onto a usb stick.
setup in the -current installer should be modified to use UUID instead of devices names in /etc/fstab, as done in Slint and most other Linux distributions. No need to change the kernel configuration (even if doing that doesn't hurt).
Personally, I prefer to use labels, where possible. At least you can make them meaningful. I hate seeing a fstab full of meaningless UUIDS
Also, I wouldn't want to see lvm style /dev/vgname/lvname entries being replaced by UUIDS as the lvm names are both location independent and convey meaning (that is, as long as you're not daft enough to call them something like vg01/lv01 ^waves to Redhat*)
Personally, I prefer to use labels, where possible.
And you can create them again after a partition resize or stick replacement.
I always use labels too, except for the root partition as I don't use a initrd and the kernel itself doesn't support labels. But apart from that
Code:
LABEL=Backup /mnt/Backup auto noauto,users 0 0
LABEL=Gutenberg /mnt/Gutenberg auto noauto,users 0 0
LABEL=Lexar_64G /mnt/Lexar auto noauto,users 0 0
LABEL=MuziekArchief /mnt/Archief auto noauto,users 0 0
LABEL=MyBook_WD1T /mnt/MyBook auto noauto,users 0 0
LABEL=SanDisk_32G /mnt/SanDisk auto noauto,users 0 0
LABEL=Toshiba_2T /mnt/Toshiba auto noauto,users 0 0
LABEL=Videos_WD1.5T /mnt/Videos auto noauto,users 0 0
LABEL=DaneElec_2G /mnt/DaneElec vfat noauto,users,fmask=0133 0 0
LABEL=EnVivo_MP3 /mnt/EnVivo vfat noauto,users,fmask=0133 0 0
LABEL=KINGSTON_4G /mnt/Kingston vfat noauto,users,fmask=0133 0 0
UUID=F009-64A5 /mnt/Lumix vfat noauto,users,ro,fmask=0333 0 0
LABEL=TimeMachine /mnt/TimeMachine ntfs-3g noauto,fmask=0133 0 0
(the first group is everything with a Linux type fs, the 2nd sticks, my Lumix camera which I cannot label, etc).
PS: The SanDisk and Lexar entries are for USB sticks too, but they have been REformatted with a Linux fs, so can be mounted with a file type of 'auto'. Most of the other entries are only mounted when needed and are often OFFline.
Last edited by ehartman; 03-30-2020 at 10:34 AM.
Reason: Addition about Linux formatted USB sticks
How frequently do you issue a command like "mkfs.<fileystem type> /dev/<name>"?
Quite often - for backup, restore and/or check and defrag.
Quote:
This [partuuid] will change if you delete then recreate the partition, or resize it.
Less often. An other issue would be when exchanging my on- and off-site backup disks.
Actually the external [usb] disks that are / may be connected at boot time cause problems. Afterwards the sequence in which the other external devices are connected can easily be managed.
I personally use udev rules to create aliases:
Code:
# 73-burdi01.rules : Additional udev rules
# ========================================
# (c) DLCB 3/1-2020
# External USB disk is sometimes /dev/sdb, sometimes /dev/sdf or whatever
KERNEL=="sd*", SUBSYSTEMS=="scsi", ATTRS{vendor}=="WD", ATTRS{model}=="Elements 25A3", SYMLINK+="sdxb%n"
KERNEL=="sd*", SUBSYSTEMS=="scsi", ATTRS{vendor}=="TOSHIBA", ATTRS{model}=="External USB 3.0", SYMLINK+="sdxd%n"
The sdxb* disk (/I) is my external backup disk.
Note that the aliases can also be used to easily apply mount options - as is done for the sdxd* (/J) disk.
The sdh* entries allow my sundry usb disks/sticks to be mounted afterwards. Mounting an additional stick will result in /dev/sdi*.
The /dummy entries stop my Xubuntu system automounting them.
Quite often - for backup, restore and/or check and defrag.
This is likely the minority of people using computers. I rarely format my disks and I don't personally know anyone who formats theirs on a regular basis.
Quote:
Originally Posted by burdi01
I personally use udev rules to create aliases:
Code:
# 73-burdi01.rules : Additional udev rules
# ========================================
# (c) DLCB 3/1-2020
# External USB disk is sometimes /dev/sdb, sometimes /dev/sdf or whatever
KERNEL=="sd*", SUBSYSTEMS=="scsi", ATTRS{vendor}=="WD", ATTRS{model}=="Elements 25A3", SYMLINK+="sdxb%n"
KERNEL=="sd*", SUBSYSTEMS=="scsi", ATTRS{vendor}=="TOSHIBA", ATTRS{model}=="External USB 3.0", SYMLINK+="sdxd%n"
I like this idea! But it doesn't seem like it'd work in my case as I have 2 devices that have the same model name in udevadm. Plus it seems like a lot of work to get the info to build these udev rules every time I add a device to the system. UUIDs are simple and I only need to tweak them in the fstab (my root, home, and EFI partition are all on a single NVMe device, so unless I add a second one to the system, I won't need to worry about tweaking my initrd or elilo.conf to use UUIDs for the time being.
Hi again , for me , its not a big problem , i rebuild changing floppy device as modular in to HUGE kernel config.
Arround if people format or not .... every people when make new install format the partition ... if you installs on sdb , but when reboot , remove usb stick ...and sdb IS now sda , then boot fails ..cause sdb non exist without usb plugged ... its a very strange scenario , but i found some times , ever under ASROCK , motherboards , NEVER under netbook/notebook , only in to PC , with some asrock like extreme 4.
If changing the floppy device YES to MODULAR , is a problem for the installer , then no change , i can live with a some kernel rebuild.
Last edited by USUARIONUEVO; 03-30-2020 at 03:45 PM.
We have the full GNU developer suite, that is gcc, g++, gnat, gfortran, gdb, but not full Apple/LLVM development suite.
We have LLVM, lldb, clang, clang++, but not flang or f18 (for Fortran). This is a bit annoying if the users chooses to build most of the stuff with, clang, but ends up building BLAS/Atlas/OpenBLAS with gfortran.
Serious question... do we have compiler packages that are not being used anywhere in the system? If Pat isn't building anything using flang or f18, I'm not sure if he would include it (but I don't know development that well, and it could very well be that he's already including development software that isn't being used in building Slackware).
But if he does package development software that isn't being used, how likely are people to use flang and f18? There doesn't even seem to be SlackBuilds for them on SBo, so it seems like it might be something that is rarely used and may not have a place to be included with Slackware itself and is to be better maintained on SBo.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
