July 2013 - Arch-general - lists.archlinux.org

[arch-general] syslinux 6.01-1 issues
by Karol Blazewicz 06 Jul '13

06 Jul '13

I'm using syslinux for my bootloader. I'm using BIOS, not UEFI, on a 32-bit system. After updating syslinux 5.10-3 -> 6.01-1 the modules' symlinks in /boot/syslinux didn't get updated and still point to /usr/lib/syslinux/ instead of to /usr/lib/syslinux/bios e.g. menu.c32 -> /usr/lib/syslinux/menu.c32 which prevents the syslinux menu from appearing on boot (modules not found). Running '# /usr/bin/syslinux-install_update -i -a -m' doesn't help. Should I remove all the symlinks from /boot/syslinux and only copy the needed files back? I didn't install syslinux manually so i don't know why should I have to do this. Did I miss / misunderstand something?

4 8

[arch-general] patch for syslinux install script
by Matthew Gyurgyik 06 Jul '13

06 Jul '13

There is a slight change in behaviour. When preforming an update, all c32 modules in /usr/lib/syslinux/bios/ will get copied/symlinked. Previously we only updated/copied modules that were already in /boot/syslinux. Patches can also be found here: http://pyther.net/archlinux/syslinux/6/20130706/ Matthew Gyurgyik PKGBUILD: --- /tmp/syslinux/PKGBUILD 2013-07-06 08:55:21.000000000 -0400 +++ syslinux/PKGBUILD 2013-07-06 07:45:18.811510802 -0400 @@ -4,7 +4,7 @@ pkgname="syslinux" pkgver="6.01" -pkgrel="2" +pkgrel="3" arch=('x86_64' 'i686') pkgdesc="Collection of boot loaders that boot from FAT, ext2/3/4 and btrfs filesystems, from CDs and via PXE" url="http://syslinux.zytor.com/" @@ -29,62 +29,62 @@ source=("https://www.kernel.org/pub/linu sha1sums=('d7bc1b188677f77ac2d7060d25491dc29877a9c4' 'b0f174bcc0386fdf699e03d0090e3ac841098010' - 'b1d915045fe3094f5359df043c53e73a4dc32745') + '2a7c1abe9816f6f702f425499a10582eebf94632') _build_syslinux_bios() { - + rm -rf "${srcdir}/${pkgname}-${pkgver}-bios/" || true cp -r "${srcdir}/${pkgname}-${pkgver}" "${srcdir}/${pkgname}-${pkgver}-bios" cd "${srcdir}/${pkgname}-${pkgver}-bios/" - + ## Do not try to build syslinux with our default LDFLAGS, it will fail unset LDFLAGS - + make PYTHON="python2" bios make PYTHON="python2" bios installer - + } _build_syslinux_efi64() { - + rm -rf "${srcdir}/${pkgname}-${pkgver}-efi64/" || true cp -r "${srcdir}/${pkgname}-${pkgver}" "${srcdir}/${pkgname}-${pkgver}-efi64" cd "${srcdir}/${pkgname}-${pkgver}-efi64/" - + ## Unset all compiler FLAGS for efi64 build unset CFLAGS unset CPPFLAGS unset CXXFLAGS unset LDFLAGS unset MAKEFLAGS - + make PYTHON="python2" efi64 make PYTHON="python2" efi64 installer - + } _build_syslinux_efi32() { - + rm -rf "${srcdir}/${pkgname}-${pkgver}-efi32/" || true cp -r "${srcdir}/${pkgname}-${pkgver}" "${srcdir}/${pkgname}-${pkgver}-efi32" cd "${srcdir}/${pkgname}-${pkgver}-efi32/" - + ## Unset all compiler FLAGS for efi32 build unset CFLAGS unset CPPFLAGS unset CXXFLAGS unset LDFLAGS unset MAKEFLAGS - + make PYTHON="python2" efi32 make PYTHON="python2" efi32 installer - + } build() { - + cd "${srcdir}/${pkgname}-${pkgver}/" - + ## Do not try to build the Windows or DOS installers and DIAG files sed 's|diag libinstaller dos win32 win64 dosutil txt|libinstaller txt|g' -i "${srcdir}/${pkgname}-${pkgver}/Makefile" || true sed 's|win32/syslinux.exe win64/syslinux64.exe||g' -i "${srcdir}/${pkgname}-${pkgver}/Makefile" || true @@ -92,73 +92,73 @@ build() { sed 's|dos/syslinux.com||g' -i "${srcdir}/${pkgname}-${pkgver}/Makefile" || true sed 's|INSTALLSUBDIRS = com32 utils dosutil|INSTALLSUBDIRS = com32 utils|g' -i "${srcdir}/${pkgname}-${pkgver}/Makefile" || true sed 's|install -m 644 -c $(INSTALL_DIAG) $(INSTALLROOT)$(DIAGDIR)|# install -m 644 -c $(INSTALL_DIAG) $(INSTALLROOT)$(DIAGDIR)|g' -i "${srcdir}/${pkgname}-${pkgver}/Makefile" || true - + ## Fix FHS manpage path sed 's|/usr/man|/usr/share/man|g' -i "${srcdir}/${pkgname}-${pkgver}/mk/syslinux.mk" || true - + ## Build syslinux-efi if [[ "${CARCH}" == "x86_64" ]]; then _build_syslinux_efi64 fi - + if [[ "${CARCH}" == "i686" ]]; then _build_syslinux_efi32 fi - + ## Build syslinux-bios _build_syslinux_bios - + } _package_syslinux_bios() { - + cd "${srcdir}/${pkgname}-${pkgver}-bios/" - + ## Install Syslinux bios make INSTALLROOT="${pkgdir}/" AUXDIR="/usr/lib/syslinux/bios/" bios install - + ## Remove syslinux.exe,syslinux64.exe,syslinux.com and dosutil dir rm "${pkgdir}/usr/lib/syslinux/bios"/syslinux.{com,exe} || true rm "${pkgdir}/usr/lib/syslinux/bios/syslinux64.exe" || true rm -rf "${pkgdir}/usr/lib/syslinux/bios/dosutil/" || true - + ## Remove com32 and diag dirs rm -rf "${pkgdir}/usr/lib/syslinux/bios/diag/" || true rm -rf "${pkgdir}/usr/lib/syslinux/bios/com32/" || true - + ## Move extlinux binary to /usr/bin install -d "${pkgdir}/usr/bin" mv "${pkgdir}/sbin/extlinux" "${pkgdir}/usr/bin/extlinux" rm -rf "${pkgdir}/sbin/" - + ## Install docs install -d "${pkgdir}/usr/share/doc" cp -ar "${srcdir}/${pkgname}-${pkgver}/doc" "${pkgdir}/usr/share/doc/syslinux" - + ## Install the default configuration install -D -m0644 "${srcdir}/syslinux.cfg" "${pkgdir}/boot/syslinux/syslinux.cfg" - + ## Install the installation and update script ## This script is maintained at git://gist.github.com/772138.git ## Script not yet updated for syslinux-efi install -D -m0755 "${srcdir}/syslinux-install_update" "${pkgdir}/usr/bin/syslinux-install_update" - + } package() { - + cd "${srcdir}/${pkgname}-${pkgver}/" - + if [[ "${CARCH}" == "x86_64" ]]; then cd "${srcdir}/${pkgname}-${pkgver}-efi64/" make INSTALLROOT="${pkgdir}/" AUXDIR="/usr/lib/syslinux/" efi64 install fi - + if [[ "${CARCH}" == "i686" ]]; then cd "${srcdir}/${pkgname}-${pkgver}-efi32/" make INSTALLROOT="${pkgdir}/" AUXDIR="/usr/lib/syslinux/" efi32 install fi - + _package_syslinux_bios - + } syslinux-install_update: --- /tmp/syslinux/syslinux-install_update 2013-07-06 08:55:11.000000000 -0400 +++ syslinux/syslinux-install_update 2013-07-06 07:42:58.931760621 -0400 @@ -1,7 +1,7 @@ #!/bin/bash # # Sylinux Installer / Updater Scripts -# Copyright (C) 2011 Matthew Gyurgyik <pyther(a)pyther.net> +# Copyright (C) 2013 Matthew Gyurgyik <pyther(a)pyther.net> # # This program is free software; you can redistribute it and/or # modify it under the terms of the GNU General Public License @@ -293,13 +293,13 @@ install_mbr() { return 0 } -_install() { +install_modules() { # Copy all com32 files to /boot for file in "${libpath}"/*.c32; do file=${file##*/} # Symlink files if /boot resides on the same partition as root if [[ "$boot" = root ]]; then - ln -s "${libpath#$CHROOT}/$file" "$bootpath/$file" &> /dev/null + ln -sf "${libpath#$CHROOT}/$file" "$bootpath/$file" &> /dev/null elif [[ "$boot" = boot ]]; then cp "$libpath/$file" "$bootpath/$file" fi @@ -313,59 +313,43 @@ _install() { cp "$pciids_file" "$bootpath/pci.ids" &> /dev/null fi fi +} + +_install() { + install_modules if device_is_raid "$bootpart"; then - echo "Detected RAID on /boot - installing Syslinux with --raid" + echo "Detected RAID on /boot" "$extlinux" --install "$bootpath" -r > /dev/null 2>&1 else "$extlinux" --install "$bootpath" > /dev/null 2>&1 fi if (( $? )); then - echo "Syslinux install failed" + echo "syslinux install failed" exit 2 else - echo "Syslinux install successful" + echo "syslinux install successful" fi touch "$CHROOT/$autoupdate_file" } update() { - # Update c32 files in /boot, if /boot is not on same fs - if [[ "$boot" = boot ]]; then - for file in "$bootpath"/*.c32; do - file=${file##*/} - cp "$libpath/$file" "$bootpath/$file" &> /dev/null - done - if [[ -f "$bootpath/pci.ids" ]]; then - cp "$pciids_file" "$bootpath/pci.ids" &> /dev/null - fi - fi - - # Ensure core modules exist and if not install them - for file in "${core_modules[@]}"; do - if [[ ! -f $bootpath/$file ]]; then - if [[ "$boot" = root ]]; then - ln -s "${libpath#$CHROOT}/$file" "$bootpath/$file" &> /dev/null - elif [[ "$boot" = boot ]]; then - cp "$libpath/$file" "$bootpath/$file" - fi - fi - done + install_modules if device_is_raid $bootpart; then - echo "Detected RAID on /boot - installing Syslinux with --raid" + echo "Detected RAID on /boot" "$extlinux" --update "$bootpath" -r &> /dev/null else "$extlinux" --update "$bootpath" &> /dev/null fi if (($?)); then - echo "Syslinux update failed" + echo "syslinux update failed" exit 2 else - echo "Syslinux update successful" + echo "syslinux update successful" fi }

