RE: Fedora-livecd-list Digest, Vol 27, Issue 25
by Lehal Parminder (GS-FI/ENG3-NA)
Hello,
How can we create a live CD containing files which are not in a RPM?
More specifically, I need to create a live CD containing tomcat and a
custom web application(jsp). The custom web application is in war
format. Is it possible to do it without creating a rpm for the custom
app?
Regards,
Parminder S. Lehal
-----Original Message-----
From: fedora-livecd-list-bounces(a)redhat.com
[mailto:fedora-livecd-list-bounces@redhat.com] On Behalf Of
fedora-livecd-list-request(a)redhat.com
Sent: Tuesday, July 24, 2007 12:00 PM
To: fedora-livecd-list(a)redhat.com
Subject: Fedora-livecd-list Digest, Vol 27, Issue 25
Send Fedora-livecd-list mailing list submissions to
fedora-livecd-list(a)redhat.com
To subscribe or unsubscribe via the World Wide Web, visit
https://www.redhat.com/mailman/listinfo/fedora-livecd-list
or, via email, send a message with subject or body 'help' to
fedora-livecd-list-request(a)redhat.com
You can reach the person managing the list at
fedora-livecd-list-owner(a)redhat.com
When replying, please edit your Subject line so it is more specific
than "Re: Contents of Fedora-livecd-list digest..."
Today's Topics:
1. Re: [PATCH] alternate syslinux menus (fixed) (Jeremy Katz)
2. Re: [PATCH] alternate syslinux menus (fixed) (Jeremy Katz)
3. [PATCH] persistence - VERY ROUGH first pass (Douglas McClendon)
----------------------------------------------------------------------
Message: 1
Date: Mon, 23 Jul 2007 14:32:50 -0400
From: Jeremy Katz <katzj(a)redhat.com>
Subject: Re: [Fedora-livecd-list] [PATCH] alternate syslinux menus
(fixed)
To: fedora-livecd-list(a)redhat.com
Message-ID: <1185215570.15644.11.camel(a)localhost.localdomain>
Content-Type: text/plain
On Mon, 2007-07-23 at 08:21 -0400, Patrice Guay wrote:
> However, the timeout delay does not work. I had the same issue when I
> was using syslinux-3.36-2 (includes vesamenu.c32) with the
> livecd-creator script unpatched. The timeout countdown does not start.
> Did you notice the same behavior?
Some syslinux versions have this bug. I don't remember when it was
introduced, but based on looking at the changelog, I fixed it in 3.36-3.
The fix should be able to be applied to any earlier version with the
problem as well IIRC
Jeremy
------------------------------
Message: 2
Date: Mon, 23 Jul 2007 14:32:53 -0400
From: Jeremy Katz <katzj(a)redhat.com>
Subject: Re: [Fedora-livecd-list] [PATCH] alternate syslinux menus
(fixed)
To: fedora-livecd-list(a)redhat.com
Message-ID: <1185215573.15644.13.camel(a)localhost.localdomain>
Content-Type: text/plain
On Thu, 2007-07-19 at 14:49 -0500, Matt Domsch wrote:
> livecd-creator look for multiple syslinux menus
>
> livecd-creator doesn't work on CentOS5 because the copy of syslinux in
> CentOS 5 doesn't include vesamenu.c32, but instead has menu.c32.
> Patch below has it look for both in priority order.
>
> Fixed to copy the right list of files into isolinux/.
Thanks Matt; applied.
Jeremy
------------------------------
Message: 3
Date: Tue, 24 Jul 2007 03:43:57 -0500
From: Douglas McClendon <dmc.fedora(a)filteredperception.org>
Subject: [Fedora-livecd-list] [PATCH] persistence - VERY ROUGH first
pass
To: fedora-livecd-list(a)redhat.com
Message-ID: <46A5BBCD.9000705(a)filteredperception.org>
Content-Type: text/plain; charset="iso-8859-1"
Attached is a _first pass_ patch that enables LiveOS persistence for
livecd-tools. Before you read this and get _too_ excited, note that I'm
really
only posting this because of the f8t1 devel freeze. If I get any
encouragement,
I am very willing to work my ass off in the next few days to get this
cleaned up
into respectable shape for a potential f8t1 feature. But I also realize
it is
probably just too late for that. (OTOH the code is already structured so
that it
is obvious that in the absence of a persistence bootarg, the code has no
impact)
The Principals Of OPeration are-
- unless a boot argument of "persistence[=[devspec][:pathspec]]" is
seen,
nothing will behave differently, except for the existence of a new tool
/usr/sbin/livetool
- after booting normally (no persistence bootarg), if you invoke
"/usr/sbin/livetool persistence initialize [devspec][:pathspec]"
then a persistence file will be initialized. By tomorrow I should have
an
option that allows the existing in-ram-overlay to be live migrated to
the new
file (thus freeing the ram by the time the command completes). I have
done this
manually. Currently this tool is not implemented. Creating a sparse or
zeros
file of any size (say 512M) should work fine.
e.g. dd if=/dev/zero of=/mnt/stick/LiveOS/Persistence-mylabel \
bs=1k count=1 seek=$(( 1024 * 512)
- to use the persistence file on a subsequent boot, add the bootarg
"persistence" which is equivalent to "persistence=auto"
- devspec can be in the following forms (should be obvious what they
mean),
and defaults to auto, which means to search all mountable partitions.
(the
search process mounts readonly (with paranoid blockdev --setro as well)
sda1
sdb
/dev/sdc3
LABEL=MyLabel
UUID=MyUUID
- pathspec defaults to /LiveOS/Persistence-LIVEOS_LABEL
(e.g. /LiveOS/Persistence-Fedora-7-Live-i386)
if pathspec does not start with a /, it prepends the above default.
(e.g. persistence=:dmc would mean to search all partitions for
/LiveOS/Persistence-Fedora-7-Live-i386-dmc)
if pathspec starts with a / then it is used as is. e.g.
persistence=:/home/dmc/testpers would search all partitions(and whole
devices)
for /home/dmc/testpers )
To round out the examples, persistence=LABEL="my usb
stick":/my/path/to/file
Finally: Known bugs:
1) I had to comment out the mayflower generated init's trap and set -e
2) ext3's inability to mounted readonly is annoying (yeah, I know
norecovery or
ext2 will probably get it for me, still annoying)
3) choice handling is broken. Don't use auto when it will find more
than one
entry. Maybe just don't use auto at all.
4) livetool doesn't do anything. For now, just create a sparse file of
any
interesting length (512M is fine) as mentioned above.
Well, that about covers it for now. As always, comments, suggestions,
and
criticisms will be greatly appreciated. (though feel free to wait 48
hours for
plenty of obvious improvements, such as fixing those known bugs).
"release early, release often"...
-dmc