for having a better
forum than IRC to address criticisms.
peace...
-dmc
Douglas McClendon wrote:
Fedorans,
Can you spare 50 or 100K? If you can spare 100K/700M in the forthcoming
Fedora-12 LiveCD, I can provide you with a rebootless installation
experience.
http://fedoraproject.org/wiki/Features
Jeroen van Meeuwen wrote:
On 07/16/2009 04:07 PM, Jeremy Katz wrote:
On Wednesday, July 15 2009, Douglas McClendon said:
In my livecd generation tools I go to a bit of extra hassle to play
symlink games with /boot/vmlinuz-$(uname -r), such that it doesn't get
put into the squashfs, since
Jeremy Katz wrote:
On Wednesday, July 15 2009, Douglas McClendon said:
In my livecd generation tools I go to a bit of extra hassle to play
symlink games with /boot/vmlinuz-$(uname -r), such that it doesn't get
put into the squashfs, since a copy of it is in the container iso/usb
filesystem
Colin Walters wrote:
Wait, so it's persisting any changes you made to the target drive?
That sounds quite cool actually, and I misunderstood the original
post. Concretely with your change, if I've connected to a wireless
network with NetworkManager, that would get saved in the target
drive's
It may well be that this has been discussed on this list before, and
worse yet, that I may have even participated, but if so I've long
forgotten, and it doesn't seem easy enough to search for.
In my livecd generation tools I go to a bit of extra hassle to play
symlink games with
Fedorans,
Can you spare 50 or 100K? If you can spare 100K/700M in the forthcoming
Fedora-12 LiveCD, I can provide you with a rebootless installation
experience.
http://fedoraproject.org/wiki/Features/RebootlessInstaller
The short story is that you boot the LiveCD/USB, run the installation,
Thorsten Leemhuis wrote:
On 14.07.2009 10:04, Douglas McClendon wrote:
[...]In any event, I'd love to hear what people think. [...]
I for one think rebooting after install is a very good thing, as only a
full reboot makes sure the install (including boot loaders) was
completely successful
Jon Masters wrote:
On Tue, 2009-07-14 at 02:04 -0600, Douglas McClendon wrote:
Can you spare 50 or 100K? If you can spare 100K/700M in the forthcoming
Fedora-12 LiveCD, I can provide you with a rebootless installation
experience.
http://fedoraproject.org/wiki/Features/RebootlessInstaller
Felix Miata wrote:
On 2009/07/14 02:04 (GMT-0600) Douglas McClendon composed:
[snip]
http://viros.org/rebootless
Doesn't kexec, which does a BIOS bypassing reboot, accomplish what you want?
OpenSUSE's installer has had kexec_reboot=1 by default for a version or two
(I think default started
Christoph Höger wrote:
Hi,
although (as others pointed out) a reboot may be necessary one way or
the other, my opinion would be: Why not?
Currently you are *forced* to reboot which now seems not to be a must
have.
Thanks for the feedback. Glad to see somebody else can see the added
value
Colin Walters wrote:
On Tue, Jul 14, 2009 at 4:04 AM, Douglas
McClendondmc.fed...@filteredperception.org wrote:
i.e. simply a checkbox before beginning installation stating whether you want
rebootless instead of traditional.
I don't think the installation process needs more questions.
Colin Walters wrote:
Another thing to keep in mind that immediately post-installation there
are going to be updates, which will at a minimum need desktop reset
(fast reboot experience), or more likely system restart.
I don't exactly get this. I might understand some negligible things.
But
Martin Sourada wrote:
On Tue, 2009-07-14 at 02:04 -0600, Douglas McClendon wrote:
Fedorans,
Can you spare 50 or 100K? If you can spare 100K/700M in the forthcoming
Fedora-12 LiveCD, I can provide you with a rebootless installation
experience.
http://fedoraproject.org/wiki/Features
Rahul Sundaram wrote:
On 07/14/2009 08:08 PM, Christoph Wickert wrote:
Am Dienstag, den 14.07.2009, 19:05 +0530 schrieb Rahul Sundaram:
On 07/14/2009 07:02 PM, Christoph Höger wrote:
Hi,
although (as others pointed out) a reboot may be necessary one way or
the other, my opinion would be: Why
Paul W. Frields wrote:
On Tue, Jul 14, 2009 at 08:09:09AM -0600, Douglas McClendon wrote:
Colin Walters wrote:
Another thing to keep in mind that immediately post-installation there
are going to be updates, which will at a minimum need desktop reset
(fast reboot experience), or more likely
Christoph Höger wrote:
We are talking about a live cd installation, yes? You can close the
installer then.
We were talking about anaconda. And I still don't know a sane (aka no
manual chroot) way to go from livecd into the fresh installed
environment.
If you look at the feature page and
Rahul Sundaram wrote:
On 07/14/2009 08:23 PM, Christoph Höger wrote:
We are talking about a live cd installation, yes? You can close the
installer then.
We were talking about anaconda. And I still don't know a sane (aka no
manual chroot) way to go from livecd into the fresh installed
Christoph Wickert wrote:
Am Dienstag, den 14.07.2009, 08:09 -0600 schrieb Douglas McClendon:
Colin Walters wrote:
Another thing to keep in mind that immediately post-installation there
are going to be updates, which will at a minimum need desktop reset
(fast reboot experience), or more likely
Douglas McClendon wrote:
Christoph Wickert wrote:
Am Dienstag, den 14.07.2009, 08:09 -0600 schrieb Douglas McClendon:
2. Imagine after the installation you switch rebootless to the new
system and install a kmod. But you are still running the kernel
from the installation
Christoph Wickert wrote:
Am Dienstag, den 14.07.2009, 20:12 +0530 schrieb Rahul Sundaram:
On 07/14/2009 08:08 PM, Christoph Wickert wrote:
Am Dienstag, den 14.07.2009, 19:05 +0530 schrieb Rahul Sundaram:
On 07/14/2009 07:02 PM, Christoph Höger wrote:
Hi,
although (as others pointed out) a
Christoph Wickert wrote:
Am Dienstag, den 14.07.2009, 09:27 -0600 schrieb Douglas McClendon:
Douglas McClendon wrote:
Christoph Wickert wrote:
Am Dienstag, den 14.07.2009, 08:09 -0600 schrieb Douglas McClendon:
2. Imagine after the installation you switch rebootless to the new
Bill McGonigle wrote:
On 07/14/2009 11:04 AM, Christoph Wickert wrote:
2. Imagine after the installation you switch rebootless to the new
system and install a kmod. But you are still running the kernel
from the installation medium and kmods get installed for the
Colin Walters wrote:
On Tue, Jul 14, 2009 at 7:38 AM, Douglas
McClendondmc.fed...@filteredperception.org wrote:
If so, one way to describe the major
benefit of my rebootless installer, is that you get to boot the livecd/usb
environment, *then use it as such*, and at your option, desire, and
of youtube videos demonstrating the user
experience of rebootless installation with a stock f11-i686 liveusb onto
an acer aspire one netbook.
Future announcements will be made on website's news/front page, so I
won't spam here.
http://filteredperception.org
peace...
-dmc
Douglas McClendon
A new GPLv3 - F11 compatible - _rebootless_ LiveOS installer is ready
for alpha testers.
Read all about it here, with full screenshot tour, src and binary rpms,
online browsable source tree, and beginnings of a FAQ.
http://viros.org/rebootless (redirects to:)
Richard W.M. Jones wrote:
On Mon, Sep 08, 2008 at 12:03:21PM -0400, Perry N. Myers wrote:
Ben Guthro wrote:
In my endeavor to set up a build environment for our developers
experimenting with oVirt / libvirt, I have come across a general
dislike that the build of the ovirt managed node
Jerry Vonau wrote:
Yeah, you could easily just do a snapshot and then set LIVE_BLOCK to
that.
Got a magic string? ;-) DMC, Can you point me in the direction please?
I'll play around...
Here is an example. Note, that trying to do the below on your normal
rootfs would not be doable (though
Richard Shaw wrote:
On Mon, Aug 4, 2008 at 8:51 AM, Jeremy Katz [EMAIL PROTECTED]
The problem is that incorporating the changes back in basically boils
down to make a new image. Which isn't that difficult to do, it's just
a matter of having the disk space for it and also the time
Jerry Vonau wrote:
Hi all:
Just been playing around with a LiveUSB stick and persistence, and it
occurred to me that if you make any changes at all, anaconda will not
pick them up. The reasoning for this is that /usr/sbin/liveinst looks
for:
if [ -z $LIVE_BLOCK ]; then
if [ -b
Jerry Vonau wrote:
Douglas McClendon wrote:
Jerry Vonau wrote:
Now the real question, what would be the best way to have anaconda
pickup the persistent overlay for the install to hard-drive part.
Sure. Why not go hog wild and just install rebootlessly too while you
are at it :)
http
Antonio Olivares wrote:
Dear all,
I have asked the following question on [EMAIL PROTECTED]
But then it clicked to me that I should have directed the question here on
livecd list.
Is automounting of LVM volumes by a livecd dangerous?
Probably you've heard this before, but the short answer
[EMAIL PROTECTED] wrote:
Douglas McClendon [EMAIL PROTECTED] wrote:
If that doesn't help or answer you question, try to add more detail to
your question.
Douglas -
Thanks for the reply.
I use the live usb tools to create my live USB stick with a 2047 MB
overlay. I boot from it and let
Coco Computers Consulting wrote:
When I boot with Centos 5.1 Live CD, a df command shows the root
filesystem / is mounted to /dev/mapper/livecd-rw and shows a total of
about 4GB with 50% available. Is this disk space from my local hard
drive? How is it carved out? My local hard drive is
[EMAIL PROTECTED] wrote:
After I format and reinitialize my Live USB, do I have to let it run
through all of the updates and reinstall my applications?
Do we have the tools to pull all of that data off and restore it?
I'm not entirely sure what you mean. One thing that is possible is to
Skunk Worx wrote:
I'm using F9 and the livecd-tools-017.1-1.fc9.i386.rpm (from koji).
When I try to build my iso from a config, I get a list of rpm names and
sizes, then livecd-creator bails out.
My set of rpms is large and apparently exceeds the 4096L * 1024 * 1024
default value set in
Jeremy Katz wrote:
On Wed, 2008-06-04 at 19:12 +0100, Pedro Silva wrote:
So, how does the persistance work:
- Persistance is created with livecd-iso-to-disk, if I run it again
without the overlay flag, previous persistance overlay is deleted?
Yes. Also, the overlay is specific to the
Jeremy Katz wrote:
On Wed, 2008-06-04 at 19:12 +0100, Pedro Silva wrote:
So, how does the persistance work:
- Persistance is created with livecd-iso-to-disk, if I run it again
without the overlay flag, previous persistance overlay is deleted?
Yes. Also, the overlay is specific to the
Jerry Vonau wrote:
Gary Thomas wrote:
Are there image options other than squashFS for the LiveCD?
I ask because building squashFS images on the PowerPC is
excruciatingly slow :-(
There is an undocumented option --skip-compression that should leave the
ext3fs.img file in LiveOS instead of
ergodic wrote:
---An attempt to test F-9 Live from USB Stick failed with the following results:
This is a current limitation of qemu (at least). You could try booting
on real hardware that is known to work with f8 and livecd-iso-to-disk.
Also, what you probably meant to do (if it would
Jeremy Katz wrote:
On Mon, 2008-03-10 at 22:02 -0500, Douglas McClendon wrote:
ergodic wrote:
---An attempt to test F-9 Live from USB Stick failed with the following results:
This is a current limitation of qemu (at least). You could try booting
on real hardware that is known to work
I think I've mentioned this idea here sometime in the past couple years,
but for various reasons, I'll bring it up now just for the digital record-
feature: persistent desktops
example obvious non-portable implementation:
Use the recently merged persistence feature, along with software
Jeremy Katz wrote:
After long periods of waiting and hoping, etc I'm just about to do a
push of some changes that at least give us a good base to build on for
persistent live images. They're very very very heavily based off of
Douglas McClendon's patches that he posted here a month or two, but
Daniel P. Berrange wrote:
On Thu, Feb 21, 2008 at 01:57:08AM +, Daniel P. Berrange wrote:
On Wed, Feb 20, 2008 at 08:01:32PM -0500, Jeremy Katz wrote:
On Tue, 2008-02-19 at 19:16 +, Daniel P. Berrange wrote:
from its kickstart recipe. Currently developers building the appliance have
Daniel P. Berrange wrote:
On Wed, Feb 20, 2008 at 09:49:57PM -0600, Douglas McClendon wrote:
Daniel P. Berrange wrote:
Some other examples of scenarios where you want to build appliance images
but
do not have virtualization capabilities directly accessible.
- Machines where the user's
Warren Togami wrote:
I'm not sure what's going on here. Prior to resending it I tested it by
sending the mail to myself, and it worked.
http://fedorapeople.org/~wtogami/temp/0001-ChrootCreator-class-and-chroot-creator-tool-instal.patch
Looks like you're hitting the old git formatted patch
Disclaimer: take these claims with the proverbial grain of salt, as I
can on occasion be a bit over-optimistic or over-committal...
Second Disclaimer: read the first disclaimer again.
BUT THAT SAID...
The Bad News: my SuperDeviceMapperCaching technique does not (yet[1])
appear to actually
Jeremy Katz wrote:
Moving to the more appropriate list, original is at
https://www.redhat.com/archives/fedora-devel-list/2008-January/msg03188.html
for those not on fedora-devel
On Thu, 2008-01-31 at 16:11 -0600, Douglas McClendon wrote:
I keep hearing these crazy rumors that RedHat actually
Asheesh Laroia wrote:
On Mon, 4 Feb 2008, Tim Wood wrote:
I think you're looking for something like this. If bob had a file
called 'my_file.html' in his home directory, he'd do this to copy it
to the root of the cd:
%post --nochroot
cp /home/bob/my_file.html $LIVE_ROOT/
Right - but if
Jeremy Katz wrote:
On Mon, 2008-02-04 at 18:51 -0600, Douglas McClendon wrote:
Jeremy Katz wrote:
Outside of those changes, everything looks pretty straight-forward and
reasonable. We'll want a little more error checking in
livecd-iso-to-disk and it might also be nice to have another tool
Jeremy Katz wrote:
On Sat, 2008-01-26 at 01:42 -0600, Douglas McClendon wrote:
I'm putting together a feature enhancement patch for livecd-tools, that
will basically just allow multiple instances of --config on the command
line, and then build something that is the same as if one --config
Tim Wood wrote:
Thanks. That will work. InstantMirror does look more maintainable but
has the downside (at v0.4) that it looks a little early to use as the
basis of real work.
Yes- I assumed --cache was so obvious, that you must have wanted
something for a wider purpose than just livecd
Jeremy Katz wrote:
On Mon, 2008-01-14 at 13:42 -0600, Douglas McClendon wrote:
Jeremy Katz wrote:
On Sun, 2008-01-13 at 22:32 -0600, Douglas McClendon wrote:
The main problem, is that no install method is specified. For now, I'm
just going to do a little parsing, taking the first repo line
Tim Wood wrote:
I've been (finally) setting up a local Fedora 8 Repository. In the
process, I've discovered that os+updates+development now approaches
20G. Given that a lot of that material is not relevant to me --at a
guess 2G of the archive plus update and dev versions so 4-6G-- I
Jeremy Katz wrote:
On Sun, 2008-01-13 at 22:32 -0600, Douglas McClendon wrote:
The main problem, is that no install method is specified. For now, I'm
just going to do a little parsing, taking the first repo line, and
converting it into
install
url --url=bla
While not required
I'm currently working on my livecd generator, and making it compatible
with the kickstart format that livecd-tools expects.
My method involves a traditional anaconda network install going under qemu.
So here is what I noticed when I tried feeding a flattened version of
FYI- I've somewhat cryptically alluded to grand plans for improving
LiveCD boot speed on this list in the past.
While I'm still quite some time from having the time to implement it, I
did outline my method on squashfs-devel yesterday.
The basic idea is to replace all the disk seeks for file
to solve it...
I am currently going to double-check the result using livecd-creator
(well, revisor uses livecd-creator tools, doesn't it?... but I will give
it a try.)
Sebastian
Douglas McClendon wrote:
[EMAIL PROTECTED] wrote:
Hi there!
I am going to build a customized Fedora Live CD
[EMAIL PROTECTED] wrote:
Hi there!
I am going to build a customized Fedora Live CD with some educational
applications using revisor. In the repo config, I needed to exclude
*.i586 and aspell-* (apart from aspell and aspell-en) to solve
conflicts. In the end, the image was successfully
hoping that I could install from that and it
filled up again. Checkmate.
MikeD
On Thu, 2008-01-03 at 15:30 -0800, Mike Dickson wrote:
Ran that and yes the snapshot area filled up BEFORE the errors. Let
me know what I can do
MikeD
On Thu, 2008-01-03 at 16:31 -0600, Douglas McClendon
Mike Dickson wrote:
Guys,
I got a LiveCD + Persistence usb drive running from your scripts, but
got I/O errors if I tried to do a yum update.
Before that I was able to vi test.txt and put some text in and it
survived a reboot.
What can I do to address the i/o errors?
My first
Thiago Braga Santana wrote:
Hello List.
I customizing the livecd of Fedora 6 you developed. I urgently need to
understand two parameters of the kernel. LIVEINST and LIVEIMG, must
fully understand the usefulness of each.
Recently I discovered a problem with the livecd, a problem which
. This is definitely not a magic bullet solution.
more later...
-dmc
MikeD
On Thu, 2008-01-03 at 15:30 -0800, Mike Dickson wrote:
Ran that and yes the snapshot area filled up BEFORE the errors. Let
me know what I can do
MikeD
On Thu, 2008-01-03 at 16:31 -0600, Douglas McClendon wrote:
Mike
Can someone tell me if there is anything I can do to de-regress f8's
pm-hibernate?
What I mean is that it seems like in f7, pm-hibernate saved the kernel
buffer/filesystem caches as well as the minimal needed stuff. Now in
f8, every time I resume, system performance is crap because
I wasn't paying close enough attention to my thunderbird tab completion,
this mail was meant for fedora-devel.
Douglas McClendon wrote:
Can someone tell me if there is anything I can do to de-regress f8's
pm-hibernate?
What I mean is that it seems like in f7, pm-hibernate saved the kernel
gmvects wrote:
On Thu, 2007-12-27 at 20:55 -0600, Douglas McClendon wrote:
Vects wrote:
Hello there,
I want to create minimal fedora livecd with some local addons, I don't
need any desktop. I used minimal.ks but it has missed login things,
somebody could advise me what to add to livecd
Thiago Braga Santana wrote:
Hello to everyone on the list.
I am having a big problem with the lvm2 livecd, on computers that use
the Hard Disk SATA2.
I'm curious, what is the problem?
I need the help of someone of the list to make a
livecd without lvm2.
device-mapper is needed for
Sriram Kailasam wrote:
Hello all,
I have created a live cd with modified linux kernel using livecd-create tool.
Just installing the kernel rpm on the system using rpm -ivh works fine.
But when I try booting from the livecd, it gives the following error.
Just starting from the top, looks
WARNING: THE FOLLOWING IS A VERY ALPHA EXPERIMENTAL DEVELOPMENT FEATURE
If you have to ask what this is all about, it isn't ready for your
testing yet. Please wait a bit longer.
More variations of this on the way for testing purposes, but for the
moment, this might work-
(actually it seems
Douglas McClendon wrote:
# this extracts the modified livecd-iso-to-disk
isodump -R -i Fedora-8-Live-i686.persistence.iso \
-x /LiveOS/zyx-livecd-iso-to-disk \
zyx-livecd-iso-to-disk
Actually that should be isoinfo, not isodump. And in case your email
client likes to reinterpret leading
-10-16 02:09:02.0 -0500
@@ -0,0 +1,223 @@
+#!/bin/bash
+#
+# findoverlay - set up persistence overlay loop device (/dev/live-overlay)
+#
+# Copyright 2007 Douglas McClendon [EMAIL PROTECTED]
+#
+# Licensed under the GPLv2. See the file COPYING for details.
+#
+
+# the overlay option value
mdda wrote:
I have created a new Fedora spin 'EeeDora' specifically for the EeePC. The
Live Image boots fine (very fine). Live install works in manual mode, but
with a kickstart file (I'd like to make this completely automatic) Anaconda
goes through the installation (writing packages=100%),
Thiago Braga Santana wrote:
Jeremy, thank you for your information. I still need to file KS.CFG
original, which was used in the development of LIVECD fedora-7-kde -
i386.iso
If you no longer have this file, you can at least spend some URL me so
that I can download it?
I thought this
Jeremy Katz wrote:
The simplest way to get this to work would be to set the http_proxy
environment variable which should then get picked up and used by yum.
More than that is going to require adding some syntax (and thus require
a little more thought)
Is there any way to set http_proxy like
Are the SQUASHFS errors important?
Can you rule out media errors? Perhaps try booting the iso under qemu,
and seeing if the problematic commands succeed?
-dmc
--
Fedora-livecd-list mailing list
Fedora-livecd-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-livecd-list
Asheesh Laroia wrote:
On Tue, 13 Nov 2007, Antonio Olivares wrote:
Dear all,
I have created a livecd using livecd tools, xmaxima
does not work :(
If you use the live CD in an emulator, does it work?
I fear the CD may not have been burned properly.
-- Asheesh.
Uhh... yeah, that :) (you
dzho002 wrote:
Hi folks,
I created a Fedora Core 8 live CD using the
livecd-creator tool successfully. It boots up fine
from a USB pen drive and is able to install to hard
drive. But there is a problem with the size of /
partition (dev/sda2) on the hard disk. The commands df
and fdisk report
Chris Lalancette wrote:
All,
I'm working with the latest version of livecd-creator available in rawhide,
which is livecd-tools-012-1.fc8. I noticed a bug when using the --base-on
option; basically, it is testing for the existence of the squashfs.img, but that
path can't possibly exist
offset wrote:
Newbie alert :)
Looking to get up-to-speed on Fedora LiveCD so I can custom build my own
security tools that I can boot from cd, rather than lug around my laptop
everywhere. I did see the Security fedora livecd wiki, so I'll have to poke
around there as well.
I'm getting the
Rahul Sundaram wrote:
Hi
Would it be possible to add a boot option in the live images to directly
invoke either the graphical or console installer.
I don't see why not.
And of course at the same time, parse and use ks= from the cmdline if
present.
-dmc
Very useful for low resource
Tim Wood wrote:
+1
FWIW, some LiveCDs have an index.htm or index.html file in the root of
the cdrom that holds the readme and links to an html version of the GPL,
etc. Going off memory, there's an autorun dot something file in the
root of many windows cds that is used to automatically open
Tim Wood wrote:
Two different recommendations have been posted on what version of Fedora
to use (F7 presumably with livecd-tools 009 vs. rawhide and livecd-tools
from git). Rawhide and git (seems to me) to be a formula for a very
unstable development environment. But, livecd-tools 009 and F7
Alexandre Magaz Graça wrote:
Hi,
Since some days ago, livecd-creator is falling with this traceback
(latest git version):
Traceback (most recent call last):
File /usr/bin/livecd-creator, line 1503, in module
sys.exit(main())
File /usr/bin/livecd-creator, line 1483, in main
I may yet file a bug, if I can provide instructions on how to reproduce
this. But since I'm working from an extremely modified environment,
I'll just ask for general advice-
I've spun an selinux-enabled livecd, and upon starting up, and starting
udev, I get a whole bunch of 'errors' (perhaps
Here is another update to my devicemapper-snapshot based LiveOS
persistence implementation.
Still developer quality, and nothing really changed since the last
version other than bringing it up to date with the current livecd-tools
git tree.
Other than what I mentioned in the prior posts,
Douglas McClendon wrote:
Here is another update to my devicemapper-snapshot based LiveOS
persistence implementation.
Actually... _here_ it is.
-dmc
diff -Naur livecd.200709260026/config/livecd-fedora-7-desktop.ks livecd.overlay/config/livecd-fedora-7-desktop.ks
--- livecd.200709260026/config
Jeremy Katz wrote:
On Fri, 2007-09-21 at 05:27 -0500, Douglas McClendon wrote:
This patch moves the /isolinux directory on the livecd to
/boot/isolinux, and the /syslinux directory on liveusb to /boot/syslinux.
I think that this will be make the livecd appear less intimidating to
new non
Alexandre Magaz Graça wrote:
En/na Douglas McClendon ha escrit:
This patch moves the /isolinux directory on the livecd to
/boot/isolinux, and the /syslinux directory on liveusb to /boot/syslinux.
I think that this will be make the livecd appear less intimidating to
new non-linux-guru users
rossini ro wrote:
I want to edit the .ks file and set homepage of firefox to www.google.com.
But I don't know how to.
So is there any suggestion?
For whatever reason, I believe in fedora this may be the config file you
want to change... (or at least understand)
The attached patch implements the solution recently discussed, to avoid
wasting 1.2M of ram during LiveOS sessions, during the non-install times
when the 1.2M of ram for the minimized filesystem overlay is not
actually needed.
This implementation involves putting osmin in its own squashfs, and
The attached patch moves the loop modprobe call in mayflower generated
init, to before the udevsettle call. Thus also removing the while-wait
loop that Jeremy wisely added to my dynamic loop device patch.
Theoretically, one could argue that the while-wait loop is still needed,
as the udevsettle
Jeremy recently committed a patch which changed the number of loop
devices created from 128 to 16. I don't know if there was some
measurable performance reason for this or not. I had always guessed
that the reason David chose such a large number originally was because
of the fact that unlike in
This patch introduces a global variable 'interactive' which is defined
as true if stdout of livecd-creator is attached to a tty. This global
is then used to add the -no-progress option to mksquashfs for
non-interactive sessions. Thus making logfiles created by redirecting
the output of
This patch increases the default size of the ram overlay from 512M to 1T.
I thought about adding an option in the same way as the prior
num_loopdevs option, but I don't think that controlling the overlay size
in this way is actually useful.
IMO the solution to controlling the ram overlay size,
Colin Walters wrote:
On 9/20/07, Douglas McClendon [EMAIL PROTECTED] wrote:
Another benefit is making the iso directory structure look nicer and
more intuitively understandable for someone looking at it under windows.
[...]
This also
would make the usb/iso directory structure look cleaner
Andrew Overholt wrote:
Hi,
For the past few days I've been unable to create a live image on my laptop.
Is there something wrong with my machine or with the way I'm invoking
livecd-creator? I'm on F7 i386 with some rawhide stuff.
$ sudo ../creator/livecd-creator --cache /tmp/fedoradevelcache
Jonathan Steffan wrote:
Jon Steer wrote:
I'd like to make the livecd create a little quieter and not have it print
out the block writing like below.
32539/32769 99%[===
]-
I can't seem to find where this is written? I added a quiet
This is the first in a series of patches that implements the livecd
filesystem layout changes I proposed in an RFC a couple days ago.
Please note, that I am not all that intent on pushing these on people if
they don't want them. But I'm intent enough that I felt like throwing a
working set
This patch makes the livecd filesystem layout match the layout that
currently gets put on liveusb via livecd-iso-to-disk. Namely,
/squashfs.img or /ext3fs.img
and /osmin.gz
get put under /LiveOS/
-dmc
diff -Naur livecd.1.remove_sysroot_from_iso/creator/isotostick.sh
This patch moves the /isolinux directory on the livecd to
/boot/isolinux, and the /syslinux directory on liveusb to /boot/syslinux.
I think that this will be make the livecd appear less intimidating to
new non-linux-guru users. Aesthetics.
Since I don't use ppc myself, I didn't attempt to
This patch prepends the fslabel that the user gives to livecd-creator,
to the filesystem image names on the livecd and liveusb.
This got a bit uglier than I had in mind at first, though possibly in a
way that has a beneficial side effect-
Currently in the liveusb case, instead of a CDLABEL
1 - 100 of 177 matches
Mail list logo
