Bug#256766: base-config: Wrong consolefont? Seeing ae ligature instead of line drawing chars
Quoting Karl Hegbloom ([EMAIL PROTECTED]): > Package: base-config > Version: 2.29 > Severity: normal > > Used d-i 2004/06/28 to install in a VMware. All good, up until base- Which image exactly? Which locale? I'm doing detailed tests of both sarge_d-i and sid_d-i images and this well known problem of tc1 is supposed to be away for weeks. Which kernel ? 2.4 or 2.6 ?
Bug#256710: Catalan translations
Quoting Jordi Mallach ([EMAIL PROTECTED]): > Package: discover1 > Severity: wishlist > > Attached are the Catalan translations for the program and debconf > templates. The programs translation is also slightly outdated. Attached is the file to be updated ca.po Description: application/gettext
Re: preparing for tc2
Quoting Joey Hess ([EMAIL PROTECTED]): > Several fixes have gone into testing, but I still have these issues listed as > important and unresolved in testing: > > - some broken m68k images (fix: mke2fs fix needed; UNKNOWN) Yep ? The IRC meeting lead to nothing on that topic. > - broken sparc64 module loading (fix: busybox-cvs 20040415-3) > >The buybox-cvs fix cannot go in until we've dealt with netcfg. Either we >update netcfg, or we need a newer busybox-cvs that turns udhcp back >on to avoid breaking the netcfg in testing. I plan to do the latter >by a NMU soon, if nothing else is done. We had a few people, namely Giuseppe Sacco and Martin Krafft, who volunteered for netcfg testing. maybe they should coordinate with Joshua and Thomas, now. > - mips Installs on r4k-ip22 needs 36 mb ram (fix: unknown -- new >glibc?) > >If it's the new glibc, then just rebuilding the images using the rc1 >branch should fix these problems. Can someone check this? Thiemo Seufer mentioned during the meeting he is OK to check this thing, but he wasn't sure about having enough time It seems that a quite large agreement is achieved about the new languagechooser/countrychooser scheme. having it in tc2 would seem to be a very important improvement, and is also needed for BiDi support in 2nd stage. This is not strictly release critical and I still remember we both agreed to postpone these after rc1 (so, after tc2) at the end of Debconf. However, lot of time passed since thenand I tested this stuff nearly daily, always changing languages here and there (I even have now a framework for testing netboot images and possibly find nasty crash bugs like the one you found for Arabic). So, I think I need to convince you that pushing languagechooser/countrychooser/lowmem (the 3 are needed in the same time) to testing will be an enhancement and NOT introducing new bugs like it may have been in the past. Oh, and while I'm at it, choose-mirror, if pushed to testing needs either a solid review of the code in sort-countriesor commenting this script temporarily if unsure (thus needing a new upload). BTW, this script can be "set -e". tc2 needs of course a small string freeze. I would say that 3-4 days may be enough as long as a one-week delay for warning translators before the freeze is allowed. A string freeze over a week-end is better (say, from a Thursday 18:00 up to a Sunday 18:00 UTC) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#256710: Catalan translations
Quoting Jordi Mallach ([EMAIL PROTECTED]): > Package: discover1 > Severity: wishlist > > Attached are the Catalan translations for the program and debconf > templates. The debconf translation does not fit templates.pot. Attached is your file after msgmerge with templates.pot. Can you please update? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: tagging 256774
Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.7.95.1 > tags 256774 pending Bug#256774: "tasksel" misspelled in warnings and errors Tags were: patch Tags added: pending > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: USB Problems
Well, I'm very sure (90% sure) that it was TC1. I know beta4 is up there now and I remember seeing a TC1 images then a note saying "if TC1 doesn't work, try beta4" and beta4 images were right below. But yes, I understand what you're saying. On Mon, 28 Jun 2004 17:59:51 -0700, Karl Hegbloom <[EMAIL PROTECTED]> wrote: > > On Mon, 2004-06-28 at 16:21 -0400, Nathan Widmyer wrote: > > On Mon, 28 Jun 2004 15:23:46 -0400, Joey Hess <[EMAIL PROTECTED]> wrote: > > > > > > Nathan Widmyer wrote: > > > > I'm trying to install Debian sarge on a hard drive in a USB enclosure. > > > > I got the 110MB sarge image. > > > > > > Which version? > > > > > > > The date on the file is June 22nd, so thats either the date from the > > original file on debians' server or the date I finished downloading > > the image. If there a way to tell definitely because opening the > > readme, it only says "Debian GNU/Linux testing "Sarge" - Official > > NetInst Snapshot i386 Binary-1 CD" > > You should rename the iso right after you download it to something like > "sarge-i386-netinst-2004.06.28.iso" so that the iso-8601 date is encoded > in the file name. They cannot rename it on the server, or the "current" > link will break. > > -- > Karl Hegbloom <[EMAIL PROTECTED]> > > > -- > 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: USB Problems
On Mon, 2004-06-28 at 16:21 -0400, Nathan Widmyer wrote: > On Mon, 28 Jun 2004 15:23:46 -0400, Joey Hess <[EMAIL PROTECTED]> wrote: > > > > Nathan Widmyer wrote: > > > I'm trying to install Debian sarge on a hard drive in a USB enclosure. > > > I got the 110MB sarge image. > > > > Which version? > > > > The date on the file is June 22nd, so thats either the date from the > original file on debians' server or the date I finished downloading > the image. If there a way to tell definitely because opening the > readme, it only says "Debian GNU/Linux testing "Sarge" - Official > NetInst Snapshot i386 Binary-1 CD" You should rename the iso right after you download it to something like "sarge-i386-netinst-2004.06.28.iso" so that the iso-8601 date is encoded in the file name. They cannot rename it on the server, or the "current" link will break. -- Karl Hegbloom <[EMAIL PROTECTED]> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#256774: "tasksel" misspelled in warnings and errors
Package: tasksel
Version: 2.03
Severity: minor
Tags: patch
The warning and error functions misspell "tasksel" as "taskel".
The attached patch fixes them.
--
Matt Kraai[EMAIL PROTECTED]http://ftbfs.org/
Index: tasksel/tasksel.pl
===
--- tasksel/tasksel.pl (revision 606)
+++ tasksel/tasksel.pl (working copy)
@@ -13,11 +13,11 @@
my $descdir="/usr/share/tasksel";
sub warning {
- print STDERR "taskel: @_\n";
+ print STDERR "tasksel: @_\n";
}
sub error {
- print STDERR "taskel: @_\n";
+ print STDERR "tasksel: @_\n";
exit 1;
}
Bug#256091: marked as done (gzip error in ed's postinst)
Your message dated Mon, 28 Jun 2004 14:12:09 -0700 with message-id <[EMAIL PROTECTED]> and subject line hardware problem has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) -- Received: (at submit) by bugs.debian.org; 24 Jun 2004 23:52:02 + >From [EMAIL PROTECTED] Thu Jun 24 16:52:02 2004 Return-path: <[EMAIL PROTECTED]> Received: from zoon.lafn.org [206.117.18.9] by spohr.debian.org with esmtp (Exim 3.35 1 (Debian)) id 1Bde0g-0002W6-00; Thu, 24 Jun 2004 16:52:02 -0700 Received: from localhost (host-66-81-183-46.rev.o1.com [66.81.183.46]) by zoon.lafn.org (8.12.3p3/8.11.3) with ESMTP id i5ONpwLI062462 for <[EMAIL PROTECTED]>; Thu, 24 Jun 2004 16:52:00 -0700 (PDT) (envelope-from [EMAIL PROTECTED]) Received: from kraai by localhost with local (Exim 4.32) id 1Bdc95-Ho-58 for [EMAIL PROTECTED]; Thu, 24 Jun 2004 14:52:35 -0700 Date: Thu, 24 Jun 2004 14:52:35 -0700 From: Matt Kraai <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Subject: gzip error in ed's postinst Message-ID: <[EMAIL PROTECTED]> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.6+20040523i Sender: Matt Kraai <[EMAIL PROTECTED]> X-Virus-Scanned: clamd / ClamAV version 0.70, clamav-milter version 0.70j Delivered-To: [EMAIL PROTECTED] X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_25 (1.212-2003-09-23-exp) on spohr.debian.org X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE autolearn=no version=2.60-bugs.debian.org_2004_03_25 X-Spam-Level: Package: debian-installer Version: http://people.debian.org/~joeyh/d-i/images/2004-06-24/floppy/ I sometimes see the following error (2 out of the 4 most recent tries): Setting up ed (0.2-20) ... gzip: stdin: invalid compressed data--crc error install-info(/usr/share/info/ed.info.gz): read gzip -cd http://ftbfs.org/ --- Received: (at 256091-done) by bugs.debian.org; 29 Jun 2004 00:41:28 + >From [EMAIL PROTECTED] Mon Jun 28 17:41:28 2004 Return-path: <[EMAIL PROTECTED]> Received: from zoon.lafn.org [206.117.18.9] by spohr.debian.org with esmtp (Exim 3.35 1 (Debian)) id 1Bf6gi-00071R-00; Mon, 28 Jun 2004 17:41:28 -0700 Received: from localhost (host-66-81-199-39.rev.o1.com [66.81.199.39]) by zoon.lafn.org (8.12.3p3/8.11.3) with ESMTP id i5T0fNPL036819 for <[EMAIL PROTECTED]>; Mon, 28 Jun 2004 17:41:27 -0700 (PDT) (envelope-from [EMAIL PROTECTED]) Received: from kraai by localhost with local (Exim 4.32) id 1Bf3QA-RY-4m for [EMAIL PROTECTED]; Mon, 28 Jun 2004 14:12:10 -0700 Date: Mon, 28 Jun 2004 14:12:09 -0700 From: Matt Kraai <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Subject: hardware problem Message-ID: <[EMAIL PROTECTED]> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.6+20040523i Sender: Matt Kraai <[EMAIL PROTECTED]> X-Virus-Scanned: clamd / ClamAV version 0.70, clamav-milter version 0.70j Delivered-To: [EMAIL PROTECTED] X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_25 (1.212-2003-09-23-exp) on spohr.debian.org X-Spam-Status: No, hits=-3.0 required=4.0 tests=BAYES_00 autolearn=no version=2.60-bugs.debian.org_2004_03_25 X-Spam-Level: Howdy, I think this is a hardware problem, so I'm closing this bug. -- Matt Kraai[EMAIL PROTECTED]http://ftbfs.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#256766: base-config: Wrong consolefont?
More information... It may be a console-tools bug (though I'm not certain) since the same problem occurs (of course) in aptitude and anything else trying to use the line drawing characters. They are just not present in the console font being used. -- Karl Hegbloom <[EMAIL PROTECTED]> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Grub and XFS root.
I've tried two installs with XFS / and no /boot partition. It hangs at grub-install. When I go to the second console, and kill off the grub and grub-install script, then run grub by hand and type: grub> setup (hd0) (hd0,1) ... it succeeds and I can boot the machine with no apparent problems. If I let it use the default ext3 file system, it never hangs, and it works fine. -- Karl Hegbloom <[EMAIL PROTECTED]> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#256766: base-config: Wrong consolefont? Seeing ae ligature instead of line drawing chars
Package: base-config Version: 2.29 Severity: normal Used d-i 2004/06/28 to install in a VMware. All good, up until base- config. Now I see ae ligatures instead of console line drawing characters in the border of the debconf widgets (see the attached png). I don't recall seeing this in the 2004/05/25 I had used previously... don't know if it's the d-i or the base-config that is a fault. You tell me and we'll both know. -- Karl Hegbloom <[EMAIL PROTECTED]> <>
sysresccd.org, run_qtparted, Success resizing NTFS (XP)
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? -- Karl Hegbloom <[EMAIL PROTECTED]> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#256572: Debian Installation Report
One more observation about the disk paritioner. If you make a mistake, and there are 2 identical partitions on different drives, mounted on the same directory, it is not possible to delete the second instance of this. If the paritiomer is asked to do that, it will delete the parition on the first drive. A second attempt removes the incorrect partition, but the correct partition has to be created again. This is unexpected and confusing behaviour. -- Regards, -o) Matthijs Melchior Maarssen /\\ [EMAIL PROTECTED] Netherlands _\_v -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#248071: Hot plugged devices shouldn't be marked "auto"
On Mon, Jun 28, 2004 at 10:36 +0200, Thomas Hood wrote: > I think that pcmcia-cs should ship with an /etc/pcmcia/network > script that does nothing by default. I agree. But how do we provide a smooth upgrade here? Default to the new behaviour on new installations but ask using debconf during upgrades from earlier versions with the old behaviour? > The installer should enable the hotplug mechanism for all interfaces > on PCMCIA cards. That means listing those interface names on "map" > lines in the "mapping hotplug\n\tscript grep" stanza. It already does (barring bugs), but I see in another mail that you already know that. > All other interfaces should be marked "auto". The installer only configures one interface (except lo). Thomas Hood writes: > The upshot of this for hw-detect and pcmcia-cs is that they have to > be set up in one of the two following ways. > > 1. pcmcia-cs ifups/ifdowns interfaces on 16 bit PCMCIA cards >by default (as now) and hw-detect does not list such interfaces >in /etc/network/devhotplug, instead listing them in >/etc/network/devcardmgr (so that netcfg knows not to mark them >as "auto"). (This requires a change to hw-detect.) I thought that this was difficult previously but now I know that one can simply look in /var/run/stab to determine whether a network interface is a 16-bit card (Cardbus interfaces aren't listed). So implementing this in hw-detect should as simple as changing one line in the gen_pcmcia_devnames function in hw-detect.sh. Changing this in netcfg should be simple as well. > 2. pcmcia-cs does not ifup/ifdown interfaces on 16 bit PCMCIA cards >by default (which requires a change to pcmcia-cs) and hw-detect >lists such interfaces in /etc/network/devhotplug (as now). This solution would be preferable, but is it feasible to make this change for sarge? > Currently, pcmcia-cs ifups/ifdowns interfaces on 16 bit PCMCIA cards > and hw-detect lists such cards in /etc/network/devhotplug, which > is not one of the reasonable options: we shouldn't have hotplug and > cardmgr battling for control of those interfaces. I agree that this is ugly, but is it a problem in practice? -- Pelle -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#256374: Installation hangs on Compaq Presario 1220 while loading module 'ide-cd' during hardware detection for the CD-ROM drive (beta4, i386, linux26)
On Sun, Jun 27, 2004 at 19:54 -0300, Robin Blondon wrote: > In the installer, I found that instead of ejecting and reinserting the > card I can go into the shell and kill and restart cardmgr. The > intstaller then detected the card after choosing to detect network > hardware from the installer menu. Hrm... strange. It could be because the installer first lacks the necessary modules and then fails to restart cardmgr properly when the modules are available. What if you choose detect network hardware a second time without killing and restarting cardmgr? And, by the way, do you have a Cardbus card or a 16-bit card? > The first set of messages are: > Configuring network interfaces...Error for wireless request "Set ESSID" > (8B1A): > SET failed on device eth0 ; No such device. > Error for wireless request "Set Encode" (8B2A) : > SET failed on device eth0 ; No such device. > Error for wireless "Set Mode" (8B06) : > SET failed on device eth0 ; No such device. Actually, the card should not be brought up by this init script. It should be brought up by cardmgr or hotplug. This means that the installer failed to recognise that the network interface was a PCMCIA card and thus erroneously added an "auto eth0" line to /etc/network/interfaces. > The second set of messages after starting PCMCIA services are: > /lib/modules/2.4.25-1-386/kernel/drivers/pcmcia/yenta_socket.o: > init_module: No such device > Hint: insmod errors can be caused by incorrect module parameters, > including invalid IO or IRQ parameters. > You may find more information in syslog or the output from dmesg > /lib/modules/2.4.25-1-386/kernel/drivers/pcmcia/yenta_socket.o: insmod > /lib/modules/2.4.25-1-386/kernel/drivers/pcmcia/yenta_socket.o failed > /lib/modules/2.4.25-1-386/kernel/drivers/pcmcia/yenta_socket.o: indmos > yenta_socket failed The problem here is probably that yenta_socket isn't the right module. Could you try loading i82365 instead? The pcmcia-cs package should have detected this but maybe something went wrong. > Is there anything else I should try? You could check the logs during the installation, i.e. "grep cardmgr /var/log/syslog". -- Pelle -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#256572: Debian Installation Report
Joey Hess wrote: Matthijs Melchior wrote: Debian-installer-version: 20040616 ftp.debian.org Please tell us the url of the image you downloaded for the install. I hope this is sufficent info: http://cdimage.debian.org/pub/cdimage-testing/cd/jigdo-area/i386/sarge-i386-1.jigdo http://cdimage.debian.org/pub/cdimage-testing/cd/jigdo-area/i386/sarge-i386-2.jigdo downloaded dd 20040622 -- -o) Matthijs Melchior Maarssen /\\ [EMAIL PROTECTED] Netherlands _\_v -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: preparing for tc2
|| On Mon, 28 Jun 2004 14:43:32 -0700 || Joshua Kwan <[EMAIL PROTECTED]> wrote: jk> On Mon, 28 Jun 2004 17:57:01 -0300, Otavio Salvador wrote: >> What is bloking netcfg to going to testing? jk> 0.70 sucks. Now that we have Thomas Hood on the bandwagon it's been bugfix jk> city here in netcfg land. Right and so why doesn't try to stop to fix new issues and stabilize it to have it in testing near? -- O T A V I OS A L V A D O R - E-mail: [EMAIL PROTECTED] UIN: 5906116 GNU/Linux User: 239058 GPG ID: 49A5F855 Home Page: http://www.freedom.ind.br/otavio - "Microsoft gives you Windows ... Linux gives you the whole house." pgpypv3k8yo6R.pgp Description: PGP signature
Re: preparing for tc2
On Mon, 28 Jun 2004 17:57:01 -0300, Otavio Salvador wrote: > What is bloking netcfg to going to testing? 0.70 sucks. Now that we have Thomas Hood on the bandwagon it's been bugfix city here in netcfg land. -- Joshua Kwan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#248071: TODO for hw-detect and/or pcmcia-cs
On Mon, 2004-06-28 at 22:47, Osamu Aoki wrote: > > 2. pcmcia-cs does not ifup/ifdown interfaces on 16 bit PCMCIA cards > >by default (which requires a change to pcmcia-cs) and hw-detect > >lists such interfaces in /etc/network/devhotplug (as now). > > Yes. This will be nice since these ifup/ifdown hack in pcmcia-cs is > Debian specific hack added in pre-Woody days. I like to see this but > the pcmcia-cs maintainer looks like he is determined to keep current > feature with good reason. pcmcia-cs has a new maintainer who may have different ideas. > As I see, the only compromise pcmcia-cs maintainer may accept should be > the one which he does not need to worry about use[r]s complaining unhappy > upgrade experiences. We certainly don't want to inconvenience users who upgrade pcmcia-cs. > Thomas, is it possible for you to provide debconf low priority question > to customize pcmcia-cs in traditional ways with ifup/ifdown hack > (default of pcmcia-cs package) and alternatively to customize pcmcia-cs > without old Debian ifup/ifdown hack (seeded by debian-installer). > This is like new hotplug package. What I would suggest is that /etc/pcmcia/network be modified so that it does nothing (by default) if a flag file named something like '/etc/pcmcia/network.no-default-ifupdown' is present. The sarge installer could then create this file in order to select the new behavior. Thus, people who merely upgrade pcmcia-cs don't see a change in behavior but people who install sarge get the new behavior. If the pcmcia-cs maintainer preferred he could give the admin the chance to create this flag file by answering a debconf question in the affirmative. -- Thomas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: preparing for tc2
|| On Mon, 28 Jun 2004 15:51:31 -0400 || Joey Hess <[EMAIL PROTECTED]> wrote: jh> - broken sparc64 module loading (fix: busybox-cvs 20040415-3) jh>The buybox-cvs fix cannot go in until we've dealt with netcfg. Either we jh>update netcfg, or we need a newer busybox-cvs that turns udhcp back jh>on to avoid breaking the netcfg in testing. I plan to do the latter jh>by a NMU soon, if nothing else is done. What is bloking netcfg to going to testing? -- O T A V I OS A L V A D O R - E-mail: [EMAIL PROTECTED] UIN: 5906116 GNU/Linux User: 239058 GPG ID: 49A5F855 Home Page: http://www.freedom.ind.br/otavio - "Microsoft gives you Windows ... Linux gives you the whole house." pgp7HjoWKEAG6.pgp Description: PGP signature
Re: ssh support for notebooks :) --> screen?
Hi, On Mon, Jun 28, 2004 at 01:07:21AM +0100, Colin Watson wrote: > On Mon, Jun 28, 2004 at 01:25:21AM +0200, Osamu Aoki wrote: > > On Sun, Jun 27, 2004 at 08:21:18PM +0100, Colin Watson wrote: > > > openssh-client-udeb. I didn't package scp because it's straightforward > > > to do the same thing with ssh and tar, but I suppose I could add it. > > > > openssh-client-udeb is sufficient for me. I only meant some SCP like > > functionality. I really doubt needs to login to another machine from a > > machine running on initrd. So really stripped down ssh shall be enough > > (no X forwarding etc.) > > Sure, although some people (e.g. me :-)) do like to be able to log into > other machines from the middle of a d-i install. You can use that > facility to ask for help, for instance. That is a very good point. There is no man nor info on d-i process. Hmmm... How come I missed it. I guess I was only looking for ssh-client-udeb. It did not hit me to look under "o". Thanks. > > Just nit pick. It is ssh+cat == scp. 'scp foo [EMAIL PROTECTED]:bar' is like > > 'bar"'. "tar" is a sepatete issue although > > it is an idiom used with ssh to move multiple files. (These files will > > not be concatenated if moved with ssh+tar in the famous way.) > > I beg to differ. scp preserves file modes, for instance, unlike ssh+cat. You got me. I should have said, for my requirements, I can do file transfer simply by ssh+cat. Use of tar looked overkill to me but tar and cat are already parts of busybox. No difference in binary size. > > By the way, speaking of basic functionality of initrd, I do not see > > "screen" command missing in initrd nor in pool/* as udeb. I wonder how > > you are handling some operations which kill the remote terminal > > connection used for the install. > > We don't perform such operations. :-) I do not have Big IBM here either. But someday when I want to boot broken LCD old notebook PC, I may need it. Osamu -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#248071: TODO for hw-detect and/or pcmcia-cs
Hi, this bug is now filed to netcfg as I understand :) On Mon, Jun 28, 2004 at 07:45:38PM +0200, Thomas Hood wrote: > The upshot of this for hw-detect and pcmcia-cs is that they have to > be set up in one of the two following ways. > > 1. pcmcia-cs ifups/ifdowns interfaces on 16 bit PCMCIA cards >by default (as now) and hw-detect does not list such interfaces >in /etc/network/devhotplug, instead listing them in >/etc/network/devcardmgr (so that netcfg knows not to mark them >as "auto"). (This requires a change to hw-detect.) Maybe this may be more easily implemented considering the audience of this bug. But IMHO, it is not nice. Why retain Debian specific hack in the installer pcmcia-cs udeb system which has no need to have compatibility with ifupdown package of Potato. > 2. pcmcia-cs does not ifup/ifdown interfaces on 16 bit PCMCIA cards >by default (which requires a change to pcmcia-cs) and hw-detect >lists such interfaces in /etc/network/devhotplug (as now). Yes. This will be nice since these ifup/ifdown hack in pcmcia-cs is Debian specific hack added in pre-Woody days. I like to see this but the pcmcia-cs maintainer looks like he is determined to keep current feature with good reason. As I see, the only compromise pcmcia-cs maintainer may accept should be the one which he does not need to worry about uses complaining unhappy upgrade experiences. Thomas, is it possible for you to provide debconf low priority question to customize pcmcia-cs in traditional ways with ifup/ifdown hack (default of pcmcia-cs package) and alternatively to customize pcmcia-cs without old Debian ifup/ifdown hack (seeded by debian-installer). This is like new hotplug package. This should give people upgrading from Woody smooth transition while fresh Sarge install can get nice hotplug enabled system. ... wait pcmcia-cs package you are talking may be udeb. Well, in that case, we can share code base with updated deb package, isn't it? Just a thought... (By the way, tc1 CD was detecting 16bit PCMCIA NIC but recent sid-di are not detecting 16bit PCMCIA NIC any more. A bit wondering.) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: preparing for tc2
Joey Hess wrote: > - broken sparc64 module loading (fix: busybox-cvs 20040415-3) I meant to write 20040507-1 there. -- see shy jo signature.asc Description: Digital signature
s390 d-i report
It still doesn't work, but with the new zipl-installer.postinst it comes a lot closer. netcfg (actually netcfg-static) still doesn't work the first time. What you have to do is to select IUCV, which generates an error, and then go back in from the main menu, select option #3 (network config), and everything works fine the second time. The symptoms are as follows: whatever you enter is sort of recognized--that is, if you choose CTC and you don't have any CTC devices in your configuration, you're told so. But if you do choose the interface type you have (qeth, in my case), the installer simply asks you to choose an interface type again. I have no idea why this is. I've looked through s390/netdevice and I'm not seeing the problem. I'm going to try to add IUCV support soon, because that should be pretty straightforward. Once you've gotten past the network device configuration, everything goes smoothly up until "Make System Bootable". At this point, the stock install fails, because of a missing symlink for /vmlinuz. The patch I just posted for zipl-installer.postinst fixes this and adds a correct parmline for the DASD configuration. Installing this could in theory be done from the 3270 console. I find that a huge pain, so I've been doing a chroot to /target, removing /etc/securetty, and enabling inetd, so I have a smarter terminal to work with. Then I can telnet to the chroot'ed /target, use cat and ^D to copy zipl-installer.postinst to /tmp, and then, from the console, cp /target/tmp/zipl* /var/lib/dpkg/info chmod 755 /var/lib/dpkg/info/zipl* Rebooting the system from the installer doesn't work. Woody just ran /sbin/halt and advised the user to IPL from the root DASD device; I think a similar trick will be needed for Sarge. The problem with reboot is that it, in the S/390 world, attempts to boot from the last device you IPLed from, which will be either the card deck or the tape drive, rather than your new root disk. After that, the next problem is that base-config tries to run on the console. Since the 3270 is a line-mode EBCIDC terminal that does not understand ANSI terminal codes, this fails messily. The workaround is to replace /etc/inittab with /etc/inittab.real. Then run /sbin/halt, and, from the console, IPL from your root device. Remember that you will have inetd running and a root telnet session will be enabled. Then telnet in as root (it'll be nice when we have sshd on the install system), and run base-config from your telnet session. After that everything goes smoothly again. Once it's done and you've installed sshd, put /etc/securetty back and disable telnetd in /etc/inetd.conf. Adam -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
20040627 i386 sid_d-i netinsta 2.4 OK
Environment: VmWare Platform : i386 Kernel : 2.4 Locale : fr_FR Image : netinst Priority : high Result : OK -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#256738: rootskel: amd64 support.
Package: rootskel Version: 0.78 Tags: patch Could you please apply the attached patch? This is required for amd64 to find it's linker. Kurt --- debian/rules.orig 2004-06-28 22:05:13.996244951 +0200 +++ debian/rules2004-06-28 22:04:08.413811353 +0200 @@ -26,6 +26,9 @@ dh_testroot $(MAKE) install +ifeq ($(shell dpkg-architecture -qDEB_BUILD_ARCH),amd64) + ln -s lib debian/rootskel/lib64 +endif binary-indep: build install
Re: USB Problems
On Mon, 28 Jun 2004 15:23:46 -0400, Joey Hess <[EMAIL PROTECTED]> wrote: > > Nathan Widmyer wrote: > > I'm trying to install Debian sarge on a hard drive in a USB enclosure. > > I got the 110MB sarge image. > > Which version? > The date on the file is June 22nd, so thats either the date from the original file on debians' server or the date I finished downloading the image. If there a way to tell definitely because opening the readme, it only says "Debian GNU/Linux testing "Sarge" - Official NetInst Snapshot i386 Binary-1 CD" > > > > I can boot with either 2.4 or 2.6 > > kernel and after I partition the hard drive and when it starts to > > write the base-install data, the busy light on the drive enclosure > > stays on continuously, even after my laptop is powered down. I get a > > dbootstrap error, and in a console, it says it can't find the USB > > device file. If I go back through the setup, the USB hard drive is > > not shown anywhere to install to. To resume normal operation I have > > to turn the enclosure off, wait an appropriate amount of time, then > > turn it back on then it's okay. > > > > The only non-standard thing I do is add the option > > "hw-detect/start_pcmcia=false" because if not, when PCMCIA is loaded, > > it locks up my laptop and I need to remove the AC adapter and battery > > before it will budge. > > > > The enclosure is a Hotway HD2-U2FW Firewire 400/USB 2.0 enclosure > > arouund a Maxtor 80GB hard drive. The enclosure has had 0 problems in > > Windows, so it sounds like something is fishy with the USB HDD > > drivers. > > Yes, it sounds like large data transfers are hosing the drive.. > > -- > see shy jo > > > > signature.asc - 1K > Is that something the folks that write Debian can fix or is that more for the linux kernel crowd? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: lvm
Processing commands for [EMAIL PROTECTED]: > reassign 256301 lvmcfg Bug#256301: LVM in Beta 4 Bug reassigned from package `installation-reports' to `lvmcfg'. > -- Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#256604: marked as done (Can't exec "0")
Your message dated Mon, 28 Jun 2004 15:47:27 -0400 with message-id <[EMAIL PROTECTED]> and subject line Bug#256604: fixed in tasksel 2.03 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) -- Received: (at submit) by bugs.debian.org; 28 Jun 2004 03:20:37 + >From [EMAIL PROTECTED] Sun Jun 27 20:20:37 2004 Return-path: <[EMAIL PROTECTED]> Received: from smtp814.mail.sc5.yahoo.com [66.163.170.84] by spohr.debian.org with smtp (Exim 3.35 1 (Debian)) id 1BemhB-00088f-00; Sun, 27 Jun 2004 20:20:37 -0700 Received: from unknown (HELO triplehelix.org) ([EMAIL PROTECTED]@68.126.234.108 with login) by smtp814.mail.sc5.yahoo.com with SMTP; 28 Jun 2004 03:20:36 - Received: from darjeeling.triplehelix.org (darjeeling.wifi.triplehelix.org [192.168.0.7]) by triplehelix.org (Postfix) with ESMTP id 13D312E0FB; Sun, 27 Jun 2004 20:20:36 -0700 (PDT) Received: from joshk by darjeeling.triplehelix.org with local (Exim 3.36 #1 (Debian)) id 1Bemh9-00082A-00; Sun, 27 Jun 2004 20:20:35 -0700 Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: Joshua Kwan <[EMAIL PROTECTED]> To: Debian Bug Tracking System <[EMAIL PROTECTED]> Subject: Can't exec "0" X-Mailer: reportbug 2.62 Date: Sun, 27 Jun 2004 20:20:35 -0700 Message-Id: <[EMAIL PROTECTED]> Sender: Joshua Kwan <[EMAIL PROTECTED]> Delivered-To: [EMAIL PROTECTED] X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_25 (1.212-2003-09-23-exp) on spohr.debian.org X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE autolearn=no version=2.60-bugs.debian.org_2004_03_25 X-Spam-Level: Package: tasksel Version: 1.52 Severity: important After quitting aptitude without installing anything: Can't exec "0": No such file or directory at /usr/bin/tasksel line 252. $0 maybe? -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.7-mm3 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (ignored: LC_ALL set to en_US.UTF-8) Versions of packages tasksel depends on: ii libc6 2.3.2.ds1-13 GNU C Library: Shared libraries an ii libtextwrap10.1-1text-wrapping library with i18n - ii slang1a-utf81.4.9-4 The S-Lang programming library wit --- Received: (at 256604-close) by bugs.debian.org; 28 Jun 2004 19:53:44 + >From [EMAIL PROTECTED] Mon Jun 28 12:53:44 2004 Return-path: <[EMAIL PROTECTED]> Received: from newraff.debian.org [208.185.25.31] (mail) by spohr.debian.org with esmtp (Exim 3.35 1 (Debian)) id 1Bf2CG-0003Ew-00; Mon, 28 Jun 2004 12:53:44 -0700 Received: from katie by newraff.debian.org with local (Exim 3.35 1 (Debian)) id 1Bf26B-0001h4-00; Mon, 28 Jun 2004 15:47:27 -0400 From: Joey Hess <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] X-Katie: $Revision: 1.51 $ Subject: Bug#256604: fixed in tasksel 2.03 Message-Id: <[EMAIL PROTECTED]> Sender: Archive Administrator <[EMAIL PROTECTED]> Date: Mon, 28 Jun 2004 15:47:27 -0400 Delivered-To: [EMAIL PROTECTED] X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_25 (1.212-2003-09-23-exp) on spohr.debian.org X-Spam-Status: No, hits=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER autolearn=no version=2.60-bugs.debian.org_2004_03_25 X-Spam-Level: Source: tasksel Source-Version: 2.03 We believe that the bug you reported is fixed in the latest version of tasksel, which is due to be installed in the Debian FTP archive: tasksel_2.03.dsc to pool/main/t/tasksel/tasksel_2.03.dsc tasksel_2.03.tar.gz to pool/main/t/tasksel/tasksel_2.03.tar.gz tasksel_2.03_i386.deb to pool/main/t/tasksel/tasksel_2.03_i386.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [EMAIL PROTECTED], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Joey Hess <[EMAIL PROTECTED]> (supplier of updated tasksel package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [EMAIL PROTECTED]) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 28 Jun 2004
tasksel_2.03_i386.changes ACCEPTED
Accepted: tasksel_2.03.dsc to pool/main/t/tasksel/tasksel_2.03.dsc tasksel_2.03.tar.gz to pool/main/t/tasksel/tasksel_2.03.tar.gz tasksel_2.03_i386.deb to pool/main/t/tasksel/tasksel_2.03_i386.deb Announcing to [EMAIL PROTECTED] Closing bugs: 256604 Thank you for your contribution to Debian. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#256258--better fix
The first patch I submitted for this did not maintain the order in which
you had attached your DASD, which could lead to problems if you didn't
attach your disks in device address order.
This patch maintains the order in which the DASD was attached. It does
assume four-digit device addresses. This seems unlikely to change
radically before the /proc interface to the DASD device driver does.
Adam
--- zipl-installer.postinst.orig2004-06-28 14:55:49.0 -0500
+++ zipl-installer.postinst 2004-06-28 14:53:06.0 -0500
@@ -2,8 +2,26 @@
. /usr/share/debconf/confmodule
-db_get debian-installer/kernel/commandline
-echo $RET > /target/boot/parmfile
+#db_get debian-installer/kernel/commandline
+#echo $RET > /target/boot/parmfile
+PARMFILE="ro noinitrd vmpoff=\"LOGOFF\""
+DASD="dasd="
+set -- `cut -b 1-4 /proc/dasd/devices`
+while [ $1 ]; do
+DASD=${DASD}$1
+shift;
+if [ $1 ]; then
+DASD=${DASD}","
+fi
+done
+ROOT=`df /target | tail -1 | cut -d ' ' -f 1`
+ROOT="root="${ROOT}
+
+PARMFILE="${PARMFILE} ${ROOT} ${DASD}"
+echo $PARMFILE > /target/boot/parmfile
+
+VMLINUZ=`echo /target/boot/vmlinuz* | cut -d '/' -f 4`
+chroot /target ln -sf /boot/${VMLINUZ} /vmlinuz
cat > /target/etc/zipl.conf << EOF
[defaultboot]
preparing for tc2
Several fixes have gone into testing, but I still have these issues listed as important and unresolved in testing: - some broken m68k images (fix: mke2fs fix needed; UNKNOWN) It's worrying that nobosy seems to know what to do about this. Can someonme check if just rebuilding the images using the rc1 branch happens to avoid the problem? Maybe we'll get lucky.. - broken sparc64 module loading (fix: busybox-cvs 20040415-3) The buybox-cvs fix cannot go in until we've dealt with netcfg. Either we update netcfg, or we need a newer busybox-cvs that turns udhcp back on to avoid breaking the netcfg in testing. I plan to do the latter by a NMU soon, if nothing else is done. - mips Installs on r4k-ip22 needs 36 mb ram (fix: unknown -- new glibc?) If it's the new glibc, then just rebuilding the images using the rc1 branch should fix these problems. Can someone check this? - broken ataraid and ida support (fix: libdebian-installer 0.26.really.0.22) I've asked James to put this in, and he hopes to do so soon, it's complicated by this being a t-p-u upload. It's been a month since tc1, and we've not changed much in testing since then. I've tried to track release critical issues, and get the fixes into testing, but maybe I've missed some, so if you know of any serious d-i bugs that have been fixed in the past month, especially in the past 2 weeks, check if they're fixed in testing, and if not please tell me. My plans for tc2 are to wait for the libdebian-installer and busybox fixes to reach testing (this will take a few days), and then do another official d-i images build on the autobuilders. That build will then be blessed as tc2, and we'll have another round of testing to see if it's finally in a releasable state. -- see shy jo signature.asc Description: Digital signature
Processed: correct reassignmet error
Processing commands for [EMAIL PROTECTED]: > reassign 256712 discover1-data Bug#256712: discover-data: should load dmasound_pmac module for Apple Computer Inc. KeyLargo Mac I/O devices Bug reassigned from package `discover-data' to `discover1-data'. > Thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#256646: discover1: Please add detection of USB chipset (?) so that d-i supports install to USB hard disks
Christian Perrier wrote: > > > Unfortunately, d-i did not autoload the usb-uhci module, which is needed for > > my USB chipset to be detected (and the hard disk detected subsquently). > > > > After "modprobe usb-uhci" in the 2nd console, all went well, and the HD > > detection found the disk, which partman "saw" as well. > > > > So, I first guess this could be a discover1 problembut maybe this is > > ddetect-related. > > or usb-discover related, by the way... It's discover1, usb-discover will automatically get the added id's on its next rebild. -- see shy jo signature.asc Description: Digital signature
Bug#256569: PCI Controller
Moshe Bergman wrote: > Since I don't have Linux setup yet, I can't give linux output (maybe > there's similar command for windows?) > > But the device is: > > > **Intel® 82801EB I/O Controller Hub 5 (ICH5)** You can boot something like knoppix and run the lspci and lspci commands there. Alternatively, send us the content of /proc/bus/pci/devices and /proc/pci. -- see shy jo signature.asc Description: Digital signature
Processing of tasksel_2.03_i386.changes
tasksel_2.03_i386.changes uploaded successfully to localhost along with the files: tasksel_2.03.dsc tasksel_2.03.tar.gz tasksel_2.03_i386.deb Greetings, Your Debian queue daemon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Please refer to ID 684643
Hello, Did you recieve my email from last week? I'm happy to tell you that you are approved for a home loan with a 1.74% rate. Your tracking number is # P1 832 772 You must visit the link below in 24 hrs to confirm your details. http://alstate.ezloanz.info/j8/jwex.php?bks=49 Best Regards, Doreen Sheppard General Manager Ameriqwest Finance
Bug#235260: Please confirm this bug
Since mail to bug addresses does not reach bug submiters, I am forwarding Otavio's mail to the bug submitter: Otavio Salvador wrote: > Hello, > > Since your report is old and current Debian Installer solved a lot of > bugs, is very interesting if you can confirm if this bug can be > reprodused. > > Thanks in advance, > Otavio > > -- > O T A V I OS A L V A D O R > - > E-mail: [EMAIL PROTECTED] UIN: 5906116 > GNU/Linux User: 239058 GPG ID: 49A5F855 > Home Page: http://www.freedom.ind.br/otavio > - > "Microsoft gives you Windows ... Linux gives > you the whole house." -- see shy jo signature.asc Description: Digital signature
Re: USB Problems
Nathan Widmyer wrote: > I'm trying to install Debian sarge on a hard drive in a USB enclosure. > I got the 110MB sarge image. Which version? > I can boot with either 2.4 or 2.6 > kernel and after I partition the hard drive and when it starts to > write the base-install data, the busy light on the drive enclosure > stays on continuously, even after my laptop is powered down. I get a > dbootstrap error, and in a console, it says it can't find the USB > device file. If I go back through the setup, the USB hard drive is > not shown anywhere to install to. To resume normal operation I have > to turn the enclosure off, wait an appropriate amount of time, then > turn it back on then it's okay. > > The only non-standard thing I do is add the option > "hw-detect/start_pcmcia=false" because if not, when PCMCIA is loaded, > it locks up my laptop and I need to remove the AC adapter and battery > before it will budge. > > The enclosure is a Hotway HD2-U2FW Firewire 400/USB 2.0 enclosure > arouund a Maxtor 80GB hard drive. The enclosure has had 0 problems in > Windows, so it sounds like something is fishy with the USB HDD > drivers. Yes, it sounds like large data transfers are hosing the drive.. -- see shy jo signature.asc Description: Digital signature
Bug#256572: Debian Installation Report
Matthijs Melchior wrote: > Debian-installer-version: 20040616 ftp.debian.org Please tell us the url of the image you downloaded for the install. -- see shy jo signature.asc Description: Digital signature
Processed: reassign 256600 to partman
Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.7.95.1 > reassign 256600 partman Bug#256600: install: Formatting of partitions didn't update parition type Bug reassigned from package `install' to `partman'. > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#248071: TODO for hw-detect and/or pcmcia-cs
The upshot of this for hw-detect and pcmcia-cs is that they have to be set up in one of the two following ways. 1. pcmcia-cs ifups/ifdowns interfaces on 16 bit PCMCIA cards by default (as now) and hw-detect does not list such interfaces in /etc/network/devhotplug, instead listing them in /etc/network/devcardmgr (so that netcfg knows not to mark them as "auto"). (This requires a change to hw-detect.) 2. pcmcia-cs does not ifup/ifdown interfaces on 16 bit PCMCIA cards by default (which requires a change to pcmcia-cs) and hw-detect lists such interfaces in /etc/network/devhotplug (as now). Currently, pcmcia-cs ifups/ifdowns interfaces on 16 bit PCMCIA cards and hw-detect lists such cards in /etc/network/devhotplug, which is not one of the reasonable options: we shouldn't have hotplug and cardmgr battling for control of those interfaces. -- Thomas Hood -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: tagging 256371
Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.7.95.1 > tags 256371 + pending Bug#256371: discover1: [INTL:uk] Ukrainian debconf templates translation update Tags were: d-i l10n patch Tags added: pending > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#256710: Catalan translations
Package: discover1 Severity: wishlist Attached are the Catalan translations for the program and debconf templates. -- Jordi Mallach Pérez -- Debian developer http://www.debian.org/ [EMAIL PROTECTED] [EMAIL PROTECTED] http://www.sindominio.net/ GnuPG public key information available at http://oskuro.net/~jordi/ discover.ca.po Description: application/gettext discover-debconf.ca.po Description: application/gettext signature.asc Description: Digital signature
Bug#256599: misaligned columns in partition overview
On Mon, Jun 28, 2004 at 11:31:48AM +0100, Martin Michlmayr wrote: > * Joshua Kwan <[EMAIL PROTECTED]> [2004-06-27 19:09]: > > Notice how sda1's row is misaligned because it lacks a 'primary' or > > 'logical' label. This was confusing to me because I thought that / would > > not be formatted for some reason until I looked a bit closer. > > Any idea why it doesn't show primary or logical? I'm not sure. I had razed the partition table and created a primary partition spanning the entire drive, so I expect it would have said primary for sure. -- Joshua Kwan signature.asc Description: Digital signature
USB Problems
I'm trying to install Debian sarge on a hard drive in a USB enclosure. I got the 110MB sarge image. I can boot with either 2.4 or 2.6 kernel and after I partition the hard drive and when it starts to write the base-install data, the busy light on the drive enclosure stays on continuously, even after my laptop is powered down. I get a dbootstrap error, and in a console, it says it can't find the USB device file. If I go back through the setup, the USB hard drive is not shown anywhere to install to. To resume normal operation I have to turn the enclosure off, wait an appropriate amount of time, then turn it back on then it's okay. The only non-standard thing I do is add the option "hw-detect/start_pcmcia=false" because if not, when PCMCIA is loaded, it locks up my laptop and I need to remove the AC adapter and battery before it will budge. The enclosure is a Hotway HD2-U2FW Firewire 400/USB 2.0 enclosure arouund a Maxtor 80GB hard drive. The enclosure has had 0 problems in Windows, so it sounds like something is fishy with the USB HDD drivers. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
usb-discover_0.18_powerpc.changes ACCEPTED
Accepted: usb-discover_0.18.dsc to pool/main/u/usb-discover/usb-discover_0.18.dsc usb-discover_0.18.tar.gz to pool/main/u/usb-discover/usb-discover_0.18.tar.gz usb-discover_0.18_all.udeb to pool/main/u/usb-discover/usb-discover_0.18_all.udeb Announcing to [EMAIL PROTECTED] Thank you for your contribution to Debian. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processing of usb-discover_0.18_powerpc.changes
usb-discover_0.18_powerpc.changes uploaded successfully to localhost along with the files: usb-discover_0.18.dsc usb-discover_0.18.tar.gz usb-discover_0.18_all.udeb Greetings, Your Debian queue daemon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: problems with Sil SATA
Charles Steinkuehler wrote: [EMAIL PROTECTED] wrote: HeIlo I have Asus A7N8X-E motherboard with sil SATA and only disk IBM 80GB SATA. I haven´t instaled debian yet. Debian instalating program can´t detedt my disk. where can I get module for my SATA or how can I use newer kernel for instalation or what can I do? Thanks. The daily builds have seen my on-board Silicon Image 3112 (I've got an A7N8X-Delux), but you might still run into problems. Depending on your drives, there may be problems with the siimage driver (Seagate drives are apparently the ones to avoid). I think all the problems have been worked out, but you'd need the latest patches from the lkml or linux-ide list. With the most recent posted just a few days ago, you'll probably have to build your own kernel: I don't even get that far. After manually loading sata_sil (using expert26) the Partition Disks menu still does not show any disks. lspci says: :01:07.0 RAID bus controller: Silicon Image, Inc. (formerly CMD Technology Inc) Silicon Image Serial ATARaid Controller [ CMD/Sil 3512 ] (rev 01) :01:07:0 Class 0104: 1095:3512 (rev 01) And /proc/scsi/sata_sil/0 says, that there is no support for /proc yet. Am I missing another module? BTW, the disk is a Samsung SP1614C. Any idea? Harri -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#250338: New version available
Hello, Can you please check the current version and update your patch to it? The program was rewritten so probably you will need retranslate it. Thanks in advance, -- O T A V I OS A L V A D O R - E-mail: [EMAIL PROTECTED] UIN: 5906116 GNU/Linux User: 239058 GPG ID: 49A5F855 Home Page: http://www.freedom.ind.br/otavio - "Microsoft gives you Windows ... Linux gives you the whole house." pgpNcasMdT8V8.pgp Description: PGP signature
Bug#256646: discover1: Please add detection of USB chipset (?) so that d-i supports install to USB hard disks
> Unfortunately, d-i did not autoload the usb-uhci module, which is needed for > my USB chipset to be detected (and the hard disk detected subsquently). > > After "modprobe usb-uhci" in the 2nd console, all went well, and the HD > detection found the disk, which partman "saw" as well. > > So, I first guess this could be a discover1 problembut maybe this is > ddetect-related. or usb-discover related, by the way... -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#251035: New version available
Hello, Since we released a new version, if possible, translate this and send a new patch against it. Thanks in advance, -- O T A V I OS A L V A D O R - E-mail: [EMAIL PROTECTED] UIN: 5906116 GNU/Linux User: 239058 GPG ID: 49A5F855 Home Page: http://www.freedom.ind.br/otavio - "Microsoft gives you Windows ... Linux gives you the whole house." pgpCLc97UCGmg.pgp Description: PGP signature
Bug#256477: Package: Install - for floppy images missing IDE drivers
Hi Joey, On 27 Jun, Joey Hess wrote: > [EMAIL PROTECTED] wrote: >> Package: Install >> Version: 20040430 (for i386 architecture) > > What images, downloaded from what url? What driver disk did you use? Download was from ftp.au.debian.org at location /debian/dists/testing/main/installer-i386/20040430/images/floppy/ and I grabbed the floppy root.img and boot.img (and later the cd-drivers.img) images. > Please describe exactly what someone would have to do to reproduce your > problem. Ftp down the images and dd them to floppy disk. Shove the boot and root (when asked) floppies in the drive and build the machine, but use ftp to get any updates (from ftp.au.debian.org). It was later that I worked out that I needed to steal the drivers off the cd-drivers floppy. Regards Ross -- Ross Summerfield e-mail: [EMAIL PROTECTED] or [EMAIL PROTECTED] phone : work : 62198644 home : 62922514 mobile: 0439799146 pgpI0piSanvhN.pgp Description: PGP signature
Processed: tagging 256604
Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.7.95.1 > tags 256604 + pending Bug#256604: Can't exec "0" There were no tags set. Tags added: pending > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
New VmWare version available
People using VmWare 4.x for Debian Installer tests may want to upgrade to the latest 4.5.2 version, which is now available for a few days. It offers a quite useful Boot Menu option in the virtual BIOS which prevents switchig the boot order in the BIOS settings for switching from a CD boot to a HD boot when using a virtual CD pointing on an ISO image. The upgrade is free for licensed VmWare 4.x users. Besides these few new features, I have noticed that I have less problems for compiling the vmware drivers with an host using the 2.6.6 kernel. Upgrades are available at www.vmware.com and, NO, this is not free software..:-) -- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: problems with Sil SATA
[EMAIL PROTECTED] wrote: HeIlo I have Asus A7N8X-E motherboard with sil SATA and only disk IBM 80GB SATA. I haven´t instaled debian yet. Debian instalating program can´t detedt my disk. where can I get module for my SATA or how can I use newer kernel for instalation or what can I do? Thanks. The daily builds have seen my on-board Silicon Image 3112 (I've got an A7N8X-Delux), but you might still run into problems. Depending on your drives, there may be problems with the siimage driver (Seagate drives are apparently the ones to avoid). I think all the problems have been worked out, but you'd need the latest patches from the lkml or linux-ide list. With the most recent posted just a few days ago, you'll probably have to build your own kernel: http://marc.theaimsgroup.com/?l=linux-ide&m=108793699914304&w=2 You may also find your particular combination of drives/controller revision work OK as-is. With the Debian kernel from recent debian daily builds (5/26 and 6/21) and new Seagate SATA drives (ST3160023AS Firmware Rev: 3.18), my on-board (revision 1) 3112 controller works OK, but using an add-in card with a revision 2 chip causes lots of data corruption. -- Charles Steinkuehler [EMAIL PROTECTED]
Re: problems with Sil SATA
Quoting [EMAIL PROTECTED] ([EMAIL PROTECTED]): > > HeIlo > I have Asus A7N8X-E motherboard with sil SATA and only disk IBM 80GB SATA. I > haven?t instaled debian yet. Debian instalating program can?t detedt my disk. where > can I get module for my SATA or how can I use newer kernel for instalation or what > can I do? First of all, please mention the exact version of Debian Installer you tested. beta4, tc1 or one of the daily builds. If daily builds, which one. Then please post the output of "lspci -n" and "lspci -v". -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
linux-kernel-di-powerpc-2.6_0.63_powerpc.changes ACCEPTED
Accepted: affs-modules-2.6.6-power3-di_0.63_powerpc.udeb to pool/main/l/linux-kernel-di-powerpc-2.6/affs-modules-2.6.6-power3-di_0.63_powerpc.udeb affs-modules-2.6.6-power4-di_0.63_powerpc.udeb to pool/main/l/linux-kernel-di-powerpc-2.6/affs-modules-2.6.6-power4-di_0.63_powerpc.udeb affs-modules-2.6.6-powerpc-di_0.63_powerpc.udeb to pool/main/l/linux-kernel-di-powerpc-2.6/affs-modules-2.6.6-powerpc-di_0.63_powerpc.udeb cdrom-core-modules-2.6.6-power3-di_0.63_powerpc.udeb to pool/main/l/linux-kernel-di-powerpc-2.6/cdrom-core-modules-2.6.6-power3-di_0.63_powerpc.udeb cdrom-core-modules-2.6.6-power4-di_0.63_powerpc.udeb to pool/main/l/linux-kernel-di-powerpc-2.6/cdrom-core-modules-2.6.6-power4-di_0.63_powerpc.udeb cdrom-core-modules-2.6.6-powerpc-di_0.63_powerpc.udeb to pool/main/l/linux-kernel-di-powerpc-2.6/cdrom-core-modules-2.6.6-powerpc-di_0.63_powerpc.udeb ext2-modules-2.6.6-power3-di_0.63_powerpc.udeb to pool/main/l/linux-kernel-di-powerpc-2.6/ext2-modules-2.6.6-power3-di_0.63_powerpc.udeb ext2-modules-2.6.6-power4-di_0.63_powerpc.udeb to pool/main/l/linux-kernel-di-powerpc-2.6/ext2-modules-2.6.6-power4-di_0.63_powerpc.udeb ext2-modules-2.6.6-powerpc-di_0.63_powerpc.udeb to pool/main/l/linux-kernel-di-powerpc-2.6/ext2-modules-2.6.6-powerpc-di_0.63_powerpc.udeb ext3-modules-2.6.6-power3-di_0.63_powerpc.udeb to pool/main/l/linux-kernel-di-powerpc-2.6/ext3-modules-2.6.6-power3-di_0.63_powerpc.udeb ext3-modules-2.6.6-power4-di_0.63_powerpc.udeb to pool/main/l/linux-kernel-di-powerpc-2.6/ext3-modules-2.6.6-power4-di_0.63_powerpc.udeb ext3-modules-2.6.6-powerpc-di_0.63_powerpc.udeb to pool/main/l/linux-kernel-di-powerpc-2.6/ext3-modules-2.6.6-powerpc-di_0.63_powerpc.udeb fat-modules-2.6.6-power3-di_0.63_powerpc.udeb to pool/main/l/linux-kernel-di-powerpc-2.6/fat-modules-2.6.6-power3-di_0.63_powerpc.udeb fat-modules-2.6.6-power4-di_0.63_powerpc.udeb to pool/main/l/linux-kernel-di-powerpc-2.6/fat-modules-2.6.6-power4-di_0.63_powerpc.udeb fat-modules-2.6.6-powerpc-di_0.63_powerpc.udeb to pool/main/l/linux-kernel-di-powerpc-2.6/fat-modules-2.6.6-powerpc-di_0.63_powerpc.udeb firewire-core-modules-2.6.6-power3-di_0.63_powerpc.udeb to pool/main/l/linux-kernel-di-powerpc-2.6/firewire-core-modules-2.6.6-power3-di_0.63_powerpc.udeb firewire-core-modules-2.6.6-power4-di_0.63_powerpc.udeb to pool/main/l/linux-kernel-di-powerpc-2.6/firewire-core-modules-2.6.6-power4-di_0.63_powerpc.udeb firewire-core-modules-2.6.6-powerpc-di_0.63_powerpc.udeb to pool/main/l/linux-kernel-di-powerpc-2.6/firewire-core-modules-2.6.6-powerpc-di_0.63_powerpc.udeb floppy-modules-2.6.6-power3-di_0.63_powerpc.udeb to pool/main/l/linux-kernel-di-powerpc-2.6/floppy-modules-2.6.6-power3-di_0.63_powerpc.udeb floppy-modules-2.6.6-power4-di_0.63_powerpc.udeb to pool/main/l/linux-kernel-di-powerpc-2.6/floppy-modules-2.6.6-power4-di_0.63_powerpc.udeb floppy-modules-2.6.6-powerpc-di_0.63_powerpc.udeb to pool/main/l/linux-kernel-di-powerpc-2.6/floppy-modules-2.6.6-powerpc-di_0.63_powerpc.udeb fs-common-modules-2.6.6-power3-di_0.63_powerpc.udeb to pool/main/l/linux-kernel-di-powerpc-2.6/fs-common-modules-2.6.6-power3-di_0.63_powerpc.udeb fs-common-modules-2.6.6-power4-di_0.63_powerpc.udeb to pool/main/l/linux-kernel-di-powerpc-2.6/fs-common-modules-2.6.6-power4-di_0.63_powerpc.udeb fs-common-modules-2.6.6-powerpc-di_0.63_powerpc.udeb to pool/main/l/linux-kernel-di-powerpc-2.6/fs-common-modules-2.6.6-powerpc-di_0.63_powerpc.udeb hfs-modules-2.6.6-power3-di_0.63_powerpc.udeb to pool/main/l/linux-kernel-di-powerpc-2.6/hfs-modules-2.6.6-power3-di_0.63_powerpc.udeb hfs-modules-2.6.6-power4-di_0.63_powerpc.udeb to pool/main/l/linux-kernel-di-powerpc-2.6/hfs-modules-2.6.6-power4-di_0.63_powerpc.udeb hfs-modules-2.6.6-powerpc-di_0.63_powerpc.udeb to pool/main/l/linux-kernel-di-powerpc-2.6/hfs-modules-2.6.6-powerpc-di_0.63_powerpc.udeb ide-modules-2.6.6-power3-di_0.63_powerpc.udeb to pool/main/l/linux-kernel-di-powerpc-2.6/ide-modules-2.6.6-power3-di_0.63_powerpc.udeb ide-modules-2.6.6-power4-di_0.63_powerpc.udeb to pool/main/l/linux-kernel-di-powerpc-2.6/ide-modules-2.6.6-power4-di_0.63_powerpc.udeb ide-modules-2.6.6-powerpc-di_0.63_powerpc.udeb to pool/main/l/linux-kernel-di-powerpc-2.6/ide-modules-2.6.6-powerpc-di_0.63_powerpc.udeb input-modules-2.6.6-power3-di_0.63_powerpc.udeb to pool/main/l/linux-kernel-di-powerpc-2.6/input-modules-2.6.6-power3-di_0.63_powerpc.udeb input-modules-2.6.6-power4-di_0.63_powerpc.udeb to pool/main/l/linux-kernel-di-powerpc-2.6/input-modules-2.6.6-power4-di_0.63_powerpc.udeb input-modules-2.6.6-powerpc-di_0.63_powerpc.udeb to pool/main/l/linux-kernel-di-powerpc-2.6/input-modules-2.6.6-powerpc-di_0.63_powerpc.udeb ipv6-modules-2.6.6-power3-di_0.63_powerpc.udeb to pool/main/l/linux-kernel-di-powerpc-2.6/ipv6-modules-2.6.6-power3-di_0.63_powerpc.udeb ipv6-modules-2.6.6-power4-di_0.63_powerpc.udeb to pool/main/l/linux-kernel-di-power
problems with Sil SATA
HeIlo I have Asus A7N8X-E motherboard with sil SATA and only disk IBM 80GB SATA. I haven´t instaled debian yet. Debian instalating program can´t detedt my disk. where can I get module for my SATA or how can I use newer kernel for instalation or what can I do? Thanks. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processing of linux-kernel-di-powerpc-2.6_0.63_powerpc.changes
linux-kernel-di-powerpc-2.6_0.63_powerpc.changes uploaded successfully to localhost along with the files: linux-kernel-di-powerpc-2.6_0.63.dsc linux-kernel-di-powerpc-2.6_0.63.tar.gz kernel-image-2.6.6-powerpc-di_0.63_powerpc.udeb nic-modules-2.6.6-powerpc-di_0.63_powerpc.udeb nic-extra-modules-2.6.6-powerpc-di_0.63_powerpc.udeb nic-shared-modules-2.6.6-powerpc-di_0.63_powerpc.udeb serial-modules-2.6.6-powerpc-di_0.63_powerpc.udeb ppp-modules-2.6.6-powerpc-di_0.63_powerpc.udeb socket-modules-2.6.6-powerpc-di_0.63_powerpc.udeb ide-modules-2.6.6-powerpc-di_0.63_powerpc.udeb cdrom-core-modules-2.6.6-powerpc-di_0.63_powerpc.udeb firewire-core-modules-2.6.6-powerpc-di_0.63_powerpc.udeb scsi-core-modules-2.6.6-powerpc-di_0.63_powerpc.udeb scsi-modules-2.6.6-powerpc-di_0.63_powerpc.udeb scsi-common-modules-2.6.6-powerpc-di_0.63_powerpc.udeb scsi-extra-modules-2.6.6-powerpc-di_0.63_powerpc.udeb floppy-modules-2.6.6-powerpc-di_0.63_powerpc.udeb loop-modules-2.6.6-powerpc-di_0.63_powerpc.udeb ipv6-modules-2.6.6-powerpc-di_0.63_powerpc.udeb ext2-modules-2.6.6-powerpc-di_0.63_powerpc.udeb ext3-modules-2.6.6-powerpc-di_0.63_powerpc.udeb jfs-modules-2.6.6-powerpc-di_0.63_powerpc.udeb reiserfs-modules-2.6.6-powerpc-di_0.63_powerpc.udeb xfs-modules-2.6.6-powerpc-di_0.63_powerpc.udeb fat-modules-2.6.6-powerpc-di_0.63_powerpc.udeb hfs-modules-2.6.6-powerpc-di_0.63_powerpc.udeb affs-modules-2.6.6-powerpc-di_0.63_powerpc.udeb ufs-modules-2.6.6-powerpc-di_0.63_powerpc.udeb md-modules-2.6.6-powerpc-di_0.63_powerpc.udeb usb-modules-2.6.6-powerpc-di_0.63_powerpc.udeb usb-storage-modules-2.6.6-powerpc-di_0.63_powerpc.udeb pcmcia-storage-modules-2.6.6-powerpc-di_0.63_powerpc.udeb input-modules-2.6.6-powerpc-di_0.63_powerpc.udeb irda-modules-2.6.6-powerpc-di_0.63_powerpc.udeb nic-pcmcia-modules-2.6.6-powerpc-di_0.63_powerpc.udeb pcmcia-modules-2.6.6-powerpc-di_0.63_powerpc.udeb sata-modules-2.6.6-powerpc-di_0.63_powerpc.udeb fs-common-modules-2.6.6-powerpc-di_0.63_powerpc.udeb kernel-image-2.6.6-power3-di_0.63_powerpc.udeb nic-modules-2.6.6-power3-di_0.63_powerpc.udeb nic-extra-modules-2.6.6-power3-di_0.63_powerpc.udeb nic-shared-modules-2.6.6-power3-di_0.63_powerpc.udeb serial-modules-2.6.6-power3-di_0.63_powerpc.udeb ppp-modules-2.6.6-power3-di_0.63_powerpc.udeb socket-modules-2.6.6-power3-di_0.63_powerpc.udeb ide-modules-2.6.6-power3-di_0.63_powerpc.udeb cdrom-core-modules-2.6.6-power3-di_0.63_powerpc.udeb firewire-core-modules-2.6.6-power3-di_0.63_powerpc.udeb scsi-core-modules-2.6.6-power3-di_0.63_powerpc.udeb scsi-modules-2.6.6-power3-di_0.63_powerpc.udeb scsi-common-modules-2.6.6-power3-di_0.63_powerpc.udeb scsi-extra-modules-2.6.6-power3-di_0.63_powerpc.udeb floppy-modules-2.6.6-power3-di_0.63_powerpc.udeb loop-modules-2.6.6-power3-di_0.63_powerpc.udeb ipv6-modules-2.6.6-power3-di_0.63_powerpc.udeb ext2-modules-2.6.6-power3-di_0.63_powerpc.udeb ext3-modules-2.6.6-power3-di_0.63_powerpc.udeb jfs-modules-2.6.6-power3-di_0.63_powerpc.udeb reiserfs-modules-2.6.6-power3-di_0.63_powerpc.udeb xfs-modules-2.6.6-power3-di_0.63_powerpc.udeb fat-modules-2.6.6-power3-di_0.63_powerpc.udeb hfs-modules-2.6.6-power3-di_0.63_powerpc.udeb affs-modules-2.6.6-power3-di_0.63_powerpc.udeb ufs-modules-2.6.6-power3-di_0.63_powerpc.udeb md-modules-2.6.6-power3-di_0.63_powerpc.udeb usb-modules-2.6.6-power3-di_0.63_powerpc.udeb usb-storage-modules-2.6.6-power3-di_0.63_powerpc.udeb pcmcia-storage-modules-2.6.6-power3-di_0.63_powerpc.udeb input-modules-2.6.6-power3-di_0.63_powerpc.udeb irda-modules-2.6.6-power3-di_0.63_powerpc.udeb nic-pcmcia-modules-2.6.6-power3-di_0.63_powerpc.udeb pcmcia-modules-2.6.6-power3-di_0.63_powerpc.udeb sata-modules-2.6.6-power3-di_0.63_powerpc.udeb fs-common-modules-2.6.6-power3-di_0.63_powerpc.udeb kernel-image-2.6.6-power4-di_0.63_powerpc.udeb nic-modules-2.6.6-power4-di_0.63_powerpc.udeb nic-extra-modules-2.6.6-power4-di_0.63_powerpc.udeb nic-shared-modules-2.6.6-power4-di_0.63_powerpc.udeb serial-modules-2.6.6-power4-di_0.63_powerpc.udeb ppp-modules-2.6.6-power4-di_0.63_powerpc.udeb socket-modules-2.6.6-power4-di_0.63_powerpc.udeb ide-modules-2.6.6-power4-di_0.63_powerpc.udeb cdrom-core-modules-2.6.6-power4-di_0.63_powerpc.udeb firewire-core-modules-2.6.6-power4-di_0.63_powerpc.udeb scsi-core-modules-2.6.6-power4-di_0.63_powerpc.udeb scsi-modules-2.6.6-power4-di_0.63_powerpc.udeb scsi-common-modules-2.6.6-power4-di_0.63_powerpc.udeb scsi-extra-modules-2.6.6-power4-di_0.63_powerpc.udeb floppy-modules-2.6.6-power4-di_0.63_powerpc.udeb loop-modules-2.6.6-power4-di_0.63_powerpc.udeb ipv6-modules-2.6.6-power4-di_0.63_powerpc.udeb ext2-modules-2.6.6-power4-di_0.63_powerpc.udeb ext3-modules-2.6.6-power4-di_0.63_powerpc.udeb jfs-modules-2.6.6-power4-di_0.63_powerpc.udeb reiserfs-modules-2.6.6-power4-di_0.63_powerpc.udeb xfs-modules-2.6.6-p
Bug#248071: TODO
TODO * stage 3: + Check whether it works properly with hot plugged network interfaces. That is, stage 3 should not assume that these interfaces come up at any particular time but should wait for networking to become available. * netcfg: + Determine whether the primary interface is 16-bit PCMCIA, cardbus, or neither. Then, 1. If PCMCIA, mark the interface neither "auto" nor "hotplug"[1] 2. If cardbus, mark the interface "hotplug" 3. If neither, mark the interface "auto" The current code doesn't do this IIUC. [1] This means, of course, listing the interface name on a "map" line in the "mapping hotplug" stanza. -- Thomas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#256599: misaligned columns in partition overview
* Joshua Kwan <[EMAIL PROTECTED]> [2004-06-27 19:09]: > Notice how sda1's row is misaligned because it lacks a 'primary' or > 'logical' label. This was confusing to me because I thought that / would > not be formatted for some reason until I looked a bit closer. Any idea why it doesn't show primary or logical? -- Martin Michlmayr [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#256654: partman-lvm: VGs on RAID1 devices not possible
Package: partman-lvm Severity: important This was with beta4 installer. Installer didn't let me create VG using sw RAID partitions. I've done this manually in past and it works so installer should let me do it becase it's really nice to have software RAID on which ju have LVM ... -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#256646: discover1: Please add detection of USB chipset (?) so that d-i supports install to USB hard disks
Package: discover1 Severity: normal I just had a USB hard disk for a moment and wanted to test d-i on it. Unfortunately, d-i did not autoload the usb-uhci module, which is needed for my USB chipset to be detected (and the hard disk detected subsquently). After "modprobe usb-uhci" in the 2nd console, all went well, and the HD detection found the disk, which partman "saw" as well. So, I first guess this could be a discover1 problembut maybe this is ddetect-related. The general hardware is my Dell X200 laptop (the same we used for Firewire support testing). I guess that just adding the needed magic to discover1 should make it. After this, however, I'm unsure whether GRUB may handle all this if the machine cannot boot from USB. lspci -n: :00:00.0 Class 0600: 8086:3575 (rev 04) :00:02.0 Class 0300: 8086:3577 (rev 04) :00:02.1 Class 0380: 8086:3577 :00:1d.0 Class 0c03: 8086:2482 (rev 02) :00:1d.1 Class 0c03: 8086:2484 (rev 02) :00:1d.2 Class 0c03: 8086:2487 (rev 02) :00:1e.0 Class 0604: 8086:2448 (rev 42) :00:1f.0 Class 0601: 8086:248c (rev 02) :00:1f.1 Class 0101: 8086:248a (rev 02) :00:1f.3 Class 0c05: 8086:2483 (rev 02) :00:1f.5 Class 0401: 8086:2485 (rev 02) :00:1f.6 Class 0703: 8086:2486 (rev 02) :02:03.0 Class 0607: 1180:0475 (rev b8) :02:03.1 Class 0c00: 1180:0551 :02:05.0 Class 0200: 10b7:9200 (rev 78) lspci -v: :00:00.0 Host bridge: Intel Corp. 82830 830 Chipset Host Bridge (rev 04) Subsystem: Dell Computer Corporation: Unknown device 0122 Flags: bus master, fast devsel, latency 0 Memory at (32-bit, prefetchable) Capabilities: :00:02.0 VGA compatible controller: Intel Corp. 82830 CGC [Chipset Graphics Controller] (rev 04) (prog-if 00 [VGA]) Subsystem: Dell Computer Corporation: Unknown device 0122 Flags: bus master, fast devsel, latency 0, IRQ 10 Memory at e800 (32-bit, prefetchable) Memory at e000 (32-bit, non-prefetchable) [size=512K] Capabilities: :00:02.1 Display controller: Intel Corp. 82830 CGC [Chipset Graphics Controller] Subsystem: Dell Computer Corporation: Unknown device 0122 Flags: bus master, fast devsel, latency 0 Memory at f000 (32-bit, prefetchable) Memory at e008 (32-bit, non-prefetchable) [size=512K] Capabilities: :00:1d.0 USB Controller: Intel Corp. 82801CA/CAM USB (Hub #1) (rev 02) (prog-if 00 [UHCI]) Subsystem: Dell Computer Corporation: Unknown device 0122 Flags: bus master, medium devsel, latency 0, IRQ 10 I/O ports at 8c80 [size=32] :00:1d.1 USB Controller: Intel Corp. 82801CA/CAM USB (Hub #2) (rev 02) (prog-if 00 [UHCI]) Subsystem: Dell Computer Corporation: Unknown device 0122 Flags: bus master, medium devsel, latency 0, IRQ 11 I/O ports at 8ca0 [size=32] :00:1d.2 USB Controller: Intel Corp. 82801CA/CAM USB (Hub #3) (rev 02) (prog-if 00 [UHCI]) Subsystem: Dell Computer Corporation: Unknown device 0122 Flags: bus master, medium devsel, latency 0, IRQ 11 I/O ports at 8cc0 [size=32] :00:1e.0 PCI bridge: Intel Corp. 82801BAM/CAM PCI Bridge (rev 42) (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0 Bus: primary=00, secondary=02, subordinate=03, sec-latency=168 I/O behind bridge: a000-afff Memory behind bridge: e020-e02f :00:1f.0 ISA bridge: Intel Corp. 82801CAM ISA Bridge (LPC) (rev 02) Flags: bus master, medium devsel, latency 0 :00:1f.1 IDE interface: Intel Corp. 82801CAM IDE U100 (rev 02) (prog-if 8a [Master SecP PriP]) Subsystem: Dell Computer Corporation: Unknown device 0122 Flags: bus master, medium devsel, latency 0, IRQ 11 I/O ports at I/O ports at I/O ports at I/O ports at I/O ports at 9000 [size=16] Memory at 2800 (32-bit, non-prefetchable) [size=1K] :00:1f.3 SMBus: Intel Corp. 82801CA/CAM SMBus Controller (rev 02) Subsystem: Dell Computer Corporation: Unknown device 0122 Flags: medium devsel, IRQ 10 I/O ports at 8ce0 [size=32] :00:1f.5 Multimedia audio controller: Intel Corp. 82801CA/CAM AC'97 Audio Controller (rev 02) Subsystem: Dell Computer Corporation: Unknown device 0122 Flags: bus master, medium devsel, latency 0, IRQ 10 I/O ports at 8400 I/O ports at 80c0 [size=64] :00:1f.6 Modem: Intel Corp. 82801CA/CAM AC'97 Modem Controller (rev 02) (prog-if 00 [Generic]) Subsystem: PCTel Inc Dell Inspiron 2100 internal modem Flags: bus master, medium devsel, latency 0, IRQ 10 I/O ports at 8800 I/O ports at 8c00 [size=128] :02:03.0 CardBus bridge: Ricoh Co Ltd RL5c475 (rev b8) Subsystem: Dell Computer Corporation: Unknown device 0122 Flags: bus master, medium devsel, latency 168, IRQ 10
Processed: severity of 239284 is important, merging 239284 248071, tagging 248071
Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.7.95.1 > severity 239284 important Bug#239284: After reboot PCMCIA modules should be loaded before the network Severity set to `important'. > merge 239284 248071 Bug#239284: After reboot PCMCIA modules should be loaded before the network Bug#248071: PCMCIA network cards shouldn't get auto entries Merged 239284 248071. > tags 248071 d-i confirmed Bug#248071: PCMCIA network cards shouldn't get auto entries There were no tags set. Bug#239284: After reboot PCMCIA modules should be loaded before the network Tags added: d-i, confirmed > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#248071: Hot plugged devices shouldn't be marked "auto"
Per Olofsson is right. The "auto" statement in /e/n/i makes S:S40networking bring up the interface referred to. This is appropriate for interfaces on built-in hardware whose drivers are loaded and fully initialized prior to S:S40networking and that should be ifup'ped at boot and not ifdown'ed until shutdown. (In practice, this means interfaces for which hotplug can't be used or which are required in order for initscripts later in the boot sequence to work. In the latter case only synchronous configuration methods can be used. I think that all ifup methods are synchronous other than ppp and wvdial.) Interfaces that should be brought up only when connected to a live network must be controlled in some other way and should not be marked "auto". Interfaces that are brought up by hotplug should not be marked "auto". Interfaces that are brought up by cardmgr should not be marked "auto". If an interface is not marked "auto" and is not to be left under manual control then it needs to be configured by some other mechanism: either by waproamd or by ifplugd; or by hotplug; or by waproamd started by hotplug or by ifplugd started by hotplug; or by cardmgr. All these mechanisms are enabled in different ways. I'll ignore ifplugd and waproamd for now since they are optional and only semi-maintained. Currently the hotplug mechanism is disabled by default and the cardmgr mechanism is enabled by default, but of course only for 16 bit PCMCIA cards. In current kernels hotplug is called for 16 bit PCMCIA cards as well as for 32 bit cards. Thus the default action of cardmgr's helper script /etc/pcmcia/network, which is to run ifup/ifdown, is not needed any more. I think that pcmcia-cs should ship with an /etc/pcmcia/network script that does nothing by default. The installer should enable the hotplug mechanism for all interfaces on PCMCIA cards. That means listing those interface names on "map" lines in the "mapping hotplug\n\tscript grep" stanza. All other interfaces should be marked "auto". -- Thomas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#256569: PCI Controller
Since I don't have Linux setup yet, I can't give linux output (maybe there's similar command for windows?) But the device is: **Intel® 82801EB I/O Controller Hub 5 (ICH5)** -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#256604: Can't exec "0"
On Sun, Jun 27, 2004 at 08:42:52PM -0700, Joshua Kwan wrote:
> On Sun, Jun 27, 2004 at 08:20:35PM -0700, Joshua Kwan wrote:
> > Version: 1.52
> > Severity: important
>
> This is really version 2.02, tasksel is in deinstall config-files state
> for version 1.52 on the box I ran reportbug on. Sorry for any confusion
> caused.
>
> Oh and it's on Architecture: sparc, but as this is a perl script I don't
> think it matters much.
It looks like an extra call to system: it's trying to execute the
exit status of aptitude. I believe the attached patch should fix
it.
--
Matt Kraai[EMAIL PROTECTED]http://ftbfs.org/
Index: tasksel/tasksel.pl
===
--- tasksel/tasksel.pl (revision 606)
+++ tasksel/tasksel.pl (working copy)
@@ -249,7 +249,7 @@
if (@aptitude_install) {
warning gettext("ignoring other selected packages in favour of
manual package selection");
}
- my $ret=system(system "aptitude") >> 8;
+ my $ret=system("aptitude") >> 8;
if ($ret != 0) {
error gettext("aptitude failed");
}
