livecd March 2006

livecd@lists.fedoraproject.org

17 participants
50 discussions

Kadischi - User Manuals, File Formats
by J. Hartline 21 Mar '06

21 Mar '06

Hi. Chitlesh, could we also get these reviewed and try to get them in CVS. In RPM the standard project files like INSTALL, README.1ST, TODO are obsolete. RPM use manuals available via man(1). I've written the final drafts and have them attached to bugzilla BZ #185834 here: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=185834 I'm working ona few other things here at the moment too. Thanks. J. Hartline

2 2

weekly reports boken link
by Skunk Worx 20 Mar '06

20 Mar '06

This page : http://fedoraproject.org/wiki/Kadischi/WeeklyReports ...has a link in : Jan 16, 2006 The first Kadischi Weekly Report was published. ChitleshGoorah will write Kadischi's WeeklyReport each week. ...namely : http://fedoraproject.org/wiki/Projects/WeeklyReports/2005-Jan-16#kadischi ...which is broken cuz it's the wrong year :-) 2006 works. --- John

2 1

Kadischi - wiki
by J. Hartline 20 Mar '06

20 Mar '06

Chitlesh I also notice some changes relating to Fedora Core 4. The wiki should apply to all non-legacy releases so FC4 information is still valid. Keep this in mind when editing the wiki please. On another note, the CVS has been brought up to speed with FC5 with the exception of the buildstamp file contents. The current CVS will not work with FC4 because of small changes, it could however support both Core 4 and 5 using some conditionals. (Which I think is a good idea, but is more maintainable via RPM) Thus I'm working on getting a base for trying to get something within Extras) If this becomes a large problem, this is what we will do, for now the CVS should be current, and that is what it is. The wiki should not obsolete or not cover non-legacy Core releases however. I'll be looking over various things relating to Kadischi, a man page in sections (1) has also been submitted along with sections (5) for kadischi(1) and build.conf which should be kadischi.conf I think. (kadischi.conf(5)) These are drafts and shopuld be reviewed heavily and improved which I'll work on also from time to time. Thanks. J. Hartline

1 0

no joy with the following package set...
by Skunk Worx 19 Mar '06

19 Mar '06

I tried this set and there is no startx command, the runlevel in inittab is 3, and /sbin/init 5 just goes back to the console login. No /usr/X11R6 either, which is probably hampering X window. I guess you're already working on this but I thought I'd mention it. %packages @base @development-libs @development-tools @gnome-software-development @office @x-software-development --- John

2 1

getting Xorg to install from kickstart, and bug 185830
by Jane Dogalt 19 Mar '06

19 Mar '06

I think these two things may be related. First, I filed bug 185830, in which I was running kadischi, and while it was invoking anaconda, it *reconfigured my network*!!!. I think this is related to what I was discussing earlier about being fearful of anaconda probing the hardware of the build system while running under kadischi. I suspect that somehow anaconda running under kadischi did to the host build system (reconfiguring the network) what it was supposed to be doing to the target system (which for us, during install, has no 'real' network to reconfigure). In a possibly related fashion, I can't seem to get X installed on my livecd. Everything other than the xserver itself (libX11-bla, gnome, openoffice) installed, but not X itself. Even when my xconfig line in my kickstart matched the build host system (which I think it shouldn't have to), X didn't get installed. I suspect this has something to do with when and how anaconda installs the X server. I understand that maybe my knoppix-like goals don't necessarily map 1-1 with the specific-hardware-appliance users. I think it would be nice if kadischi could satisfy both crowds. If not, I'm sure I can hack together whatever I need. But regardless, I think we(???) need to at least go over kadischi's use of anaconda and make sure that the kad-anaconda doesn't directly affect (and I'd prefer also - is not directly affected by) the build host system. -jdog __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

3 3

request for comments in 04auth.sh: disabling firewall why?
by Jane Dogalt 19 Mar '06

19 Mar '06

I understand the disabling of selinux in 04auth.sh, but why is the user's firewall setting (presumably from both an interactive or kickstart install) overridden? I think 04auth.sh especially needs some comments (around this line in particular) chroot $1 /usr/sbin/lokkit --quiet --nostart -f --disabled -jdog __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

3 3

need: mount -really-readonly, or a way to detect uncleanly unmounted FS
by Jane Dogalt 19 Mar '06

19 Mar '06