2 1

Re: [arch-general] [arch-dev-public] Bootstrap images for installing Arch from another system
by Romain Labolle 05 Jul '13

05 Jul '13

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 30/06/2013 02:00, Thomas Bächler wrote: > Am 28.06.2013 20:02, schrieb Thomas Bächler: >> Am 22.06.2013 21:19, schrieb Pierre Schmitz: >>>>> I'd say we include this script into the releng scripts >>>>> (either archiso or create a nwe package; atm I use some >>>>> additional script for releasing an ISO image) and upload >>>>> such a tar at the same time as the ISO image. >>>> >>>> I was thinking about including this into >>>> arch-install-scripts, but I am unsure if it really fits in >>>> there. >>> >>> Yes, seems difficult. As I said, I also have other scripts >>> like creating torrents etc. that are used for a realease. Maybe >>> we can create a releng repo/package for these. >> >> Regardless of where the scripts end up, should we publish these >> images with the July ISO? I can write a short README for it. > > Script is here for the moment: > https://github.com/brain0/genbootstrap > Just to point out something: when using arch-chroot, the following command is executed (with $1=/tmp/root.x86_64/): mountpoint -q "$1" || track_mount "$1" "$1" --bind; Since /tmp/root.x86_64/ is not a mountpoint, we got /tmp/root.x86_64/ binded on itself, which override any previous mount points under /tmp/root.x86_64/, especially /tmp/root.x86_64/mnt. So if you install arch that way, you install it on your /tmp, and not on the mounted partition. So you need to either mount your partition after entering the chroot or bind /tmp/root.x86_64/ before mounting it. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.20 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBAgAGBQJR1tGBAAoJENjIqLe6T5zr7ccQAJrgXj44s9Tx3zHPLgmJOtBn ZB3cEDB9odujJyRbUiYdNUBplgxpPAnIO4wpZRBSxe298JuVzf10vR4UzEChQ2xN M/WYrFBdzy4DYbuo4akamN1eutA98tF4tbHSvToPa/gxQmEgq6mXBPdhaE8R94+j qg44W0gPmvMkndNDzbDGcFaoggaOi6zJ9T6vWdpD5H0T/2My078MR7nQ1Njtf5Rr W85UjQTAJ/WI1+ziYU/Aor1U15yqtoVRUfzkloGbHErZgQIjrU3rlQTu4Wqh72ZX b2rW3rygJFrGzh1TDYCkFK+0D6fx5ALnA5kdtXdQyv80Mgnql3r0TYoT0DhAEewe Ql4MV29+LNaPZFFxQfsdxf2GxicxJk+RUcBZPrEDTMEvchLFmI5+d6NmtETcj35n Wv5lDuv8fTpaPfsmGQTHpEcRNkoHNNkEt6IzyJLtRoJjgwsf6cwSyNIwzrQQ7QNv Tj4CY7pmWgto2HGP5vO5AhOaI7LXzynPS9EZRJ2Bz2MQtH0tTKX2vUDWWgd3nLHH MCpwLL/1jErrs7sQEiEeHTP9AEGQtevPIEmTL4EA4isey0rzEuuDJQfR0pbFIERK Yob06gnmSUEC/vBIBE4HAUAqga3y/oP788xSaDBndeVcprkBdM+wPIhsDymFtA9M IrEQk7ETVD3HcnDpX52W =SsUr -----END PGP SIGNATURE-----

