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.
So in a VM of course, I decided to do a dry-run of f2fs (--Current of course) - given that I am using a SSD(SATA , not NVME though) , I set all the partitions as f2fs.
Code:
/boot ~ 300MM
/ ~ 63GB
/home ~ 153GB
swap ~ 32GB
When getting to the point of installing LILO is where I run into trouble, I select where Linux is installed and then LILO freaks out..
I know perhaps a while back a similar thread might have been created, but I don't recall nor what the work-around solution is.
Is this a limitation with lilo or f2fs , or both as they just seem to not play nice with each other? What is the suggestion on getting this to work as I would love to have my SSD just run f2fs partitions (with a swap of course).
So in a VM of course, I decided to do a dry-run of f2fs (--Current of course) - given that I am using a SSD(SATA , not NVME though) , I set all the partitions as f2fs.
Code:
/boot ~ 300MM
/ ~ 63GB
/home ~ 153GB
swap ~ 32GB
When getting to the point of installing LILO is where I run into trouble, I select where Linux is installed and then LILO freaks out..
I know perhaps a while back a similar thread might have been created, but I don't recall nor what the work-around solution is.
Is this a limitation with lilo or f2fs , or both as they just seem to not play nice with each other? What is the suggestion on getting this to work as I would love to have my SSD just run f2fs partitions (with a swap of course).
IF you use F2FS as root filesystem, you should use a separate boot partition, formatted with a filesystem supported by LILO, i.e. EXT4FS.
LILO cannot work with (and have no support for) this F2FS, because on F2FS filesystem is no guarantee that a file will remain in a "fixed" position on disk.
Last edited by LuckyCyborg; 11-05-2021 at 12:55 PM.
IF you use F2FS as root filesystem, you should use a separate boot partition, formatted with a filesystem supported by LILO, i.e. EXT4FS.
LILO cannot work with (and have no support for) this F2FS, because on F2FS filesystem is no guarantee that a file will remain in a "fixed" position on disk.
Yep, that did it. I think perhaps the installer should be amended and included F2FS , as requiring a non F2FS partition - just like how the installer always warns you that you cannot install lilo on an XFS superblock - or maybe just before Slackware 15.0 come out - just something in the documentation to give idiots like me a heads up
-edit
Basically - WARNING: If you use XFS or F2FS , make sure you have a separate /boot partition that is any other FS except for XFS or F2FS (I assume BTRFS might work too?)... Still - even though this is now solved, I wonder how GRUB would handle this - I bet GRUB just doesn't care - but I haven't worked with GRUB to know.
Yep, that did it. I think perhaps the installer should be amended and included F2FS , as requiring a non F2FS partition - just like how the installer always warns you that you cannot install lilo on an XFS superblock - or maybe just efore Slackware 15.0 come out - just something in the documentation to give idiots like me a heads up
-edit
Basically - WARNING: If you use XFS or F2FS , make sure you have a separate /boot partition that is any other FS except for XFS or F2FS (I assume BTRFS might work too?)... Still - even though this is now solved, I wonder how GRUB would handle this - I bet GRUB just doesn't care - but I haven't worked with GRUB to know.
The GRUB's second stage literally reads the filesystem(s) to find the files - compared with LILO which uses absolute positions on sectors.
Last edited by LuckyCyborg; 11-05-2021 at 01:14 PM.
The GRUB's second stage literally reads the filesystem(s) to find the files - compared with LILO which uses absolute positions on sectors.
Sounds like another case for GRUB then, would be nice if the installer added that option - I have tried to install grub (in a VM of course) but given that I screwed up somewhere, after rebooting it dumped me in a GRUB console - so yea I screwed the pooch on that one, but I will revisit GRUB at another time.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.