imgcreate/fs.py
by Bruno Wolff III
imgcreate/fs.py | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
New commits:
commit 73bd6807678ff80b46196b7113f0582f03e84637
Author: Bruno Wolff III <bruno(a)wolff.to>
Date: Sat Jul 24 08:26:56 2010 -0500
Do lazy umounts to reduce the impact of umount issues.
By doing lazy umounts, if a umount can't be done (such as in the case of
the problem triggered by bug 617844), livecd-creator doesn't clean up after
itself. This ties up storage and loop devices.
This will mitigate problems where mounts are pinned by livecd-creator,
umounts are incorrectly done in the wrong order, or if the user is poking
around in the mount points while livecd-creator is running. It will not
fix a case where a umount is missed.
This should mitigate the symptoms of bug 509427, but not the root cause
(which is likely the problem reported in bug 617844.
diff --git a/imgcreate/fs.py b/imgcreate/fs.py
index 142ecd2..16445a5 100644
--- a/imgcreate/fs.py
+++ b/imgcreate/fs.py
@@ -112,7 +112,7 @@ class BindChrootMount:
if not self.mounted:
return
- rc = subprocess.call(["/bin/umount", self.dest])
+ rc = subprocess.call(["/bin/umount", "-l", self.dest])
if rc != 0:
raise MountError("Unable to unmount filesystem at %s" % self.dest)
self.mounted = False
@@ -353,7 +353,7 @@ class DiskMount(Mount):
def unmount(self):
if self.mounted:
logging.debug("Unmounting directory %s" % self.mountdir)
- rc = subprocess.call(["/bin/umount", self.mountdir])
+ rc = subprocess.call(["/bin/umount", "-l", self.mountdir])
if rc == 0:
self.mounted = False
else:
13 years, 10 months
Building a livecd by kickstarting off of a satellite server
by paul.armor@usbank.com
Hi all,
I'm wondering if anyone here has ever used livecd-creator to build an iso,
by pointing the .ks at a satellite server.
For what it's worth, I'm using livecd-tools-013-8.el5.1 from epel, on a
recently updated 5.5 machine, to do the iso creation.
I've done nfs and http based kickstarts (non livecd-creator) in the past,
I can do a local/file kickstart to create the livecd, but can't seem to
work out how to get livecd-creator to do the http install from a channel
on our satellite server.
I don't seem to have the google prowess to find out if anyone else has
ever done this (or at left traces on line).
Thanks in advance for any help!
Paul Armor
U.S. BANCORP made the following annotations
---------------------------------------------------------------------
Electronic Privacy Notice. This e-mail, and any attachments, contains information that is, or may be, covered by electronic communications privacy laws, and is also confidential and proprietary in nature. If you are not the intended recipient, please be advised that you are legally prohibited from retaining, using, copying, distributing, or otherwise disclosing this information in any manner. Instead, please reply to the sender that you have received this communication in error, and then immediately delete it. Thank you in advance for your cooperation.
---------------------------------------------------------------------
13 years, 10 months
Help: How to enable rootfs in rw mode?
by Lee Eric
Hi all,
I make a LiveCD by my self(not using livecd-tools) which is based on
Fedora 12. And I download an official LiveCD from Fedora website for
study. What I found is the root filesystem of LiveCD is in rw mode. I
noticed that there's an image named osmin.img in LiveOS folder of
Fedora LiveCD ISO image. It seems a LVM snapshot, for further
information I found there's a sentence in Wikipedia says: "Some
Linux-based Live CD systems also use snapshots to simulate read-write
access on a read-only compact disc.". So what I feel confused is how
to make it available in a LiveCD.
Here are steps how do I make my own LiveCD.
1. Create a folder in /tmp called LiveOS.
2. Using yum to create a small base system in LiveOS folder.
3. Modify /etc/sysconfig/readonly-root. READONLY=no, TEMPORARY_STATE=yes
4. Add some folders in /etc/rwtab like /etc, /home, /root.
5. Make a squashfs image by using mksquashfs and rename the image as ext3fs.img.
6. Create a folder in /tmp called iso.
7. Using isolinux as boot loader for the image and copy necessary
files including initramfs and vmlinuz in /tmp/iso/isolinux.
8. Copy the ext3fs.img to /tmp/iso/LiveOS folder.
9. Burning the ISO image.
After these steps the ISO image boots up okay by using qemu. And
/root, /home, /etc are in rw mode, services start okay. But when I
wanna restart or stop the system, it shows
umount: /etc: device is busy.
/etc:
init: rc0 main process (935) killed by KILL signal
Then system hangs.
So my question is what I shall I do for this LiveCD then can make the
root fs in rw mode like official Fedora LiveCD? Do I need to use LVM
snapshot as Wiki said "Some Linux-based Live CD systems also use
snapshots to simulate read-write access on a read-only compact disc."?
If yes, could anyone tell me how to achieve that? I really appreciate
that.
Thanks,
Regards,
Eric
P.S. Please do not just reply "Using livecd-tools them make yourself
easier", I ask questions here for study. Thanks.
13 years, 10 months
livecd-iso-to-disk reworked for self-replication of user customized LiveOS images was: Re: [SoaS] Call for Testing: Duplicating SoaS via CMD
by Frederick Grose
On Tue, Apr 6, 2010 at 1:38 PM, Frederick Grose <fgrose(a)gmail.com> wrote:
> On Mon, Mar 29, 2010 at 4:16 PM, Peter Robinson <pbrobinson(a)gmail.com>wrote:
>
>>
>> {...}
>
> *
*
*
*
*This post reopens the discussion of end user customization of LiveOS spins,
like **Sugar on a Stick.*
*
*
Ticket: https://bugzilla.redhat.com/show_bug.cgi?id=448030
(There is earlier discussion at
http://lists.sugarlabs.org/archive/soas/2010-April/000998.html.)
I've attached several patches to the bugzilla ticket, which breakdown the
changes for somewhat easier review:
1. One each, for the new --copy-overlay and --copy-home options and
update to livecd-iso-to-disk.pod for help on usage.
2. Another pair for the --builder-message <message> and
--releasefile <filepath> options with .pod changes for help.
3. And finally a pair that addresses the new to have usage help within
the livecd-iso-to-disk shell script.
The --copy-overlay and --copy-home additions extend the utility of the
script to allow the user/learner to replicate their personally modified
image.
The --builder-message and --releasefile options label the remixed image to
prevent confusion with the pristine versions, and to credit the builder for
their changes.
Because the livecd-iso-to-disk script is so often redistributed in
standalone fashion, it is worth the space and effort to include usage
documentation and help in the script itself. This should help the general
understanding of the script and its methods, given its presently-limited
documentation.
In the 1st and 3rd patches, there are many white-space changes that I
couldn't avoid in order to clarify the local variable name changes made to
match the broader scope of the script (for example, $ISO to $SRC and $USBDEV
to $TGTDEV). In addition, there are some block order changes that make use
and documentation easier to follow.
I also standardized the Bash conditional expression and list pipeline style
to the more modern, [[ Expression ]] && [[ Expression ]] format. (See
http://wiki.bash-hackers.org/syntax/ccmd/conditional_expression.)
This means that variables within the special double brackets need not be
quoted and the old test-type operators -a -o should not be used.
I'm sorry that all the changes may make review more critical, but it was
practically necessary.
Thank you for taking the time to review these proposed changes.
This is not the complete solution for end-user/learner customization of
Sugar on a Stick. Some of the missing pieces might be listed:
1. Graphical interface support
(See http://wiki.sugarlabs.org/go/Activities/Toaster for a project
that may provide this.)
2. An option to install a traditional filesystem on devices with
sufficient storage capacity.
3. Overlay space consumption monitoring. (Sugar Cellar, in
http://wiki.sugarlabs.org/go/Sugar_on_a_Stick/Sugar_Clone, provides
a basic, command-line report.)
3. An option to write LiveOS .iso files for quick and inexpensive
mass distribution.
4. Support for Macintosh compatible booting and replication.
The 'More robust iso', http://wiki.sugarlabs.org/go/More_robust_iso, feature
proposal can be aided by some of the installation options available in
livecd-iso-to-disk. In particular, using the --home-size-mb <size> option
creates a non-compressed (but loop mounted) filesystem for the home
directory.
SoaS deployments in schools may want to configure images without any
operating system overlay (providing consistency and stability) and use the
extra, persistent storage space for recoverable home directory storage that
can be easily backed up, shared, or swapped (by remounting the /home
folder). This would allow convenient and rapid sharing of limited
workstations in a classroom, library, or clubhouse all without the need to
reboot the workstation.
We can work to add a Sugar Frame or Journal feature to restart X with a new,
Sugar-usable Journal within attached filesystems. I expect there will be
some confusion as plug-in or wireless Journals allow Learners to appropriate
more computing devices in a way previously not possible.
--Fred
13 years, 10 months
live_locale= no longer work
by muayyad.alsadi@ojuba.org
hello,
the inird used to have script to override language of livecd through
live_locale=
after moving to dracut
this feature no longer exists
I found /usr/share/dracut/modules.d/10redhat-i18n/parse-i18n.sh
but I'm not sure it's what I'm looking for
as we used to pass live_locale to override language at boot prompt
https://bugzilla.redhat.com/show_bug.cgi?id=454105
13 years, 10 months
Livecd-Tools Meeting Summary 07-13-2010 @ 12:00UTC
by David Huff
===livecd-tools===
Tttendees: apevec, brunowolff, huff, jgreguske
==Topics==
=Procedure=
- We would love three ack's before push but right now if we can get one
good review + ack on list we will push.
- If you understand what's going on and it doesn't appear to do
something crazy then it should be OK to ack
- controversial patches will require three acks's
- Are we going to worry a lot about back ports?
- developing mainly for rawhide
=Patches=
Form list that need review:
- livecd-iso-to-disk --format fails with SD/MMC partitions Frederick Grose
- Enabled Images on SELinux Disabled Hosts Jay Greguske
- Destructive behavior in --skipcopy option of livecd-iso-to-disk
Frederick Grose
=BZ=
Ones we looked at:
- https://bugzilla.redhat.com/show_bug.cgi?id=589776 (>F12)
- https://bugzilla.redhat.com/show_bug.cgi?id=509427
=Next steps=
- apevec review SELinux patch
- brunowolff review skipcopy patch
- huff look at loop back mount BZ
- next build will be for multiple release, we will deferred incompatible
stuff, ie BZ 589776
13 years, 10 months
IRC meeting
by David Huff
I did not get a lot of response form the when is good meeting request.
Does tomorrow morning at 8am eastern time work for everyone?
-David
13 years, 10 months
Booting live usb stick off iMac
by James Heather
Can anyone tell me how I can create a live USB stick that will boot from
an iMac?
The restriction here is that I mustn't alter the config of the Mac in
any way (because it's not my machine and I can't risk screwing it up).
Googling suggests that I need to mess with EFI, but I don't really
understand the details.
J.
13 years, 10 months
Time it takes to review bug/patch in bugzilla?
by Richard Shaw
I posted the following patch[1] to the livecd-iso-to-disk script on
June 17th and still have not gotten any feedback. Not even a "Hey, you
suck a programming, don't ever do that again".
This list is relatively low volume, but I can't even count the number
of times someone has posted about a problem to other lists and I've
typically seen responses to the effect of, "File a bug report, or
better, submit a patch!"
Well that's exactly what I did, but taking nearly a month (and still
waiting) to receive any feedback does not do much to motivate people
to participate.
Richard
[1] http://bugzilla.redhat.com/show_bug.cgi?id=604942
13 years, 10 months