On Wed, Aug 02, 2017 at 07:58:05PM +0100, Ben Hutchings wrote:
> On Wed, 2017-08-02 at 12:26 +1000, Vincent McIntyre wrote:
> > Package: hw-detect
> > Version: 1.124
> > Severity: normal
> > Tags: patch
> >
> > I keep seeing this in installer logs, back t
On Mon, Dec 17, 2018 at 02:29:27AM +0100, Cyril Brulebois wrote:
> Steve McIntyre (2018-12-17):
> > But... The problem you're most likely seeing is caused by a simple
> > fact. The *netboot* image ends up downloading significant chunks of
> > the installer and the base system at runtime from the
On Mon, Dec 17, 2018 at 01:18:59AM +, Steve McIntyre wrote:
> On Mon, Dec 17, 2018 at 11:00:25AM +1100, Vincent McIntyre wrote:
> >Hello
> >
> >I was trying to download the netboot image for amd64,
> >because the one I have (2018-12-06) has a segfault in libc6.
>
Hello
I was trying to download the netboot image for amd64,
because the one I have (2018-12-06) has a segfault in libc6.
The link on the installer team page
https://www.debian.org/devel/debian-installer/
for the _netinst_ image points at
Not quite sure about the wording, but a first try:
diff --git a/en/install-methods/install-tftp.xml
b/en/install-methods/install-tftp.xml
index 868c70155..7236fa836 100644
--- a/en/install-methods/install-tftp.xml
+++ b/en/install-methods/install-tftp.xml
@@ -178,7 +178,10 @@ For PXE booting,
Below is a known-good partitioning recipe similar to your use case.
It puts all of /, not just /boot, in a real partition.
I think the main difference is the start of the second stanza
614401000 1 lvm
while you have
100 1000 -1 xfs
There may be a bug in handling -1 as the upper
It would be good to make this change.
Is there some reason to not include a build stamp in the installer
initrd at, say, /build-stamp? This would be the same string as in
boot-screens/f1.txt (e.g. 20170615+deb9u2).
Regards
--
A discussion with Steve suggested looking at when udev updates
/dev/disk/by-uuid - has something changed that stops that directory
being refreshed after partman-base is done (or at least before
bootstrap-base starts)?
I ran some stretch/jessie comparison installs on the following VM system:
Package: lowmem
Version: 1.45
Severity: normal
Poking around an install environment I looked in /lib/main-menu.d
and found these files:
10rescue
5lowmem
Then I found the original commit message:
commit b9741a97a349f9ed4364b3411c3ab8afc590e385
Author: Joey Hess
On Wed, Aug 02, 2017 at 07:58:05PM +0100, Ben Hutchings wrote:
>
> But this still prints error messages for missing modules. I think the
> function should be implemented as:
>
> is_available () {
> modprobe -qn "$1"
> }
>
I agreee, much better!
Package: hw-detect
Version: 1.124
Severity: normal
Tags: patch
I keep seeing this in installer logs, back to jessie.
Aug 2 01:52:11 main-menu[193]: (process:224): modprobe: invalid option -- 'l'
I rated this normal rather than minor because the way it is working
now the is_available()
Tags: patch
Thanks
Can this be fixed please? I wasted an hour tracking this down
while trying to resolve another issue.
--- lib/auto-lvm.sh.org 2017-08-02 10:24:35.773321165 +1000
+++ lib/auto-lvm.sh 2017-08-02 10:24:49.709392154 +1000
@@ -302,7 +302,7 @@
defvgname="$RET"
We noticed this issue today and there is a further aspect to it.
I won't have time to make a proper bug report for a couple of days.
The initrd path that was given to the pxe netboot installer
gets included in the boot command line, to wit:
the promised attachment, inline
uname -a: Linux testbox 4.9.0-3-amd64 #1 SMP Debian 4.9.30-2+deb9u2
(2017-06-26) x86_64 GNU/Linux
lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation Skylake Host
Bridge/DRAM Registers [8086:191f] (rev 07)
lspci -knn: Subsystem: Dell Device [1028:06b9]
On Fri, Jul 28, 2017 at 12:28:58PM +1000, Vincent McIntyre wrote:
> the promised attachment, inline
A perusal of the syslog turned up this
A perusal of the syslog turned up this
Jul 28 01:27:32 grub-installer: info: Installing grub on '/dev/sdc'
Jul 28 01:27:32 grub-installer: info: g
On Tue, Mar 21, 2017 at 09:45:24PM +0100, Baptiste Jammet wrote:
> Hi Vince,
>
> Dixit Vincent McIntyre, le 20/03/2017 :
>
> >> +ifname instead of mac address
> ...
> >Not having really worked with stretch yet (ie target audience member),
> >I'm had no re
On Sun, Mar 19, 2017 at 05:31:53PM +0100, Baptiste Jammet wrote:
Thanks for raising these important items.
...
> +ifname instead of mac address
> +
> +
> +The installer and the installed systems will now use ifnames by default
> +instead of mac for network interface names.
> +
> +
> +
Not
(we were discussing having a branch of manual for each stable release)
This appears to have happened - thanks Samuel!
https://anonscm.debian.org/viewvc/d-i/branches/manual/jessie/
I think it would be worth mentioning the existence of this
in the trunk README - suggested patch below. Please let
Package: installation-guide
Severity: minor
Tags: d-i patch
thanks
(resending as a bug, my post to -boot didn't elicit any replies)
For some years the disable_autoconfig preseed has been shown
in the appendix on preseeding. However setting that just sets
use_autoconfig appropriately. Yet
Hi,
For some years the disable_autoconfig preseed has been shown
in the appendix on preseeding. However setting that just sets
use_autoconfig appropriately. Yet use_autoconfig is not even
mentioned in the appendix, ever.
There might be something I'm missing here, such as disable_autoconfig
is
I just realised this went to the libc maintainers;
I was expecting it would go to the debian-installer team.
This might be an issue in the way libc6-udeb is being used
within debian-installer, rather than libc6-udeb itself.
I don't know how to figure out if that is the case;
if it is the case,
On Thu, Jun 25, 2015 at 05:51:02PM +0100, Justin B Rye wrote:
Vincent McIntyre wrote:
Justin B Rye wrote:
It's good, but I've got a couple of English usage nitpicks:
And I'm happy to have you pick the nits off my contribution :)
Would you care to peruse #789652, which is related
Package: installation-guide
Tags: patch
thanks
see also #760923.
Not sure this is quite correct for powerpc.
Index: manual/en/post-install/shutdown.xml
===
--- manual/en/post-install/shutdown.xml (revision 69984)
+++
On Sun, Jun 09, 2013 at 01:47:36AM +0200, Cyril Brulebois wrote:
Vincent McIntyre vincent.mcint...@csiro.au (30/04/2013):
gah. The patch was not ok. My apologies for such a gross error.
I caught this by testing with 1.86 as downloaded from the archive.
Thanks, Vincent.
Applied locally
On Sun, Jun 09, 2013 at 01:47:36AM +0200, Cyril Brulebois wrote:
Vincent McIntyre vincent.mcint...@csiro.au (30/04/2013):
gah. The patch was not ok. My apologies for such a gross error.
I caught this by testing with 1.86 as downloaded from the archive.
Thanks, Vincent.
Applied locally
the archive.
[PATCH] Actually set bootdev.
After taking all the trouble to get the right value into
the $bootdev shell variable, ensure that we db_set
grub-installer/bootdev with that value.
Signed-off-by: Vincent McIntyre vincent.mcint...@csiro.au
---
grub-installer |8 ++--
1 file
-scan
- don't abuse the 'seen' flag
Signed-off-by: Vincent McIntyre vincent.mcint...@csiro.au
---
debian/grub-installer.templates | 13 +
grub-installer | 99 +--
2 files changed, 109 insertions(+), 3 deletions(-)
diff --git a/debian
Hi Joey
thank you for your helpful comments. I'm working on fixing the issues.
I do have one question because I'm completely new to the translation
side of things...
On Thu, Apr 25, 2013 at 08:28:27AM -0400, Joey Hess wrote:
There are also some hardcoded user-visible strings embedded in the
Sadly, this issue will probably be in wheezy as nobody digged enough
to tackle this down and we get rid of it before the last version of
D-I is released.
Please see my working (for me), tested, waiting-for-review patch [1]
sent to the -boot list yesterday.
Cheers
Vince
[1]
On Thu, Apr 25, 2013 at 09:33:01AM +0200, Gaudenz Steinlin wrote:
Hi Vince
Please see my working (for me), tested, waiting-for-review patch [1]
sent to the -boot list yesterday.
Do you know how the problem can be triggerd. As far as I remember only
some installation from USB are
On Mon, Apr 22, 2013 at 02:38:24PM +1000, Vincent McIntyre wrote:
Hi,
I am attempting to fix the grub-installer issues last referenced in the
thread # d-i wheezy rc2 preparation, take 2. The current state of my
patch is shown at the end of this message. The basic idea is to add a
question
.
This should help the user avoid grub-installer writing to the MBR
of the wrong device (e.g. #696877) and fix the issue of preseeded
values of bootdev being ignored (e.g. #666974).
Signed-off-by: Vincent McIntyre vincent.mcint...@csiro.au
---
debian/grub-installer.templates | 16 +
debian/po
Hi,
I am attempting to fix the grub-installer issues last referenced in the
thread # d-i wheezy rc2 preparation, take 2. The current state of my
patch is shown at the end of this message. The basic idea is to add a
question which lets the user select which disk to use for installation
of the grub
On Mon, Apr 08, 2013 at 02:51:07PM +0200, Cyril Brulebois wrote:
Vincent McIntyre vincent.mcint...@csiro.au (08/04/2013):
May I remind people about #696877 (when installing from USB stick,
grub writes the MBR to the wrong device - the USB stick).
I think this problem has been around
On Fri, Apr 19, 2013 at 10:16:54AM +1000, Vincent McIntyre wrote:
Hokay. Below is a very rough patch.
v2 has a couple of the rough edges knocked off...
diff --git a/debian/grub-installer.templates b/debian/grub-installer.templates
index 888a656..ad840ce 100644
--- a/debian/grub
(please cc: me, not subscribed)
May I remind people about #696877 (when installing from USB stick,
grub writes the MBR to the wrong device - the USB stick).
I think this problem has been around in some form or other in squeeze
(eg #666974) and possibly before and I really think it needs fixing.
(please cc:, not subscribed)
Hi,
I have taken a swing at this, see below.
When writing, one thing that I found particularly confusing is the sentence:
The literalauto/literal boot label is not yet defined everywhere.
_Where_ is it not defined? I'm not understanding what universe that
On Mon, Apr 08, 2013 at 02:51:07PM +0200, Cyril Brulebois wrote:
Vincent McIntyre vincent.mcint...@csiro.au (08/04/2013):
May I remind people about #696877 (when installing from USB stick,
grub writes the MBR to the wrong device - the USB stick).
I think this problem has been around
On Fri, Feb 22, 2013 at 01:17:37AM +0100, Samuel Thibault wrote:
Hello,
Vincent McIntyre, le Tue 19 Feb 2013 14:44:50 +1100, a écrit :
I would like to be able to control IPv6 support via preseeding.
This is not currently mentioned in the preseeding appendix.
Indeed.
Is this patch
Hi,
I would like to be able to control IPv6 support via preseeding.
This is not currently mentioned in the preseeding appendix.
Is this patch sufficient or are there parts I am missing?
Vince
Index: appendix/preseed.xml
===
---
Cyril Brulebois k...@debian.org wrote:
Thank you very much. I guess it might be nice to also mention how to
avoid running into this situation, maybe be preseeding the proper
value at a given stage of the installation. I'll try and figure that
out when testing images later today.
Quite some
2. Manually partition disk on each install
To do this I just don't preseed any partitioning details.
If the installer does not know what to do, it should ask you.
If that doesn't work, does setting just
partman-auto/automatically_partition 80custom__custom
do the trick?
3. Manually
Hi Paul,
you said
Grub install failed:
- proposes to install on first hard drive (as always)
- but first hard drive was the USB stick
- install failed, USB stick not damaged (whew)
- post installation:
- regenerated device map and reinstalled grub bootloader
Is there a good
tags patch
thanks
Hi,
I believe the entirety of the required patch is at the end of this message.
Please consider applying it.
I'd like to make a plea for an easily-findable branch or tag series
for making updates like this to the installation guide which-applies-
to-the-current-'stable'.
When
Hi
I was planning to test the beta1 installer using the netboot images.
I can't see an links on the installer page [1] to relevant beta1 images.
For netinst, there is e.g. [2].
But the equivalent netboot location is [3], poking around in there
reveals no images marked as beta1, but somewhat older
Package: installation-guide
Severity: normal
Tags: patch
Hi
please consider this patch explaining the use of DEBCONF_DEBUG
when debugging a preseeded installation. I found it a helpful tool.
Cheers
Vince
Index: manual/en/appendix/preseed.xml
Hi
please consider this patch explaining the use of DEBCONF_DEBUG
when debugging a preseeded installation. I found it a helpful tool.
Is this the appropriate location within the manual?
Please cc: me in replies, I am not subscribed.
Cheers
Vince
Index: manual/en/appendix/preseed.xml
Package: grub-installer
Version: 1.60+squeeze3
Severity: important
*** Please type your report below this line ***
When I specify in my preseeding file:
d-i partman-auto/disk string /dev/sdb
d-i grub-installer/bootdev string /dev/sdb
grub-installer ignores me
I realised the code fragments I showed are from master, not the
squeeze branch. However I don't think it makes a difference.
Firstly the code parsing grub-mkdevicemap has not changed.
Secondly even if the condition
([ $default_bootdev != '(hd0)' ] \
! partmap
Hi,
I was trying to test something on squeeze/amd64 today.
What I wanted was a daily netboot image [1] so I could PXE boot into rescue
mode. But none of those amd64 dailies are building, according to overview.log.
I tried to fall back to a daily netinst cd image [2].
That fails with a 404 error.
Package: installation-reports
Boot method: network (PXE/DHCP)
Image version:
http://people.debian.org/~joeyh/d-i/images/daily/netboot/
dated 20100826-03:56
# cat /var/log/installer/lsb-release
DISTRIB_ID=Debian
DISTRIB_DESCRIPTION=Debian GNU/Linux installer
DISTRIB_RELEASE=6.0
Hi,
this problem is also occurring on Dell Optiplex 780 machines,
the PCI ID of the network card is 8086:10de.
I tried installing using this netboot image:
http://ftp.au.debian.org/debian/dists/lenny/main/installer-i386/current/images/netboot/debian-installer/i386/
which has the date stamp
Hi,
#492897 has been closed, Add support for mdadm metadata formats 1.x.
Does that change the situation with this bug?
Is the reversion to 0.9 format still being considered, or has it
been decided?
Cheers
Vince
--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject
I think I've identified the issue here. Details at the end.
In short:
partman-auto-raid v15 creates /dev/md0 with a v1.1 superblock.
The version of grub being used (0.97-47lenny2) doesn't handle this
version of the superblock metadata AFAICT (see e.g. #554500).
This seems to be causing the
On Thu, 11 Feb 2010, vincent.mcint...@csiro.au wrote:
The options for resolving it (so lenny-via-squeeze works) seem to be:
- add a debconf configuration item to specify the metadata version
I started a patch but I have absolutely no idea what I'm doing.
The attached is just an attempt to
Package: partman-auto-raid
Version: 15
Severity: wishlist
Tags: patch
Hi,
I found what I think is a minor error in the partman-auto-raid/README
(the elements of the recipes should be separated by periods, not commas).
The attached corrects that and tries to clarify two parts of the text
I
I noticed a small discrepancy in the type for this question.
packages/netcfg/debian/netcfg-dhcp.template says:
Template: netcfg/dhcp_timeout
Type: text
Description: for internal use; can be preseeded
Timeout for trying DHCP
Default: 15
but the documentation[1] says:
# If you have
Found the problem, which is documented but it's somewhat difficult
to parse. This change in my preseed file fixed the issue:
- d-i mirror/udeb/suite string lenny
+ d-i mirror/udeb/suite string testing
Cheers
Vince
--
To UNSUBSCRIBE, email to
Package: installation-guide
Severity: wishlist
Tags: patch
In relation to #552787, I've attempted to improve the relevant text
in the preseeding appendix of the manual. It's a bit wordier (sorry
translators).
Cheers
Vince
Index: trunk/manual/en/appendix/preseed.xml
I've had a quick look at this, I _think_ the attached is all that
is required.
regards
Vince
Index: tzsetup/debian/common.templates.in
===
--- tzsetup/debian/common.templates.in (revision 61048)
+++
Package: installation-reports
Version: [i386][squeeze][20091026-21:55]
Severity: normal
*** Please type your report below this line ***
-- Package-specific info:
Boot method: network
Image version:
http://people.debian.org/~joeyh/d-i/images/daily/netboot/debian-installer/i386/
Package: installation-reports
Severity: normal
*** Please type your report below this line ***
-- Package-specific info:
Boot method: USB key built with netbootin
Image version: Lenny Netinstall
5.0.3 Lenny Official i386 NETINST Binary-1
(20090906-12:06)
Date: 2009-10-05T10:00 GMT
talking to myself again...
Luk Claes wrote...
Feel free to test with the version in proposed-updates to really make
sure it's fixed.
I'm not completely sure how to do this. From what I can gather from [1]
I need to build my own installer image, which I'll have a go at.
I initially
Package: installation-reports
Severity: normal
I cannot netinstall 'etch' with the 'etch' installer.
I am using a well-tested PXE boot setup, see eg #517644.
I selected suite=etch on the installer boot line.
I select ftp.au.debian.org as the mirror in the choose-mirror screen.
After that,
Can someone check that choose-mirror is the correct version please?
And that it actually works?
I reopened #517644 but have had no response after 3+ weeks.
See also #532840, which might be related.
Hopefully this can be sorted out before 5.0.2 goes out.
Thanks
Vince
--
To UNSUBSCRIBE,
package: choose-mirror
tags 517644 + reopen
thanks
Hi,
I just tried to use the lenny installer to install an etch i386 system.
The same issue as before occurs, see the /var/log/installer/syslog
extract below.
I redid the install with suite=oldstable in the PXE boot line and got
the same
I've confirmed this behaviour also occurs when using ftp.au.debian.org as
the mirror, instead of our local apt-proxy.
--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Package: installation-reports
Severity: normal
Boot method: network (PXE/DHCP)
Image version:
http://ftp.au.debian.org/lenny/dists/lenny/main/installer-amd64/current/images/netboot/
The installer image files are marked
This is a Debian 5.0 (lenny) installation netboot image.
It was built
Package: installation-reports
Boot method: network
Image version:
http://people.debian.org/~joeyh/d-i/images/daily/netboot/debian-installer/i386/
DISTRIB_ID=Debian
DISTRIB_DESCRIPTION=Debian GNU/Linux installer
DISTRIB_RELEASE=5.0 (lenny) - installer build 20090121-20:04
Package: debian-installer
Severity: minor
I was trying to install 'etch' with the 'lenny' dailies and I got
caught by the change in the way disks names are handled, ie preseeding
d-i partman-auto/disk string /dev/discs/disc0/disc
no longer works.
I was reading the partman docs and noticed a
Hi,
I'm trying to preseed a machine and am getting stuck on the partitioning.
This email is to ask people to search their memory to see if they recall
a similar problem.
The preseed files I am using work perfectly well with another machine,
that has a smaller hard disk (20Gb vs 40Gb).
I can
package: debian-installer
Version: Debian GNU/Linux installer 4.0 (installer build 20070308etch2)
severity: minor
I was wondering how to set a label on a partition (not a partition
table, but a label that e2label could read).
I couldn't see this documented in [1] so I wrote a patch, attached.
I think this was fixed very recently, if you look back at the traffic
in http://lists.debian.org/debian-boot/2008/07
The installer should at least prompted you to supply a .fw firmware file.
Did it do this?
The firmware can be obtained from the firmware-* packages, e.g.
package: debian-installer
severity: wishlist
Hi,
I was looking at packages/apt-setup/generators/and noticed a
difference between the way that 91security and 92volatile add lines
to the new sources.list file (subversion, r54582):
91security does this -
echo deb http://$host/
Hi,
I was trying to make a recipe that differs only slightly from the
multi_scheme pre-cooked recipe, which has a real /boot and everything
else including swap in an LVM volume group.
The differences were that
* I want a separate, real / partition, with all the others in LVM.
* I don't want a
Hi Jeremy
[ for some reason I did not get an email with your question, only the
bug did... Should I have gotten one if you sent mail just to the bug?
This may have been a transitory problem in our email system.
]
Is this also the last message you see when using Expert Installation?
Yes,
addendum:
see also bug #439462
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=439462
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Package: installation-reports
INSTALL REPORT
Debian-installer-version: lenny i386 hd-media daily 2008.07.21
(see comments for details)
uname -a: (does not boot)
Date: 2008.07.22
Method:
How did you install? Boot from USB key.
What did you boot off? USB key
If network install, from
I tried lenny beta 2, that booted successfully.
http://ftp.nl.debian.org/debian/dists/testing/main/installer-i386/current/images/hd-media/boot.img.gz
md5: 6d3bb654070a821de94774f89dd5d11d
http://cdimage.debian.org/cdimage/lenny_di_beta2/i386/iso-cd/debian-LennyBeta2-i386-netinst.iso
md5:
I tried 20080721 again, to be sure I hadn't muffed the usb install.
I redid the setup of the key, as described in the initial report,
double-checking I did not have the think mounted by usbmount or
whatever while I was zcatting to it.
Same result.
I see 'linux' and 'initrd.gz' all
Vincent, have you made another Debian installation on the same system
since your original installation report (9 Mar 2007)? Did you
experencie a similar issue? If you have not, would you take the time to
boot a recent build of d-i (netboot mini.iso will do) and see if the
problem is still
Package: installation-reports
Boot method: usb key
Image version: [1] lenny beta 1 boot.img.gz, plus [2] netinst .iso image
[1]
http://cdimage.debian.org/cdimage/lenny_di_beta1/i386/iso-cd/debian-testing-i386-netinst.iso
(md5: 23e8300f117a3d305b46a889ba71da83)
[2]
Package: base-config
Version: 2.73
Severity: normal
Hi,
not sure what the severity is, please adjust to suit.
I was examining the /etc/host.conf file on some etch boxes.
host.conf(5) explains that
multi Valid values are on and off. If set to on, the resolv+ library will
return
Package: debian-installer-manual
Severity: minor
Tags: patch
*** Please type your report below this line ***
Hi,
I have been looking into preseeding and partitioning, and noticed what
appears to be an omission in the example code.
The example shows a nice expert recipe but does not include the
Package: debian-installer-manual
Severity: minor
Tags: patch
*** Please type your report below this line ***
Hi,
The coverage of partitioning in the preseeding appendix is quite brief
and I think it would be helpful to point people to the additional
information available in
I've just found something in my preseeding file that seems to change the
story here.
For some reason I had this as the first line of the expert recipe item:
partman-auto/expert_recipe string boot-root
instead of
d-i partman-auto/expert_recipe string boot-root
Argh.
I commented out the
Package: debian-installer
Version: etch 4.0r0
Severity: minor
*** Please type your report below this line ***
Hi,
This issue did not cause any problems during the installation, but I
don't think it is intended behaviour, so I've guessed minor severity.
This seems to be the same problem as
Package: installation-reports
INSTALL REPORT
Debian-installer-version: etch amd64 netinst 4.0r0 (20070308)
uname -a: Linux testhost.atnf.CSIRO.AU 2.6.18-4-amd64 #1 SMP Fri May 4 00:37:33
UTC 2007 x86_64 GNU/Linux
Date: 2007.06.05
Method:
How did you install? netinst cdrom, with 'install'
Package: installation-reports
Boot method: CD, with the command 'install'
Image version: Netinst daily image
http://cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/i386/iso-cd/debian-testing-i386-netinst.iso, version 20070211-2.iso
md5sum: 045f122cd20090fca10772c72f61ab57
Date:
On Mon, 25 Dec 2006, Frans Pop wrote:
apologies for the late response...
I've written a new section explaining the default configuration and how to
configure exim4 after the installation. The new section is intended to be
included in chapter 8 which has some post-installation information.
A
retitle 402851 [i386][netinst][daily 20061212] Dell Optiplex 745 (mostly
successful)
thanks mate
it helps googlers if the machine model name is in the title...
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Package: installation-reports
INSTALL REPORT
Debian-installer-version: etch i386 netinst daily 2006.12.12
md5sum 135db969cce6d94c64adb9f42764581a
uname -a: Linux testhost 2.6.18-3-686 #1 SMP Mon Dec 4 16:41:14 UTC 2006 i686
GNU/Linux
Date: 2006.12.13
Method:
How did you install? netinst
Package: installation-guide
Hi,
in the installation guide, at
http://d-i.alioth.debian.org/manual/en.i386/ch06s03.html
there is a discussion of Configuring Your Mail Transport Agent that
no longer reflects the debian installer (at least as of rc1 or later).
In the d-i tree the text is at
Please understand that I think the default config you've arrived at
is good. I was just a bit surprised that the exim4 step was missing;
when it didn't show up I thought something was amiss.
I understand the wish not to bother people with the questions about
MTA configuration, these can be
Package: installation-reports
Boot method: cdrom, with command install
Image version: Etch RC1 netinst
http://cdimage.debian.org/cdimage/etch_di_rc1/i386/iso-cd/debian-testing-i386-netinst.iso
Date: 2006 Nov 30 0500 GMT
Machine: Dell Poweredge 1850, no raid controller
BIOS A05, MPT
Package: installation-reports
INSTALL REPORT
Debian-installer-version:
http://cdimage.debian.org/cdimage/etch_di_beta3/i386/iso-cd/debian-testing-i386-netinst.iso
uname -a:
Linux tinsley 2.6.16-2-686 #1 Fri Aug 18 19:01:49 UTC 2006 i686 GNU/Linux
Date: 2006-08-23T22_00_00+1000
Method:
How
Package: installation-reports
INSTALL REPORT
Debian-installer-version:
http://cdimage.debian.org/cdimage/etch_di_beta3/i386/iso-cd/debian-testing-i386-netinst.iso
uname -a:
Linux tinsley 2.6.16-2-686 #1 Fri Aug 18 19:01:49 UTC 2006 i686 GNU/Linux
Date: 2006-08-23T22_00_00+1000
Method:
How
Package: installation-reports
INSTALL REPORT
Debian-installer-version:
http://cdimage.debian.org/cdimage/etch_di_beta3/i386/iso-cd/debian-testing-i386-netinst.iso
uname -a:
Linux tinsley 2.6.16-2-686 #1 Fri Aug 18 19:01:49 UTC 2006 i686 GNU/Linux
Date: 2006-09-09T22_00_00+1000
Method:
How
On Wed, 15 Dec 2004, Frans Pop wrote:
On Wednesday 15 December 2004 14:37, Frans Pop wrote:
I've created a new image set that contains all available usb modules on
the initrd. This will only work for sparc64; sparc32 has no additional
usb modules. http://kitenet.net/~joey/tmp/sunblade/2/
I was wondering if discover plays a role here. I noticed a couple
of unknown items in pci.list that match pci ids in my SB100.
The USB controller entry seems correct however
108e1103usb usb-ohciRIO USB
Hmmm. There may be a clue there.
Can you get the output
1 - 100 of 163 matches
Mail list logo