1 0

[arch-general] reading messages during shutdown
by F. Gr. 05 Jul '13

05 Jul '13

Hi, I've noticed that there are some warning during the halt/reboot process. How can I read these messages?

3 2

Re: [arch-general] [arch-dev-public] [FYI] systemd 205, cgroup attribute changes
by Oon-Ee Ng 05 Jul '13

05 Jul '13

On Fri, Jul 5, 2013 at 12:56 AM, Dave Reisner <d(a)falconindy.com> wrote: > On Wed, Jul 03, 2013 at 02:44:12PM -0400, Dave Reisner wrote: >> On Wed, Jul 03, 2013 at 12:48:49PM -0400, Dave Reisner wrote: >> > Hey all, >> > >> > systemd 205 was just tagged, and brings some major, promised, cgroup changes >> > [1]. I'll be pushing this into [testing] tonight. I do NOT expect that this >> > release will ever move to [core], but maybe I'll be pleasantly surprised. >> > >> > The NEWS file [2] is fairly large and warrants a read, particularly about the >> > new machine API. >> > >> > Cheers, >> > Dave >> > >> > [1] http://lists.freedesktop.org/archives/systemd-devel/2013-June/011521.html >> > [2] http://cgit.freedesktop.org/systemd/systemd/tree/NEWS >> >> On second thought, this may not be hitting [testing] so soon. systemd >> --user sessions will be broken, and I need to work out exactly what's >> happening with some of the applets like logind. I think the best course >> of action for this upgrade may be to simply advise a reboot. >> >> d > > If anyone wants a package to play with anyways, I've setup a repo: > > [falconindy] > Server = http://repo.falconindy.com/$arch > > Apologies if your DNS hasn't caught up for the A record yet -- you can > find it on he.net: > > $ host repo.falconindy.com ns1.he.net > > level3 and openDNS seem to have scavenged the record already, while > google has not. > > Have fun. Worrying for me that --user setups are broken, as I've grown to rely on that. Is this something incidental that will be fixed or something more fundamental.