Does anyone know any of a truly read only method (available tool) for detecting if a filesystem (ext3 esp, vfat/ntfs/xfs/etc...) has been unmounted cleanly? Specifically, the feature of a livecd mounting all visible filesystems read-only is very nice. But there are a pair of big danger issues, which I should go see if knoppix is even bothering to check for these days- suspend and journaling It used to be fairly safe in a livecd to just do a mount -ro. But these days you have things like the severely annoying ext3 behaviour of modifying the disk during a -ro mount, as well as suspended operating systems (i.e. that great new feature in fc5) being very unhappy (I mean very unhappy) if their mounted filesystems get modified at all while they are asleep. My proposed workaround, requiring the tool above, is to only read-only mount filesystems which have been flagged as cleanly unmounted. I imagine this applies to suspended ms-windows filesystems as well. So does anybody know of a simple tool which can, without modifying a partition, see if it's been cleanly unmounted. I suppose it's just a matter of reading a fs spec and reading some bit somewhere, but I'd rather not write the tool myself if possible. -jdog __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

2 1

Kadischi - preload utilities and daemon
by J. Hartline 19 Mar '06

19 Mar '06

Hi. I was readong an older message about preload available here: http://sourceforge.net/projects/preload with the proposal being here: http://www.cs.toronto.edu/~behdad/blog/preload.txt Is this something we should still consider with Kadischi? I would imagine the preliminary benchmarks would be done before having an answer for that question, but is this also something that is plausible on top of say.. SquashFS? Not the usability, rather the speed and performance differences. I would imagine so. It is slightly interesting since it "predicts" what a user is doing, thus caching data related to library routines, etc. Sounds like it could be useful. J. Hartline

2 5

kadischi+kickstart is broken how exactly?
by Jane Dogalt 18 Mar '06

18 Mar '06

Hello, A few years ago I worked on generating livecds using mandrake as a base. I'd like to start using fedora as a base and it looks like kadischi is the place to start. Things here look rough around the edges, so I'm hoping you can help answer at least this first major question of mine. (and I'll throw in my first reactions to the system) I just ran my first experiment with kadischi using kickstart on FC5T3, and to my surprise given the status listed on the development wiki, it worked. It might not have worked exactly like I wanted it to, but given that this is only my 2nd trivial (successful) kadischi experiment, I was not unsatisfied. I.e. it produced an iso, which booted my system. Mind you I saw some non-fatal bad sector errors, but given that a subsequent "find / -print" didn't choke, I think it 'worked'. I sort of expected gdm and X to be installed, and for it not to be half the size (450M vs 850M) of my first trivial non-kickstart experiment, but again, it did in fact 'work'. Pretty much everything I would want to do with kadischi involves using kickstart, so please elaborate on the development page as to how it's broken if in fact it still is. Otherwise- - my first fc4 experiment died in anaconda, but I couldn't care less(fc5 is practically here already) - to get fc5t3 to work, I followed the docs, but had to manually apply most of one of the 2 patches, because parts of it were already in cvs. Maybe telling patch to blast ahead and ignoring rejects would have worked, but that certainly doesn't feel comfortable. - I also had to install autoconf/automake which aren't part of a braindead default fc5t3 install, and thus should be in docs in the yum install line. - I just noticed that nice rpm spec file posted, and see all those interesting gettext and other commands in the build section which should probably be noted in the docs (I'm guessing they might suppress some of the scarier warnings which didn't seem to prevent me from getting a bootable iso) -jdog __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

5 29

Expectation Setting
by Jeremy Katz 18 Mar '06

18 Mar '06

One thing that I'm seeing is that a lot of people are interested in live CDs (which isn't bad), but I really think that we need to be taking care to set their expectations properly. Everything being produced now is clearly just testing quality and there are significant issues that need to be addressed before we can move beyond that. Sending lots of people out with what we currently have and having it reproduced and distributed has a strong possibility of a negative perception of Fedora and the Fedora Live CD project. Therefore, can we please be sure to be emphasizing that this is all currently development work and not at all considered final? With things based on FC5 test releases, it's (somewhat) obvious without being stated but we need to be extremely clear as Fedora Core 5 is actually released and the live CDs that we're producing are still development versions. In other stuff, I've spent a little bit of time trying to clean up a few things while I've been testing the FC5 trees that are being produced. Expect to see more of it probably the start of next week (need to spend today making sure things are ready for Extras to correspond with FC5 as well as so that the next development tree can be opened up) Thanks, Jeremy

6 10

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

livecd March 2006