Re: Bug#685268: unblock: isc-dhcp/4.2.4-1
On Sun, Aug 19, 2012 at 12:25:52PM +0200, Cyril Brulebois wrote: Michael Gilbert mgilb...@debian.org (18/08/2012): Andrew hasn't yet made it clear which version he's been planning to support in wheezy [0], but he did upload this one well before the freeze. Nice try: [2012-07-01] Accepted 4.2.4-1 in unstable (low) (Andrew Pollock) Thanks for trying Michael. I'd been desperately trying to get 4.2.4-1 in before the freeze, but Real Life got in the way, and I didn't feel I had a good case for a freeze exception for 4.2.4-1, given it was my own inability to get it in on time that was the reason it got caught up by the freeze. signature.asc Description: Digital signature
Re: [pkg-dhcp-devel] Non-udhcpc DHCP clients in d-i?
On Sun, Jan 23, 2011 at 08:15:43AM +0100, Christian PERRIER wrote: Quoting Matthew Palmer (mpal...@debian.org): Does any architecture use a DHCP client other than udhcpc? netcfg has support for running dhclient and pump, but so far as I can tell (from some grepping around in installer/build/pkg-lists) nobody uses that code. I'm on The code is probably lying there because we *were* using dhclient in the past. We stopped doing so when the ISC DHCP utilities moved from v2 to v3. A udeb is still built by isc-dhcp...but, from install/build/pkg-lists files, no build is using it anymore. CC'ing ISC DHCP maintainers (lead by Andrew Pollock) for more complete advice. I don't know anything, I just work here :-) http://lists.debian.org/debian-boot/2009/06/msg00207.html http://lists.debian.org/debian-boot/2009/07/msg00404.html looks relevant. If I can stop making a udeb, please let me know, I'd love for isc-dhcp not to get stuck in unstable to testing transitions because it happens to make a udeb that isn't needed any more. regards Andrew signature.asc Description: Digital signature
Re: Intending to upload DHCP v4 to unstable (small transition necessary)
Otavio and I had a chat over Jabber, this is just a summary for those people following along at home... On Sat, Jun 26, 2010 at 03:43:21PM -0300, Otavio Salvador wrote: Hello, On Tue, Jun 22, 2010 at 5:13 AM, Adam D. Barratt a...@adam-barratt.org.uk wrote: One thing I should have spotted earlier - the dhcp packages build a udeb, which has changed name with the move to v4; was that discussed with the d-i team? Not that I'm aware of. I pointed Otavio to http://lists.debian.org/debian-boot/2010/03/threads.html#00104 He recalls it now. Looking at the diff it looks like the udeb lacks the Provides/Replaces for the udeb and that will cause a breakage in kfreebsd-*. I've queued up a patch to fix it in netcfg to push as soon as the upload it done for sid. Andrew, can you ping me when doing it? (from D-I POV it can be done). So d-i sounds like they're cool with things. I need to address #551054, which I'll endeavour to do in experimental prior to uploading to unstable. I still await an ACK from the release team. regards Andrew signature.asc Description: Digital signature
Re: Debian Installer is switching to busybox' udhcp client
On Mon, Mar 08, 2010 at 01:38:13AM +0100, Frans Pop wrote: Hi Andrew, Just for your information. Debian Installer is switching to the udhcp client from busybox as the default dhcp client. The switch has already been made in daily built D-I images for most architectures (the kfreebsd ones still use dhcp3). Primairy reason is of course the much smaller size of the client. As far as I'm concerned we should keep the dhcp3-client-udeb around, even if all arches switch to udhcpc. Reason is that netcfg still supports the dhcp3 client, and will automatically prefer it to udhcpc if installed. So it can still be very useful, e.g. for troubleshooting. If/when you make the switch to version 4 (with the rename back to dhcp probably) we'll make sure that netcfg supports that version as well. Thanks for the heads up. regards Andrew signature.asc Description: Digital signature
Signed preseed files?
Hi, This is a bit of a stream of consciousness, so apologies if it's a bit incoherent... A bit of a thought experiment: you want to be able to reliably show that your installation environment hasn't been tampered with. How do you do this? Assuming the installation environment is a PXE-booted, preseeded one, how do you do this? Firstly, you want to validate your installation server. For a PXE boot, you need to verify that pxelinux.0 is what it should be. This can be done out of band, by checking the checksum with what's on a Debian mirror. Next, you want to validate everything under pxelinux.cfg/ This can also be done out of band, by checking the checksum, except this could be locally customised. Hopefully it's easily eyeballed. Next, you want to validate everything referenced by the config in pxelinux.cfg/ There's already an MD5SUMS file on the Debian mirror, e.g. /debian/dists/lenny/main/installer-i386/current/images/MD5SUMS to help with this, but it's not signed. What would it take to GPG sign this? At this point, there's some deviation from the stock supplied netboot config, but let's say there's a preseed file in use. In an ideal world, this would be stored in a revision control system, so it should be able to be verified against this. But could d-i itself also verify the integrity of the preseed file once it was retrieved, if it also retrieved a detached signature? I'm guessing you'd have to pass an argument to d-i to say what key to expect the preseed to be signed by? Then I guess you've just shifted the point of compromise to the PXELINUX config, which has to pass the GPG key ID... Not sure if that's an improvement or not. I guess see what I said earlier about validating these config files. Anyone else got any thoughts on how to improve the non-repudiation of a netbooted d-i install? regards Andrew signature.asc Description: Digital signature
Bug#562122: netcfg: Improve preseeding of network device to use
Package: netcfg Version: 1.51 Severity: wishlist I've just sat through many installs on ThinkPad T41, T43 vintage laptops, using PXE, wired Ethernet, and a preseeded installation. I've preseeded netcfg/choose_interface to auto, to try and avoid the netcfg/choose_interface question being asked. What I suspect is the problem, is the wireless interface is showing link so the question still gets asked. My thoughts on how to extend this functionality was: allow preseeding the interface to use based on: 1) vendor component of the MAC 2) PCI ID 3) some substring of the interface description because preseeding the specific interface by name is a non-starter, due to the way Linux can't consistently enumerate the interfaces. -- System Information: Debian Release: 5.0.3 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.26-2-686 (SMP w/1 CPU core) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Reusing existing partitions
Hi, We have a fairly basic partition layout. Basically we have a a root partition, a swap partition, and a large data partition. d-i currently uses partitions 1, 5 and 7 for these. We want to be able to preserve partition 7 (or even all of them) under normal circumstances and just reformat the filesystem on partition 1 when doing a new install. If a user wants to explicitly do a fully destructive install, then we'd go and repartition (probably producing the same layout) and reformat all filesystems. So, is there a correct way of accomplishing this with d-i? Currently, we'd been running an early_command that erased the first partition, and then we preseeded d-i to use the largest free space. That seems to be causing a second swap partition to be created. If you repeat this process too many times, the partition table starts to look ridiculous :-) We basically want to be able to avoid repartitioning, and just selectively reformat specific filesystems. Can we tell d-i to just avoid partitioning altogether, and the partitioning/formatting logic handled in an external script? regards Andrew signature.asc Description: Digital signature
Bug#490578: partman: Please provide RAID10 support
Package: partman Severity: wishlist I went to try and use the latest Lenny d-i netboot image to PXE boot a machine (using the rescue mode) to construct a RAID10 array before moving the array to another computer. Unfortunately the raid10 kernel module wasn't available, so I was unable to do this from a rescue shell. The absence of the kernel module for the RAID10 personality suggests to me that partman probably isn't supporting RAID10 either, hence this bug. -- System Information: Debian Release: 4.0 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-6-686 Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
/etc/dhcp3/dhclient.conf
Hi, I'm fiddling around the dhcp3-client package to get some support in for the domain-search option (option 119). I noticed that the /etc/dhcp3/dhclient.conf file that is on a system I installed with the daily lenny PowerPC netinst CD from a couple of days ago isn't the one that ships with the dhcp3-client package. Could you please add domain-search to the list of options requested from the DHCP server? Thanks. regards Andrew signature.asc Description: Digital signature
Re: D-I switched to dhcp3-client
On Fri, Jul 13, 2007 at 08:59:37PM +0200, Frans Pop wrote: Hi Andrew, Joey and I have switched over D-I to use the dhcp3-client udeb yesterday. We'll do some basic testing over the next few days, but if you don't hear from us you can assume things are working OK. Excellent. We do still plan to keep looking for a smaller alternative. No worries, fine by me. I hate having the package frozen so early in the release cycle just because it makes udebs. regards Andrew signature.asc Description: Digital signature
dhcp3-client-udeb should work now
Hi, I had another look at #398966 at Debconf, and got to the bottom of it, so aside from the fact that it's bloody huge, it should now be viable for use in d-i. I'm really keen to see the back of the DHCPv2 packages in Debian, so will it be okay to swap d-i to the v3 udeb until such time that a smaller alternative is found? regards Andrew signature.asc Description: Digital signature
Bug#381244: partman-auto-lvm: Always calling the volume group Debian is probably not a good idea
Package: partman-auto-lvm Severity: minor RedHat did something similar. It's a real mess when you have a disk that has been installed in this manner, and you want to pull it out and plug it into another machine that has also been installed in this manner. You end up with duplicate volume group names, and a world of hurt. I would strongly recommend making it more unique and using the hostname of the installation. regards Andrew -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.15-1-686 Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: klibc-dhcp-client and D-I
On Sun, May 21, 2006 at 02:13:11AM +0200, Geert Stappers wrote: The patch applied cleanly, I got a working udeb from it. To make klibc-ipconfig transmit the DHCP vendor class d-i and get the DHCP preseeding filename in a text file, it needs the attached patch. Sweet. So was that all the missing functionality that made ipconfig unsuitable? regards Andrew -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: dhcp3-client and D-I
On Fri, May 19, 2006 at 10:26:12AM +1000, Andrew Pollock wrote: On Tue, May 16, 2006 at 10:43:01PM -0500, Joey Hess wrote: Andrew Pollock wrote: Okay. I've had a preliminary play with ipconfig over the weekend. Seems relatively straightforward to slot it into netcfg's dhcp.c. What I need to understand is the necessity to set a vendor-class-identifier attribute in with the request, is this a nicety or a need-to-have? ipconfig won't do it. It enables useful abilities like setting the appropriate default mirror for all installs to a network. It's a new feature since sarge, so not something a lot of people are using yet but very potentially powerful and useful for larger networks. Yes, I read a related bug report when I was searching for this thread in my email, looks good. Anyway, good news: The recent busybox change that dropped modutils makes the i386 root floppy too large, triggering a lot of reorganisation (and degraded functionality), after which we have enough free space on there for the dhcp 3 client, so turn it back on and we can look at including it. Done. Next upload, hopefully by the weekend at the latest, will include dhcp3-client-udeb again. So said upload finally made it out of NEW the other day... I note in another thread Gert's got a patch that extends the functionality of ipconfig. regards Andrew -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: dhcp3-client and D-I
On Wed, May 17, 2006 at 02:55:02PM +0200, Geert Stappers wrote: On Wed, May 17, 2006 at 01:14:25AM +1000, Andrew Pollock wrote: [ ... ] Okay. I've had a preliminary play with ipconfig over the weekend. Seems relatively straightforward to slot it into netcfg's dhcp.c. What I need to understand is the necessity to set a vendor-class-identifier attribute in with the request, is this a nicety or a need-to-have? ipconfig won't do it. The other thing that ipconfig doesn't currently do is send the hostname with the request, which is an optional feature for some people on cable. That's potentially fixable though, as one of the ways of invoking ipconfig includes a hostname. I've built a udeb from ipconfig, and twiddled with netcfg enough to test it out, I've just been having some problems rebuilding d-i, but I'll try again during the week. Is the source of the ipconfig udeb public available? If yes: Where? I made a privately hacked up udeb, here's the diff: diff -urN klibc-1.3.19/debian/control klibc-udeb/debian/control --- klibc-1.3.19/debian/control 2006-05-18 17:19:59.019824009 -0700 +++ klibc-udeb/debian/control 2006-05-14 16:04:36.159174709 -0700 @@ -37,3 +37,9 @@ full-function counterparts. They are intended for inclusion in initramfs images and embedded systems. +Package: klibc-ipconfig +XC-Package-Type: udeb +Architecture: any +Section: debian-installer +Description: ipconfig built with klibc + This package contains just ipconfig from klibc diff -urN klibc-1.3.19/debian/klibc-ipconfig.install klibc-udeb/debian/klibc-ipconfig.install --- klibc-1.3.19/debian/klibc-ipconfig.install 1969-12-31 16:00:00.0 -0800 +++ klibc-udeb/debian/klibc-ipconfig.install2006-05-17 22:08:10.808005100 -0700 @@ -0,0 +1,2 @@ +debian/tmp/usr/lib/klibc/bin/ipconfig +debian/tmp/lib/klibc*.so diff -urN klibc-1.3.19/debian/lintian/klibc-ipconfig klibc-udeb/debian/lintian/klibc-ipconfig --- klibc-1.3.19/debian/lintian/klibc-ipconfig 1969-12-31 16:00:00.0 -0800 +++ klibc-udeb/debian/lintian/klibc-ipconfig2006-05-14 16:06:01.988320755 -0700 @@ -0,0 +1 @@ +klibc-ipconfig: statically-linked-binary a -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: dhcp3-client and D-I
On Tue, May 16, 2006 at 10:43:01PM -0500, Joey Hess wrote: Andrew Pollock wrote: Okay. I've had a preliminary play with ipconfig over the weekend. Seems relatively straightforward to slot it into netcfg's dhcp.c. What I need to understand is the necessity to set a vendor-class-identifier attribute in with the request, is this a nicety or a need-to-have? ipconfig won't do it. It enables useful abilities like setting the appropriate default mirror for all installs to a network. It's a new feature since sarge, so not something a lot of people are using yet but very potentially powerful and useful for larger networks. Yes, I read a related bug report when I was searching for this thread in my email, looks good. Anyway, good news: The recent busybox change that dropped modutils makes the i386 root floppy too large, triggering a lot of reorganisation (and degraded functionality), after which we have enough free space on there for the dhcp 3 client, so turn it back on and we can look at including it. Done. Next upload, hopefully by the weekend at the latest, will include dhcp3-client-udeb again. Looks like netcfg already supports sending the vendor-class-identifier with dhcp3. Are there any changes to the dhclient-script interface that we will need to look out for? I don't think so. I think we need to do some merging between what's floating around in d-i and what goes in the dhcp3-client-udeb, as I think either a dhclient.conf or dhclient-script is also shipping somewhere else, unless you'd rather do it this way. regards Andrew -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: dhcp3-client and D-I
On Tue, May 16, 2006 at 06:54:55AM +0200, Noèl Köthe wrote: Am Sonntag, den 14.05.2006, 09:10 +1000 schrieb Andrew Pollock: Hello Andrew, we had the D-I BoF here at Debconf6 some hours ago. 1. the D-I will use 2 but 3 will be install on the system which is installed Sounds good. Yes, but the idea was rejected. They want to use the same version which they want to install on the system (like the kernel, too). With the removal of the kernel 2.4 from the bootfloppies there might be more space on them but its not known how much exactly. Joeyh will check this but the only alternative then will be reducing the size with removing unneeded functions/extensions for the dhclient for the udeb (dhcp3-client-tiny;)). If I find out more I will inform you. Okay. I've had a preliminary play with ipconfig over the weekend. Seems relatively straightforward to slot it into netcfg's dhcp.c. What I need to understand is the necessity to set a vendor-class-identifier attribute in with the request, is this a nicety or a need-to-have? ipconfig won't do it. The other thing that ipconfig doesn't currently do is send the hostname with the request, which is an optional feature for some people on cable. That's potentially fixable though, as one of the ways of invoking ipconfig includes a hostname. I've built a udeb from ipconfig, and twiddled with netcfg enough to test it out, I've just been having some problems rebuilding d-i, but I'll try again during the week. regards Andrew -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Integrating klibc's ipconfig into netcfg
Hello, I've been meaning to do this for probably a year, but I've finally gotten around to actually looking into what is involved in using ipconfig in netcfg as a replacement to dhcp-client, so we can get rid of DHCPv2 altogether. The first observation I've made is that it doesn't appear to pass the hostname in the request. I'm attempting to clarify this with the author at the moment, but if someone with more C-fu than myself wants to take a look, I'd appreciate it. If indeed this is the case, is this a show stopper? I recall some bugs filed in the past from people trying to install on a cable connection where the cable provider required the hostname in order to issue a lease, so I'm assuming it is. regards Andrew signature.asc Description: Digital signature
Re: Integrating klibc's ipconfig into netcfg
On Sun, May 14, 2006 at 11:00:59PM +0200, Geert Stappers wrote:
On Mon, May 15, 2006 at 03:33:08AM +1000, Andrew Pollock wrote:
Hello,
I've been meaning to do this for probably a year, but I've finally gotten
around to actually looking into what is involved in using ipconfig in netcfg
as a replacement to dhcp-client, so we can get rid of DHCPv2 altogether.
The first observation I've made is that it doesn't appear to pass the
hostname in the request.
In dhcp.c is this code snippet:
| case DHCLIENT:
| /* First, set up dhclient.conf */
|
| if ((dc = file_open(DHCLIENT_CONF, w)))
| {
| fprintf(dc, send dhcp-class-identifier \d-i\;\n );
| if (dhostname)
| {
| fprintf(dc, send host-name \%s\;\n, dhostname);
| }
| fclose(dc);
| }
So only when dhostname is set, it sends the hostname in the request.
Yup, I figured it wasn't something that happened all the time.
I'm attempting to clarify this with the author at the moment,
but if someone with more C-fu than myself wants to take a look,
I'd appreciate it.
I hope the above text did help.
If indeed this is the case, is this a show stopper? I recall some bugs filed
in the past from people trying to install on a cable connection where the
cable provider required the hostname in order to issue a lease, so I'm
assuming it is.
Beside sending the hostname for cable providers,
there is also the need to send dhcp-class-identifier d-i,
to allow DHCP preseeding.
I think that getting it to set random options is going to be a big ask, it's
too lightweight for that. Might be back to the drawing board...
Does that mean the that cases there are largely irrelevant? I mean pump
doesn't appear to support setting that vendor-class-identifier option...
regards
Andrew
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Create software raid array during install, error when filesystems is created.
On Tue, Jan 11, 2005 at 10:37:38PM +0100, Bj?rn Nilsson wrote: Thank you for looking into this issue. What you describe is what I was trying to do. Did not quite understand the basic concepts of RAID I guess, but now I think I get it. What I did: I marked the newly created RAID0 volume and pressed enter, and I got a question if I wanted to create a new partiton table on it, and what type it should be. Options was msdos and a whole bunch of other types (this menu coming up is a bug?). Yes, possibly. The way to do it is you partition your disk as normal, and mark the partition as a RAID volume. Then, after completing partitioning, you configure RAID, creating your RAID device. You then create a filesystem on it, or use it as a physical volume for LVM. If you do the latter, you then create your VG(s) from the PV, and then create LV(s) from your VG(s) and then create filesystems on your LV(s). I then created partitions on the RAID0 volume (hda1, hda5, hda6 etc) and this being possible is a bug too? Possibly. I haven't put a lot of thought into it at the moment, I was more concerned about setting you straight on how it should be done. Clearly, if partman's allowing you do stuff that is Plain Wrong (tm) it's a deficiency in the interface if not a bug. Hope this helps. regards Andrew
Re: Create software raid array during install, error when filesystems is created.
On Thu, Jan 06, 2005 at 10:07:48PM +0100, Bj?rn Nilsson wrote: Hi, I have 2 equally sized IDE PATA disks. I created a partition covering the whole drive on each disk, the partition type was raid. I created a software RAID0 array, and in turn created partitions on it and set them to ReiserFS. So you created one big RAID partition, and then made partitions in it? This is contrary to the way RAID on Linux works, and if partman allowed you to do it, that's a bug, and explains what happened next... In the next step, When the filesystem are supposed to be created a get a red screen telling me: Failed to create ReiserFS part1 on RAID0- unit0. If i swich to the third virtual console i see this messsage: Stat of the device /dev/md/0/part1 failed. I have tried RAID1 also, ext3 instead of Reiser. Also tried to use the LVM to set up a volume group and so on, all with about the same result, failure when creating file system. So I installed on just 1 drive as normal, and that worked fine (impressive stuff with the hw autodetection btw!) I have tried with rc2 and nightly build from 2005-01-05, same result I read some problems with lilo or grub when using software raid, but that seems unrelated becouse this is well before any bootloader is installed. If you want to do what you've described, you'll need to put LVM over the top of the RAID0 volume, and create multiple logical volumes out of it, and treat them as you would partitions. regards Andrew -- linux.conf.au 2005 - http://linux.conf.au/ - Birthplace of Tux April 18th to 23rd - http://linux.conf.au/ - LINUX Canberra, Australia - http://linux.conf.au/ -Get bitten! signature.asc Description: Digital signature
Re: [WISHLIST] Choosing the ESSID in the non expert mode of the debian-installer
On Wed, Dec 08, 2004 at 07:43:27PM +0100, Florent CHANTRET wrote: [snip] I have a little wish about the Debian installer. If you detect a WIFI network card, you prompt for the WEPKEY but not for the ESSID. It's a bit frustrating cause if someone know the WEPKEY, chance he knows the ESSID too. Moreover, someone securing a WIFI network with a WEPKEY will often secure it by disabling DHCP, disabling ESSID broadcasting and the default any ESSID won't work. From there, 2 options (for a skilled user) : - Switching to a console and editing /etc/network/interface to change the ESSID - Installing in expert mode What a pity to boot in expert mode only for an ESSID. So, in my own opinion, there is two solutions : - Considering that knowing a WIFI WEPKEY is for experts, only prompt for it in expert mode - Or better, in standard mode, prompt for the ESSID but with the any default value. It's a little stuff but would be appreciable for a skilled WIFI user that don't know much of Debian (first install of a Debian for example) and would be disappointed if it can''t enter it. He would probably not be skilled enough to swith to a console during the net install process. Every time I've done an install lately (and I _haven't_ done one in expert mode for absolutely ages) I've been prompted for the ESSID prior to providing the WEP key. I have a pretty simple Access Point, and as far as I know, it broadcasts its ESSID. regards Andrew -- linux.conf.au 2005 - http://lca2005.linux.org.au/ - Birthplace of Tux April 18th to 23rd - http://lca2005.linux.org.au/ - LINUX Canberra, Australia - http://lca2005.linux.org.au/ -Get bitten! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#283780: Install report: rc2 on PowerBook G3, all good, but miss LVM
Package: installation-reports INSTALL REPORT Debian-installer-version: rc2 uname -a: Linux andrewpollock 2.6.8-powerpc #1 Sun Oct 3 13:22:21 CEST 2004 ppc GNU/Linux Date: Wed Dec 1 21:15:24 EST 2004 Method: netinst CD Machine: Apple PowerBook G4 Processor: Memory: Root Device: IDE? SCSI? Name of device? Root Size/partition table: /dev/hda #type name length base ( size ) system /dev/hda1 Apple_partition_map Apple 63 @ 1 ( 31.5k) Partition map /dev/hda2 Apple_HFS Apple_HFS_Untitled_2 83623936 @ 262208( 39.9G) HFS /dev/hda3 Apple_Bootstrap bootstrap 1602 @ 64 (801.0k) NewWorld bootblock /dev/hda4 Apple_Free Extra 260542 @ 1666 (127.2M) Free space /dev/hda5 Apple_UNIX_SVR2 swap 101 @ 84886145 (488.3M) Linux swap /dev/hda6 Apple_UNIX_SVR2 root39062501 @ 85886146 ( 18.6G) Linux native /dev/hda7 Apple_Free Extra101 @ 83886144 (488.3M) Free space /dev/hda8 Apple_Free Extra 31352841 @ 124948647 ( 15.0G) Free space FilesystemType Size Used Avail Use% Mounted on /dev/hda6 ext3 20G 271M19G 2% / tmpfstmpfs 264M 0 264M 0% /dev/shm Block size=512, Number of Blocks=156301488 DeviceType=0x0, DeviceId=0x0 Output of lspci and lspci -n: :00:0b.0 Host bridge: Apple Computer Inc. UniNorth 2 AGP :00:10.0 VGA compatible controller: ATI Technologies Inc RV350 [Mobility Radeon 9600 M10] 0001:01:0b.0 Host bridge: Apple Computer Inc. UniNorth 2 PCI 0001:01:12.0 Network controller: Broadcom Corporation BCM4306 802.11b/g Wireless LAN Controller (rev 03) 0001:01:13.0 CardBus bridge: Texas Instruments PCI1510 PC card Cardbus Controller 0001:01:17.0 ff00: Apple Computer Inc. KeyLargo/Intrepid Mac I/O 0001:01:18.0 USB Controller: Apple Computer Inc. KeyLargo/Intrepid USB 0001:01:19.0 USB Controller: Apple Computer Inc. KeyLargo/Intrepid USB 0001:01:1a.0 USB Controller: Apple Computer Inc. KeyLargo/Intrepid USB 0001:01:1b.0 USB Controller: NEC Corporation USB (rev 43) 0001:01:1b.1 USB Controller: NEC Corporation USB (rev 43) 0001:01:1b.2 USB Controller: NEC Corporation USB 2.0 (rev 04) 0002:06:0b.0 Host bridge: Apple Computer Inc. UniNorth 2 Internal PCI 0002:06:0d.0 ff00: Apple Computer Inc. UniNorth/Intrepid ATA/100 0002:06:0e.0 FireWire (IEEE 1394): Apple Computer Inc. UniNorth 2 FireWire (rev 81) 0002:06:0f.0 : Apple Computer Inc. UniNorth 2 GMAC (Sun GEM) (rev ff) :00:0b.0 0600: 106b:0034 :00:10.0 0300: 1002:4e50 0001:01:0b.0 0600: 106b:0035 0001:01:12.0 0280: 14e4:4320 (rev 03) 0001:01:13.0 0607: 104c:ac56 0001:01:17.0 ff00: 106b:003e 0001:01:18.0 0c03: 106b:003f 0001:01:19.0 0c03: 106b:003f 0001:01:1a.0 0c03: 106b:003f 0001:01:1b.0 0c03: 1033:0035 (rev 43) 0001:01:1b.1 0c03: 1033:0035 (rev 43) 0001:01:1b.2 0c03: 1033:00e0 (rev 04) 0002:06:0b.0 0600: 106b:0036 0002:06:0d.0 ff00: 106b:003b 0002:06:0e.0 0c00: 106b:0031 (rev 81) 0002:06:0f.0 : 106b:0032 (rev ff) Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot worked:[O] Configure network HW: [O] Config network: [O] Detect CD: [O] Load installer modules: [O] Detect hard drives: [O] Partition hard drives: [O] Create file systems:[O] Mount partitions: [O] Install base system:[O] Install boot loader:[O] Reboot: [O] Comments/Problems: Still no LVM support? Partman tantalisingly has the Configure LVM option but there's still no way to make an LVM PV that I can see... -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#282458: Install report: sid_d-i on a Dell Latitude D600
Package: installation-reports INSTALL REPORT Debian-installer-version: sid_d-i 20041121 uname -a: Linux debian 2.6.8-1-686 #1 Thu Nov 11 13:18:29 EST 2004 i686 GNU/Linux (I manually installed the 686 kernel after the install) Date: Mon Nov 22 20:02:49 EST 2004 Method: netinst CD Machine: Dell Latitude D600 Processor: Intel(R) Pentium(R) M processor 1.60GHz Memory: 512M Root Device: IDE, /dev/hda Root Size/partition table: major minor #blocks name 3 0 39070080 hda 3 1 20482843 hda1 3 2 498015 hda2 3 3 498015 hda3 3 4 17591175 hda4 254 02097152 dm-0 254 12097152 dm-1 254 21048576 dm-2 254 32097152 dm-3 FilesystemType Size Used Avail Use% Mounted on /dev/hda2 ext3 478M 115M 338M 26% / tmpfstmpfs 265M 0 265M 0% /dev/shm /dev/mapper/base-home ext3 2.1G 8.5M 1.9G 1% /home /dev/mapper/base-tmp ext3 1.1G 8.5M 945M 1% /tmp /dev/mapper/base-usr ext3 2.1G 221M 1.7G 12% /usr /dev/mapper/base-var ext3 2.1G 450M 1.5G 24% /var Output of lspci and lspci -n: :00:00.0 Host bridge: Intel Corp. 82855PM Processor to I/O Controller (rev 03) :00:01.0 PCI bridge: Intel Corp. 82855PM Processor to AGP Controller (rev 03) :00:1d.0 USB Controller: Intel Corp. 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #1 (rev 01) :00:1d.1 USB Controller: Intel Corp. 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #2 (rev 01) :00:1d.2 USB Controller: Intel Corp. 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #3 (rev 01) :00:1d.7 USB Controller: Intel Corp. 82801DB/DBM (ICH4/ICH4-M) USB 2.0 EHCI Controller (rev 01) :00:1e.0 PCI bridge: Intel Corp. 82801 PCI Bridge (rev 81) :00:1f.0 ISA bridge: Intel Corp. 82801DBM LPC Interface Controller (rev 01) :00:1f.1 IDE interface: Intel Corp. 82801DBM (ICH4) Ultra ATA Storage Controller (rev 01) :00:1f.5 Multimedia audio controller: Intel Corp. 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) AC'97 Audio Controller (rev 01) :00:1f.6 Modem: Intel Corp. 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) AC'97 Modem Controller (rev 01) :01:00.0 VGA compatible controller: ATI Technologies Inc Radeon R250 Lf [Radeon Mobility 9000 M9] (rev 02) :02:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5705M Gigabit Ethernet (rev 01) :02:01.0 CardBus bridge: O2 Micro, Inc. OZ711EC1 SmartCardBus Controller (rev 20) :02:01.1 CardBus bridge: O2 Micro, Inc. OZ711EC1 SmartCardBus Controller (rev 20) :02:03.0 Network controller: Intel Corp. PRO/Wireless 2200BG (rev 05) :00:00.0 0600: 8086:3340 (rev 03) :00:01.0 0604: 8086:3341 (rev 03) :00:1d.0 0c03: 8086:24c2 (rev 01) :00:1d.1 0c03: 8086:24c4 (rev 01) :00:1d.2 0c03: 8086:24c7 (rev 01) :00:1d.7 0c03: 8086:24cd (rev 01) :00:1e.0 0604: 8086:2448 (rev 81) :00:1f.0 0601: 8086:24cc (rev 01) :00:1f.1 0101: 8086:24ca (rev 01) :00:1f.5 0401: 8086:24c5 (rev 01) :00:1f.6 0703: 8086:24c6 (rev 01) :01:00.0 0300: 1002:4c66 (rev 02) :02:00.0 0200: 14e4:165d (rev 01) :02:01.0 0607: 1217:7113 (rev 20) :02:01.1 0607: 1217:7113 (rev 20) :02:03.0 0280: 8086:4220 (rev 05) Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot worked:[O] Configure network HW: [O] Config network: [O] Detect CD: [O] Load installer modules: [O] Detect hard drives: [O] Partition hard drives: [O] Create file systems:[O] Mount partitions: [O] Install base system:[O] Install boot loader:[O] Reboot: [O] Comments/Problems: No problems. It all went well. It didn't detect my builtin Centrino wireless adapter, but I don't think anything is detecting it. I've got to go visit Intel's website once the desktop task finishes downloading and installing. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: lilo/grub image background? [was Re: bootsplash option for d-i?]
On Tue, Nov 16, 2004 at 08:06:25PM +0100, Xan wrote: Since we're mentioning Ubuntu, the reason we rejected the bootsplash patch for the Ubuntu kernel was that including it broke the part of the installer that starts up the framebuffer in a way that we concluded was impossible to repair within the design of bootsplash. And what's about lilo/grub background image?. Is that an option in d-i? Perhaps an interesting thing: if we could not have the bootsplash, we could have lilo/grub graphical display. I believe that boils down to the grub and lilo packages providing one, and there being a consensus on what the image should be... I have also heard that in certain combinations of hardware, kicking into the video mode required to display the graphic causes issues, so in the interests of reliability, it has been left alone. regards Andrew -- linux.conf.au 2005 - http://lca2005.linux.org.au/ - Birthplace of Tux April 18th to 23rd - http://lca2005.linux.org.au/ - LINUX Canberra, Australia - http://lca2005.linux.org.au/ -Get bitten! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: lilo/grub image background? [was Re: bootsplash option for d-i?]
On Tue, Nov 16, 2004 at 10:09:09PM +0100, Xan wrote: Okay. Thanks. I see that debian seems less-graphical than another distro veyr long time :) Yeah, it's that whole lowest-common-denominator-across-11-architectures thing... regards Andrew -- linux.conf.au 2005 - http://lca2005.linux.org.au/ - Birthplace of Tux April 18th to 23rd - http://lca2005.linux.org.au/ - LINUX Canberra, Australia - http://lca2005.linux.org.au/ -Get bitten! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: bootsplash option for d-i?
On Mon, Nov 15, 2004 at 03:01:23PM +0100, Xan wrote: Dilluns 15 Novembre 2004 05:45, en/na Andrew Pollock (Andrew Pollock [EMAIL PROTECTED]) va escriure: I fully understand the reasoning behind the kernel team's rejection of this patch, What is this reasoning? I'm not subscribed to the debian-kernel list. I want to know that. Take a look at http://lists.debian.org/debian-kernel/2004/06/msg00590.html regards Andrew -- linux.conf.au 2005 - http://lca2005.linux.org.au/ - Birthplace of Tux April 18th to 23rd - http://lca2005.linux.org.au/ - LINUX Canberra, Australia - http://lca2005.linux.org.au/ -Get bitten! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: bootsplash option for d-i?
On Mon, Nov 15, 2004 at 04:19:18PM +, Colin Watson wrote: On Mon, Nov 15, 2004 at 03:45:42PM +1100, Andrew Pollock wrote: On Sun, Nov 14, 2004 at 04:47:02PM +0100, Sven Luther wrote: Notice that the debian-kernel team has refused the bootsplash patch in its current implementation, so there will be no bootsplash kernel in debian anytime soon, and this is at best a post-sarge discussion. I fully understand the reasoning behind the kernel team's rejection of this patch, but it is kinda sad nonetheless... I marvelled at how someone's Fedora install booted up the other day, and was similiarly impressed with the Ubuntu Live CD. Since we're mentioning Ubuntu, the reason we rejected the bootsplash patch for the Ubuntu kernel was that including it broke the part of the installer that starts up the framebuffer in a way that we concluded was impossible to repair within the design of bootsplash. Yeah I get the impression that bootsplash as it currently stands is really poorly implemented, it's just got a feature that everyone really wants to have. Bring on bootsplash MkII. -- linux.conf.au 2005 - http://lca2005.linux.org.au/ - Birthplace of Tux April 18th to 23rd - http://lca2005.linux.org.au/ - LINUX Canberra, Australia - http://lca2005.linux.org.au/ -Get bitten! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: bootsplash option for d-i?
On Sun, Nov 14, 2004 at 04:47:02PM +0100, Sven Luther wrote: On Sat, Nov 13, 2004 at 09:52:03PM +0100, Xan wrote: Hi, I just want to know if in the new debian installer is considered the possibility that the user could select a bootsplash kernel: - I think that it were cool for desktop users. So perhaps in novice mode d-i could ask to user if he/she wants a boot with image or not; or not, maybe a desktop user don't want to see this kind of questions (it's a topic for discusion, maybe). But in expert mode, I think it should be included. - I think that what splash is the default should be a discussion topic. But, in meantime, we could have debblue [http://debblue.debian.net/]. Personally, I wish an animated spiral debian logo that grows more and more as progress bar (a complete spiral is 100% of boot process). But it's an idea and probably implies more work (better use done work). Notice that the debian-kernel team has refused the bootsplash patch in its current implementation, so there will be no bootsplash kernel in debian anytime soon, and this is at best a post-sarge discussion. I fully understand the reasoning behind the kernel team's rejection of this patch, but it is kinda sad nonetheless... I marvelled at how someone's Fedora install booted up the other day, and was similiarly impressed with the Ubuntu Live CD. I know it's only aesthetics, but perception is reality... -- linux.conf.au 2005 - http://lca2005.linux.org.au/ - Birthplace of Tux April 18th to 23rd - http://lca2005.linux.org.au/ - LINUX Canberra, Australia - http://lca2005.linux.org.au/ -Get bitten! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Debian installer and non-official drivers
On Thu, Oct 28, 2004 at 04:38:05AM -0400, Joey Hess wrote: Cajus Pollmeier wrote: Just one question. Lets say I'd put some extra driver modules for hardware not officially supported by the debian installer on a floppy disk (in form of an a .udeb) and let the installer load this file during the installation in order to detect the additional hardware. Would this udeb get installed into my target system later on? If this additional driver is needed for i.e. disk access, it should be placed in the initrd when the target kernel gets installed. It would not. You can however include a udeb on your floppy that installs a prebaseconfig hook script which would run after the base system is installed, or a base-installer hook script which would run just before base is installed (or perhaps both), and at that point do one of these things, in approximate order of difficulty and inverse order of cleanliness and desirability: a. copy the module into /target from the d-i system b. install a .deb of the module into /target from the floppy c. add something to sources.list for the apt repository you should have that contains the .deb, and then use apt-install to get it installed We probably want to make sure that this is pretty clearly documented for vendors who may wish to provide their own third party drivers. It may be wishful thinking on my behalf, but it'd be nice if we can be incorporating as possible, so vendors aren't throwing up their hands (any more than they already are) when it comes to having Debian as a platform they're prepared to support... regards Andrew -- linux.conf.au 2005 - http://lca2005.linux.org.au/ - Birthplace of Tux April 18th to 23rd - http://lca2005.linux.org.au/ - LINUX Canberra, Australia - http://lca2005.linux.org.au/ -Get bitten! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#278496: Comments on RAID in partman
On Wed, Oct 27, 2004 at 05:53:31AM -0400, Matthew P McGuire wrote: Overall the installtion of the box using the daily build was not a problem. I used the daily build to try out the RAID support recently added to partman. Everything worked absolutely great after I figured out one small catch with /boot partition. It appears that when using software RAID it is necessary to have the /boot part on at least one partition outside of the array so that grub or lilo can be installed. Without knowing this I went through a number of trial and error configurations until I had the array set up correctly. Initially I mistakenly tried to make the RAID array bootable using the interface. This failed on all partition attempts. It occurred to me that a boot block on the RAID didn't make sense, so it may be wise to remove the ability to flag the /dev/md devices as bootable. As a result the /boot partition was necessary. I would recommend adding a dialog that the /boot partition is necessary for root raid installations. This will help other new users of the RAID installation tools to avoid these mistakes. You can boot from a RAID volume. I think there's currently a bug with lilo-installer, where it doesn't quite get it right... regards Andrew -- linux.conf.au 2005 - http://lca2005.linux.org.au/ - Birthplace of Tux April 18th to 23rd - http://lca2005.linux.org.au/ - LINUX Canberra, Australia - http://lca2005.linux.org.au/ -Get bitten! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: lvm on raid
On Sun, Oct 24, 2004 at 02:16:24PM -0400, Joey Hess wrote:
Andrew Pollock wrote:
Patch attached. Will submit it to the BTS shortly. I'm doing some tests with
qemu, but it's slooow. Would appreciate some testing by others...
Wouldn't this behave badly if the user selected 0 partitions? An array
in degraded mode of zero partitions probably won't work.. Are there any
other lower bounds it should check to ensure that the result is a usable
array, even if in degraded mode?
There's a loop that doesn't exit until the user has selected at least one
partition. I tested that, and it works fine. It works the same way mdcfg
currently does if the user doesn't select two partitions.
This part of my patch:
- # Loop until the correct amount of active devices has been selected
- while [ ${SELECTED} -ne ${DEV_COUNT} ]; do
+ # Loop until at least one device has been selected
+ until [ ${SELECTED} -gt 0 -a ${SELECTED} -le ${DEV_COUNT} ];
regards
Andrew
--
linux.conf.au 2005 - http://lca2005.linux.org.au/ - Birthplace of Tux
April 18th to 23rd - http://lca2005.linux.org.au/ - LINUX
Canberra, Australia - http://lca2005.linux.org.au/ -Get bitten!
signature.asc
Description: Digital signature
Re: LVM on software RAID - LILO
On Sat, Oct 23, 2004 at 07:00:47PM +0300, Fabian Fagerholm wrote: On Sat, 2004-10-09 at 21:16 +0300, Fabian Fagerholm wrote: I tried the following (3 x HDD): In partman, set up the three disks to have identical partition tables: * A small primary partition with boot flag set. * A large logical partition. * A small logical partition. I then took all the small primary partitions and created a RAID1 out of them (/dev/md/0). I put /boot on this (ReiserFS). Then, I took the large logical partitions and created a RAID5 out of them (/dev/md/1). The small logical partitions were marked as swap. I manually ran pvcreate and vgcreate on /dev/md/1. Then, using partman, I added logical volumes for /, /usr, /var, /home and /tmp. Still using partman, I assigned the mount points and chose to format all logical volumes as ReiserFS. Partman finished its work. However, as a result of this, GRUB install was disabled, and LILO was to be used instead. LILO install didn't work; I tried specifying the first disk's MBR manually but LILO failed whatever I tried. Am I right in assuming that both LILO and GRUB should work, since they can read the kernel image and initrd from one of the disks in the RAID1 array that comprises /boot, and the initrd contains all neccessary things to access / on RAID5 and LVM? Ie. is it enough that /boot is on RAID1 or plain partition with no LVM? I just tried with a cd image downloaded from the following url: http://cdimage.debian.org/pub/cdimage-testing/daily/i386/current/sarge-i386-netinst.iso The build date was 22-Oct-2004. It's now possible to mark a RAID array for use with LVM. However, if I do the above, the installer disables GRUB, and LILO refuses to install to the default option (/dev/md1: Master Boot record) which seems to be wrong for this kind of setup. I expected to see /dev/md0 as the default. I tried installing on /dev/md0 and /dev/ide/host0/bus0/target0/lun0/disc, but I just got the error messages The path /dev/md0 does not represent a partition of a hard disk device and Running /sbin/lilo failed with error code 1. However, it does seem that it's impossible to do what I wanted. When I adjusted the scenario, I got everything to work. I split up the three disks into three partitions: * A primary partition with the boot flag set, * a large logical partition and * a small logical partition. I then marked the primary partitions for RAID use, the large logical partition for RAID use, and the small logical partition as swap. Then, I assembled a RAID1 with the three primary partitions, and a RAID5 with the three large logical partitions. After that (and here's the key difference), I chose to format the RAID1 as ReiserFS and mount it as /, and created an LVM volume group on the RAID5, which I populated with logical volumes for /usr, /var, /home and /tmp. All partitions were ReiserFS. This worked like a charm, and GRUB was nicely installed. So: it should be clearly documented that it is not possible, in any way, to put your / on RAID5, not with GRUB and not with LILO. My assumption that it would be enough for the boot loader to access the initrd from one of the disks in the RAID1 array (with /boot on it) to be able to access / on RAID5 was apparently not correct -- or at least it doesn't work in d-i when installing the boot loader. Perhaps it would work if booting off another medium and skipping the installation of a boot loader in d-i. I think you struct the same lilo-installer bug that I did yesterday, when I was doing some RAID1 experiments. I told it to use /dev/discs/disc0/disc and it installed fine, iirc. Joey said it's a known bug. -- linux.conf.au 2005 - http://lca2005.linux.org.au/ - Birthplace of Tux April 18th to 23rd - http://lca2005.linux.org.au/ - LINUX Canberra, Australia - http://lca2005.linux.org.au/ -Get bitten! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: lvm on raid
On Wed, Oct 20, 2004 at 01:30:38PM +0200, Christian Perrier wrote:
Quoting Andrew Pollock ([EMAIL PROTECTED]):
That's a shame. I would have thought it'd be relatively easy to implement,
but I haven't given the innards of what's involved close inspection...
Well, the non easiest thing is maybe getting someone volunteering for
implementing this..:-)
:-)
Patch attached. Will submit it to the BTS shortly. I'm doing some tests with
qemu, but it's slooow. Would appreciate some testing by others...
regards
Andrew
--
linux.conf.au 2005 - http://lca2005.linux.org.au/ - Birthplace of Tux
April 18th to 23rd - http://lca2005.linux.org.au/ - LINUX
Canberra, Australia - http://lca2005.linux.org.au/ -Get bitten!
Common subdirectories: mdcfg-1.06/debian and mdcfg-1.07/debian
diff -u mdcfg-1.06/mdcfg.sh mdcfg-1.07/mdcfg.sh
--- mdcfg-1.06/mdcfg.sh 2004-09-30 05:59:27.0 +1000
+++ mdcfg-1.07/mdcfg.sh 2004-10-24 14:15:30.0 +1000
@@ -222,19 +222,12 @@
db_get mdcfg/raid1sparecount
SPARE_COUNT=${RET}
REQUIRED=$(($DEV_COUNT + $SPARE_COUNT))
- if [ $REQUIRED -gt $NUM_PART ] ; then
- db_subst mdcfg/notenoughparts NUM_PART ${NUM_PART}
- db_subst mdcfg/notenoughparts REQUIRED ${REQUIRED}
- db_input critical mdcfg/notenoughparts
- db_go mdcfg/notenoughparts
- return
- fi
db_set mdcfg/raid1devs
SELECTED=0
- # Loop until the correct amount of active devices has been selected
- while [ ${SELECTED} -ne ${DEV_COUNT} ]; do
+ # Loop until at least one device has been selected
+ until [ ${SELECTED} -gt 0 -a ${SELECTED} -le ${DEV_COUNT} ]; do
db_subst mdcfg/raid1devs COUNT ${DEV_COUNT}
db_subst mdcfg/raid1devs PARTITIONS ${PARTITIONS}
db_input critical mdcfg/raid1devs
@@ -251,6 +244,12 @@
done
done
+ # Add missing for as many devices as weren't selected
+ while [ ${SELECTED} -lt ${DEV_COUNT} ]; do
+ MISSING_DEVICES=${MISSING_DEVICES} missing
+ let SELECTED++
+ done
+
# Remove partitions selected in raid1devs from the PARTITION list
db_get mdcfg/raid1devs
@@ -310,7 +309,7 @@
echo Raid devices count: ${DEV_COUNT}
echo Spare devices count: ${SPARE_COUNT}
echo Commandline:
- `mdadm --create /dev/md/${MD_NUM} --force -R -l raid1 -n ${DEV_COUNT} -x
${SPARE_COUNT} ${RAID_DEVICES} ${SPARE_DEVICES} ${MISSING_SPARES}`
+ `mdadm --create /dev/md/${MD_NUM} --force -R -l raid1 -n ${DEV_COUNT} -x
${SPARE_COUNT} ${RAID_DEVICES} ${MISSING_DEVICES} ${SPARE_DEVICES} ${MISSING_SPARES}`
}
md_create_raid5() {
Only in mdcfg-1.07/: .mdcfg.sh.swp
signature.asc
Description: Digital signature
Re: lvm on raid
On Sun, Oct 17, 2004 at 02:46:54PM -0400, Joey Hess wrote: martin f krafft wrote: So yesterday I tried d-i snapshot 20041005. I won't file an installation report because it was all smooth as silk, except for one problem... which may be related to my misunderstanding of the matter. Please use a current image; lvm on raid support was added 2 days ago. Fwor! Gotta give that a go... Hey, can the installer handle setting up a degraded RAID array (i.e. a RAID-1 mirror with the second disk missing) yet? mdadm can certainly handle the concept. This would be great for situations where you want RAID-1 but don't have two disks at your disposal at install time. regards Andrew -- linux.conf.au 2005 - http://lca2005.linux.org.au/ - Birthplace of Tux April 18th to 23rd - http://lca2005.linux.org.au/ - LINUX Canberra, Australia - http://lca2005.linux.org.au/ -Get bitten! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: lvm on raid
On Wed, Oct 20, 2004 at 12:55:34PM +0200, Frans Pop wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wednesday 20 October 2004 09:02, Andrew Pollock wrote: Hey, can the installer handle setting up a degraded RAID array (i.e. a RAID-1 mirror with the second disk missing) yet? mdadm can certainly handle the concept. Not ATM. There are 2 open wishlist bug to implement this (the oldest from yourself). This is extremely unlikely to be implemented before the release of Sarge. That's a shame. I would have thought it'd be relatively easy to implement, but I haven't given the innards of what's involved close inspection... regards Andrew -- linux.conf.au 2005 - http://lca2005.linux.org.au/ - Birthplace of Tux April 18th to 23rd - http://lca2005.linux.org.au/ - LINUX Canberra, Australia - http://lca2005.linux.org.au/ -Get bitten! signature.asc Description: Digital signature
Re: lvm on raid
On Wed, Oct 20, 2004 at 01:30:38PM +0200, Christian Perrier wrote: Quoting Andrew Pollock ([EMAIL PROTECTED]): That's a shame. I would have thought it'd be relatively easy to implement, but I haven't given the innards of what's involved close inspection... Well, the non easiest thing is maybe getting someone volunteering for implementing this..:-) I shall try and have a poke around (time permitting) and come up with a patch... -- linux.conf.au 2005 - http://lca2005.linux.org.au/ - Birthplace of Tux April 18th to 23rd - http://lca2005.linux.org.au/ - LINUX Canberra, Australia - http://lca2005.linux.org.au/ -Get bitten! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#275589: Install report for pre-rc2 on desktop clone (all good)
Package: installation-reports INSTALL REPORT Debian-installer-version: pre-rc2 uname -a: Linux brutus 2.4.27-1-386 #1 Fri Sep 3 06:24:46 UTC 2004 i686 GNU/Linux Date: Sat Oct 9 11:37:42 EST 2004 Method: netinst CD Machine: noname clone Processor: Pentium IV Memory: 256M Root Device: IDE Root Size/partition table: Disk /dev/hda: 120.0 GB, 120034123776 bytes 255 heads, 63 sectors/track, 14593 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/hda1 * 17295585970567 HPFS/NTFS /dev/hda272967326 249007+ 83 Linux /dev/hda373277388 498015 83 Linux /dev/hda47389 1459357874162+ 8e Linux LVM FilesystemType 1K-blocks Used Available Use% Mounted on /dev/mapper/base-root ext3 491364 54080411070 12% / tmpfstmpfs 128524 0128524 0% /dev/shm /dev/mapper/base-home ext3 982728 8243922057 1% /home /dev/mapper/base-tmp ext3 982728 8240922060 1% /tmp /dev/mapper/base-usr ext3 4128448276440 3642296 8% /usr /dev/mapper/base-var ext3 1965459250231 1610371 14% /var Output of lspci and lspci -n: :00:00.0 Host bridge: Intel Corp. 82845 845 (Brookdale) Chipset Host Bridge (rev 03) :00:01.0 PCI bridge: Intel Corp. 82845 845 (Brookdale) Chipset AGP Bridge (rev 03) :00:1e.0 PCI bridge: Intel Corp. 82801 PCI Bridge (rev 12) :00:1f.0 ISA bridge: Intel Corp. 82801BA ISA Bridge (LPC) (rev 12) :00:1f.1 IDE interface: Intel Corp. 82801BA IDE U100 (rev 12) :00:1f.2 USB Controller: Intel Corp. 82801BA/BAM USB (Hub #1) (rev 12) :00:1f.3 SMBus: Intel Corp. 82801BA/BAM SMBus (rev 12) :00:1f.4 USB Controller: Intel Corp. 82801BA/BAM USB (Hub #2) (rev 12) :01:00.0 VGA compatible controller: nVidia Corporation NV11 [GeForce2 MX/MX 400] (rev b2) :03:00.0 Multimedia audio controller: Ensoniq ES1370 [AudioPCI] (rev 01) :03:01.0 Ethernet controller: Intel Corp. 82557/8/9 [Ethernet Pro 100] (rev 08) :03:02.0 FireWire (IEEE 1394): Texas Instruments TSB12LV23 IEEE-1394 Controller :00:00.0 0600: 8086:1a30 (rev 03) :00:01.0 0604: 8086:1a31 (rev 03) :00:1e.0 0604: 8086:244e (rev 12) :00:1f.0 0601: 8086:2440 (rev 12) :00:1f.1 0101: 8086:244b (rev 12) :00:1f.2 0c03: 8086:2442 (rev 12) :00:1f.3 0c05: 8086:2443 (rev 12) :00:1f.4 0c03: 8086:2444 (rev 12) :01:00.0 0300: 10de:0110 (rev b2) :03:00.0 0401: 1274:5000 (rev 01) :03:01.0 0200: 8086:1229 (rev 08) :03:02.0 0c00: 104c:8019 Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot worked:[O] Configure network HW: [O] Config network: [O] Detect CD: [O] Load installer modules: [O] Detect hard drives: [O] Partition hard drives: [O] Create file systems:[O] Mount partitions: [O] Install base system:[O] Install boot loader:[O] Reboot: [O] Comments/Problems: It's good that I can now have the whole system on LVM. (Must try putting swap on there as well just for the heck of it). No problems, no aggravations, it was all good. signature.asc Description: Digital signature
Re: NTFS resize in partman
On Wed, Sep 29, 2004 at 08:22:13PM +0300, Anton Zinoviev wrote: Yesterday I made some changes in partman and partman-partitioning to allow resizing of NTFS partitions. This is nothing short of bloody brilliant. Good stuff. This will make it approach something close to as easy as falling off a log for existing Windoze users to install Debian on their system. You rock. regards Andrew -- linux.conf.au 2005 - http://lca2005.linux.org.au/ - Birthplace of Tux April 18th to 23rd - http://lca2005.linux.org.au/ - LINUX Canberra, Australia - http://lca2005.linux.org.au/ -Get bitten! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: plans for d-i rc2 (and Oldenburg meeting)
On Fri, Sep 17, 2004 at 08:07:32PM -0400, Joey Hess wrote: So I propose that we do a release that is not a release candidate. We could call this a test candidate (but users seemed to find that confusing before), or a technology preview release. Some of the nice new features would include - - root on LVM (done) What's the status of this? Does /boot on LVM work? I was thinking, if /boot (be that as a filesystem in it's own right, or as part of the root filesystem) is detected to be on a logical volume, the installer should fall back to using LILO as the bootloader, that way everything can be on LVM, without any caveats. regards Andrew -- linux.conf.au 2005 - http://lca2005.linux.org.au/ - Birthplace of Tux April 18th to 23rd - http://lca2005.linux.org.au/ - LINUX Canberra, Australia - http://lca2005.linux.org.au/ -Get bitten! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: netinst, wep key with spaces w/ patch
On Wed, Sep 15, 2004 at 08:32:22PM +, Chad Miller wrote: I recently installed on a friend's network, which had a WEP key with a space in it. The installer worked, but it wrote a /etc/network/interfaces file that didn't work. After boot, the key was set to the substring up to and not including the space in the WEP key. So you successfully got the wireless interface's WEP key set by entering it into the netcfg screen that asks for it? That's been giving me grief for ages. I have to switch to the second virtual terminal and manually set the key with iwconfig. What key length was it out of interest? regards Andrew -- linux.conf.au 2005 - http://lca2005.linux.org.au/ - Birthplace of Tux April 18th to 23rd - http://lca2005.linux.org.au/ - LINUX Canberra, Australia - http://lca2005.linux.org.au/ -Get bitten! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: LVM on top of RAID. Not possible?
On Tue, Sep 14, 2004 at 02:37:26PM +0200, Jesus Climent wrote: [snip] The installation needed some manual hack to pvcreate a PV with /dev/md/1 (which, BTW, became /dev/md1 after reboot !!). This would have been because the installer uses devfs, but does not install devfsd or enable devfs in the installed system. [snip] Am i missing something or we are releasing Sarge so that we cannot create LVM disks on top of RAID? I've done it (a while ago). I had to do the hackery described by someone else in an email to this list (sorry, I can't recall the details, you'll need to go searching). regards Andrew -- linux.conf.au 2005 - http://lca2005.linux.org.au/ - Birthplace of Tux April 18th to 23rd - http://lca2005.linux.org.au/ - LINUX Canberra, Australia - http://lca2005.linux.org.au/ -Get bitten! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#271477: Install report: rc1 on an Ultra 5
Package: installation-reports INSTALL REPORT Debian-installer-version: rc1 uname -a: Linux sparc 2.4.26-sparc64 #1 Sun Jun 20 02:39:17 PDT 2004 sparc64 GNU/Linux Date: Mon Sep 13 20:52:45 EST 2004 Method: netinst CD, via serial console Machine: Sun Ultra5 Processor: UltraSPARC II Memory: 128M Root Device: IDE, /dev/hda Root Size/partition table: Disk /dev/hda (Sun disk label): 16 heads, 63 sectors, 16708 cylinders Units = cylinders of 1008 * 512 bytes Device FlagStart EndBlocks Id System /dev/hda1 16212 16708249984 82 Linux swap /dev/hda2 0 496249984 83 Linux native /dev/hda3 0 16708 84208325 Whole disk /dev/hda4 496 4371 1953000 83 Linux native /dev/hda5 4371 8246 1953000 83 Linux native /dev/hda6 8246 10184976752 83 Linux native /dev/hda7 10184 11176499968 83 Linux native FilesystemType 1K-blocks Used Available Use% Mounted on /dev/hda2 ext3 234281 32839188943 15% / tmpfstmpfs 62320 0 62320 0% /dev/shm /dev/hda6 ext3 915381 8244858300 1% /home /dev/hda7 ext3 468819 8242435592 2% /tmp /dev/hda4 ext3 1830293 94807 1637836 6% /usr /dev/hda5 ext3 1830293 51193 1681450 3% /var Output of lspci and lspci -n: :00:00.0 Host bridge: Sun Microsystems Computer Corp. Ultra IIi :00:01.0 PCI bridge: Sun Microsystems Computer Corp. Simba Advanced PCI Bridge (rev 13) :00:01.1 PCI bridge: Sun Microsystems Computer Corp. Simba Advanced PCI Bridge (rev 13) :01:01.0 Bridge: Sun Microsystems Computer Corp. EBUS (rev 01) :01:01.1 Ethernet controller: Sun Microsystems Computer Corp. Happy Meal (rev 01) :01:02.0 VGA compatible controller: ATI Technologies Inc 3D Rage Pro 215GP (rev 5c) :01:03.0 IDE interface: Silicon Image, Inc. (formerly CMD Technology Inc) PCI0646 (rev 03) :00:00.0 0600: 108e:a000 :00:01.0 0604: 108e:5000 (rev 13) :00:01.1 0604: 108e:5000 (rev 13) :01:01.0 0680: 108e:1000 (rev 01) :01:01.1 0200: 108e:1001 (rev 01) :01:02.0 0300: 1002:4750 (rev 5c) :01:03.0 0101: 1095:0646 (rev 03) Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot worked:[O] Configure network HW: [O] Config network: [O] Detect CD: [O] Load installer modules: [E] Detect hard drives: [O] Partition hard drives: [E] Create file systems:[O] Mount partitions: [O] Install base system:[O] Install boot loader:[O] Reboot: [O] Comments/Problems: Had a bit of a hard time, largely because I was doing the install at 9600... I wanted to do LVM, but after I'd created a partition as an LVM physical volume and went to configure LVM, I was told that lvm-mod wasn't loaded, and maybe I'd like to do that before continuing. So I aborted the partitioning, went back to main menu and selected the load installer modules option, and explicitly loaded lvmcfg (well I told it to) and tried again. I was again told that lvm-mod wasn't loaded. As I was doing it via a serial console, I couldn't readily swap to another VT and check (I just thought of using the shell option from main menu, but it's a bit late now). So I gave up and did a normal partitioning scheme. Funnily enough, after writing out all the partitions, I got another lvm-mod not loaded message box (the only option was to acknowledge it, so it was fairly benign). Other than that, I don't think there were any problems. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#262624: Patch works
Hi, I've managed to build a d-i image to test that incorporates this patch, and it does actually work. I couldn't verify it 100% because iwconfig wasn't there for some reason, but I entered my ESSID, I entered my WEP key, and DHCP worked without further intervention. regards Andrew -- linux.conf.au 2005 - http://lca2005.linux.org.au/ - Birthplace of Tux April 18th to 23rd - http://lca2005.linux.org.au/ - LINUX Canberra, Australia - http://lca2005.linux.org.au/ -Get bitten! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#271275: netcfg: Go back button doesn't work properly if no link is detected
Package: netcfg Version: 1.01 Severity: normal Hi, I was verifying #262638 tonight, and just had the USB Ethernet adapter plugged in, without a cable plugged into it. I got the screen that says there's no link detected, and do I want to go back, or do some other stuff. If I go back, I get asked for a hostname, if I go back on that screen, I get back at the screen saying that no link is detected. regards Andrew -- System Information: Debian Release: 3.1 APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.7-1-686 Locale: LANG=C, LC_CTYPE=C -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#262638: marked as done (ethdetect: Please add manual support for Pegasus USB Ethernet adapters)
On Mon, Sep 06, 2004 at 03:03:05PM -0700, Debian Bug Tracking System wrote: Changes: ddetect (1.05) unstable; urgency=low . * Joey Hess - Add usb nic modules to the manual module list. Closes: #262638, #267402 - Hack to make this work for 2.4 which does not have a usb/nic subdir. - In ethdetect, don't prompt twice for module params in a low priority install. Confirmed. regards Andrew -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Thanks for the tips
Hi Joey, Thanks for the tips in your blog. It made me get on the horse again for another go. A few things/questions: the mini.iso created by the netboot target seemed identical to the mini.iso made by the monolithic target. How do I get an iso with all the udebs on it (or is this what the monolithic target is supposed to be? (or is this what the pkglists/*/local is for?)) How do I get the environment to more closely match that of a netinst CD (which is what I usually do install tests with)? Specifically, I was missing iwconfig in the mini.iso I was playing with today. regards Andrew -- linux.conf.au 2005 - http://lca2005.linux.org.au/ - Birthplace of Tux April 18th to 23rd - http://lca2005.linux.org.au/ - LINUX Canberra, Australia - http://lca2005.linux.org.au/ -Get bitten! signature.asc Description: Digital signature
Bug#262624: Patch works
On Sun, Sep 12, 2004 at 02:08:47AM -0700, Joshua Kwan wrote: On Sun, Sep 12, 2004 at 06:33:46PM +1000, Andrew Pollock wrote: I've managed to build a d-i image to test that incorporates this patch, and it does actually work. I couldn't verify it 100% because iwconfig wasn't there for some reason, but I entered my ESSID, I entered my WEP key, and DHCP worked without further intervention. Good! Now if you have time, I'd like you to try applying this patch (to pristine source) and seeing if it all works... because then we'll still be able to use the iwlib API effectively. I'm fairly sure this more or less duplicates what your own patch did with the code already in iwlib. Negative. Your patch didn't work (again, hard to verify, no iwconfig), but DHCP didn't work, which is a fair sign it failed. regards Andrew -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#262624: Mutter mutter
It'd be nice if reportbug had made it more obvious that attaching the patch
had failed...
--
linux.conf.au 2005 - http://lca2005.linux.org.au/ - Birthplace of Tux
April 18th to 23rd - http://lca2005.linux.org.au/ - LINUX
Canberra, Australia - http://lca2005.linux.org.au/ -Get bitten!
Common subdirectories: netcfg-1.01.orig/debian and netcfg-1.01/debian
diff -u netcfg-1.01.orig/wireless.c netcfg-1.01/wireless.c
--- netcfg-1.01.orig/wireless.c 2004-05-17 08:48:39.0 +1000
+++ netcfg-1.01/wireless.c 2004-09-11 14:33:35.0 +1000
@@ -173,6 +173,7 @@
char* rv = NULL;
int ret, keylen;
unsigned char buf [IW_ENCODING_TOKEN_MAX];
+ struct iwreq wrq;
iw_get_basic_config (wfd, iface, wconf);
@@ -215,15 +216,13 @@
rv = client-value;
}
- wconf.has_key = 1;
- wconf.key_size = keylen;
- wconf.key_flags = IW_ENCODE_ENABLED | IW_ENCODE_OPEN;
-
- strncpy (wconf.key, buf, keylen);
-
- wepkey = strdup(rv);
+ wrq.u.data.pointer = buf;
+ wrq.u.data.flags = 0;
- iw_set_basic_config (wfd, iface, wconf);
+ if (iw_set_ext(skfd, iface, SIOCSIWENCODE, wrq) 0) {
+return -1;
+ }
return 0;
+
}
Bug#262624: netcfg: Preliminary patch that may fix this
Package: netcfg Version: 1.00 Followup-For: Bug #262624 Hi, I've formalised some hacking that I did with aj a couple of weekends ago into a patch. It compiles, and I've tested the functionality of the patch in a separate program, but I haven't tested netcfg with the patch, because whilst I can build a udeb, I've no idea how to rebuild all of d-i to incorporate that udeb... :-( So, here's the patch, maybe a netcfg knowledgable person can look at it and tell if it's utter bollocks or not, and take it from there. regards Andrew -- System Information: Debian Release: 3.1 APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.7-1-686 Locale: LANG=C, LC_CTYPE=C -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Wrong kernel after install
On Tue, Aug 31, 2004 at 10:47:58AM -0400, Joey Hess wrote: Miguel Quaremme wrote: I downloaded Debian-installer RC1(i386) and all went fine but the kernel installed was kernel-image-2.6.7-1-386 while another one (kernel-image-2.6.7-1-686) should have been used instead. This is expected behavior if you were installing from a netinst CD, which only has room for one kernel. You don't say what media you installed from. Is this a FAQ item yet? regards Andrew -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#262638: pegasus loading
On Tue, Aug 31, 2004 at 04:43:42PM -0400, Joey Hess wrote: I take it that the reasoning behind adding pegasus to devnames is that the user then at least can pick their usb ethernet adaptor off the list? I checked, and the current version of ethdetect has an entry for pegasus, though using a different text than you gave. Can you give it a try and see if this bug can be closed? Correct. Something is better than nothing... I'm not sure if it will work, because the list of network modules is only those in drivers/net, while pegasus.o is in drivers/usb. Actually, I'm almost sure it *won't* work.. Hmm, okay. I shall attempt to test it with a daily build tonight anyway... regards Andrew -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Giving a talk/demo of d-i at CLUG next month
On Fri, Jun 25, 2004 at 11:48:02AM +1000, Andrew Pollock wrote: Hi, I've been dobbed in to give a talk on d-i at next month's CLUG meeting. I was planning on giving a brief blurb about the history behind the installer (where we've come from, where we're trying to go) and then launch into a couple of example installs. The main outcome desired is to get feedback on the new installer. I'll pass on that feedback afterwards... So I finally gave this talk last Thursday. Feedback was generally positive. The one thing, which more relates to base-config and exim4 in particular, was the suggestion to make it more obvious which choice the typical dialup user is going to want (I would think smarthost + fetchmail). regards Andrew signature.asc Description: Digital signature
Re: RE/FW: Please stop sending me emails
On Fri, Aug 27, 2004 at 09:48:14PM +0100, peter green wrote: can someone please remove this guy from the list before his bloody autoresponders drive us all crazy It's getting into a loop :-( His emails go to the list, back to him and around again... -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#267992: install report: PowerBook G4
Package: installation-reports INSTALL REPORT Debian-installer-version: rc1 uname -a: Linux mac 2.6.7-powerpc #1 Sat Jul 10 03:47:45 CEST 2004 ppc GNU/Linux Date: Wed Aug 25 22:32:11 EST 2004 Method: netinst CD Machine: PowerBook G4 Processor: PowerPC G4 Memory: 512M Root Device: IDE /dev/hda Root Size/partition table: /dev/hda #type name length base ( size ) system /dev/hda1 Apple_partition_map Apple 63 @ 1 ( 31.5k) Partition map /dev/hda2 Apple_HFS Apple_HFS_Untitled_2 83623936 @ 262208( 39.9G) HFS /dev/hda3 Apple_Bootstrap bootstrap 1602 @ 64(801.0k) NewWorld bootblock /dev/hda4 Apple_Free Extra 260542 @ 1666 (127.2M) Free space /dev/hda5 Apple_UNIX_SVR2 swap 101 @ 84886145 (488.3M) Linux swap /dev/hda6 Apple_UNIX_SVR2 root39062501 @ 85886146 ( 18.6G) Linux native /dev/hda7 Apple_Free Extra101 @ 83886144 (488.3M) Free space /dev/hda8 Apple_Free Extra 31352841 @ 124948647 ( 15.0G) Free space Block size=512, Number of Blocks=156301488 DeviceType=0x0, DeviceId=0x0 FilesystemType 1K-blocks Used Available Use% Mounted on /dev/hda6 ext319225040227180 18021376 2% / tmpfstmpfs 258080 0258080 0% /dev/shm Output of lspci and lspci -n: :00:0b.0 Host bridge: Apple Computer Inc. UniNorth 2 AGP :00:10.0 VGA compatible controller: ATI Technologies Inc RV350 [Mobility Radeon 9600 M10] 0001:01:0b.0 Host bridge: Apple Computer Inc. UniNorth 2 PCI 0001:01:12.0 Network controller: Broadcom Corporation BCM4306 802.11b/g Wireless LAN Controller (rev 03) 0001:01:13.0 CardBus bridge: Texas Instruments PCI1510 PC card Cardbus Controller 0001:01:17.0 ff00: Apple Computer Inc. KeyLargo/Intrepid Mac I/O 0001:01:18.0 USB Controller: Apple Computer Inc. KeyLargo/Intrepid USB 0001:01:19.0 USB Controller: Apple Computer Inc. KeyLargo/Intrepid USB 0001:01:1a.0 USB Controller: Apple Computer Inc. KeyLargo/Intrepid USB 0001:01:1b.0 USB Controller: NEC Corporation USB (rev 43) 0001:01:1b.1 USB Controller: NEC Corporation USB (rev 43) 0001:01:1b.2 USB Controller: NEC Corporation USB 2.0 (rev 04) 0002:06:0b.0 Host bridge: Apple Computer Inc. UniNorth 2 Internal PCI 0002:06:0d.0 ff00: Apple Computer Inc. UniNorth/Intrepid ATA/100 0002:06:0e.0 FireWire (IEEE 1394): Apple Computer Inc. UniNorth 2 FireWire (rev 81) 0002:06:0f.0 Ethernet controller: Apple Computer Inc. UniNorth 2 GMAC (Sun GEM) (rev 80) :00:0b.0 0600: 106b:0034 :00:10.0 0300: 1002:4e50 0001:01:0b.0 0600: 106b:0035 0001:01:12.0 0280: 14e4:4320 (rev 03) 0001:01:13.0 0607: 104c:ac56 0001:01:17.0 ff00: 106b:003e 0001:01:18.0 0c03: 106b:003f 0001:01:19.0 0c03: 106b:003f 0001:01:1a.0 0c03: 106b:003f 0001:01:1b.0 0c03: 1033:0035 (rev 43) 0001:01:1b.1 0c03: 1033:0035 (rev 43) 0001:01:1b.2 0c03: 1033:00e0 (rev 04) 0002:06:0b.0 0600: 106b:0036 0002:06:0d.0 ff00: 106b:003b 0002:06:0e.0 0c00: 106b:0031 (rev 81) 0002:06:0f.0 0200: 106b:0032 (rev 80) Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot worked:[O] Configure network HW: [O] Config network: [O] Detect CD: [O] Load installer modules: [O] Detect hard drives: [O] Partition hard drives: [O] Create file systems:[O] Mount partitions: [O] Install base system:[O] Install boot loader:[O] Reboot: [O] Comments/Problems: When partitioning, I wasn't given an option to create an LVM physical volume :-( Other than that, everything went fine. base-config asked me about a proxy server twice, as per i386 (no surprises there). -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#267339: Install Report (Sony Vaio PCG-F590 + wireless)
Package: installation-reports INSTALL REPORT Debian-installer-version: rc1 uname -a: Linux andrewpollock 2.4.26-1-386 #1 Thu Jul 22 12:46:23 JST 2004 i686 GNU/Linux Date: Sun Aug 22 11:46:32 EST 2004 Method: Booted from netinst CD, installed from HTTP mirror (ftp.au.debian.org), transparently proxied Machine: Sony Vaio PCG-F590 laptop Processor: Pentium III Memory: 256M Root Device: IDE. /dev/hda Root Size/partition table: Disk /dev/hda: 20.0 GB, 20003880960 bytes 255 heads, 63 sectors/track, 2432 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/hda1 11337107394217 HPFS/NTFS /dev/hda2 *13381646 2482042+ 83 Linux /dev/hda316472432 6313545f W95 Ext'd (LBA) /dev/hda516472392 5992213+ 83 Linux /dev/hda623932432 321268+ 82 Linux swap FilesystemType 1K-blocks Used Available Use% Mounted on /dev/hda2 ext3 2443004211804 2107100 10% / tmpfstmpfs 128512 0128512 0% /dev/shm /dev/hda5 ext3 5898124 32872 5565644 1% /home Output of lspci and lspci -n: :00:00.0 Host bridge: Intel Corp. 440BX/ZX/DX - 82443BX/ZX/DX Host bridge (rev 03) :00:01.0 PCI bridge: Intel Corp. 440BX/ZX/DX - 82443BX/ZX/DX AGP bridge (rev 03) :00:07.0 ISA bridge: Intel Corp. 82371AB/EB/MB PIIX4 ISA (rev 02) :00:07.1 IDE interface: Intel Corp. 82371AB/EB/MB PIIX4 IDE (rev 01) :00:07.2 USB Controller: Intel Corp. 82371AB/EB/MB PIIX4 USB (rev 01) :00:07.3 Bridge: Intel Corp. 82371AB/EB/MB PIIX4 ACPI (rev 03) :00:08.0 FireWire (IEEE 1394): Sony Corporation CXD3222 i.LINK Controller (rev 02) :00:09.0 Multimedia audio controller: Yamaha Corporation YMF-744B [DS-1S Audio Controller] (rev 02) :00:0a.0 Communication controller: Conexant HSF 56k Data/Fax Modem (Mob WorldW SmartDAA) (rev 01) :00:0c.0 CardBus bridge: Ricoh Co Ltd RL5c478 (rev 80) :00:0c.1 CardBus bridge: Ricoh Co Ltd RL5c478 (rev 80) :01:00.0 VGA compatible controller: Neomagic Corporation NM2380 [MagicMedia 256XL+] (rev 10) :00:00.0 0600: 8086:7190 (rev 03) :00:01.0 0604: 8086:7191 (rev 03) :00:07.0 0601: 8086:7110 (rev 02) :00:07.1 0101: 8086:7111 (rev 01) :00:07.2 0c03: 8086:7112 (rev 01) :00:07.3 0680: 8086:7113 (rev 03) :00:08.0 0c00: 104d:8039 (rev 02) :00:09.0 0401: 1073:0010 (rev 02) :00:0a.0 0780: 14f1:2443 (rev 01) :00:0c.0 0607: 1180:0478 (rev 80) :00:0c.1 0607: 1180:0478 (rev 80) :01:00.0 0300: 10c8:0016 (rev 10) Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot worked:[O] Configure network HW: [E] Config network: [O] Detect CD: [O] Load installer modules: [O] Detect hard drives: [O] Partition hard drives: [O] Create file systems:[O] Mount partitions: [O] Install base system:[O] Install boot loader:[O] Reboot: [O] Comments/Problems: The only problem I struck was on the configuration of the network. I performed this install with my wireless card, an Avaya (orinoco chipset) PCMCIA adapter. The wireless adapter was detected, and I was prompted for an ESSID and WEP key. The WEP key wasn't set when the wireless network was brought up though, so I had to manually switch to the second terminal to set it with iwconfig to get DHCP to work. I've already filed a bug against netcfg (#262624) on this. I also think I was prompted about a proxy server twice, once when doing the initial apt-get update, and once when adding security repository. I wasn't paying close attention, so I'll check again shortly when I do another test install with a different setup. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#249041: marked as done (Please support disk labels (LABEL=))
On Fri, Aug 13, 2004 at 01:48:55AM -0700, Debian Bug Tracking System wrote: On Fri, May 14, 2004 at 04:58:56PM +0100, Martin Michlmayr wrote: Please add an option to specify a disk label (max 16 characters), and use that in fstab if it's available. Partman already allows users to specify disk labels but it doesn't use them in /etc/fstab. I consider this dangerous and confusing for the users. More confusing and dangerous than a SCSI disk being removed (or failing), the SCSI bus relocating itself and nothing mounting properly on next boot? Please consider. Other distributions do, and have done so for some time. It's more robust. regards Andrew -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Question Concerning Change In Console Text Size While Booting Up
On Wed, Aug 11, 2004 at 07:55:52PM -0300, Joey Hess wrote: It's hotplug. This is being fixed. Hotplug seems to be quite the problem child lately... -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Opinion about sarge install
On Sun, Aug 08, 2004 at 03:01:45PM -0300, [EMAIL PROTECTED] wrote: Hey folks, Just some opinion about the sarge install process. I installed a july daily build(I can't remember the exact one, but i think it was 25) on my computer that has just the very common hardware(i386 arch) with the 2.6 kernel. I consider myself a getting-to-intemediate-level user and here's some things you might consider (or not :P): 1)X configuration should be more automatic. I couldn't get the x server to work on the first try. So I just did some copy and paste for the config file I backedup from my old Mandrake distro I replaced with debian. If Mandrake can, why can't debian get the configuration right with not much user intervention and technical knowledge? These would make things much easier; It would probably be interesting and useful for the X packaging team to see a diff between the config that was generated from configuring X and the config you ultimately had to use to get X working. In my experience, provided you give the X configuration the right input, it does a reasonable job of getting X working. 2) I select the desktop package collection and then later when I was trying to install some software I found out make, gcc and other tools were not installed. I think these tools should be installed on any install because unfortunetelly not everything come on .deb packages from a organized repository; This is a matter of opinion. Not everyone wants a compiler installed by default. Firewalls don't need a compiler. If you want to build stuff, apt-get install build-essential. Whether the desktop task should install build-essential is debateable. I'm inclined to think there should be a Development task that installs at least build-essential packages... 3) It should be a way to find out what's the best mirror. I had to try I few until I found that was acceptably fast. Well that's going to vary from person to person. I'm not sure how something like apt-spy can be integrated with the mirror selection process. 4) My TV card(PixelView Pro w/ FM) doesn't worked after the installation. And still doesn't. OFFTOPIC: If anyone has any document or anything that can help me get it to work, it would be very much appreciated.Those things on Google did not work, I'll try harder to get this card to work and I have more free time :) I think that's all, Guilherme If God came down on Christmas day, I know exactly what He'd say He'd say Oi! to the punks, Oi! to the skins, Oi! to the world and everybody wins! No Doubt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Opinion about sarge install
On Sun, Aug 08, 2004 at 11:56:00PM +0100, peter green wrote: It would probably be interesting and useful for the X packaging team to see a diff between the config that was generated from configuring X and the config you ultimately had to use to get X working. In my experience, provided you give the X configuration the right input, it does a reasonable job of getting X working. i think the point is that the X setup tool needs a full auto mode almost every other distro has auto setup of X (even some debian based ones like KNOPPIX) normal users CANNOT be expected to answer those kind of questions You should jump on [EMAIL PROTECTED] and have a discussion about this. I think it's been discussed in the past. The main thing is, Knoppix runs on 1 architecture, the X configuration has to work on all 11. I believe Branden has said in the past that autodetection of the monitor and video card can have undesirable results (like hanging the system) on some combinations of hardware and architectures. That said, it may be feasible to autodetect everything on i386, which is the probably the architecture that X is most installed on... I don't know. Talk to the X folks if you feel strongly about it. regards Andrew -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#263162: Please describe your tasksel policy, and re-add the tex task
On Fri, Aug 06, 2004 at 04:55:29PM +0200, Sven Luther wrote: On Thu, Aug 05, 2004 at 09:44:21PM -0400, Joey Hess wrote: Andrew Pollock wrote: Can you please elaborate? I've just read the README file, and I'm not a lot wiser as to why the tex packages don't fit the policy? I'd like a task for installing latex related stuff. I suspect that less than 25% of our users use tex. It could conceivably So, we have only various server stuff that most of our users really don't care about ? Also, getting both KDE and gnome in one task is sure not to be popular for the slow bandwidth modem users. Amen. And it's defaulting to KDE to boot, which is starting to piss me off. I think at least having a GNOME desktop and KDE desktop task is a Good Thing. Users can always select both, if in doubt. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#263162: Please describe your tasksel policy, and re-add the tex task
On Fri, Aug 06, 2004 at 06:04:21PM -0400, Joey Hess wrote: Andrew Pollock wrote: Amen. And it's defaulting to KDE to boot, which is starting to piss me off. It's pissed me off ever since I filed the bug on gnome-session over one month ago, got it fixed, and then watched the package not get into testing over and over again. But that's offtopic for this bug report. :-( I think at least having a GNOME desktop and KDE desktop task is a Good Thing. Users can always select both, if in doubt. Our reasons for not doing that are well documented in the archives, and will not be repeated here. I shall go trawl the archives then. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#263162: Please describe your tasksel policy, and re-add the tex task
On Tue, Aug 03, 2004 at 10:30:48AM -0400, Joey Hess wrote: Frank Kuester wrote: I could not find those criteria written in any of the bug reports, or in /usr/share/doc/tasksel. There was also no explanation why specifically the tex task (and the science task, too) was removed. I would be happy to cooperate with you and provide a new, better tex task, but I need to know the criteria first. tasks/README in the tasksel source package. I can't imagine any changes to the tex task that would make it fit the new policy. Can you please elaborate? I've just read the README file, and I'm not a lot wiser as to why the tex packages don't fit the policy? I'd like a task for installing latex related stuff. regards Andrew -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
USB ethernet adapter support?
Hi, What would it take, and is there any chance of getting into d-i at this late stage, for d-i to support USB ethernet adapters? I've finally gotten around to doing some tests on my VAIO (PCG-F590), which doesn't have an ethernet adapter. Since I've been running wireless at home, I usually use that for my network connectivity, however I want to do a demo install on my laptop at CLUG next month, and I'll have to be relying on physical ethernet. I plugged my USB ethernet adapter in, and booted the current d-i CD, however it did not detect the adapter (an SMC Pegasus chipset based adapter). Furthermore, I note that in the manual list, pegasus isn't an option. I note that the pegasus module is available in the kernel's module directory, so I guess it's just a case of detecting it? How can I help, or is it too late? regards Andrew -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#262624: netcfg: does not set WEP key when one is specified
Package: netcfg Version: 1.00 Severity: normal Hi, I was testing the daily build of d-i from sarge on my laptop for a change, and I have a wireless network, with WEP. I was prompted for a WEP key, and I entered it in the format --nn, but from inspection with iwconfig on VT2, the WEP key was not actually set. Prior to being asked for a WEP key, iwconfig didn't report an encryption key in use at all, and after supplying one, it reported --00 as the encryption key. Leaving the WEP key blank when asked correctly set encryption to off altogether. So it seems that there is a problem with feeding the encryption key to iwconfig. If I manually set the key in VT2 things proceed as they should. regards Andrew -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.7-1-686 Locale: LANG=C, LC_CTYPE=C -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#262626: netcfg: description error for e100 driver
Package: netcfg Version: 1.00 Severity: minor Hi, I was testing d-i with my laptop, without the wireless card, with a USB ethernet adapter. It doesn't seem to have detected the USB ethernet adapter, and presented me with a list of drivers. I note that the e100 driver has the same description as the e1000 driver, namely Intel(R) PRO/1000 Gigabit Ethernet, which isn't correct. regards Andrew -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.7-1-686 Locale: LANG=C, LC_CTYPE=C -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Debian Installer : 1st stage stats broken (anonymous SVN checkout broken)
On Wed, Jun 16, 2004 at 07:25:30AM +0200, Christian Perrier wrote: Because anonymous SVN checkout is currently broken for d-i, the 1st stages statistics are also broken. I'll try to keep you posted with possible changes. Non anonymous checkout is possible, however, so you can still commit your changes. Can someone fix the anonymous checkout on the SVN repository? Since I got a connection refused on port 3691, I presume this is still broken? Any idea if/when it'll be fixed? Doesn't look like 3690 is listening either, or was it always svn+ssh? regards Andrew -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Pegasus USB ethernet adapter support (was: Bug#262626: netcfg: description error for e100 driver)
On Sun, Aug 01, 2004 at 02:18:51AM -0700, Joshua Kwan wrote:
On Sun, Aug 01, 2004 at 05:19:46PM +1000, Andrew Pollock wrote:
I was testing d-i with my laptop, without the wireless card, with a USB
ethernet adapter. It doesn't seem to have detected the USB ethernet
adapter, and presented me with a list of drivers.
I don't think this is supported, sorry. File a separate bug against
linux-kernel-di-i386{,-2.6} if you really think this should be
available.
It would consist of making a nic-usb-modules package and I don't think
we even have room for that on the floppies...
The pegasus (and kaweth for that matter) modules are already in place in the
modules directory for the d-i image I'm currently testing. No further udebs
or space required.
regards
Andrew
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#262638: ethdetect: Please add manual support for Pegasus USB Ethernet adapters
Package: ethdetect Version: 1.00 Severity: wishlist Hi, Given the lateness of this request, this is the least intrusive way of getting USB Ethernet adapter support into d-i... Could you please add the following line to the devnames file that winds up as /etc/network/devnames.gz: pegasus:Pegasus chipset based USB Ethernet adapters In the longer term, it'd be nice if ethdetect can detect this automatically. It seems a modinfo pegasus on a box running a 2.6 kernel spits out all the associated vendor/product ID's that the pegasus driver recognises if you need this information. I haven't wrapped my head around how the current ethernet driver detection works, so I'm not sure what's required. regards Andrew (Cursing himself for not testing this sooner) -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.7-1-686 Locale: LANG=C, LC_CTYPE=C -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: ssh
On Fri, Jul 16, 2004 at 05:20:37PM +0900, Kenshi Muto wrote: As you know, telnet package is client, not server. I don't think we should remove telnet package, because telnet is useful for really connect to other old machine, or analyze a network application problem. I'm trying to get into the habit of using netcat for that instead. I like using the harden-* packages, and harden-clients conflicts with telnet. I can install telnet-ssl to get around that, but given I'm never actually using the TELNET protocol, I'm just using telnet to connect to arbitrary ports, I figure I might as well use netcat and be done with it... Andrew -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Introduction
On Mon, Aug 02, 2004 at 03:52:20AM +1000, James Mills wrote: On Sun, Aug 01, 2004 at 06:36:42PM +0100, Colin Watson wrote: Should do, but searching is more awkward. Thanks. [Please keep further questions on the mailing list, if you would.] Shit. Does this list not have an explicit Reply-To header to the mailing list address either ? THis is the 2nd list I've come across that is configured this way. My apolagies. No it doesn't. That's really really evil. If you have a decent mail client (i.e. Mutt) it'll handle the Mail-Followup-To header and do the right thing if you go a group reply. regards Andrew -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#236423: reassigning to hotplug
reassign 236423 hotplug tags 236423 - help thanks Hi, I've done some more investigation, and added a placemarker echo line to the end of /etc/init.d/discover, and the ich2rom modprobe attempt occurs well and truly after /etc/init.d/discover has finished, so the problem is no longer discover. It seems to be hotplug that is causing it, but I can't see directly the cause. If I'm reading the modules.dep file correctly, ich2rom depends on some MTD related modules, but nothing depends on ich2rom, so it's not getting loaded by way of a dependency. If I add ich2rom to /etc/hotplug/blacklist, the problem goes away. I've attached a transcript of two boots, one without ich2rom in /etc/hotplug/blacklist and one with it in, and you can see the difference. If I can be of any further assistance, please let me know. regards Andrew Linux version 2.6.7-1-686 ([EMAIL PROTECTED]) (gcc version 3.3.4 (Debian 1:3.3.4-2)) #1 Thu Jul 8 05:36:53 EDT 2004 BIOS-provided physical RAM map: BIOS-e820: - 0009fc00 (usable) BIOS-e820: 0009fc00 - 000a (reserved) BIOS-e820: 000f - 0010 (reserved) BIOS-e820: 0010 - 0fff (usable) BIOS-e820: 0fff - 0fff8000 (ACPI data) BIOS-e820: 0fff8000 - 1000 (ACPI NVS) BIOS-e820: ffbc0100 - ffbc0101 (reserved) BIOS-e820: fff0 - 0001 (reserved) 0MB HIGHMEM available. 255MB LOWMEM available. found SMP MP-table at 000fb6d0 On node 0 totalpages: 65520 DMA zone: 4096 pages, LIFO batch:1 Normal zone: 61424 pages, LIFO batch:14 HighMem zone: 0 pages, LIFO batch:1 DMI 2.3 present. ACPI: RSDP (v000 AMI ) @ 0x000f9e90 ACPI: RSDT (v001 AMIINT INTEL845 0x0010 MSFT 0x0097) @ 0x0fff ACPI: FADT (v001 AMIINT INTEL845 0x0011 MSFT 0x0097) @ 0x0fff0030 ACPI: MADT (v001 AMIINT 0x0009 MSFT 0x0097) @ 0x0fff00b0 ACPI: DSDT (v001 INTEL BROKDALE 0x1000 MSFT 0x010d) @ 0x ACPI: PM-Timer IO Port: 0x808 ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled) Processor #0 15:0 APIC version 20 ACPI: IOAPIC (id[0x02] address[0xfec0] global_irq_base[0x0]) IOAPIC[0]: Assigned apic_id 2 IOAPIC[0]: apic_id 2, version 32, address 0xfec0, GSI 0-23 ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level) Enabling APIC mode: Flat. Using 1 I/O APICs Using ACPI (MADT) for SMP configuration information Built 1 zonelists Kernel command line: root=/dev/hda2 ro vga=0x318 console=ttyS0,115200 single Initializing CPU#0 PID hash table entries: 1024 (order 10: 8192 bytes) Detected 1504.185 MHz processor. Using pmtmr for high-res timesource Console: colour dummy device 80x25 Memory: 252160k/262080k available (1515k kernel code, 9224k reserved, 659k data, 148k init, 0k highmem) Checking if this processor honours the WP bit even in supervisor mode... Ok. Calibrating delay loop... 2973.69 BogoMIPS Security Scaffold v1.0.0 initialized Dentry cache hash table entries: 32768 (order: 5, 131072 bytes) Inode-cache hash table entries: 16384 (order: 4, 65536 bytes) Mount-cache hash table entries: 512 (order: 0, 4096 bytes) CPU: Trace cache: 12K uops, L1 D cache: 8K CPU: L2 cache: 256K Intel machine check architecture supported. Intel machine check reporting enabled on CPU#0. CPU0: Intel P4/Xeon Extended MCE MSRs (12) available CPU0: Thermal monitoring enabled CPU: Intel(R) Pentium(R) 4 CPU 1500MHz stepping 07 Enabling fast FPU save and restore... done. Enabling unmasked SIMD FPU exception support... done. Checking 'hlt' instruction... OK. enabled ExtINT on CPU#0 ESR value before enabling vector: ESR value after enabling vector: ENABLING IO-APIC IRQs ..TIMER: vector=0x31 pin1=2 pin2=-1 Using local APIC timer interrupts. calibrating APIC timer ... . CPU clock speed is 1503.0208 MHz. . host bus clock speed is 100.0213 MHz. checking if image is initramfs...it isn't (ungzip failed); looks like an initrd Freeing initrd memory: 4584k freed NET: Registered protocol family 16 PCI: PCI BIOS revision 2.10 entry at 0xfdb71, last bus=3 PCI: Using configuration type 1 mtrr: v2.0 (20020519) ACPI: Subsystem revision 20040326 ACPI: Interpreter enabled ACPI: Using IOAPIC for interrupt routing ACPI: PCI Root Bridge [PCI0] (00:00) PCI: Probing PCI hardware (bus 00) PCI: Transparent bridge - :00:1e.0 ACPI: Power Resource [URP1] (off) ACPI: Power Resource [URP2] (off) ACPI: Power Resource [FDDP] (off) ACPI: Power Resource [LPTP] (off) ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 *11 12 14 15) ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 10 *11 12 14 15) ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 6 7 10 *11 12 14 15) ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 7 10 *11 12 14 15) ACPI: PCI Interrupt Link [LNKE] (IRQs
Bug#236423: Problem persists
On Mon, Jul 26, 2004 at 06:20:04PM +0200, Gaudenz Steinlin wrote: tags 236423 +help Thanks On Sat, Jun 26, 2004 at 02:09:55PM +1000, Andrew Pollock wrote: Hi, I'm operating with 1.2004.02.08-7, and I'm still seeing the same stuff getting spat out during the boot process. If there's any more information I can provide, don't hesitate to ask. I'm trying to find out what goes wrong, but I just don't get it. I'm a bit lost. According to the lspci output of your machine there is no device that lists either the i810_rng or ich2rom modules in pci.lst. So I really don't know why these modules still get loaded. Could you please send me the versions of the packages discover1 and discover1-data you are using and make sure neither of discover, discover-data and libdiscover2 are installed on your system. To further investigate I also need the output of lspci -x. With this I can reproduce the exact PCI information from your machine. Don't despair. I suspect hotplug is now the culprit. I'll do some more testing and get back to you. Do you have any idea why hotplug would be trying to load the wrong modules? regards Andrew -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: sysresccd.org, run_qtparted, Success resizing NTFS (XP)
On Mon, Jun 28, 2004 at 03:32:43PM -0700, Karl Hegbloom wrote: I thought I'd let everyone know that the www.sysresccd.org beta has a qtparted on it that runs on a framebuffer, and can successfully resize a Windows XP NTFS partition. Boot the CD, type run_qtparted. After the resize, boot XP, and let it fsck the disk. Everything seems to be working fine! We need this technology! I wonder how hard it would be to make a udeb, or get the NTFS supporting parted into our partition editor... Can the d-i partition editor resize like that? I agree. This would seriously facilitate Windoze users in trying out Debian in as non-intrusive a manner as possible. I think the above CD is the one I used on a friend's laptop to shrink WinXP to make room for Debian. Works amazingly well. So I guess it would mean that partman has some option to resize existing partitions... regards Andrew -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Giving a talk/demo of d-i at CLUG next month
On Sat, Jun 26, 2004 at 01:38:27PM +0200, Gaudenz Steinlin wrote: I just gave a talk about debian-installer at debian day on LinuxTag. It's title was debian-installer internals. You can download the slides at http://www.soziologie.ch/~steinlin/d-i/talk/. Thanks! Very nice slides. I'll use some of the content and give you credit. regards Andrew -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Hacking on d-i
On Sun, Jun 27, 2004 at 01:00:32PM +0800, John Summerfield wrote: I'd like to make a few minor changes for my own use - specify my local mirror, maybe partition layout and such. I started out by unpacking the initrd to see what's in it, and was pretty happy to see debian-installer is a shell script: there's almost no limit to the magic one can do there on a good day:-) There's no clue there as to what to do, but I did try the alternative f/e (bogl) and discovered it does nothing useful. A bit of finding and grepping and I discovered where the list of mirrors is. I've _not_ found a sensible way to change that list, nor to specify my preferred value in any kind of configuration file. Next, I went looking for the d-i home page. I tried www.debian.org/debian-installer - no, not there. Finally, Google gave up some clues and I finished up at https://alioth.debian.org/projects/d-i/ Have you been to http://www.debian.org/devel/debian-installer ? There, I find This project has no visible documents . No subprojects have been set up, or you cannot view them. What you need to do is checkout a copy of the d-i subversion repository. See http://www.nl.debian.org/devel/debian-installer/svn There's a lot of documentation, some of it quite enlightening within a directory of the source tree. The question: where is the information I need to change the mirror to be chosen, specify any initial defaults I need? btw My browser doesn't like the certificate from this site, its issuer is unknown. Yep, that's normal. :-| Andrew -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#256301: LVM in Beta 4
On Sat, Jun 26, 2004 at 01:37:54AM +0200, Leszek wrote: Yesterday I've tried to use Beta 4 on my friend's comp; the problem was that upon selecting a root partition for a format and setting up a swap part. , it started bugging me about LVM. No matter which option I went for ( and I've tried everything ) it kept spitting out errors ( no physical partitions set up for LVM, cannot add group, etc ) Has this hard disk that you were installing onto ever had LVM used on it in the past, with another distribution perhaps? Just wondering if the disk had some physical volume signatures lying around on it that didn't get blown away with a format or something... regards Andrew -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#256301: LVM in Beta 4
On Sun, Jun 27, 2004 at 03:19:41PM +0200, Leszek wrote: Sorry for being vague - this was my friend's comp and I have no access to it now. We were trying to install Debian on what used to be a Slackware 9.1 root partition. In the Partitioning tool, I have chosen this partition up for a format, fs type ext3, mount at / , mount options defaults, bootable off. Then, I selected done setting up the partition. At this point, the partitioning tool created ext3 on the partition, and I was back at the main list of all partitions. The links below the list said something like help on partitioning guided partitioning and Set up LVM . Even lower, at the lower left, there was a link to go back . But, there was *no* link to continue at the lower right. So, I thought I ought to set up this LVM thing now ( help on partitionning just got me to a help page, of course, and guided partitioning got me to the list of partitionning tasks like erase the whole /dev/hda and manually edit the partition table - so, with no continue, setting up LVM seemed like the only option I can go for at this moment ) Ah, okay. I don't know why you didn't have the equivalent of finish partitioning and continue. If you specifically selected configure LVM, and didn't have the prerequisite LVM stuff done, then it will most probably barf at you as it has. The crux of the problem is why didn't you have a finish partitioning and continue type menu option... Thanks for helping clear this up... regards Andrew -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#236423: Problem persists
reopen 236423 thanks Hi, I'm operating with 1.2004.02.08-7, and I'm still seeing the same stuff getting spat out during the boot process. If there's any more information I can provide, don't hesitate to ask. regards Andrew -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Giving a talk/demo of d-i at CLUG next month
Hi, I've been dobbed in to give a talk on d-i at next month's CLUG meeting. I was planning on giving a brief blurb about the history behind the installer (where we've come from, where we're trying to go) and then launch into a couple of example installs. The main outcome desired is to get feedback on the new installer. I'll pass on that feedback afterwards... I don't think I'll get into the internals too much, but if there's anything I can answer myself from reading the source and the doco in the source, I might have to ask a few silly questions about here... regards Andrew -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: RAID1 on / planned?
On Sun, Jun 13, 2004 at 02:49:26PM +0100, Martin Michlmayr wrote: * Charles Steinkuehler [EMAIL PROTECTED] [2004-06-11 14:45]: I'm pretty handy with shell scripting, and could probably come up with a fix to the grub stuff (espeically with the nice auto-detect stuff in mkinitrd already working!), if that would be of assistance. It would be good if you could find out why LILO and GRUB fail in the first place instead of being able to cope with the situation. Then we can figure out whether we need to put in a workaround or whether LILO/GRUB should just get fixed. I'll look into it more closely after exams (if it isn't sorted by then) but I think in the case of GRUB (from what I've read wrt the hacks to get it to work) it's because /dev/md/0 doesn't correspond to a BIOS device. I get the general impression that GRUB, whilst a very cool bootloader, is a bit rough around the edges when you want to do some of the more esoteric stuff... regards Andrew -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: tasksel rewrite
On Wed, Jun 09, 2004 at 07:09:58AM +0200, Christian Perrier wrote: I think that Debcon was an eye-opener on lot of usability issues for d-i. Can someone who went post a bit of a summary? Andrew (who wish he went) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: [d-i daily 040605] Potentially misleading DHCP retry screen
On Mon, Jun 07, 2004 at 06:58:07AM +0200, Christian Perrier wrote: Besides this, what do others think about this suggestion? It sounded reasonable to me, as does your rewording of it. regards Andrew -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: RAID1 install fails
On Mon, May 31, 2004 at 12:50:25PM -0300, Martin Michlmayr wrote: * W. Borgert [EMAIL PROTECTED] [2004-05-31 12:13]: GRUB message on vt3: /dev/md0 does not have any corresponding BIOS drive. LILO: An installation step failed. (...) failing step is: Install the LILO boot loader on a hard disk. I don't know how to get LILO and GRUB to boot from RAID. I thought it might just work... anyone got a good idea? Bulk hackery, that's how. See http://lists.debian.org/debian-boot/2004/05/msg03665.html This worked for me insofar as I got GRUB to install, but I didn't seem to have a menu.lst, despite the above saying I should have. I had to do further hackery at a grub prompt along the lines of: root (hd0,0) kernel /vmlinuz ro root=/dev/md0 md=0,/dev/foo,/dev/bar initrd /initrd.img boot where /dev/foo (and optionally /dev/bar) were the members of my /dev/md0. (Optional, as in my case, I was trying to build a degraded RAID1). If you have an md1, add 1,/dev/baz,/dev/blaz to the above incantation. Once I managed to boot into the sucker, I recreated my initrd for good measure, and ran update-grub, and it built a menu for me. It wasn't for the faint of heart at all. HTH Andrew -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: RAID1 install fails
On Sun, May 30, 2004 at 11:06:16PM +, W. Borgert wrote: On Sun, May 30, 2004 at 06:35:41PM -0300, Martin Michlmayr wrote: * W. Borgert [EMAIL PROTECTED] [2004-05-30 18:40]: /usr/sbin/mkinitrd: RAID support requires raidtools2 Failed to create initrd image. root on RAID is currently not supported, due to the bug you just saw. With newer d-i images, you should get a warning of root is RAID or LVM. Does somebody have the bug number or at least the name of the package the bug is filed against? Because I'm keen to do a complete RAID1 install, I would like to test again as soon as the bug is closed. TIA! Well the problem is with mkinitrd from initrd-tools. And it used to work. Is initrd-tools being maintained by the new kernel team also, in Herbert's absence? Andrew -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: sysresccd.org
On Thu, May 27, 2004 at 06:45:01PM -0700, Karl Hegbloom wrote: Have you folks seen http://www.sysresccd.org/ ? I think it would be awesome to have something like that based on Debian. The QTparted tool seems to work fairly well -- it runs in a frame-buffer. They also have a nice version of links that uses the frame-buffer as well. QTparted is just mad. I love it. I helped a friend install Debian on his laptop recently, and I had some rescue CD (I've got a bit of a collection happening) that used QTparted, and it was as easy as falling off a log to resize his NTFS partition to make some room. It's like a free version of Partition Magic. Andrew -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Suggestions for udeb development?
On Thu, May 27, 2004 at 10:43:23PM -0700, Matt Zimmerman wrote: I am interested in getting the evms udeb into a working state, and would appreciate any pointers regarding an efficient way to organize my development environment so that I can iteratively make changes to the udeb and test. For instance, is there a way that I can get d-i to download a udeb over the network, or from a mounted filesystem, in preference (or in addition) to those on the installation media? Pointers to any existing resources on this subject appreciated. I'd be interested in hearing how you go, because last time I tried to do some udeb testing to test a patch before I submitted it, I got into a horrible, horrible mess and gave up. I'd like to try again. regards Andrew -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
PowerPC installation experience
Package: install-reports This (attempted) install was performed on my spiffy new PowerBook G4, using the daily built CD netboot image from 20040522. This was done using the install mode, as opposed to expert. I picked en_AU as my language. The next choice, keyboard layout, defaulted to European, which I thought was a bit unusual. I picked American English instead. DHCP failed, because I was unplugged (wanted to use wireless, too bad it seems, must send a nastigram to Broadcom), so I manually configured the onboard (but didn't plug in). I switched from VT1 to VT2 to quickly inspect the current partition table, and on switching back to VT2, the background changed from blue to red. # Note to self, try to reproduce partition rename hang problem When partitioning, the partman main menu offered configuring LVM as an option, however making a partition an LVM phyiscal volume was not, so I couldn't progress very far with using LVM. I made a bunch of plain ordinary partitions. I was next confronted with a message saying that no NewWorld boot partition was found. I had made an 850K partition of this type with partman. Switching to VT2 to look with mac-fdisk reported the size of the partition as only 830K and as of type Apple_Bootstrap. I would have figured this was what yaboot was after? I opted not to go back and frig with the partitioning any further, as it was the default option. The base system installation proceeded. Setting up exim took an absolutely inordinate amount of time due to the fact that DNS was not available. I thought a fake start-stop-daemon was used during the install? This delay caused the progress bar to sit at 70% for quite some time, making it look as if the install had hung. VT3 showed exim4-daemon-light sitting at Starting MTA: for ages. Configuring yaboot was a failure, it displayed a message saying that no hard disks had been found with an Apple_Bootstrap partition. Aha, apparently the name of the partition is the whole problem. I called it nwboot for want of something. Reran the partition disks step, renamed the name of the bootstrap partition to bootstrap (that's all I did, honest), and told it to write the changes. Again, I was confronted with the No NewWorld boot partition was found message (verified with mac-fdisk that the partition was now indeed called bootstrap - it was). The yaboot install step was retried, and again failed. I started examining the yaboot udeb's postinst. I can't grok the mostrosity of a sed call right now (a bit pressed for time) but the output of a parted -s /dev/discs/disc0/disc is: (Manually transposed, so not 100% anatomically accurate with the output) Disk geometry for /dev/ide/host0/bus0/target0/lun0/disc: 0.000-76319.085 megabytes Disk label type: mac Minor Start End Filesystem NameFlags 1 0.000 0.031 Apple 3 0.031 0.841 bootstrap boot 2 128.031 40960.031 hfs+Apple_HFS_Untitled_2 4 40960.031 41448.312 ext3rootroot 5 41448.313 41936.594 linux-swap swapswap 6 41936.595 43843.943 ext3usr 7 43843.944 45751.292 ext3home 8 45751.293 47658.642 ext3var 9 47658.642 48612.316 ext3tmp At this point I aborted the installation, as I'd procrastinated enough and had to do some work on an assignment. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Partman
Hi, Partman seems to be a bit busted (i386, powerpc) (daily build from the 15th) Current partition table is: IDE1 #1 primary 60G ntfs #2 primary 500Mext3 #3 primary 60G LVM If I select #2, the menu choices are: Usage method: dont_use Done setting up the partition If I select dont_use, I can use it as a swap area, LVM PV or a RAID device. Can't delete the partition. Similar behavior if I select #3, except it defaults to using it as a physical volume for LVM. Andrew signature.asc Description: Digital signature
DHCP issues
Hi, (Using daily build from the 15th) DHCP fails, get the DHCP didn't work, sometimes it's slow, wanna try it again or not message. Tried it again a few times. No joy. Logs showed: udhcpc: script /usr/share/udhcpc/default/script failed: No such file or directory Andrew signature.asc Description: Digital signature
Re: sarge install problems on powerpc
On Mon, May 17, 2004 at 10:56:41AM +1200, Allen Unueco wrote: Colin Watson wrote: On Mon, May 17, 2004 at 01:22:11AM +1200, Allen Unueco wrote: With both versions I can't switch to any other virtual consoles. I have a newer 15 PowerBook G4 and I have been using the 'fn' key but fn-alt-F* doesn't do anything. Because of this I haven't really be able to fine out what is going on. Use the Command/Apple key instead. I've tried a lot of key combos and I can't get any of them to switch between consoles. I feel your pain. Ctrl+right/left arrow worked for me. On one boot, alt+f2 did work, on a subsequent boot it (and every other combination) didn't. Really weird. I too have a 15 PowerBook G4 (a week old). Andrew -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#248902: installation-report debian-installer beta4, arch i386
On Thu, May 13, 2004 at 11:13:01PM +0100, Martin Michlmayr wrote: * tbm [EMAIL PROTECTED] [2004-05-13 21:02]: * Nico Dietrich [EMAIL PROTECTED] [2004-05-13 20:22]: LABEL=/ / ext3defaults1 1 LABEL=/home /home ext3defaults1 2 How did you get those LABELs? Did you do that by hand after d-i? Someone suggested a while ago to use LABEL= in d-i. Can someone who uses this feature explain exactly how it works? If I put LABEL=/home in a /etc/fstab, how does Linux know which partition is associated with this label? Basically, at filesystem creation time (or afterwards) labels are added to the filesystems. AFAIK, this is an ext2/3 and xfs feature, I'm not aware of other filesystems that have it, someone may correct me. This can be done with the mke2fs/tune2fs/mkfs.xfs -L option, or the e2label/xfs_admin programs. From fstab(5): Instead of giving the device explicitly, one may indicate the (ext2 or xfs) filesystem that is to be mounted by its UUID or volume label (cf. e2label(8) or xfs_admin(8)), writing LABEL=label or UUID=uuid, e.g., `LABEL=Boot' or `UUID=3e6be9de-8139-11d1-9106-a43f08d823a6'. This will make the system more robust: adding or removing a SCSI disk changes the disk device name but not the filesystem volume label. So, it would actually be probably more desirable to mount using the UUID than the label (however the label is more memorable), as most filesystems have a UUID, whereas only a few support a label. I would suggest that in the case of ext2/3 and XFS, when a filesystem is created, it automatically gets labelled with a name relevant to what the filesystem mount point should be, but perhaps in all cases the /etc/fstab entry uses the filesystem's UUID. The administrator can, if need be in a recovery situation, mount /usr by going mount LABEL=/usr /usr, but the system would normally mount /usr by it's UUID. Hope this helps. Andrew signature.asc Description: Digital signature
Bug#247934: Spelling mistake in Low Memory error message
Package: debian-installer There's a spelling mistake in the Low Memory message that came up when I ran d-i in qemu: Among is spelt as amoung -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Software RAID support
On Fri, May 07, 2004 at 09:26:23AM +1000, Herbert Xu wrote: On Fri, May 07, 2004 at 09:20:03AM +1000, Andrew Pollock wrote: I thought it was behaviour by design. IIRC, the script explicitly grepped out non-ok mirror devices. This was fixed in 0.1.63: * Add inactive MD constituent devices as well (closes: #238514). Ah. It's been a couple of months since I played with it. Cool. Andrew -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Software RAID support
On Tue, May 04, 2004 at 07:35:38PM +0200, Paul Fleischer wrote: On Sunday 02 May 2004 03:16, Martin Michlmayr wrote: Paul, Now that beta4 is out, what are your plans of getting mdcfg and partman-md uploaded to get some testing? As I am not sure how to go about it, I have no plans. But I am very interrested in getting them uploaded, so that we can get a larger testing base. What's the status of these programs? Actually, they are quite useable. mdcfg currently only supports RAID1, but it can easily be extended. There are three major showstoppers for a sucessfull installation with software RAID right now: 1) Neither the grub nor the lilo installer can handle md-devices it at all. They fail miserably when both /boot and / partitions are md-devices. You sure? When I last played with RAID1 and mdadm, I had GRUB doing funky stuff with everything being on MD devices. 2) The initrd image generated by mkinitrd only activates the first md-device for some weird reason. mkinitrd is fussy, the mirror must be fully built and healthy to be used. Andrew -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#236423: ping
Hi, I'd like to help resolve this. I haven't had a response to my last response. regards Andrew -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Software RAID support
On Fri, May 07, 2004 at 07:59:19AM +1000, Herbert Xu wrote: Andrew Pollock [EMAIL PROTECTED] wrote: 2) The initrd image generated by mkinitrd only activates the first md-device for some weird reason. mkinitrd is fussy, the mirror must be fully built and healthy to be used. It shouldn't be. It's meant to pick up whatever disks are listed in the superblocks or raidtab. If that's not the case, please file a bug. What I'm saying is I've found from experience with RAID1 (using mdadm) that if the MD device the root filesystem was on was not in a healthy state when mkinitrd was run, it wouldn't put the commands in the initrd to attach the other half of the mirror on bootup. So if the mirror was still syncronising at mkinitrd run time, or the mirror was only built with one member, that's the way the mirror would be on subsequent reboots. I thought it was behaviour by design. IIRC, the script explicitly grepped out non-ok mirror devices. Andrew -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#247627: INSTALL REPORT
On Thu, May 06, 2004 at 01:01:03AM -0700, Matt Kraai wrote: It should use either the kernel-image-$version or kernel-image-$version-smp package, where $version is the output of uname -r | cut -d . -f 1,2 2.4 unless said package is not included in the output of chroot /target apt-cache search kernel-image | grep ^kernel-image | cut -d -f1 | uniq kernel-image-2.4.25-1-386 kernel-image-2.6.3-1-386 Would you please send the output of both commands? Hmm, would you look at that... The netinst CD's only got 386 kernels on it... -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Kernels on netinst CD
Hi, Any chance of putting more than just the i386 kernel (i.e. an i686 one) on the netinst CDs? regards Andrew -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#247780: partman LV filesystem detection problem
Package: partman Hi, Rather than repartition, this time I chose to leave my partitioning as it was (/dev/hda2 = ext3 /dev/hda3 = swap /dev/hda4 = LVM) and reactivate the existing VG. This worked fine, and the partitioner showed the partition arrangement as it should. When I then went to each LV, and went to mount them, the partitioner said that no filesystem was detected on the LV, and only gave me the choice of formatting it, not leaving it as it was and mounting it. I suspect something's amiss with the filesystem detection code. Andrew -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
