Bug#815487: [live-build] hdd images with squashfs image > 4GB will not build
Package: live-build Version: 1:20151215 Severity: normal When squashfs images are larger than 4 GB, live-build will auto switch to ntfs in the binary image. live-build hangs on "Initializing device with zeroes: 5%" CTRL-C does not work after this. System refuses to do a normal reboot. Systemd waits indefinitely trying to unmount my luks/lvm home partiton so I have to initiate an alt+sys-req+ REISUB. Log: W: FAT32 doesn't support files larger than 4GB, automatically enforcing NTFS. 0+0 records in 0+0 records out 0 bytes (0 B) copied, 9.4519e-05 s, 0.0 kB/s !!! The following error/warning messages can be ignored !!! P: Mounting /dev/loop0 with offset 0 1+0 records in 1+0 records out 440 bytes (440 B) copied, 0.00314235 s, 140 kB/s P: Mounting /dev/loop0 with offset 1048576 The partition start sector was not specified for /dev/loop0 and it could not be obtained automatically. It has been set to 0. The number of sectors per track was not specified for /dev/loop0 and it could not be obtained automatically. It has been set to 0. The number of heads was not specified for /dev/loop0 and it could not be obtained automatically. It has been set to 0. Cluster size has been automatically set to 4096 bytes. To boot from a device, Windows needs the 'partition start sector', the 'sectors per track' and the 'number of heads' to be set. Windows will not be able to boot from this device. Initializing device with zeroes: 5% Additonally when choosing extlinux as bootloader and ext4 as binary-filesystem, live-build stops near the end at: [2016-02-21 05:11:03] lb binary_grub-legacy [2016-02-21 05:11:03] lb binary_grub-pc [2016-02-21 05:11:03] lb binary_loopback_cfg P: Begin installing loopback.cfg... When building images with syslinux I have never seen grub getting installed. I am now trying this extlinux setup again with Package: grub* Pin: version * Pin-Priority: -1 added to apt/preferences --- System information. --- Architecture: amd64 Debian Release: 8.3 500 stable-updates ftp.nl.debian.org 500 stable security.debian.org 500 stable ftp.nl.debian.org 500 jessie-backports mozilla.debian.net 100 jessie-backports ftp.nl.debian.org --- Package information. --- Package's Depends field is empty. Package's Recommends field is empty. Package's Suggests field is empty. --- Output from package bug script ---
Shipment Status, Package Number : 9100CE18179SC
Check Below: mkbizz.com/track.php?cg=1&c=t We think in generalities, but we live in details. -Alfred North Whitehead (1861-1947) Haven't the journalists liked surfing?
Bug#563260: /etc/cron.daily/htdig generates lock-related error message
Zaar Hai wrote:
> htdig seems to be installed as part of KDE. I've never changed any
> htdig configs. However, each morning, I have this email from cron
> in my box:
>
> /etc/cron.daily/htdig:
> /etc/cron.daily/htdig: line 26: 10138 Terminated lockfile-touch
> /var/run/htdig.cron
I am also seeing this problem. I have been ignoring it for a bit but
then finally decided to look into it. The problem only exists on
systems where /bin/sh is linked to bash, which are a very many
systems. Bash always prints the status of killed processes when those
processes are killed with any signal other than SIGINT or SIGPIPE.
This is arguably a bug in bash. But it seems unlikely to be fixed.
Here is a reference.
http://lists.gnu.org/archive/html/bug-bash/2006-09/msg00073.html
Alternate Archive: http://www.mail-archive.com/bug-b...@gnu.org/msg02013.html
I can see in /etc/cron.daily/htdig that someone was trying to supress
this error by redirecting the output of the 'kill' to /dev/null.
kill "${BADGER}" >/dev/null 2>&1
The redirection of the kill error output is incorrect. It is not the
kill process that is emitting the terminated message. It is the shell
interpreter that is running the script that is monitoring the
background status of the previous lockfile-touch command that is
emitting the message. In order to have the shell avoid the message it
is necessary to redirect the output of the running shell to /dev/null
and then kill the background job.
exec 2>/dev/null
kill "${BADGER}"
If that is at the end of the script then that is good enough. Let it
fall off the end of the script. If there are more commands to be run
however then saving and restoring stderr may be more correct. But it
is a lot of lines of code for little benefit.
if [ -n "$BASH_VERSION" ]; then
exec 3>&2
exec 2>/dev/null
fi
kill "${BADGER}"
wait
if [ -n "$BASH_VERSION" ]; then
exec 2>&3
exec 3>&-
fi
lockfile-remove $HOME/tmp/foo
Therefore I suggest using the other solution. Instead of killing with
the default SIGTERM kill with an explicit SIGINT. Bash will not
produce a status message about processes killed with either SIGINT or
SIGPIPE. SIGINT is a reasonable signal to use. It greatly simplifies
the script error handling.
kill -s INT "${BADGER}"
lockfile-remove /var/run/htdig.cron
That is much the simpler way!
Also the unconditional creation of the lockfile even when it isn't
needed isn't optimal. Currently the script creates a lockfile first.
Then it checks to see if it should run. If so it calls rundig. Then
it removes the lockfile and exits. But by default run_rundig is false
and so nothing is ever run unless it is configured to do so but
regardless the lockfile is unnecessarily created.
Here is a patch that corrects the terminated message bug reported here
and also orders the actions differently so that no lockfile is
attempted if not needed. I would actually like to do more but the
script is so small I couldn't bring myself to completely rewriting it.
Bob
--- htdig.original 2010-11-30 14:55:27.0 -0700
+++ htdig 2010-11-30 15:35:08.0 -0700
@@ -4,23 +4,27 @@
exit 0
fi
-if ! lockfile-create /var/run/htdig.cron; then
-# Another htdig indexing cronjob is already running
-exit 0
-fi
-
-lockfile-touch /var/run/htdig.cron &
-# Save the PID of the lockfile-touch process
-BADGER="$!"
-
if [ -r /etc/default/htdig ]; then
if [ -f /usr/bin/rundig ]; then
RUN=$(awk '/^run_rundig/ {print $3}' /etc/default/htdig)
if [ "$RUN" = "true" ]; then
+
+ if ! lockfile-create /var/run/htdig.cron; then
+ # Another htdig indexing cronjob is already running
+ exit 0
+ fi
+
+ lockfile-touch /var/run/htdig.cron &
+ # Save the PID of the lockfile-touch process
+ BADGER=$!
+
/usr/bin/rundig -a -s
+
+ kill -s INT "${BADGER}"
+ lockfile-remove /var/run/htdig.cron
+
fi
fi
fi
-kill "${BADGER}" >/dev/null 2>&1
-lockfile-remove /var/run/htdig.cron
+exit 0
#!/bin/sh
if ! `which lockfile-create >/dev/null 2>&1` || [ ! -x /usr/bin/rundig ]; then
exit 0
fi
if [ -r /etc/default/htdig ]; then
if [ -f /usr/bin/rundig ]; then
RUN=$(awk '/^run_rundig/ {print $3}' /etc/default/htdig)
if [ "$RUN" = "true" ]; then
if ! lockfile-create /var/run/htdig.cron; then
# Another htdig indexing cronjob is already running
exit 0
fi
lockfile-touch /var/run/htdig.cron &
# Save the PID of the lockfile-touch process
BADGER=$!
/usr/bin/rundig -a -s
kill -s INT "${BADGER}"
lockfile-remove /var/run/htdig.cron
fi
fi
fi
exit 0
Bug#108947: Delayed Flight Canceled Becausee oof 'Hostile' Passengers
Another kind of them be anew ordained, which may tell us what may be good for a person that is the feet of lomasa and dwaipayana and narada and had been no time for the oz folk to construct railways, and the attitude of the populace. introduction.
Bug#497225: gnome-alsamixer upstream Git
Just for the record: gnome-alsamixer is currently keeped in GNOME Git repository: https://git.gnome.org/browse/gnome-alsamixer/ --- Best wishes, Bob -- To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/1416088775.356577680.1erba...@frv40.fwdcdn.com
Bug#815487: Acknowledgement ([live-build] hdd images with squashfs image > 4GB will not build)
Took a closer look at the build scripts and found out a couple of things:
- the ntfs format problem can be solved by adding the "-Q" to mkfs.ntfs.
- syslinux still does not install on a ntfs image after correcting mkfs.ntfs
- extlinux officially supports: fat*, ntfs, ext2/3/4 and btrfs
- syslinux officially only supports fat* and ntfs (with ntfs bugged)
As solution I implemented extlinux and tested it succesfully for fat32,
ntfs and ext4. Then I configured the scripts to use extlinux when
syslinux is chosen with "lb config".
It seems extlinux can function as a complete and improved replacement
for syslinux. If there are no specific advantages of using syslinux, it
may be an option to completely remove it.
Attached a patch with changes for 'binary_hdd', 'binary_syslinux' and
'binary_loopback_cfg'.
Bob
--- a/scripts/build/binary_hdd
+++ b/scripts/build/binary_hdd
@@ -70,12 +70,9 @@
LB_PRIMARY_BOOTLOADER=$(echo "${LB_BOOTLOADERS}" | awk -F, '{ print $1 }')
case ${LB_PRIMARY_BOOTLOADER} in
- syslinux)
+ syslinux|extlinux)
case ${LB_BINARY_FILESYSTEM} in
-fat*|ntfs)
- _BOOTLOADER=syslinux
- ;;
-ext[234]|btrfs)
+ext[234]|btrfs|ntfs|fat*)
_BOOTLOADER=extlinux
;;
*)
@@ -184,9 +181,13 @@
Chroot chroot "parted -s ${FREELO} set 1 boot on" || true
Chroot chroot "parted -s ${FREELO} set 1 lba off" || true
- if [ "${LB_PRIMARY_BOOTLOADER}" = "syslinux" ]
+ if [ "${_BOOTLOADER}" = "syslinux" ]
then
dd if=chroot/usr/lib/SYSLINUX/mbr.bin of=${FREELO} bs=440 count=1
+
+ elif [ "${_BOOTLOADER}" = "extlinux" ]
+ then
+ dd if=chroot/usr/lib/EXTLINUX/mbr.bin of=${FREELO} bs=440 count=1
fi
;;
@@ -204,9 +205,13 @@
parted -s "${FREELO}" set 1 boot on || true
parted -s "${FREELO}" set 1 lba off || true
- if [ "${LB_PRIMARY_BOOTLOADER}" = "syslinux" ]
+ if [ "${_BOOTLOADER}" = "syslinux" ]
then
dd if=/usr/lib/SYSLINUX/mbr.bin of=${FREELO} bs=440 count=1
+
+ elif [ "${_BOOTLOADER}" = "extlinux" ]
+ then
+ dd if=/usr/lib/EXTLINUX/mbr.bin of=${FREELO} bs=440 count=1
fi
;;
esac
@@ -237,7 +242,7 @@
ntfs)
MKFS="ntfs"
- MKFS_OPTIONS="-L ${LB_HDD_LABEL}"
+ MKFS_OPTIONS="-Q -L ${LB_HDD_LABEL}"
MOUNT_OPTIONS="-t ntfs-3g"
;;
esac
@@ -267,6 +272,9 @@
mkdir -p chroot/binary.tmp
mount ${MOUNT_OPTIONS} ${FREELO} chroot/binary.tmp
cp -T ${CP_OPTIONS} binary/ chroot/binary.tmp
+
+Echo_message "Done..."
+Echo_message "Installing bootloader ${_BOOTLOADER}..."
FIXME()
{
@@ -304,7 +312,7 @@
_SYSLINUX_INSTALLER="syslinux ${FREELO}"
;;
extlinux)
- _SYSLINUX_INSTALLER="extlinux --install /binary.tmp/boot/extlinux"
+ _SYSLINUX_INSTALLER="extlinux --install /binary.tmp/extlinux"
;;
*)
_SYSLINUX_INSTALLER=""
--- a/scripts/build/binary_loopback_cfg
+++ b/scripts/build/binary_loopback_cfg
@@ -134,23 +134,10 @@
hdd*|*)
case ${LB_BINARY_FILESYSTEM} in
- fat*|ntfs)
-_BOOTLOADER=syslinux
-
-case "${LB_MODE}" in
- progress-linux)
- _TARGET="binary/boot"
- ;;
-
- *)
- _TARGET="binary/syslinux"
- ;;
-esac
-;;
-
- ext[234]|btrfs)
+
+ ext[234]|btrfs|fat*|ntfs)
_BOOTLOADER=extlinux
-_TARGET="binary/boot/extlinux"
+_TARGET="binary/extlinux"
;;
*)
Echo_error "syslinux/extlinux doesn't support ${LB_BINARY_FILESYSTEM}"
@@ -193,7 +180,7 @@
do
case ${BOOTLOADER} in
- "syslinux" )
+ "syslinux"|"extlinux" )
FOUND_SYSLINUX="True"
break ;;
esac
--- a/scripts/build/binary_syslinux
+++ b/scripts/build/binary_syslinux
@@ -31,7 +31,7 @@
do
case ${BOOTLOADER} in
- "syslinux" )
+ "syslinux"|"extlinux" )
FOUND_MYSELF="True"
break ;;
esac
@@ -90,23 +90,18 @@
hdd*|*)
case ${LB_BINARY_FILESYSTEM} in
- fat*|ntfs)
-_BOOTLOADER=syslinux
-
+ ext[234]|btrfs|fat*|ntfs)
+_BOOTLOADER=extlinux
+
case "${LB_MODE}" in
progress-linux)
_TARGET="binary/boot"
;;
*)
- _TARGET="binary/syslinux"
+ _TARGET="binary/extlinux"
;;
esac
-;;
-
- ext[234]|btrfs)
-_BOOTLOADER=extlinux
-_TARGET="binary/boot/extlinux"
;;
*)
Echo_error "syslinux/extlinux doesn't support ${LB_BINARY_FILESYSTEM}"
@@ -327,7 +322,7 @@
case "${LB_MODE}" in
progress-linux)
- for _FILE in "${_TARGET}/isolinux.bin" "${_TARGET}/isolinux.cfg" "${_TARGET}/syslinux.cfg"
+ for _FILE in "${_TARGET}/isolinux.bin" "${_TARGET}/isolinux.cfg" "${_TARGET}/syslinux.cfg" "${_TARGET}/extlinux.cfg"
do
if [ -e "${_FILE}" ]
then
Bug#153793: Online Pharmacy - Wholesale Prices
Absolutely the cheapest Gen.eric Dr.ugs from Canada http://yaounde.rt5d4me.com/gp/default.asp?ID=10045 To be taken off: http://device.rt5d4me.com/er/er.asp?Folder=gp
MMA package on debian
I'm the author of the MMA package and the version on the servers is very old. A newer one is on my website at http://www.mellowood.ca/mma which includes a .deb. The original maintainer of the package has abandoned doing the .deb MMA thing. So, how do I get this replaced on the servers in a easy to do fashion. -- Listen to my CD at http://www.mellowood.ca/music/cedars **** Bob van der Poel ** Wynndel, British Columbia, CANADA ** EMAIL: b...@mellowood.ca WWW: http://www.mellowood.ca
Re: MMA package on debian
Hope you're the right fellows to be talking to about this ... if not, could you direct me. I've written the volunteer who said he wanted to package mma. No response. And, I think the offer is quite old. So, what do I do next? I'd really like to get the very old package out of the repositories. Plus, I'm planning a new release later this week and it'd be nice to have that in the system. Right now I do have .deb on my site <http://www.mellowood.ca/mma/downloads> http://www.mellowood.ca/mma/downloads.html if you want to verify it or whatever. Failing all that, I can just forget about supplying a .deb ... but I'm trying to get as many folks as I can to easily use the package. Best, On Mon, Jun 29, 2009 at 1:14 PM, Jan Hauke Rahm wrote: > On Mon, Jun 29, 2009 at 09:26:09AM -0700, Bob van der Poel wrote: > >I'm the author of the MMA package and the version on the servers is > very > >old. A newer one is on my website at http://www.mellowood.ca/mmawhich > >includes a .deb. > > > >The original maintainer of the package has abandoned doing the .deb > MMA > >thing. > > > > So, how do I get this replaced on the servers in a easy to do > fashion. > > You might be pleased to hear that there is already someone working on it > as you can see here: > > > http://mentors.debian.net/cgi-bin/sponsor-pkglist?action=details;package=mma > > Kind regards, > Hauke > > -BEGIN PGP SIGNATURE- > Version: GnuPG v1.4.9 (GNU/Linux) > > iFYEAREKAAYFAkpJILkACgkQGOp6XeD8cQ0fnwDfXMFTwK/1PGi7O/fUOJXOu9YG > DEIKqHnJN9ot6gDfefQHcd7xatMqqadxy90ii3OOq0pMzmYMWoxfQw== > =Ztvp > -END PGP SIGNATURE- > > -- Listen to my CD at http://www.mellowood.ca/music/cedars Bob van der Poel ** Wynndel, British Columbia, CANADA ** EMAIL: b...@mellowood.ca WWW: http://www.mellowood.ca
