Re: [lfs-dev] LFS Live-CD Project

"Rahul Chandra" ([email protected] via blfs-dev Mailing List) <[email protected]>
Newsgroups gmane.linux.lfs.beyond.devel,gmane.linux.lfs.devel
Message-ID <[email protected]>
On 2024-12-07 03:16, Thomas Trepl wrote:
> Am Donnerstag, dem 21.11.2024 um 08:00 -0500 schrieb Rahul Chandra:
>> I think I brought this up last year, but with the recent surge in LFS
>> users and the slew of 'editor' projects, I wanted to gauge interest
>> for this project again.
>> 
>> As far as I can remember, the discussion last time around was that we
>> would have a book that can follow LFS but be done before BLFS that
>> shows how to build a live-iso.  It would contain 2 packages
>> (squashfs-tools and mtools) and require a couple packages from BLFS
>> (mainly libisofs and the initrd). With this I also want to improve the
>> current initrd implementation in BLFS (AFAIK no editor besides me uses
>> one)
>> 
>> If people are interested I'll start on this sometime this week and
>> hopefully finish up in a few weeks. I already made some progress here:
>> https://github.com/rahulc07/lfs-live-iso.  Let me know what you think.
>> 
> Thats pretty cool - i'll immediatly have a look to your repo.
> 
> On my wishlist there are only a few points written:
> I'd like so have (of course offering help to) get a cook-book on how to
> build a CD which 
> * is usable on BIOS as well on EFI
Done
> * finds itself to boot from
Done (nearly, doesn't support lookback support so you can't boot it from 
an already partitioned disk)
> * is only setup with tools we have in {,B}LFS
Nearly done, we could add mtools and squashfs-tools to BLFS or we can 
keep them in the same place as the rest of the LiveCD
> 
> I'd be very much interested in helping to get a "how-to-build-a-lfs-cd"
> written.


-- 
Rahul

-- 
http://lists.linuxfromscratch.org/sympa/info/blfs-dev
Unsubscribe: See the above information page
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.