Anaconda settings for LiveCD install
by Jon Steer
I am creating a LAMP console-based livecd distro.
Since this is console based, I have run the problem where anaconda
assumes that the liveinst install will be X-based.
I originally thought I'd solve the problem by setting up a kickstart
file. Perhaps my kickstart wasn't complete, but, my results
were that the kickstart was processed but no livecd install occurred.
Looking further in anaconda (livecd.py) I found this piece of hardcoding
anaconda.id.bootloader.args.append("rhgb quiet")
anaconda.id.desktop.setDefaultRunLevel(5)
Not being python-speaking folk, I don't know whether there is a
parameter I can hang around this to take away rhgb and runlevel 5 when
X isn't being installed.
Any thoughts?
jon
--
"Don't stand still, if you see me running down the road, 'cause there
is trouble right behind me".
16 years, 7 months
- 2
- 1
[PATCH] overlay/persistence second pass - for developer reference only
by Douglas McClendon
(I'm getting a sense of deja vu, that I'm learning the same lesson
someone else recently learned here. Lets see if the 3rd time is the
charm...)
Attached is a revision to the persistence implementation that I posted a
couple weeks ago. This is mainly for Jeremy, Tim, and anyone else who
is interested in working on this, or something similar. I.e. at the
very least, it is worth a read to look at the issues I've dealt with,
and the several that are in comments as TODO.
It may well be that a simpler persistence implementation that involves
just extracting tarballs from usbsticks into the normal ram overlay, may
be useful instead of (or even in addition to) this kind of
implementation. (or perhaps some implementation of unionfs will make it
into fedora eventually?)
The main points of note, since the first post are-
- all sorts of bugs fixed
- I moved the overlay storage filesystem to be visible as /mnt/overlayfs
always. This solves some aspects of the current problem of not easily
being able to see how much writable space you really have available on
the rootfs. (the real answer is a combination of the device mapper
overlay file AND the filesystem it resides on).
- I've included modified /etc/rc.d/init.d/halt and functions, to handle
getting things cleanly shutdown (which is VERY important)
- ntfs is somewhat present, but not really working. I have tested with
vfat and ext3. Note that ext3 is a PITA when not cleanly unmounted- see
TODOs.
- rudimentary testing of the choice selection when multiple possible
overlay images are detected suggests it works.
- the patch format merely reflects my educational process with git, and
not that I suggest that code this immature is anywhere near ready for
merging. (i.e. inclusion of halt&functions and the origs I based them
off of. Refer to list archives for documentation on how to use
addidir/addsdir if needed)
As always, comments/criticisms/suggestions are more than welcome.
peace...
-dmc
16 years, 7 months
- 5
- 17
SRPMS for installed RPMs?
by Matt Domsch
I want to be sure, for license compliance, that all the binary bits on
the final LiveCD have corresponding source code available.
One of the "features" I'd like to see something in the stack of
livecd-tools produce is a CD/DVD/whatever of the SRPMS that match the
RPMs that go into the LiveCD. Smooge and I have both done this
ourselves, with varying degrees of ease, essentially querying all the
installed RPMs on the LiveCD after-the-fact and generating the list,
then grabbing the files etc. All very manual. I expect there's a
better way, and I'm even open to helping code it, but am looking for
direction from you - those who know the tools best...
Maybe it's really an Anaconda feature?
Advise please.
Thanks,
Matt
--
Matt Domsch
Linux Technology Strategist, Dell Office of the CTO
linux.dell.com & www.dell.com/linux
16 years, 7 months
- 7
- 24