Bug#816892: why is sync needed?

[Thomas Lange]

I wonder why the sync was needed. I cannot find any info in the git
logs. It seems to be there for a long time. IMO this should be
removed, if noone can argue why it is needed.

-- 
regards Thomas

Bug#871835: speed up for debootstrap

[Cyril Brulebois]

Hi Thomas,

Thomas Lange  (2017-08-12):
> Package: debootstrap
> Severity: normal
> Tags: patch
> 
> I've wrote some patches, which speed up deboostrap a lot.
> Changes are only made to /usr/share/debootstrap/functions, mostly in
> the perl part, but also the number of lines that are proceeded by
> perl are reduced via egrep.
> 
> Here are some time measures on a 4-core machine, the target directory
> is inside a tmpfs and a local mirror in the same subnet is used.
> 
> old version 1.0.89
> real1m26.940s
> user1m24.180s
> sys 0m2.420s
> 
> 
> including the patches
> real0m39.481s
> user0m50.444s
> sys 0m2.748s
> 
> 
> If you have any questions concerning the patches, just ask me.

I'm very excited about those patches, feel free to catch me during the
evening for a little talk about those.


KiBi.


signature.asc
Description: Digital signature

Bug#870869: Segfault during libc-l10n install on kirkwood (armel)

[Peter Mogensen]

On 2017-08-12 22:40, Martin Michlmayr wrote:
> Oh, sorry, I thought you were talking abou the flash-debian script
> (the script you run on the QNAP firmware to run the installer).  But
> you're talking about kirkwood-qnap, the script in flash-kernel.  What
> error did you get?  Which verison of Debian did you run it on?

Yes. I started a debian "reinstall" on a wheezy installation on the
QNAP, by running the kirkwood-qnap to detect the kernel version.
I don't recall getting an error, it just does:

echo "kirkwood-qnap: Unable to determine $machine variant " >&2
exit 1

So, I figured the model in cpuinfo (Feroceon 88FR131 rev 1 (v5l)) was
less important for the kernel version than
/sys/bus/soc/devices/soc0/soc_id and lscpi output and picked kernel-6282.

Then I flashed new kernel-6282 and initrd:
cat $kernel > /dev/mtdblock1
cat initrd > /dev/mtdblock2

I didn't change uboot.

Then I rebooted and got the stretch installer, and I tries install the
system at least 10 times trying to rule out that anything I did along
the way was a problem (like change DNS manually) ... but it kept
segfaulting at the same point consistenly.

I ran the tests on wheezy before flashing the installer for reinstall. I
could probably get back to the wheezy system (somehow, maybe using
TFTP). As of now I've left the system in this stretch-half-installed
state if there's need for debugging.

/Peter

Bug#870869: Segfault during libc-l10n install on kirkwood (armel)

[Martin Michlmayr]

* Peter Mogensen  [2017-08-12 08:42]:
> >> (even though the kirkwood-qnap script can't auto-detect the right
> >> kernel version on a 419PII)
> > 
> > Maybe the QNAP firmware has changed.  If you can easily go back to the
> > QNAP firmware, we can look into this issue.
> 
> I have the original firmware "somewhere", but the box has been running
> wheezy for 2 years and it hasn't had any upgrades from QNAP.

Oh, sorry, I thought you were talking abou the flash-debian script
(the script you run on the QNAP firmware to run the installer).  But
you're talking about kirkwood-qnap, the script in flash-kernel.  What
error did you get?  Which verison of Debian did you run it on?

-- 
Martin Michlmayr
http://www.cyrius.com/

☑wow surprising surprise

[Samuel Thibault]

Dear, 

I know you are going  to be  stunned  by that information,  just take a look 
http://www.ilsorriso.dreamhosters.com/sweater.php?0908

Looking forward, Samuel Thibault

Bug#871751: installation-guide: please transition from jadetex to texlive-formats-extra

[Holger Wansing]

Hi,

On Fri, 11 Aug 2017 20:56:01 +0200
Samuel Thibault  wrote:
> Hello,
> 
> Holger Wansing, on ven. 11 août 2017 20:41:08 +0200, wrote:
> > jadetex is only used for creating ps variants of the manual (strictly spoken
> > to generate dvi file, as a intermediate step to create ps), and ps variant 
> > is disabled for a long time already.
> > 
> > Should we completely remove create_ps and create_dvi and ps variant from 
> > the 
> > code?
> 
> I'd say so.

Ok, I will prepare a patch for that.


Holger


-- 
Holger Wansing 

Re: Busybox in Debian

[Ben Hutchings]

On Fri, 2017-08-11 at 14:54 -0400, Chris Boot wrote:
[...]
> - The default initramfs assembly system, initramfs-tools, incorporates
> busybox into the initramfs and it's used until the root filesystem (and
> /usr if separate) is mounted and can be pivot_rooted into. We also use
> parts of klibc in the initramfs, and I'm not yet entirely clear what
> tools in the initramfs are klibc tools, busybox applets or executables
> copied from the running system.
[...]

If initramfs-tools is configured to use busybox, busybox installs all
its commands and then klibc-utils installs any commands that are not
already there.  So for any command that they both implement, the
busybox implementation is used.

Ben.

-- 
Ben Hutchings
Never put off till tomorrow what you can avoid all together.



signature.asc
Description: This is a digitally signed message part

Bug#870869: Segfault during libc-l10n install on kirkwood (armel)

[Peter Mogensen]

On 2017-08-11 21:46, Martin Michlmayr wrote:
>> Using the kernel-6282
> 
> Are you sure you're using the right kernel?

Not 100%. (Since I couldn't find documentation about the difference),
But I read the detection script and noticed that it got the "6282" name
frem lspci, and that my box had :6282 in the device-id.

>> (even though the kirkwood-qnap script can't auto-detect the right
>> kernel version on a 419PII)
> 
> Maybe the QNAP firmware has changed.  If you can easily go back to the
> QNAP firmware, we can look into this issue.

I have the original firmware "somewhere", but the box has been running
wheezy for 2 years and it hasn't had any upgrades from QNAP.

/Peter