imgcreate/live.py
by Brian C. Lane
imgcreate/live.py | 8 +-------
1 file changed, 1 insertion(+), 7 deletions(-)
New commits:
commit 5aa45aed7d9341749bbb68a41722661de881a8a5
Author: Brian C. Lane <bcl(a)redhat.com>
Date: Thu Mar 28 16:26:37 2013 -0700
Properly generate kernel stanzas (#928093)
diff --git a/imgcreate/live.py b/imgcreate/live.py
index 11fa7fc..4fe1ea4 100755
--- a/imgcreate/live.py
+++ b/imgcreate/live.py
@@ -556,14 +556,8 @@ menu separator
return template % args
def __get_image_stanzas(self, isodir):
- versions = []
kernels = self._get_kernel_versions()
- for kernel in kernels:
- for version in kernels[kernel]:
- versions.append(version)
-
kernel_options = self._get_kernel_options()
-
checkisomd5 = self._has_checkisomd5()
# Stanzas for insertion into the config template
@@ -572,7 +566,7 @@ menu separator
check = []
index = "0"
- for version in versions:
+ for kernel, version in ((k,v) for k in kernels for v in kernels[k]):
(is_xen, isDracut) = self.__copy_kernel_and_initramfs(isodir, version, index)
if index == "0":
self._isDracut = isDracut
11 years, 1 month
[PATCH 2/2] Correct & update livecd-iso-to-disk.sh usage statements
by Frederick Grose
commit f7211d501d7b8c81946c2cb685d8ee61a1c40ada
Author: Frederick Grose <fgrose(a)sugarlabs.org>
Date: Tue Mar 19 18:44:37 2013 -0400
Correct misleading information on the overlay, syncronize usage
statements with documentation in livecd-iso-to-disk.pod
diff --git a/tools/livecd-iso-to-disk.sh b/tools/livecd-iso-to-disk.sh
index 1a87869..8a4caa0 100755
--- a/tools/livecd-iso-to-disk.sh
+++ b/tools/livecd-iso-to-disk.sh
@@ -55,8 +55,8 @@ usage() {
such as from a CD-ROM, DVD, or download. It could also
be the
device node reference for the mount point of another
LiveOS
filesystem, including the currently-running one (such as a
- booted Live CD/DVD/USB, where /dev/live references the
running
- image device).
+ booted Live CD/DVD/USB, where /run/initramfs/livedev
+ references the booted device).
<target device>
This should be the device partition name for the attached,
@@ -81,8 +81,8 @@ usage() {
running LiveOS image, the device node reference for an attached device
with
an installed LiveOS image, or a file backed by a block device with an
installed LiveOS image. If the operating system supports persistent
- overlays for saving system changes, a pre-sized overlay may be
included with
- the installation.
+ overlays for saving system changes, a pre-sized overlay may be
specified
+ for creation during the installation.
Unless you request the --format option, the installation does not
destroy
data outside of the LiveOS, syslinux, & EFI folders on your target
device.
@@ -92,21 +92,34 @@ usage() {
LiveOS images provide embedded filesystems through the Device-mapper
component of the Linux kernel. The embedded filesystems exist within
files
such as /LiveOS/squashfs.img (the default compressed storage) or
- /LiveOS/ext3fs.img (an uncompressed version) on the primary volume
partition
- of the storage device. In use, these are read-only filesystems.
Optionally,
- one may specify a persistent LiveOS overlay to hold image-change
snapshots
- (that use write-once, difference-tracking storage) in the
- /LiveOS/overlay-<device_id> file, which, *one should note*, always
grows in
- size due to the storage mechanism. (The fraction of allocated space
that
- has been consumed by system activity and changes may be displayed by
issuing
- the 'dmsetup status' command in a terminal session of a running LiveOS
- image.) One way to conserve the unrecoverable, overlay file space, is
to
- specify a persistent home folder for user files, which will be saved
in a
- /LiveOS/home.img filesystem image file. This file space is encrypted
by
- default, but is not compressed. (One may bypass encryption with the
- --unencrypted-home installation option.) Files in this home folder
may be
- erased to recover and reuse their storage space. The home.img file is
also
- convenient for backing up or swapping user account files.
+ /LiveOS/ext3fs.img (an uncompressed version) on the primary volume
+ partition of the storage device. In use, these are read-only
filesystems.
+ On boot, a temporary, read-write root filesystem overlay is provided.
+ Optionally, one may specify a fixed-sized, persistent overlay storage
pool
+ in a /LiveOS/overlay-<device_id> file, which will hold root filesystem
+ changes via allocate-once, copy-on-write storage.
+
+ Should the overlay storage space, whether temporary or persistent, be
+ totally consumed, the filesystem will be flagged 'Invalid' and, if that
+ filesystem is the booted root filesystem, it will crash with
Input/output
+ or Bus errors. If such a crash occurs while using temporary storage
space
+ for the overlay, a simple reboot will rectify the situation. With
+ persistent storage, the situation is more dire and will require
appending
+ 'rd.live.overlay.reset' to the kernel command line on boot-up. This
will
+ reset the storage overlay to its initial, unused state (all changes are
+ lost).
+
+ One may check the number of allocated sectors of the total overlay
storage
+ by issuing the 'dmsetup status' command in a terminal session of a
running
+ LiveOS image. *One should note* though, the number of allocated
sectors in
+ the overlay always grows, even though the apparent size of the virtual
root
+ filesystem may go up and down. One way to conserve the overlay file
space,
+ is to specify persistent home folder storage for user files, which
will be
+ saved in a /LiveOS/home.img filesystem image file. This file space is
+ encrypted by default, but is not compressed. (One may bypass
encryption
+ with the --unencrypted-home installation option.) Files in this home
+ folder may be erased to reuse their storage space. The home.img file
is
+ also convenient for backing up or swapping user account files.
OPTIONS
@@ -120,11 +133,12 @@ usage() {
storage device.
--format
- Formats the target device and creates an MS-DOS partition table
(or GPT
- partition table, if the --efi option is passed).
+ Creates an MS-DOS partition table (or GPT partition table, if the
--efi
+ option is passed) and formats an ext4 filesystem on the target
device.
--msdos
- Forces format to use msdos instead of ext4.
+ Forces format to make an fat32 file system instead of an ext4
formatted
+ one.
--reset-mbr
Sets the Master Boot Record (MBR) of the target storage device to
the
@@ -183,7 +197,6 @@ usage() {
Used when installing multiple image copies to signal configuration
of
the boot files for the image in the --livedir <dir> parameter.
-
--livedir <dir>
Used with multiple image installations to designate the directory
<dir>
for the particular image.
@@ -199,50 +212,47 @@ usage() {
--swap-size-mb <size>
Sets up a swap file of <size> mebibytes (integer values only) on
the
- target device.
+ target device. A maximum <size> of 2047 MiB is permitted for
+ vfat-formatted devices.
--overlay-size-mb <size>
This option sets the overlay size in mebibytes (integer values
only).
- The overlay makes persistent storage available to the live
operating
- system, if the operating system supports it. The persistent LiveOS
- overlay holds image-change snapshots (using write-once, difference-
- tracking storage) in the /LiveOS/overlay-<device_id> file, which,
*one
- should note*, always grows in size due to the storage mechanism.
(The
- fraction of allocated space that has been consumed may be
displayed by
- issuing the 'dmsetup status' command in a terminal session of a
running
- LiveOS installation.) One way to conserve the unrecoverable,
overlay
- file space, is to specify a persistent home folder for user files,
see
- --home-size-mb below. The target storage device must have enough
free
- space for the image and the overlay. A maximum <size> of 2047 MiB
is
- permitted for vfat-formatted devices. If there is insufficient
room on
- your device, you will be given information to help in adjusting
your
- settings.
+ The overlay is a fixed-sized, persistent storage pool of sectors
in a
+ /LiveOS/overlay-<device_id> file, which will hold root filesystem
+ changes via allocate-once, copy-on-write storage. (See the
Description
+ section above for some important limitations of this storage.)
One way
+ to conserve the limited, overlay file space, is to specify a
persistent
+ home folder for user files, see --home-size-mb below. The target
+ storage device must have enough free space for the image and the
+ overlay. A maximum <size> of 2047 MiB is permitted for
vfat-formatted
+ devices. If there is insufficient room on your device, you will be
+ given information to help in adjusting your settings.
--home-size-mb <size>
Sets the home directory size in mebibytes (integer values only). A
persistent home directory will be made in the /LiveOS/home.img
- filesystem image file. This file space is encrypted by default,
but not
- compressed (one may bypass encryption with the --unencrypted-home
- installation option). Files in this home folder may be erased to
- recover and reuse their storage space. The target storage device
must
- have enough free space for the image, any overlay, and the home
- directory. Note that the --delete-home option must also be
selected to
- replace an existing persistent home with a new, empty one. A
maximum
- <size> of 2047 MiB is permitted for vfat-formatted devices. If
there is
- insufficient room on your device, you will be given information to
help
- in adjusting your settings.
+ filesystem image file. This file space is encrypted by default,
but
+ not compressed (one may bypass encryption with the
--unencrypted-home
+ installation option). Files in this home folder may be erased to
reuse
+ their storage space. The target storage device must have enough
free
+ space for the image, any overlay, and the home directory. Note
that
+ the --delete-home option must also be selected to replace an
existing
+ persistent home with a new, empty one. A maximum <size> of 2047
MiB is
+ permitted for vfat-formatted devices. If there is insufficient
room on
+ your device, you will be given information to help in adjusting
your
+ settings.
--delete-home
To prevent unwitting deletion of user files, this option must be
explicitly selected when the option --home-size-mb <size> is
selected
- and there is an existing persistent home directory on the target
device.
+ and an existing persistent home filesystem is on the target device.
--crypted-home (default that only applies to new home-size-mb
requests)
- Specifies the default option to encrypt a new persistent home
directory
- if --home-size-mb <size> is specified.
+ Specifies the default option to encrypt a new persistent home
+ filesystem if --home-size-mb <size> is specified.
--unencrypted-home
- Prevents the default option to encrypt a new persistent home
directory.
+ Prevents the default encryption of a new persistent home
filesystem.
CONTRIBUTORS
11 years, 1 month
[PATCH 1/2] Correct & update livecd-iso-to-disk.pod documentation
by Frederick Grose
commit d219ec73c631f31d3197e19b03212611ab90f615
Author: Frederick Grose <fgrose(a)sugarlabs.org>
Date: Tue Mar 19 18:24:12 2013 -0400
Correct misleading information on the overlay, update options,
syncronize
with usage info embedded in livecd-iso-to-disk.sh
diff --git a/docs/livecd-iso-to-disk.pod b/docs/livecd-iso-to-disk.pod
index 7ef0c14..16ebdea 100644
--- a/docs/livecd-iso-to-disk.pod
+++ b/docs/livecd-iso-to-disk.pod
@@ -6,7 +6,7 @@ livecd-iso-to-disk - installs bootable Live images onto
USB/SD storage devices.
=head1 SYNOPSIS
-B<livecd-iso-to-disk> [--help] [--noverify] [--format] [--reset-mbr]
[--efi] [--skipcopy] [--force] [--xo] [--xo-no-home] [--timeout <time>]
[--totaltimeout <time>] [--extra-kernel-args <args>] [--multi] [--livedir
<dir>] [--compress] [--skipcompress] [--swap-size-mb <size>]
[--overlay-size-mb <size>] [--home-size-mb <size>] [--delete-home]
[--crypted-home] [--unencrypted-home] <source> <target device>
+B<livecd-iso-to-disk> [--help] [--noverify] [--format] [--msdos]
[--reset-mbr] [--efi] [--skipcopy] [--force] [--xo] [--xo-no-home]
[--timeout <time>] [--totaltimeout <time>] [--extra-kernel-args <args>]
[--multi] [--livedir <dir>] [--compress] [--skipcompress] [--swap-size-mb
<size>] [--overlay-size-mb <size>] [--home-size-mb <size>] [--delete-home]
[--crypted-home] [--unencrypted-home] <source> <target device>
Simplest
@@ -20,7 +20,7 @@ To execute the script to completion, you will need to run
it with root user perm
=item <source>
-This may be the filesystem path to a LiveOS .iso image file, such as from
a CD-ROM, DVD, or download. It could also be the device node reference for
the mount point of another LiveOS filesystem, including the
currently-running one (such as a booted Live CD/DVD/USB, where /dev/live
references the running image device).
+This may be the filesystem path to a LiveOS .iso image file, such as from
a CD-ROM, DVD, or download. It could also be the device node reference for
the mount point of another LiveOS filesystem, including the
currently-running one (such as a booted Live CD/DVD/USB, where
/run/initramfs/livedev references the booted device).
=item <target device>
@@ -30,11 +30,15 @@ This should be the device partition name for the
attached, target device, such a
=head1 DESCRIPTION
-B<livecd-iso-to-disk> installs a Live CD/DVD/USB image (LiveOS) onto a
USB/SD storage device (or any storage partition that will boot with a
SYSLINUX bootloader). The target storage device can then boot the
installed operating system on systems that support booting via the USB or
the SD interface. The script requires a LiveOS source image and a target
storage device. The source image may be either a LiveOS .iso file, the
currently-running LiveOS image, the device node reference for an attached
device with an installed LiveOS image, or a file backed by a block device
with an installed LiveOS image. If the operating system supports
persistent overlays for saving system changes, a pre-sized overlay may be
included with the installation.
+B<livecd-iso-to-disk> installs a Live CD/DVD/USB image (LiveOS) onto a
USB/SD storage device (or any storage partition that will boot with a
SYSLINUX bootloader). The target storage device can then boot the
installed operating system on systems that support booting via the USB or
the SD interface. The script requires a LiveOS source image and a target
storage device. The source image may be either a LiveOS .iso file, the
currently-running LiveOS image, the device node reference for an attached
device with an installed LiveOS image, or a file backed by a block device
with an installed LiveOS image. If the operating system supports
persistent overlays for saving system changes, a pre-sized overlay may be
specified for creation during the installation.
Unless you request the --format option, the installation does not destroy
data outside of the LiveOS, syslinux, & EFI folders on your target device.
This allows one to maintain other files on the target disk outside of the
LiveOS filesystem.
-LiveOS images provide embedded filesystems through the Device-mapper
component of the Linux kernel. The embedded filesystems exist within files
such as /LiveOS/squashfs.img (the default compressed storage) or
/LiveOS/ext3fs.img (an uncompressed version) on the primary volume
partition of the storage device. In use, these are read-only filesystems.
Optionally, one may specify a persistent LiveOS overlay to hold
image-change snapshots (that use write-once, difference-tracking storage)
in the /LiveOS/overlay-<device_id> file, which, *one should note*, always
grows in size due to the storage mechanism. (The fraction of allocated
space that has been consumed by system activity and changes may be
displayed by issuing the 'dmsetup status' command in a terminal session of
a running LiveOS image.) One way to conserve the unrecoverable, overlay
file space, is to specify a persistent home folder for user files, which
will be saved in a /LiveOS/home.img filesystem image file. This file space
is encrypted by default, but is not compressed. (One may bypass encryption
with the --unencrypted-home installation option.) Files in this home
folder may be erased to recover and reuse their storage space. The
home.img file is also convenient for backing up or swapping user account
files.
+LiveOS images provide embedded filesystems through the Device-mapper
component of the Linux kernel. The embedded filesystems exist within files
such as /LiveOS/squashfs.img (the default compressed storage) or
/LiveOS/ext3fs.img (an uncompressed version) on the primary volume
partition of the storage device. In use, these are read-only filesystems.
On boot, a temporary, read-write root filesystem overlay is provided.
Optionally, one may specify a fixed-sized, persistent overlay storage pool
in a /LiveOS/overlay-<device_id> file, which will hold root filesystem
changes via allocate-once, copy-on-write storage.
+
+Should the overlay storage space, whether temporary or persistent, be
totally consumed, the filesystem will be flagged 'Invalid' and, if that
filesystem is the booted root filesystem, it will crash with Input/output
or Bus errors. If such a crash occurs while using temporary storage space
for the overlay, a simple reboot will rectify the situation. With
persistent storage, the situation is more dire and will require appending
'rd.live.overlay.reset' to the kernel command line on boot-up. This will
reset the storage overlay to its initial, unused state (all changes are
lost).
+
+One may check the number of allocated sectors of the total overlay storage
by issuing the 'dmsetup status' command in a terminal session of a running
LiveOS image. *One should note* though, the number of allocated sectors in
the overlay always grows, even though the apparent size of the virtual root
filesystem may go up and down. One way to conserve the overlay file space,
is to specify persistent home folder storage for user files, which will be
saved in a /LiveOS/home.img filesystem image file. This file space is
encrypted by default, but is not compressed. (One may bypass encryption
with the --unencrypted-home installation option.) Files in this home
folder may be erased to reuse their storage space. The home.img file is
also convenient for backing up or swapping user account files.
=head1 OPTIONS
@@ -50,7 +54,11 @@ Disables the image validation process that occurs before
the image is installed
=item --format
-Formats the target device and creates an MS-DOS partition table (or GUID
partition table, if the --efi option is passed).
+Creates an MS-DOS partition table (or GPT partition table, if the --efi
option is passed) and formats an ext4 filesystem on the target device.
+
+=item --msdos
+
+Forces format to make an fat32 file system instead of an ext4 formatted
one.
=item --reset-mbr
@@ -104,8 +112,7 @@ Used with multiple image installations to designate the
directory <dir> for the
=item --compress (default state for the operating system files)
-The default, compressed SquashFS filesystem image is copied on
installation. This option has no effect when the source filesystem
-is already expanded.
+The default, compressed SquashFS filesystem image is copied on
installation. This option has no effect when the source filesystem is
already expanded.
=item --skipcompress (default option when --xo is specified)
@@ -113,27 +120,27 @@ Expands the source SquashFS image on installation
into the read-only /LiveOS/ext
=item --swap-size-mb <size>
-Sets up a swap file of <size> mebibytes (integer values only) on the
target device.
+Sets up a swap file of <size> mebibytes (integer values only) on the
target device. A maximum <size> of 2047 MiB is permitted for
vfat-formatted devices.
=item --overlay-size-mb <size>
-This option sets the overlay size in mebibytes (integer values only). The
overlay makes persistent storage available to the live operating system, if
the operating system supports it. The persistent LiveOS overlay holds
image-change snapshots (using write-once, difference-tracking storage) in
the /LiveOS/overlay-<device_id> file, which, *one should note*, always
grows in size due to the storage mechanism. (The fraction of allocated
space that has been consumed may be displayed by issuing the 'dmsetup
status' command in a terminal session of a running LiveOS installation.)
One way to conserve the unrecoverable, overlay file space, is to specify a
persistent home folder for user files, see --home-size-mb below. The
target storage device must have enough free space for the image and the
overlay. A maximum <size> of 2047 MiB is permitted for vfat-formatted
devices. If there is insufficient room on your device, you will be given
information to help in adjusting your settings.
+This option sets the overlay size in mebibytes (integer values only). The
overlay is a fixed-sized, persistent storage pool of sectors in a
/LiveOS/overlay-<device_id> file, which will hold root filesystem changes
via allocate-once, copy-on-write storage. (See the Description section
above for some important limitations of this storage.) One way to conserve
the limited, overlay file space, is to specify a persistent home folder for
user files, see --home-size-mb below. The target storage device must have
enough free space for the image and the overlay. A maximum <size> of 2047
MiB is permitted for vfat-formatted devices. If there is insufficient room
on your device, you will be given information to help in adjusting your
settings.
=item --home-size-mb <size>
-Sets the home directory size in mebibytes (integer values only). A
persistent home directory will be made in the /LiveOS/home.img filesystem
image file. This file space is encrypted by default, but not compressed
(one may bypass encryption with the --unencrypted-home installation
option). Files in this home folder may be erased to recover and reuse
their storage space. The target storage device must have enough free space
for the image, any overlay, and the home directory. Note that the
--delete-home option must also be selected to replace an existing
persistent home with a new, empty one. A maximum <size> of 2047 MiB is
permitted for vfat-formatted devices. If there is insufficient room on
your device, you will be given information to help in adjusting your
settings.
+Sets the home directory size in mebibytes (integer values only). A
persistent home directory will be made in the /LiveOS/home.img filesystem
image file. This file space is encrypted by default, but not compressed
(one may bypass encryption with the --unencrypted-home installation
option). Files in this home folder may be erased to reuse their storage
space. The target storage device must have enough free space for the
image, any overlay, and the home directory. Note that the --delete-home
option must also be selected to replace an existing persistent home with a
new, empty one. A maximum <size> of 2047 MiB is permitted for
vfat-formatted devices. If there is insufficient room on your device, you
will be given information to help in adjusting your settings.
=item --delete-home
-To prevent unwitting deletion of user files, this option must be
explicitly selected when the option --home-size-mb <size> is selected and
there is an existing persistent home directory on the target device.
+To prevent unwitting deletion of user files, this option must be
explicitly selected when the option --home-size-mb <size> is selected and
there is an existing persistent home filesystem on the target device.
=item --crypted-home (default that only applies to new home-size-mb
requests)
-Specifies the default option to encrypt a new persistent home directory if
--home-size-mb <size> is specified.
+Specifies the default option to encrypt a new persistent home filesystem
if --home-size-mb <size> is specified.
=item --unencrypted-home
-Prevents the default option to encrypt a new persistent home directory.
+Prevents the default encryption of a new persistent home filesystem.
=back
11 years, 1 month
3 commits - imgcreate/live.py Makefile
by Brian C. Lane
Makefile | 2 +-
imgcreate/live.py | 8 +++++---
2 files changed, 6 insertions(+), 4 deletions(-)
New commits:
commit 7342c11b485863dcbf747ec3c99cc6b04585191b
Author: Brian C. Lane <bcl(a)redhat.com>
Date: Sat Mar 16 07:33:32 2013 -0700
Version 19.1
diff --git a/Makefile b/Makefile
index a587956..33a6e43 100644
--- a/Makefile
+++ b/Makefile
@@ -1,5 +1,5 @@
-VERSION = 19.0
+VERSION = 19.1
INSTALL = /usr/bin/install -c
INSTALL_PROGRAM = ${INSTALL}
commit 9f782637b32a3786cfd8d56dbc9a27c50f38b4dd
Author: Brian C. Lane <bcl(a)redhat.com>
Date: Thu Mar 14 11:41:46 2013 -0700
iso9660 module is names isofs
diff --git a/imgcreate/live.py b/imgcreate/live.py
index cbf59f1..11fa7fc 100755
--- a/imgcreate/live.py
+++ b/imgcreate/live.py
@@ -262,10 +262,10 @@ class LiveImageCreatorBase(LoopImageCreator):
return env
def __extra_filesystems(self):
- return "vfat msdos ";
+ return "vfat msdos isofs ";
def __extra_drivers(self):
- retval = "sr_mod sd_mod ide-cd cdrom iso9660 "
+ retval = "sr_mod sd_mod ide-cd cdrom "
for module in self.__modules:
if module == "=usb":
retval = retval + "ehci_hcd uhci_hcd ohci_hcd "
commit 3371ebd19c590feb26860dc6d8c19d6622d9c815
Author: Brian C. Lane <bcl(a)redhat.com>
Date: Thu Mar 14 11:39:36 2013 -0700
disable dracut hostonly and rescue image (#921422)
diff --git a/imgcreate/live.py b/imgcreate/live.py
index dbb4dbb..cbf59f1 100755
--- a/imgcreate/live.py
+++ b/imgcreate/live.py
@@ -305,7 +305,9 @@ class LiveImageCreatorBase(LoopImageCreator):
f = open(path, "a")
f.write('filesystems+="' + self.__extra_filesystems() + ' "\n')
f.write('drivers+="' + self.__extra_drivers() + ' "\n')
- f.write('add_dracutmodules+=" dmsquash-live pollcdrom "')
+ f.write('add_dracutmodules+=" dmsquash-live pollcdrom "\n')
+ f.write('hostonly="no"\n')
+ f.write('dracut_rescue_image="no"\n')
f.close()
def __create_iso(self, isodir):
11 years, 1 month
Can't echo to console from dracut module
by John.Florian＠dart.biz
I have a custom dracut module installed as a pre-mount hook (for Fedora
18). This shell script needs to echo some messages to the console, but
I'm having no luck making that happen. I've tried:
echo foo
echo foo > /dev/console
echo foo > /dev/kmsg
. /lib/dracut-lib.sh
info foo
. /lib/dracut-lib.sh
export DRACUT_QUIET="no"
/bin/plymouth --hide-splash
info foo
At various times, I've tried booting with rd.info=1, but my final solution
needs to not require that. All of these things work as expected from the
emergency_shell (reached by passing rd.break on the cmd-line). I've
looked at that function and haven't seen what I'm missing. I'm starting
to suspect the shell works because of the special setup in the
dracut-emergency.service systemd unit, but haven't yet tried retooling
things so that my hook scripts becomes not much more than a 'systemctl
start mycustom.service', which in turn minics dracut-emergency.service but
instead of a user shell, calls another shell script with the bulk of
what's presenty in my hook script.
Is there a simpler way or anybody know what I'm doing wrong or need to do
differently? Given that I'm doing this all in a LiveOS image, my
turn-around time for testing is rather slow and tedious.
--
John Florian
11 years, 1 month
"Input/output error" and/or "Bus error" for most commands
by John.Florian＠dart.biz
I have an easy to reproduce problem I'm experiencing with a Live image
generated from Fedora 18 bases. If too much gets written to the writable
tmpfs overlay, the host goes all wonky in that most all commands will fail
to run and immediately return one of the above error messages. For
example:
root@aos-61:46 # cat /proc/meminfo
MemTotal: 995020 kB
MemFree: 199348 kB
Buffers: 91192 kB
Cached: 637920 kB
SwapCached: 0 kB
Active: 221796 kB
Inactive: 549340 kB
Active(anon): 43120 kB
Inactive(anon): 3220 kB
Active(file): 178676 kB
Inactive(file): 546120 kB
Unevictable: 0 kB
Mlocked: 0 kB
HighTotal: 110344 kB
HighFree: 220 kB
LowTotal: 884676 kB
LowFree: 199128 kB
SwapTotal: 0 kB
SwapFree: 0 kB
Dirty: 0 kB
Writeback: 0 kB
AnonPages: 42036 kB
Mapped: 21392 kB
Shmem: 4324 kB
Slab: 16696 kB
SReclaimable: 11736 kB
SUnreclaim: 4960 kB
KernelStack: 584 kB
PageTables: 612 kB
NFS_Unstable: 0 kB
Bounce: 0 kB
WritebackTmp: 0 kB
CommitLimit: 497508 kB
Committed_AS: 92280 kB
VmallocTotal: 122880 kB
VmallocUsed: 35324 kB
VmallocChunk: 87296 kB
HardwareCorrupted: 0 kB
HugePages_Total: 0
HugePages_Free: 0
HugePages_Rsvd: 0
HugePages_Surp: 0
Hugepagesize: 4096 kB
DirectMap4k: 12280 kB
DirectMap4M: 892928 kB
root@aos-61:46 # df -h
Filesystem Size Used Avail Use% Mounted on
devtmpfs 481M 0 481M 0% /dev
tmpfs 486M 0 486M 0% /dev/shm
tmpfs 486M 296K 486M 1% /run
tmpfs 486M 0 486M 0% /sys/fs/cgroup
/dev/sda1 7.4G 1.2G 5.9G 17% /run/initramfs/live
/dev/mapper/live-rw 2.0G 1.3G 658M 67% /
tmpfs 486M 1.5M 485M 1% /tmp
root@aos-61:46 # mount
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
devtmpfs on /dev type devtmpfs
(rw,nosuid,size=492160k,nr_inodes=123040,mode=755)
securityfs on /sys/kernel/security type securityfs
(rw,nosuid,nodev,noexec,relatime)
tmpfs on /dev/shm type tmpfs (rw,relatime)
devpts on /dev/pts type devpts (rw,relatime,gid=5,mode=620,ptmxmode=000)
tmpfs on /run type tmpfs (rw,nosuid,nodev,mode=755)
tmpfs on /sys/fs/cgroup type tmpfs (rw,nosuid,nodev,noexec,mode=755)
cgroup on /sys/fs/cgroup/systemd type cgroup
(rw,nosuid,nodev,noexec,relatime,release_agent=/usr/lib/systemd/systemd-cgroups-agent,name=systemd)
cgroup on /sys/fs/cgroup/cpuset type cgroup
(rw,nosuid,nodev,noexec,relatime,cpuset)
cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup
(rw,nosuid,nodev,noexec,relatime,cpuacct,cpu)
cgroup on /sys/fs/cgroup/memory type cgroup
(rw,nosuid,nodev,noexec,relatime,memory)
cgroup on /sys/fs/cgroup/devices type cgroup
(rw,nosuid,nodev,noexec,relatime,devices)
cgroup on /sys/fs/cgroup/freezer type cgroup
(rw,nosuid,nodev,noexec,relatime,freezer)
cgroup on /sys/fs/cgroup/net_cls type cgroup
(rw,nosuid,nodev,noexec,relatime,net_cls)
cgroup on /sys/fs/cgroup/blkio type cgroup
(rw,nosuid,nodev,noexec,relatime,blkio)
cgroup on /sys/fs/cgroup/perf_event type cgroup
(rw,nosuid,nodev,noexec,relatime,perf_event)
/dev/sda1 on /run/initramfs/live type ext3 (ro,relatime)
/dev/mapper/live-rw on / type ext3 (rw,noatime,data=ordered)
systemd-1 on /proc/sys/fs/binfmt_misc type autofs
(rw,relatime,fd=29,pgrp=1,timeout=300,minproto=5,maxproto=5,direct)
mqueue on /dev/mqueue type mqueue (rw,relatime)
debugfs on /sys/kernel/debug type debugfs (rw,relatime)
tmpfs on /tmp type tmpfs (rw)
hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime)
configfs on /sys/kernel/config type configfs (rw,relatime)
none on /var/lib/stateless/writable type tmpfs (rw,relatime)
none on /var/cache/man type tmpfs (rw,relatime)
none on /var/lib/xkb type tmpfs (rw,relatime)
none on /var/log type tmpfs (rw,relatime)
none on /var/lib/dbus type tmpfs (rw,relatime)
none on /var/lib/nfs type tmpfs (rw,relatime)
none on /tmp type tmpfs (rw,relatime)
none on /var/lib/dhclient type tmpfs (rw,relatime)
none on /var/tmp type tmpfs (rw,relatime)
none on /var/lib/logrotate.status type tmpfs (rw,relatime)
none on /var/lib/random-seed type tmpfs (rw,relatime)
none on /var/spool type tmpfs (rw,relatime)
/dev/sda1 on /mnt/live type ext3 (rw,noatime)
root@aos-61:46 #
root@aos-61:46 #
root@aos-61:46 # # Lets now make it all go wonky:
root@aos-61:46 # time dd if=/dev/zero of=/foo
Bus error
real 1m15.775s
user 0m2.818s
sys 0m24.129s
root@aos-61:46 #
root@aos-61:46 # ls /root
-bash: /bin/ls: Input/output error
root@aos-61:46 # df -h
-bash: /usr/bin/df: Input/output error
root@aos-61:46 # mount
-bash: /usr/bin/mount: Input/output error
root@aos-61:46 # cat /proc/meminfo
-bash: /usr/bin/cat: Input/output error
Is this expected? Is there anything I can do, e.g., configuration-wise,
that can prevent this? Ideally this would fail much like any other full
disk situation. I understand that the overlay consumes space, i.e.,
memory, for this file growth, including file removals, but I'd at least
like to be able to remotely reboot a system when in this state, however I
can't even do that because the reboot command will either return the same
I/O error or it may succeed but get the I/O error when systemd tries to
read /usr/lib/systemd/system/reboot.target.
I dug around in bugzilla, but found nothing there. I can file a bug, but
which package is likely at fault here?
--
John Florian
11 years, 1 month
Makefile
by Brian C. Lane
Makefile | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
New commits:
commit 8b4ad39a3631eede928f10d4957a4d7ac8d4f7be
Author: Brian C. Lane <bcl(a)redhat.com>
Date: Fri Mar 8 10:02:59 2013 -0800
Version 19.0
diff --git a/Makefile b/Makefile
index ab3768b..a587956 100644
--- a/Makefile
+++ b/Makefile
@@ -1,5 +1,5 @@
-VERSION = 18.14
+VERSION = 19.0
INSTALL = /usr/bin/install -c
INSTALL_PROGRAM = ${INSTALL}
11 years, 1 month
imgcreate/live.py
by Brian C. Lane
imgcreate/live.py | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
New commits:
commit aa858efd7514da6687f0caccad7df13a2c935e49
Author: Brian C. Lane <bcl(a)redhat.com>
Date: Fri Mar 8 10:01:40 2013 -0800
iso9660 is now a module, include it
diff --git a/imgcreate/live.py b/imgcreate/live.py
index 47b9dcd..dbb4dbb 100755
--- a/imgcreate/live.py
+++ b/imgcreate/live.py
@@ -265,7 +265,7 @@ class LiveImageCreatorBase(LoopImageCreator):
return "vfat msdos ";
def __extra_drivers(self):
- retval = "sr_mod sd_mod ide-cd cdrom "
+ retval = "sr_mod sd_mod ide-cd cdrom iso9660 "
for module in self.__modules:
if module == "=usb":
retval = retval + "ehci_hcd uhci_hcd ohci_hcd "
11 years, 1 month