* Gordon Farquharson <[EMAIL PROTECTED]> [2007-12-03 00:12]:
> nslu2-utils is version 0.10+r71-13, but I don't see any changes to the
> initramfs hook that should cause this problem. I am using a DFSG image
> that does not contain the NPE-B firmware.
I guess the best way this should be handled is
I couldn't find any difference in how the kernel was setting up the
console that would affect the /proc/$dipid/fd/0 link, so I started
looking into userspace.
Busybox's console_init() tries to find and use the real console
device. It starts by checking to see if its a serial device in much
the sam
Processing commands for [EMAIL PROTECTED]:
> # Automatically generated email from bts, devscripts version 2.10.11
> reassign 453749 rootskel
Bug#453749: Fix serial console detection on ia64
Bug reassigned from package `finish-install' to `rootskel'.
> found 453749 1.57
Bug#453749: Fix serial cons
Thanks for your responses. As I was writing this report, I began to
wonder why exactly the proc trick doesn't work on some ia64 configs -
I'm investigating this now. If I can find a workable solution there,
we may be able to forego these changes - if not, I'll regenerate new
patches based on your c
Hi Frans,
On Mon, Dec 03, 2007 at 10:37:32AM +0100, Frans Pop wrote:
> On Monday 03 December 2007, Max Vozeler wrote:
> > I've carefully gone through them and noted the differences,
> > hoping to replace them all with a common commit_changes in
> > partman-base/definition.sh
>
> I agree that fact
On Mon, Dec 03, 2007 at 11:26:22AM +0100, Frans Pop wrote:
> I therefore suggest reverting David's changes (which luckily is quite
> straightforward) and then first do some refactoring of existing code as
> preparation for a reimplementation of support for erasing encrypted
> volumes.
I tend to
Andreas Gerlich <[EMAIL PROTECTED]> wrote:
In the following screens I setup the same like in the first situation:
/boot SWAP /
,, ,, ,,
| BOOT | | SWAP | | ROOT |
`---*´ `---*´ `*---´
| | |
| |
On Mon, Dec 03, 2007 at 11:26:22AM +0100, Frans Pop wrote:
I've spent about 6 hours yesterday looking at #396023 and #425829, the
issues introduced after implementation of support for erasing encrypted
volumes. I've looked at both the original patch and the changes proposed by
Jérémy.
Your su
Package: installation-reports
Boot method:
netinst CD
Image version:
daily build 2007-11-25-#2 for amd64,
using installer build from sid
http://cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/amd64/iso-cd
Date:
2007-11-29
Machine:
Dell Precision 490 workstation
Processor:
Op 02-12-2007 om 14:26 schreef Josef Wolf:
> On Sat, Dec 01, 2007 at 12:44:30PM +0100, Geert Stappers wrote:
> > An option might be a modified netcfg.
> > Build the udeb after your hack and place it in the local udeb directory
> > before rebuilding d-i.
>
> Sorry, I don't really understand
I've spent about 6 hours yesterday looking at #396023 and #425829, the
issues introduced after implementation of support for erasing encrypted
volumes. I've looked at both the original patch and the changes proposed by
Jérémy.
The main issues are that the original patch:
- relies on dmsetup to
On Monday 03 December 2007, Max Vozeler wrote:
> I've carefully gone through them and noted the differences,
> hoping to replace them all with a common commit_changes in
> partman-base/definition.sh
I agree that factoring this out makes sense. I've looked over your patch and
the thorough analysis
On Sunday 02 December 2007, Frans Pop wrote:
> The patch for partman-lvm may have fixed the symptom for normal installs,
> but it is not a structural fix.
>
> Similar errors still occurs when a user selects Guided LVM partitioning:
> /bin/autopartition: 35: dmsetup: not found
> /bin/autopartition-l
13 matches
Mail list logo
