F7 general question about livecd-creator and timezones
by Skunk Worx
My ks scripts have the timezone set to PDT (America/Los_Angeles).
Installation to a hard drive works as expected. PDT in startup and in
shells, etc.
Creating a livecd-creator iso with the same tz setting, then booting,
shows A/L_A in the /etc/sysconfig/clock file, as expected.
However the date is always EDT in the boot messages, shells, etc.
During startup I see :
(lvm)
Press I to enter interactive startup
Setting clock (utc) Mon Jun 4 00:12:59 EDT 2007
(udev)
I'm not clear on what is happening between lvm and udev in the Linux
startup sequence.
If someone could give me a hint about what to look for and where to look
for it I would appreciate the help.
---
John
14 years, 7 months
traceback when installing openssh-server
by Alexandre Magaz Graça
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
target.unmount()
File "/usr/bin/livecd-creator", line 503, in unmount
self.ayum.close()
File "/usr/lib/python2.5/site-packages/yum/__init__.py", line 92, in
close
self._repos.close()
File "/usr/lib/python2.5/site-packages/yum/repos.py", line 76, in close
repo.close()
File "/usr/lib/python2.5/site-packages/yum/yumRepo.py", line 257, in
close
self.sack.close()
File "/usr/lib/python2.5/site-packages/yum/sqlitesack.py", line 233,
in close
del self.pkgobjlist
AttributeError: pkgobjlist
I noticed that it only happened when the base group is installed. After
some tests, I discovered it was caused by the openssh-server package (ks
attached). It worked when I tested in another machine, but failed againg
after a system update which included yum (from 3.2.1-1.fc7 to 3.2.5-1.fc7).
Could someone give some hint about how to find out what is making it fail?
Thanks,
Àlex
lang ca_ES.UTF-8
keyboard es
timezone Europe/Madrid
auth --useshadow --enablemd5
xconfig --startxonboot
services --enabled=NetworkManager,dhcdbd --disabled=network
selinux --disabled
firewall --disabled
repo --name=fedora --baseurl=http://ftp.udl.es/pub/fedora/linux/releases/7/Everything/i386/os
%packages
openssh-server
@core
bash
kernel
passwd
chkconfig
rootfiles
16 years, 2 months
Trimming the size of LiveCD's
by Jeroen van Meeuwen
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Here's a thought:
1304 random packages will install 724 MB of data in /usr/share/doc
I'm sure there is /something/ to gain here. If every package on average
installs ~0.5 MB of docs... Would it worth figuring out what docs should
be on the LiveCD in the first place? I guess removing everything RPM
calls docs is too much, as this will include man-pages as well.
Any thoughts?
- --
Kind regards,
Jeroen van Meeuwen
- -kanarip
- --
http://www.kanarip.com/
RHCE, LPIC-2, MCP, CCNA
C6B0 7FB4 43E6 CDDA D258 F70B 28DE 9FDA 9342 BF08
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
iD8DBQFG19BDKN6f2pNCvwgRAhhaAJ9UCH9WetRBu6foxAgztqMvg3h6OwCeLZU5
LxWzG5TBxdQOAE3VGFp400w=
=YiuK
-----END PGP SIGNATURE-----
16 years, 2 months
selinux alerts and livecd doesn't boot
by Chitlesh GOORAH
Hello there,
i did a clean installation of the FEL F8T2 livecd.
then did the updates
then yum install livecd-tools (012)
I created a livecd like i used to do.
however during the installation of the packages for the livecd, there
are lots of selinux denial notification popped on the system tray.
it's nice to see the selinux notifier being integrated into the KDE desktop.
however, non of my 7 livecds I recreated was bootable.
during the build i can see restorecon /proc/1xxxx : permission denied.
I'm wondering if the livecd creation procedures have been changed
again that im unaware of or it's a bug.
see attachments.
chitlesh
--
http://clunixchit.blogspot.com
16 years, 2 months
udev selinux problem? "udevd_event selinux_setfilecon failed"
by Douglas McClendon
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 harmless) that look
vaguely like the following-
udevd_event selinux_setfilecon failed permission denied /dev/usbdev....
I googled for selinux_setfilecon and found basically nothing.
Do these keywords ring a bell to anyone?
the /dev/usbdev... means that I get the same error half a dozen times
(seems relative to how many usb devices are plugged in) with various
non-intuitive incarnations of that filename.
-dmc
16 years, 2 months
LIveCD/USB + Persistance
by Mike Dickson
I am interested getting a USB stick up and running w/ the F8T2 LIve
install plus adding persistence. Who is working on this and how can I
install it?
Done so far: I have F8 Developer T2 Live running on a Patriot 4 gig USB
stick. It works great but it would be really cool if I could open up
eclipse and edit my Java project and save it to the same stick.
Thanks,
MikeD
JBoss SA -- Seattle
16 years, 2 months
[PATCH 1/7] livecd filesystem layout cleanups -- remove /sysroot
by Douglas McClendon
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 of patches together, to at least scare people into voicing
approval or opposition. I would be perfectly content to file these
away, and possibly revisit them for F9. But, if people want them, I
certainly wouldn't mind seeing them applied sooner.
These have been tested on minimal spins under qemu.
VERY IMPORTANTLY: much of the code changes have to do with legacy
support in livecd-iso-to-disk and livecd-creator --base-on-iso, but I
have not tested these AT ALL. If people voice no opposition, and some
approval, then I will go to the trouble of testing those things. And in
that case, this submission is also an avenue for feedback.
Note, the --base-on-iso legacy support may be pointless, as if these
were adopted for F8, then there is no reason to allow an f8 version of
livecd-creator to run --base-on-iso against an F7 livecd.
Now on to the patches. I'll elaborate in individual emails. This first
patch, should probably be applied regardless of the rest. It simply
removes the apparently pointless /sysroot directory from the iso9660
filesystem. Please let me know if I'm wrong and this is somehow needed
by something.
6 more after this one...
-dmc
16 years, 2 months
[PATCH] overlay/persistence patch, updated, still development quality
by Douglas McClendon
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, the following new things
are relevant-
- code has not been put in to mimick the running-from-git-directory
feature that applies to mayflower. Thus the 3 files (findoverlay, and 2
.patch) files would need to be in /usr/lib/livecd-creator for it to work.
- ntfs support removed. I tested with vfat (also noticing that a mount
-t auto on a mkfs.msdos created filesystem results in vfat).
- Only livecd-fedora-7-desktop.ks has the necessary gross code to patch
/etc/rc.d/init.d/functions and halt.
- it is off by default, so the basic way to test would be-
git clone ...
cd livecd
patch -p1 < /tmp/downloaded_overlay.patch
cd creator
cp *.patch findoverlay /usr/lib/livecd-creator
./livecd-creator --config=../config/livecd-fedora-7-desktop.ks \
--fslabel=somelabel
qemu-img create testoverlay.img 4G
qemu -net none -m 384 -boot d -cdrom ./somelabel.iso \
-hdb ./testoverlay.img
under qemu:
fdisk /dev/sda, create a partition, give it a dos/vfat label (e.g. 6),
mkfs.msdos /dev/sda1
mkdir /mnt/test
mount /dev/sda1 /mnt/test
mkdir /mnt/test/LiveOS
dd if=/dev/zero of=/mnt/test/LiveOS/Persistence-somelabel- \
bs=1M count=256
# note trailing dash above, it matters.
umount /mnt/test
init 0 (or just ctrl-c qemu)
(DONE WITH INIT)
now invoke qemu again in the same way, but at isolinux boot, hit tab,
and add "overlay=auto" to the kernel boot arguments.
do some stuff
shut down cleanly
jump to (DONE WITH INIT) as often as desired... maybe things will
persist if no bugs were encountered...
Definitely much polishing and debugging yet to be done. But it does
seem to work (at least until you forget to - or are unable to - cleanly
shut down, at which point your persistence data may well become
corrupted beyond repair)
-dmc
16 years, 2 months
[PATCH 4/7] move syslinux and isolinux directories under /boot
by Douglas McClendon
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 also move the /ppc dir
to /boot/ppc on the ppc side. But I would recommend that as well if
possible.
-dmc
16 years, 2 months
[PATCH 7/7] prepend iso fslabel to fstype.img syntax
by Douglas McClendon
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 being passed on the
kernel-commandline, a uuid is passed instead. Thus as far as I could
see (and maybe I'm just tired), at that point the cdlabel is lost to the
liveusb.
What I did was have livecd-creator write out the fslabel to
/etc/LiveOS-release. And then I had mayflower read this when generating
the initramfs init, so that it would know where to look for the file.
I think /etc/LiveOS-release would also solve a problem recently brought
up by Andy (asmith11), as to how to determine in the %post of whether or
not you are in a livecd environment or not.
Anyway, there may be better methods that just didn't occur to me, but
this doesn't seem so bad to me.
food for thought, like the rest of these patches...
So, with all of these, the final cdrom filesystem layout, for the F7
livecd, would have looked like...
/boot/isolinux/(stuff that used to be in /isolinux)
/LiveOS/Fedora-7-Live-i386.squashfs.img
/LiveOS/Fedora-7-Live-i386.osmin.img
(note, no /sysroot)
and inside the squashfs.img, is only /LiveOS/Fedora-7-Live-i386.ext3.img
Maybe there should be another patch to rename the .osmin.img to
.mininst.img or something...
Again, I am not at all opposed to just shelving these for a few months,
and seeing if people are more interested in them for F9. But I like them...
-dmc
16 years, 2 months
