Hello,
don`t know if someone is interested, so i keep this short:
I`ve finished a livecd using fedora core 3 with kde and gnome for the desktops, firefox/thunderbird, openoffice and other applications. Login manager is gdm, default desktop kde, gnome can also be selected.
Auto save/restore of user sessions from usb storage (sda1) in kde - need some help to get that working in gnome.
Also included is the fedora core 3 network install kernel/initrd from boot.iso (unchanged).
Startuptime is ~1-3 Minutes on a 1,5 Ghz Amd/256Mb Ram with 52x ide cdrom drive.
Screenshots: http://www.linux4all.de/livecd/basilisk/1.40/walkthrough/wsimages.htm
Readme/Requirements/Download http://www.linux4all.de/livecd/basilisk/1.40/index.htm
Best Regards, Dirk Westfal
Dirk Westfal wrote:
don`t know if someone is interested, so i keep this short:
I`ve finished a livecd using fedora core 3 with kde and gnome for the desktops, firefox/thunderbird, openoffice and other applications. Login manager is gdm, default desktop kde, gnome can also be selected.
I'm very interested in this. I wanted to make a fedora 2 live cd for a few months now. The problem is, there is no proper documentation and all the scripts for making live cd's are buggy or not working. How did you do it? Any good documentation?
I would appreciate some more info on this.
Thanks and keep up the good work!
Arangel
Arangel Angov wrote:
Dirk Westfal wrote:
don`t know if someone is interested, so i keep this short: I`ve finished a livecd using fedora core 3 with kde and gnome for the desktops, firefox/thunderbird, openoffice and other applications. Login manager is gdm, default desktop kde, gnome can also be selected.
I'm very interested in this. I wanted to make a fedora 2 live cd for a few months now. The problem is, there is no proper documentation and all the scripts for making live cd's are buggy or not working. How did you do it? Any good documentation?
I would appreciate some more info on this.
Thanks and keep up the good work!
Arangel
I know the feeling about poor documentation, I have been trying to figure out how to create a scaled down version of FC2 and now 3, all I want is the core Linux files, Xorg and KDE, and I would like to be able to use anaconda to install it. I have no idea where to start, and searching google resulted in me pulling out my hair, and breaking a few dozen pencils. anyone have any advice they would like to share :) please.
:)
BaVinic
I know the feeling about poor documentation, I have been trying to figure out how to create a scaled down version of FC2 and now 3, all I want is the core Linux files, Xorg and KDE, and I would like to be able to use anaconda to install it. I have no idea where to start, and searching google resulted in me pulling out my hair, and breaking a few dozen pencils. anyone have any advice they would like to share :) please.
Why not just use kickstart?
-sv
seth vidal wrote:
I know the feeling about poor documentation, I have been trying to figure out how to create a scaled down version of FC2 and now 3, all I want is the core Linux files, Xorg and KDE, and I would like to be able to use anaconda to install it. I have no idea where to start, and searching google resulted in me pulling out my hair, and breaking a few dozen pencils. anyone have any advice they would like to share :) please.
Why not just use kickstart?
-sv
Kickstart has a lot of nice features, but the idea here is to create an installable boot cd, that i can give to friends to install FC from 1 cd, not 4. but I will continue to read up on kickstart , thanks Seth.
On Monday 29 November 2004 19:31, Jim Martin wrote:
seth vidal wrote:
I know the feeling about poor documentation, I have been trying to figure out how to create a scaled down version of FC2 and now 3, all I want is the core Linux files, Xorg and KDE, and I would like to be able to use anaconda to install it. I have no idea where to start, and searching google resulted in me pulling out my hair, and breaking a few dozen pencils. anyone have any advice they would like to share :) please.
Why not just use kickstart?
-sv
Kickstart has a lot of nice features, but the idea here is to create an installable boot cd, that i can give to friends to install FC from 1 cd, not 4. but I will continue to read up on kickstart , thanks Seth.
I`ve played/still am playing with kickstart a lot.
In my expirience this approach works only with a 'heavely' adjusted and tested comps file - and if you make it use just one section that includes a list of rpms that is known&tested as 'working' (that`s what i normally do).
Even then one isn`t on the safe side since a single package dependency can easely lead into a full chain that needs to be resolved (+ more interdependecies) and suddenly you have an X server (and/or a lot of other stuff) where you never wanted one.
That problem does not exist in fedora alone - just some days before i`ve seen a suse server (a root server with only LAMP, pop/imap etc) with gnome-vfs, pango, image-magick etc. installed - just because some perl modules have it filed as requirement (*shudder*).
So you almost always end up in 'hand crafting' a reasonable small subset that you can use to start with - for every new release which is somewhat time expensive.
(BTW: thanks god for yum! :)
Best Regards, Dirk Westfal
On Monday 29 November 2004 18:49, Arangel Angov wrote:
Dirk Westfal wrote:
...
I'm very interested in this. I wanted to make a fedora 2 live cd for a few months now. The problem is, there is no proper documentation and all the scripts for making live cd's are buggy or not working. How did you do it? Any good documentation?
Well... 'good docu' for the livecd build-process ... that`s a very critical point yet :)
I`m trying to create a set of scripts to facilitate the process, but it`s still not very easy to get it right and 'end-user' doable.
It starts with package dependencies (it`s quite easy to end up with a 2,8 GB install) and ends with mostly small things (some software that needs write permission in /usr, missing symlinks, changes in system scripts etc.), that can easely prevent a livecd -system from working.
I`ve automated most of the stuff using a shellscript that guides throught the build-process in ~11 steps, and eleminated a lot of pitfalls by putting the livecd-specific adjustments into rpm packages (the 'livecd- rpms' - included in the 1.40 cd in /rpms folder).
All tools i use are currently included in a 'livecd-devel.tar.gz' in the barebone image - they are working - at least for me - but there are still a lot of loose ends, and it is not 'bullet-proof' enough to turn it loose as single package.
My current approach for end-users is to provide a 'basic' image (the 'barebone') as working example that includes just yum and a few other tools that can be 'remastered' into full working system or used as a 'base' for own systems. (document: http://www.linux4all.de/livecd/barebone/customization-1.1.htm )
I would appreciate some more info on this.
perhaps via PM ?
Thanks and keep up the good work!
Arangel
Thanks a lot!
Best Regards, Dirk Westfal
man, 29.11.2004 kl. 20.16 skrev Dirk Westfal:
On Monday 29 November 2004 18:49, Arangel Angov wrote:
Dirk Westfal wrote:
...
I'm very interested in this. I wanted to make a fedora 2 live cd for a few months now. The problem is, there is no proper documentation and all the scripts for making live cd's are buggy or not working. How did you do it? Any good documentation?
Well... 'good docu' for the livecd build-process ... that`s a very critical point yet :)
I`m trying to create a set of scripts to facilitate the process, but it`s still not very easy to get it right and 'end-user' doable.
It starts with package dependencies (it`s quite easy to end up with a 2,8 GB install) and ends with mostly small things (some software that needs write permission in /usr, missing symlinks, changes in system scripts etc.), that can easely prevent a livecd -system from working.
I`ve automated most of the stuff using a shellscript that guides throught the build-process in ~11 steps, and eleminated a lot of pitfalls by putting the livecd-specific adjustments into rpm packages (the 'livecd- rpms' - included in the 1.40 cd in /rpms folder).
All tools i use are currently included in a 'livecd-devel.tar.gz' in the barebone image - they are working - at least for me - but there are still a lot of loose ends, and it is not 'bullet-proof' enough to turn it loose as single package.
My current approach for end-users is to provide a 'basic' image (the 'barebone') as working example that includes just yum and a few other tools that can be 'remastered' into full working system or used as a 'base' for own systems. (document: http://www.linux4all.de/livecd/barebone/customization-1.1.htm )
Just wondering - all that with read-only root etc. - don't this project share a lot of common goals (or at least technical ways to get there) with the stateless project?
On Monday 29 November 2004 21:38, Kyrre Ness Sjobak wrote:
man, 29.11.2004 kl. 20.16 skrev Dirk Westfal:
Just wondering - all that with read-only root etc. - don't this project share a lot of common goals (or at least technical ways to get there) with the stateless project?
Right - and I`m monitoring this project constantly (and some things, problems and solutions look quite familiar :))
The stateless-linux project uses a somewhat other approach - and has a broader target eg. server/ (harddisk installed) client, snapshots/nfs, lot`s of file/file mounts etc, while i have a lot of cd/usb - specific things eg. one main tmpfs mount for the runtime-writable root and another for temporary files, special rpms, cache archives to speed up boot and else stuff.
For the future i hope to find a way for some things to be 'compatible' :)
Best Regards, Dirk Westfal
I'm very interested in this. I wanted to make a fedora 2 live cd for a few months now. The problem is, there is no proper documentation and all the scripts for making live cd's are buggy or not working. How did you do it? Any good documentation?
Well... 'good docu' for the livecd build-process ... that`s a very critical point yet :)
Right. Dirk's packages are pretty easy to use. I've used them for 4 or 5 months to create my own stripped down version of Fedora Core 3. I have some plans to integrate an earlier version of the scripts with the Rookery Build System so that you can go from srpm repository all the way to Live CD. I do it now regularly, but need to do some more testing before releasing.
If you are interested in showing your friends Fedora Core to convince them to try Linux without installing it, Dirk's system works well.
-Steve Grubb
__________________________________ Do you Yahoo!? Meet the all-new My Yahoo! - Try it today! http://my.yahoo.com
On Mon, 29 Nov 2004 15:12:23 -0800 (PST), Steve G linux_4ever@yahoo.com wrote:
I'm very interested in this. I wanted to make a fedora 2 live cd for a few months now. The problem is, there is no proper documentation and all the scripts for making live cd's are buggy or not working. How did you do it? Any good documentation?
Well... 'good docu' for the livecd build-process ... that`s a very critical point yet :)
Right. Dirk's packages are pretty easy to use. I've used them for 4 or 5 months to create my own stripped down version of Fedora Core 3. I have some plans to integrate an earlier version of the scripts with the Rookery Build System so that you can go from srpm repository all the way to Live CD. I do it now regularly, but need to do some more testing before releasing.
How goes Rookery these days? I remember you generating a lot of patches at times to get Fedora to a certain stage.. did you get X going?
How goes Rookery these days? I remember you generating a lot of patches at times to get Fedora to a certain stage.. did you get X going?
Yes, I started into X. I added the capability to have multiple repositories so that I can have a core set of srpms and then X, apache/php, gnome, KDE, extras, etc. Being able to separate the source packages into multiple directories was a big help.
X itself isn't bad. I don't remember any significant problems. I have not ventured into Gnome or KDE yet. I'll probably grab the whole Fedora Repo later this week and see how things work out.
As for the Rookery, its close to being production ready. I need to write some code to resolve files to packages so that BuildRequires with a file name works better (I'll discuss this below), finalize the technique for solving circular dependencies, and then integrate the Live CD creation.
Because its a bootstrap build, you can't use rpm -qf to resolve files to rpms and then to srpms. Having file names in the BuildRequires makes it impossible to work out the order that the build has to proceed in. I can create a database as each package gets built so that I can lookup Requires & Prereq; but BuildRequires is a different story. I have only found one package that needed a BuildRequires on a file. I think it was mutt, but I'm not 100% sure...I think it wanted /usr/lib/sendmail. ALL of the other packages that have file names in the BuildRequires can be converted to a package name. That's what I've done in my personal repo and it works fine...its just a lot of work to maintain. :(
-Steve Grubb
__________________________________ Do you Yahoo!? The all-new My Yahoo! - What will yours do? http://my.yahoo.com
Dirk Westfal wrote:
don`t know if someone is interested, so i keep this short:
I`ve finished a livecd using fedora core 3 with kde and gnome for the desktops, firefox/thunderbird, openoffice and other applications. Login manager is gdm, default desktop kde, gnome can also be selected.
a nice new fedora project ;-)
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=119308
On 11.29 08:50, Dirk Westfal wrote:
I`ve finished a livecd using fedora core 3 with kde and gnome for the desktops, firefox/thunderbird, openoffice and other applications. Login manager is gdm, default desktop kde, gnome can also be selected.
<snip>
Way cool. I'm sure that this will be very useful. If its not too much to ask, perhaps you could do a HowTo? I'll volunteer to do the grunt work if you could provide the raw data.