Debian Bug report logs - #863761
klibc-utils: klibc does not support the reboot syscall argument

Reply or subscribe to this bug.

Toggle useless messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: Alfonso Sanchez-Beato <alfonso.sanchez-beato@canonical.com>

To: Debian Bug Tracking System <submit@bugs.debian.org>

Subject: klibc-utils: klibc does not support the reboot syscall argument

Date: Wed, 31 May 2017 08:34:04 +0200

[Message part 1 (text/plain, inline)]

Package: klibc-utils
Version: 2.0.4-8ubuntu3
Severity: normal
Tags: patch

Dear Maintainer,

klibc "reboot" command does not support the reboot syscall argument, so we
cannot do things like "reboot recovery" in devices that follow the Android
partitions conventions.

This bug has been reported in Ubuntu at
<https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1692494>

It has also been sent upstream at
<http://www.zytor.com/pipermail/klibc/2017-May/003957.html>

The attached patch resolves the issue.



-- System Information:
Debian Release: stretch/sid
  APT prefers yakkety-updates
  APT policy: (500, 'yakkety-updates'), (500, 'yakkety-security'), (500, 'yakkety-proposed'), (500, 'yakkety'), (100, 'yakkety-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.8.0-53-generic (SMP w/8 CPU cores)
Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages klibc-utils depends on:
ii  libklibc  2.0.4-8ubuntu3

klibc-utils recommends no packages.

klibc-utils suggests no packages.

-- no debconf information

[add-reboot-argument-support.patch (text/x-diff, attachment)]

[add-reboot-argument-support.patch (text/x-diff, attachment)]

Message #14 received at 863761@bugs.debian.org (full text, mbox, reply):

From: Ben Hutchings <ben@decadent.org.uk>

To: Alfonso Sanchez-Beato <alfonso.sanchez-beato@canonical.com>, 863761@bugs.debian.org

Subject: Re: klibc-utils: klibc does not support the reboot syscall argument

Date: Thu, 28 Dec 2017 23:38:19 +0000

[Message part 1 (text/plain, inline)]

Control: severity -1 wishlist
Control: tag -1 upstream

On Wed, 31 May 2017 08:34:04 +0200
Alfonso Sanchez-Beato <alfonso.sanchez-beato@canonical.com> wrote:
> Package: klibc-utils
> Version: 2.0.4-8ubuntu3
> Severity: normal
> Tags: patch
> 
> Dear Maintainer,
> 
> klibc "reboot" command does not support the reboot syscall argument, so we
> cannot do things like "reboot recovery" in devices that follow the Android
> partitions conventions.
> 
> This bug has been reported in Ubuntu at
> <https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1692494>
> 
> It has also been sent upstream at
> <http://www.zytor.com/pipermail/klibc/2017-May/003957.html>
> 
> The attached patch resolves the issue.

I'm having trouble seeing why this is important.

- What is a Debian/Ubuntu initramfs doing on a device designed for
  Android, which typically doesn't require or support use of an
  initramfs?
- Why is it important to have this facility in the initramfs, rather
  than in the 'real' system?
- Doesn't Ubuntu always use busybox and glibc in the initramfs, anyway?

(Alternately, try to convince upstream of the importance, as it doesn't
seem to have had any response yet.)

Ben.

-- 
Ben Hutchings
The two most common things in the universe are hydrogen and stupidity.

[signature.asc (application/pgp-signature, inline)]

Message #25 received at 863761@bugs.debian.org (full text, mbox, reply):

From: Alfonso Sanchez-Beato <alfonso.sanchez-beato@canonical.com>

To: Ben Hutchings <ben@decadent.org.uk>

Cc: 863761@bugs.debian.org

Subject: Re: klibc-utils: klibc does not support the reboot syscall argument

Date: Thu, 4 Jan 2018 09:36:16 +0100

[Message part 1 (text/plain, inline)]

Hi Ben,

On Fri, Dec 29, 2017 at 12:38 AM, Ben Hutchings <ben@decadent.org.uk> wrote:

> Control: severity -1 wishlist
> Control: tag -1 upstream
>
> On Wed, 31 May 2017 08:34:04 +0200
> Alfonso Sanchez-Beato <alfonso.sanchez-beato@canonical.com> wrote:
> > Package: klibc-utils
> > Version: 2.0.4-8ubuntu3
> > Severity: normal
> > Tags: patch
> >
> > Dear Maintainer,
> >
> > klibc "reboot" command does not support the reboot syscall argument, so
> we
> > cannot do things like "reboot recovery" in devices that follow the
> Android
> > partitions conventions.
> >
> > This bug has been reported in Ubuntu at
> > <https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1692494>
> >
> > It has also been sent upstream at
> > <http://www.zytor.com/pipermail/klibc/2017-May/003957.html>
> >
> > The attached patch resolves the issue.
>
> I'm having trouble seeing why this is important.
>
> - What is a Debian/Ubuntu initramfs doing on a device designed for
>   Android, which typically doesn't require or support use of an
>   initramfs?
>

Android kernels do support and use initramfs (it is always stored in the
boot partition of the device).


> - Why is it important to have this facility in the initramfs, rather
>   than in the 'real' system?
>

To be able to use arguments in the reboot command like "reboot recovery",
which will reboot but will use the recovery partition instead of the boot
partition for loading the kernel. This sort of functionality is useful when
implementing some sort of recovery after being unable to start from the
rootfs.

Note that regardless of this concrete use case, systemd reboot command does
support using arguments and there is no reason for not supporting this in
klibc too.


> - Doesn't Ubuntu always use busybox and glibc in the initramfs, anyway?
>

No, it uses klibc.


>
> (Alternately, try to convince upstream of the importance, as it doesn't
> seem to have had any response yet.)
>

Upstream seems to be dead, there has been no response to any patch sent to
the upstream list in years.

Thanks,
Alfonso


>
> Ben.
>
> --
> Ben Hutchings
> The two most common things in the universe are hydrogen and stupidity.
>
>

[Message part 2 (text/html, inline)]

Send a report that this bug log contains spam.