2 1

[arch-general] short hangs
by János Illés 04 Jul '13

04 Jul '13

Hi, my system has some annoying visual glitches and I have no idea how to determine which software is causing it. Here's the symptoms: Everything freeze. It takes 5-15 seconds and everything goes back to normal. But, the freeze is only visual, sound/music playback works continously, I can ssh to the machine, even the mouse moves and changes (!) accordingly if I hover something. Only the displayed content freezes, sometimes in the middle of an animation. There is nothing in the journal, nothing in dmesg, no spikes in the CPU usage, no IO spikes. And it happens rarely, only 5-10 times a day. My guess would be a gnome-shell or an open source radeon driver bug, but how can I be sure or test it? Bisecting package versions is nearly impossible, there are too many of them and I cannot reproduce the freeze, it just happens. I hoped it would go away but it is happening for more than a month now, and according to my searches no other arch user experience similar issue. I'm open to ideas. My full hardware spec is here: https://gist.github.com/ijanos/5a84c0c40d58410a87d7 -- János

5 6

Re: [arch-general] [arch-dev-public] /etc/shells should keep /bin/zsh
by Chris Down 02 Jul '13

02 Jul '13

(changed recipient back to arch-general) On 2 July 2013 05:50, S=C3=A9bastien Luttringer <seblu(a)seblu.net> wrote: > Have 2 paths will be painful with chsh as I describe in the bugreport. I think I might have not quite fleshed out option "a" fully. I'm talking about a&b, not a^b. >> a. both the old path and /usr/bin be acceptable >> b. only the old path be acceptable >> c. only the new path be acceptable There is also "d. allow either", which (I think) is what you believe I meant by a. I don't think having both would be confusing. It would allow people to use the new paths (which seems sane), but also use the old ones which have been used for years and years. I agree that "allow either" is not sane from any perspective. Preferentially I still think we should deprecate the old shell paths though, unless there are technical limitations.

1 0

[arch-general] /etc/shells should keep /bin/zsh
by Karol Blazewicz 01 Jul '13

01 Jul '13

I know arch-general si not for reporting bugs and I'm not trying to rush anyone, but it's been already a month of confusion wrt https://projects.archlinux.org/svntogit/packages.git/commit/trunk?h=package… https://bugs.archlinux.org/task/35724

3 2