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.
I for one, I will not touch this filesystem even it comes with human-level Artificial Intelligence, after learning about the particular way of Hans Reiser understanding of the sense of word "divorce".
Of course, whenever possible. But I am considering uses cases where using elilo or lilo are not an option. Not all users want to have only Slackware and|or another Linux on their computer.
but by making it part of basic Slackware you're forcing a lot of complexity on users that don't need it.
Users who need that complexity are usually quite capable of adding it themselves.
AS far as boot logic I have an extremely complex system which can be served easily by lilo/elilo, multiple boot devices using multiple OS's. AS for as my use elilo will boot just about anything
thanks
john
but by making it part of basic Slackware you're forcing a lot of complexity on users that don't need it.
I disagree:
This can be made optional as stated in another post.
The script grubconfig (the attached current version in Slint will be enhanced) makes easy to install GRUB. Certainly easier than running liloconfig in Expert mode: the boot loader will be installed in an ESP if available, there is no need to add stanzas for other systems.
Even manually installing GRUB in most cases just needs two commands:
I still think it should be asking for permission to overwrite files, because responsibility etc.
You go ahead and do that when deploying on machine you are responsible for, I would not give permission to do that on one of mine.
So thanks, but no thanks.
Additionally, I doubt there will be a green light for this script in its current form.
Because it would open up a way for a whole lot of other packages to follow suit, and decide not to provide a config.new "for the admin to consider"
Basically, if this slides, it would mean any package can just overwrite whatever configuration file without explicit permission, which is a security nightmare.
I would like to add that since 2012, the owners of everything Hans Reiser had as properties (excluding a small Honda and $200 cash), an amount of $60,000,000 is of Rory and Niorline Reiser, his kids, by Court decision and as damages for losing their mother.
The kids now lives in Russia, with the maternal grandparents, and Russia is (in)famous for the prejudice against women killers, starting from government and justice and ending with the organized crime.
If ever Hans Reiser will dare to step in Russia, he risks another sentence, this time for life, for killing a Russian citizen.
Meanwhile he's enjoying his 15 years sentence in USA, and there are information that the other inmates got the habit to gang beat him 'til hospitalization. Periodically.
I will end asking everyone to read Reiser4 as "Fourth Filesystem of Rory and Niorline Reiser", let's forget about that guy and to note that today the kids usually earn from DARPA prizes. I think that says everything about the Reiser4 quality.
Last edited by ZhaoLin1457; 04-12-2018 at 02:25 PM.
The argument about Reiser4 is a moot point. Unless I missed the memo, Slackware by default does not support Reiser4, much less does any modern distribution, due to ethics and politics surrounding Hans Reiser.
Actually, Slackware does not support reiser4 because the upstream kernel does not support reiser4, and any notion that we would patch the kernel to add it is a non-starter.
I would like to add that since 2012, the owners of everything Hans Reiser had as properties
The kids now lives in Russia, with the maternal grandparents, and Russia is (in)famous for the prejudice against women killers, starting from government and justice and ending with the organized crime.
If ever Hans Reiser will dare to step in Russia, he risks another sentence, this time for life, for killing a Russian citizen.
Actually, Slackware does not support reiser4 because the upstream kernel does not support reiser4, and any notion that we would patch the kernel to add it is a non-starter.
Thanks for the clarification, Pat.
If Reiser4 will be included in linux-mainline, you will make it FS by default, as in its time, it was with reiserfs?
I would prefer Grub over lilo because :
- Grub lets you use zfs as a root / boot filesystem
- Lilo crashes when you run it with more then 16 disks connected.
I need to physically disconnect drives from my NAS servers in order to run lilo after a kernel update. This annoys me quite a bit.
In an EFI enabled VirtualBox VM I installed DragonFlyBSD-5.2.0 in /dev/sdb then Slint64-14.2.1.1 on /dev/sda, from which I ran grubconfig.
DragonFly installed a PE32+ image /EFI/BOOT/BOOTX64.EFI in an ESP it made in /dev/sdb1.
At first I didn't get a boot entry for it (wondering why os-prober didn't find BOOTX64.EFI in /dev/sdb2, although in other tests it could find a similar image in /dev/sda1 for elilo), but anyway I was able to include a custom boot entry for it in /etc/grub.d/40_custom, that allows to start DragonFlyBSD.
So I assume that grub is able to start any properly chain loaded EFI application.
As an aside, this is something you can't do with elilo, as it is unable to chain load anything outside the ESP where it is installed. I don't say that to despise elilo that I use to boot the Slint installer in EFI mode, it just doesn't have the needed features for this use case (nor the many file system drivers that GRUB ships).
Incidentally, I also installed TrueOS, which amazingly installs rEFInd as boot manager.
I will also try a dual boot with FreeBSD.
Last edited by Didier Spaier; 04-13-2018 at 11:13 AM.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.