Live CD user
Hi, You might want to consider adding the GNUmed GNUmed project to the section 'who uses Debian Live' http://live.debian.net/manual/html/ch11s02.html The GNUmed project uses live-helper to create live-CD for their medical office software. the Debian-med team is considering using it but noone has found the time so far. Take care, -- Sebastian Hilbert Leipzig / Germany [www.gnumed.de] -> PGP welcome, HTML ->/dev/null -- To UNSUBSCRIBE, email to debian-live-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: Re: Problems generating a minimal iso
Thanks Daniel. I've just downloaded the latest iso release (20090131) and did the changes on the script. It worked fine until the following error: Warning: creating filesystem that does not conform to ISO-9660. Size of boot image is 4 sectors -> genisoimage: Error - boot image 'binary/isolinux.bin' has not an allowable size. Any clue? Thanks, -Igor
Live mount problem
All,
I'm having a problem mounting a partition during the 10adduser script
(live-bottom) execution. It just says "Invalid Argument". I've got a data
partition that has already has been formatted with an ext3 filesystem. In the
rest of the script it does the rest of the work relative to a root directory so
I made my calls the same. The script has:
if [ "${BOOTOPTION}" == "Yes" ]; then
mkdir /root/data
mount /dev/sda1 /root/data
fi
That's what gives me the invalid argument.
The whole point of what I'd like to do is have sort of a modular setup. I want
to be able to have a tarball of a bunch of apps and configs that the particular
kiosk will need, and the live cd will be setup expecting to untar the data and
link them etc. One of the things I'm trying to link is the /etc/shadow and
/etc/passwd. So in essence the end user will be give a cd with the live binary
stuff etc and a data tarball then on startup the scripts will mount the data
partition, soft link passwd and shadow (and some other stuff) in order to have
sort of persistence with the password changes. We don't want all the kiosks
having the same credentials.
So any help with the above problem would be great, and if anybody has tried and
succeeded (or failed) at linking the passwd and shadow files at boot time
please let me know what worked and doesn't work etc.
Thanks,
~ Scott
--
To UNSUBSCRIBE, email to debian-live-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
small addition to the manual
Hello, I've added some explanations I felt useful about Debian-live system, and some description about using grub on an ext2 usb key to boot a Debian-live system : feel free to use/fix it ... Fred. patch.20090202 Description: Binary data
Re: Live mount problem
Greetings,
On Mon, Feb 2, 2009 at 8:09 AM, swinginscott wrote:
> All,
>
> I'm having a problem mounting a partition during the 10adduser script
> (live-bottom) execution. It just says "Invalid Argument". I've got a data
> partition that has already has been formatted with an ext3 filesystem. In
> the rest of the script it does the rest of the work relative to a root
> directory so I made my calls the same. The script has:
> if [ "${BOOTOPTION}" == "Yes" ]; then
> mkdir /root/data
> mount /dev/sda1 /root/data
> fi
>
>
> That's what gives me the invalid argument.
> The whole point of what I'd like to do is have sort of a modular setup. I
> want to be able to have a tarball of a bunch of apps and configs that the
> particular kiosk will need, and the live cd will be setup expecting to untar
> the data and link them etc. One of the things I'm trying to link is the
> /etc/shadow and /etc/passwd. So in essence the end user will be give a cd
> with the live binary stuff etc and a data tarball then on startup the scripts
> will mount the data partition, soft link passwd and shadow (and some other
> stuff) in order to have sort of persistence with the password changes. We
> don't want all the kiosks having the same credentials.
> So any help with the above problem would be great, and if anybody has tried
> and succeeded (or failed) at linking the passwd and shadow files at boot time
> please let me know what worked and doesn't work etc.
I do something similar but not with persistence. I just have a custom
/etc/rc.local which tests for some stuff then runs my applications
setup needs. I have also done a proof of concept with boot param hook
and just hosted the scripts on my web site. So try moving your code to
boot param hook or if going to need offline boots, try having
/etc/rc.local test and call your custom script.
>
> Thanks,
Hope this helps.
> ~ Scott
>
>
>
>
>
> --
> To UNSUBSCRIBE, email to debian-live-requ...@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
>
>
--
To UNSUBSCRIBE, email to debian-live-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: Help needed for lenny live RC1
Daniel Baumann wrote: > there are a couple of small things needed to fix in order to release > lenny live RC1, and one big issue: the size of the cdimages needs to be > cut down to not more than 700MB. Well, I probably won't be able to help much, but I'll offer what I can. > I've uploaded current builds done with live-helper 1.0.3-1 by using > /usr/share/live-helper/examples/cron/images.sh, and the images are too big: Looking at the package lists, I see that Gnome is included into ALL FOUR desktop flavors (lxde and xfce include the gnome metapackage; kde doesn't, but almost all its depends are there nonetheless). I don't know how it happened, but clearly you don't want that. I assume that this is responsible for the huge increase in size (~300 MB) of the three non-Gnome desktop flavors since Beta2; by comparison, the Gnome flavor increased by less than 20 MB: debian-live-lenny-i386-gnome-desktop.iso : 737M --> 755M debian-live-lenny-i386-kde-desktop.iso : 707M --> 1.0G debian-live-lenny-i386-lxde-desktop.iso : 481M --> 763M debian-live-lenny-i386-xfce-desktop.iso : 509M --> 780M Thus I assume that, when that is fixed, lxde and xfce will easily fit. For gnome and kde, I renew my suggestion of excluding openoffice.org. The cumulative size of the openoffice.org* packages is more than 100 MB, that should be more than enough. I know you didn't like that suggestion, but please consider that a live-cd without openoffice.org is better than no live-cd. At least keep that as a last-resort plan if a better alternative doesn't show up. Anyway, if I find time and don't get lost in the dependency tree, I'll try to find other ways to cut 60 MB. Gerardo -- To UNSUBSCRIBE, email to debian-live-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
[patch] bug in lenny's lh_binary_iso
Hi all,
Here is a patch for /usr/bin/lh_binary_iso as distributed in lenny
(live-helper 1.0.2-4). Without this patch the iso generation fails
because of a badly constructed genisoimage command line if
$LH_DEBIAN_INSTALLER is not set to "live".
Thanks.
--
David
--- lh_binary_iso.orig 2009-02-02 20:28:07.0 +0100
+++ lh_binary_iso 2009-02-02 20:28:42.0 +0100
@@ -96,14 +96,6 @@
GENISOIMAGE_OPTIONS="${GENISOIMAGE_OPTIONS} -V \"${LH_ISO_VOLUME}\""
fi
-if In_list "stripped minimal" "${LH_PACKAGES_LISTS}"
-then
- if [ "${LH_DEBIAN_INSTALLER}" != "live" ]
- then
- GENISOIMAGE_OPTIONS="${GENISOIMAGE_OPTIONS} -m ${GENISOIMAGE_EXCLUDE}"
- fi
-fi
-
# Handle genisoimage architecture specific options
case "${LH_BOOTLOADER}" in
grub)
@@ -137,6 +129,14 @@
;;
esac
+if In_list "stripped minimal" "${LH_PACKAGES_LISTS}"
+then
+ if [ "${LH_DEBIAN_INSTALLER}" != "live" ]
+ then
+ GENISOIMAGE_OPTIONS="${GENISOIMAGE_OPTIONS} -m ${GENISOIMAGE_EXCLUDE}"
+ fi
+fi
+
cat > binary.sh << EOF
genisoimage ${GENISOIMAGE_OPTIONS} -o binary.iso binary
EOF
[patch] bug in lenny's lh_binary_iso
Hi all,
Here is a patch for /usr/bin/lh_binary_iso as distributed in lenny
(live-helper 1.0.2-4). Without this patch the iso generation fails
because of a badly constructed genisoimage command line if
$LH_DEBIAN_INSTALLER is not set to "live".
Thanks.
--
David
--- lh_binary_iso.orig 2009-02-02 20:28:07.0 +0100
+++ lh_binary_iso 2009-02-02 20:28:42.0 +0100
@@ -96,14 +96,6 @@
GENISOIMAGE_OPTIONS="${GENISOIMAGE_OPTIONS} -V \"${LH_ISO_VOLUME}\""
fi
-if In_list "stripped minimal" "${LH_PACKAGES_LISTS}"
-then
- if [ "${LH_DEBIAN_INSTALLER}" != "live" ]
- then
- GENISOIMAGE_OPTIONS="${GENISOIMAGE_OPTIONS} -m ${GENISOIMAGE_EXCLUDE}"
- fi
-fi
-
# Handle genisoimage architecture specific options
case "${LH_BOOTLOADER}" in
grub)
@@ -137,6 +129,14 @@
;;
esac
+if In_list "stripped minimal" "${LH_PACKAGES_LISTS}"
+then
+ if [ "${LH_DEBIAN_INSTALLER}" != "live" ]
+ then
+ GENISOIMAGE_OPTIONS="${GENISOIMAGE_OPTIONS} -m ${GENISOIMAGE_EXCLUDE}"
+ fi
+fi
+
cat > binary.sh << EOF
genisoimage ${GENISOIMAGE_OPTIONS} -o binary.iso binary
EOF
