Hi ftpmasters, release team, cd team,
please respectively, do:
- dak copy-installer
- urgent d-i
- start building installation images (I think it needs at least a
dinstall + a mirror pulse though); putting them into a “dot-dir”
for the time being would be nice.
Mraw,
KiBi.
signature.as
Nice work Steve,
And just in time for me. I bought a UEFI system second hand and got it
from mail on Friday. Its got a ASUS Sabertooth 990FX board with the
newest bios.
I installed with your third version of the installer and it worked.
Though still having trouble with double booting to win7 and
package: pxz
version: 4.999.9~beta+git537418b-1
severity: important
affects: busybox
x-debbugs-cc:
debian-boot@lists.debian.org,xz-ut...@packages.debian.org,jn...@users.sourceforge.net
Hi,
pxz (somtimes) produces archives broken for busybox's unxz, while they
decompress fine with unxz from xz-u
Hi Bastian,
On Sonntag, 2. September 2012, Bastian Blank wrote:
> On Sun, Sep 02, 2012 at 03:18:40PM +0200, Holger Levsen wrote:
> > ~/t$ busybox unxz typo3-src_4.5.19+dfsg1.orig.tar.xz
> > ~/t$ tar tf typo3-src_4.5.19+dfsg1.orig.tar 1>/dev/null
> > tar: Unexpected EOF in archive
> > tar: Error is
Karsten Merker wrote:
> A possible solution would be to add a recommends on
> gstreamer0.10-alsa to task-xfce-desktop, so that it gets pulled
> in during the system installation while not fiddling with the
> xfce4-mixer dependencies which are correct from the package point
> of view.
>
> What do y
Mika Rastas wrote:
>Nice work Steve,
*grin* Thanks!
>And just in time for me. I bought a UEFI system second hand and got it
>from mail on Friday. Its got a ASUS Sabertooth 990FX board with the
>newest bios.
>
>I installed with your third version of the installer and it worked.
Awesome.
>Though
Hi Holger,
Holger Levsen wrote:
> pxz (somtimes) produces archives broken for busybox's unxz, while they
> decompress fine with unxz from xz-utils packges. I noticed when trying
> to uncompress pxz compressed initramfs files, while this is an universal
> way to reproduce it:
Thanks! Could you
The debian entry that was made during install broke eighter on windows
install or Asus boot menu just wouldn't get it running. I wasn't sure could
I use efi recovery boot selection to install grub again automatically? Does
it work so or is it just for manual recovery with the system loaded as efi
a
Dough of course the verbose output is nicer.
/home# efibootmgr -v
BootCurrent:
Timeout: 3 seconds
BootOrder: ,0002,0003,0005,0001
Boot* Debian GNU/Linux
HD(3,613a4800,f4000,ea481e18-9503-404e-84ed-088f005a3ee1)File(\EFI\debian\grubx64.efi)
Boot0001 Hard DriveBIOS(2,0,00)P0: WDC W
As a matter of fact it *does* prevent the creation of more than 11 md devices
but as far as I can see this is a bug, not a feature.
In the file lib/md-base.sh:
# Find the next available MD device number
md_next_device_number () {
local md_num="$(grep ^md /proc/mdstat | \
10 matches
Mail list logo
