Hi, Nick. In this archive you can find all those things, you asked me.
See you. Steve MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="=_NextPart_000_0011_8875F89F.927DBC8D" X-Priority: 3 X-MSMail-Priority: Normal This is a multi-part message in MIME format. --=_NextPart_000_0011_8875F89F.927DBC8D Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: 7bit RE: --=_NextPart_000_0011_8875F89F.927DBC8D Content-Type: text/plain; charset="us-ascii"; format=flowed ** ** WARNING: WinProxy has detected a virus in file attached to this e-mail message! The attachment has been automatically removed to protect your network. WinProxy Administrator: [EMAIL PROTECTED] 08/05/04 13:17:37 WinProxy (Version 5.0 R1a (5.0.0.7)) - http://www.Ositis.com/ Antivirus Vendor: Panda Software Scan Engine Version: 2.10.1.6_3.1.5.211 Pattern File Version: 3.81437 (Timestamp: 2004/08/04 13:02:00) Machine name: SERVER Machine IP address: 202.59.90.202 Client: Pc6 Protocol: SMTP Virus: "W32/Plexus.A.worm" found! Attachment: release.exe ** ** --=_NextPart_000_0011_8875F89F.927DBC8D-- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: release status
On Thu, Aug 05, 2004 at 12:07:21AM +0200, Christian Leimer wrote: > >> Since the most oldworld use scsi to boot it is very important that this > >> works. > >> > >> Maybe 2.4 should be the standard for oldworld macs since I have a lot of > >> problems getting a 2.6 kernel to work with quik. > > > > 2.4 is the default for the miboot oldworld floppies, which are the default > > oldworld install. The bootx one depending on a non-free OS cannot be > > recomended by debian. > > > > I today tested the boot-floppies but miboot is gone there is only a hfs disk > with vmlinux file. I booted via openfirmware and got: unrecognized Client > Programm formatstate not valid. So it is not possible for me to boot the > installer from floppy. Well, i have no idea what you are trying to do, but my guess is that you are not looking in the right place. The miboot 2.4 floppies are at : http://people.debian.org/~luther/d-i/images/daily/powerpc-small/floppy/ > The only thing that works well is di(2.4 kernel) with BootX here on my Umax > S900. Ok. Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: r18868 - in trunk/packages/ddetect: . debian
On Wed, Aug 04, 2004 at 10:51:55PM +0100, Colin Watson wrote: > On Wed, Aug 04, 2004 at 10:10:21PM +0200, Sven Luther wrote: > > On Wed, Aug 04, 2004 at 03:08:54PM -0400, Joey Hess wrote: > > > Why should d-i care about the mouse? Shouldn't you be patching X's > > > configuration program? > > > > Well, this is the modules which will be added to the /etc/modules. I > > understand that it may well be possible that the X installation stuff, > > but i suppose the mouse should be usefull even for gpm or other non-X > > stuff, and having no mouse driver module loaded after the reboot is > > not a nice thing. > > > > Notice that i asked about this (altough addressed to Kamion) on irc > > before making the change while you where there, so you could have > > remarqued on it before i go forward and implemented this. > > If you want to discuss a design decision, this mailing list would be far > better than the transient and overfilled medium of IRC. Ok. Checking in code is obviously also a good way to get it discussed :). > > So, if this is not the right place for registering this module for > > future use, what is ? discover, which has trouble handling more than > > one module per pci id ? hotplug ? The X configuration stuff ? i have > > some doubt about Branden accepting this kind of stuff though, unless > > there is a generic module loading mechanism for X, and this doesn't > > solve the case of non-X mouse users. > > mdetect seems like clearly the right place. Its package description and > its man page both suggest that gpm could easily be modified to use it > (indeed, mdetect's default behaviour is to produce output suitable for > configuring gpm). And is it part of base, and sure to be run if the user does a clean install and chose the X task in tasksel ? Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#241179: successful install, no network in 2nd stage (pcmcia)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thursday 05 August 2004 05:42, Akkana Peck wrote: > Frederik Dannemare writes: > > No, the package is not needed for wired cards, but I assumed that > > you wanted to use your wireless card as your primary NIC during the > > installation, since the installer only handles the setup of one > > NIC. > > > > And since your very first mail was about wireless pcmcia not > > working (no mention of a second (3com) card), I have focused only > > on getting your > > I'm not sure why you say that. I looked back over the bug and I > don't see anywhere I mention wireless, and I've never been using > wireless, always this 3com ethernet (wired) card. It's not the > second card, it's the only card (I do own a wireless card, but > have never been using it during this install scenario). Argh. Sorry, I was mixing up your report with another one that looks like like it (I have been processing so many reports lately) but that other one is wireless. > If I said something somewhere to imply otherwise, it was an error > (where was that?) My fault. > > Hence, my howto/work-around was targeted for situations where the > > user has a CD-ROM and (wireless) NIC only accessible via a single > > pcmcia slot in the computer. > > I think I followed it except for the wireless-tools part. okay > > I don't get that. I'm really no expoert in d-i internals, and > > 2.4.18-bf2.4 sounds to me like a kernel from good old woody. Still, > > Yes, you're right. Ignore the 2.4.18 stuff, that was booting off > the wrong kernel. (This testing is complicated by the fact that > the installer doesn't seem willing to re-use my existing /boot, > so I have to go through three screens until grub fails, then boot > into the working system and copy files by hand into /boot, then > reboot into the stage 2 installer. I was using the wrong kernel > that time. Please ignore anything I said about modprobe errors.) will do > With the correct kernel, 2.4.26-1-386, it does start pcmcia (and > probably hotplug, though I missed seeing the messages for that) > and I do see an eth0 device with ifconfig -a, but it has no IP > address. (I set a static IP address, netmask, gateway, and > nameservers during stage 1 after I disconnected the cdrom and > connected the ethernet card.) > > However, if I ctrl-alt-f2 to get a shell while the stage 2 installer > is still running, log in as root, and run ifup eth0, then it sees > the network and I can proceed with installation. > > Why doesn't it run ifup when the stage 2 installer boots? > Might there be a sequence problem, with the network being > initialized before pcmcia/cardbus? (I'm booting with the card > still inserted from the stage1 network config step, not trying > to hotplug it after booting.) > > > let's focus on my initial attempt which is to get wireless working > > (disregaring the fact that you have a wired card also) disregard this :) I'm so sorry to have tried to mislead you. > Wireless ads two extra device swaps, and I'd have to specify an > essid at some point during the process (does the sarge installer > handle that, yes, the installer can handle stup of essid (and wep, btw). > or would I have to ctl-alt-F2 and run iwconfig by > hand?), so I'm hoping it's okay if I keep testing with the wired > card. no problem. you do that. > One other difference is that my wireless card is pcmcia while my > ethernet card is cardbus, so if there's a problem with cardbus > initialization during stage 2, the wireless card may not point that > out. Most modern cards are cardbus. > > [ description of new workaround for stage 1 ] > > > When 2st stage comes up after the reboot, you should have a working > > wireless NIC and as such you can choose to download extra packages > > via ftp, http, etc. > > Nope, that part still doesn't work. bugger. > It looks like we're down to two problems: > > 1. No provision during stage 1 for saying "I really have a network >even though the card isn't plugged in." Your workaround seems >to work (probably including the extra parts with wireless-tools, >for those using a wireless card). > > 2. Stage 2 does not initialize the network when it's running off >a cardbus card. The ctrl-alt-F2, log in, ifup, ctrl-alt-F1 >workaround seems to solve this. How about consecutive reboots when the system is installed via the sarge installer and up'n'running? Is the network then also not initialized so that you have to always do ifup manually upon every reboot? > > I forget if you have already mentioned this earlier on, but have > > you actually had the wireless card in question working in Linux at > > anytime? > > The 3Com card I'm using works fine on my working sarge (installed > using the woody installer, then upgrading; it also works on libranet, > xandros and various redhats). > I have had some issues with some versions of debian when hotplugging > the card, because the hotplug scripts reference $INTERFACE$LIFA
Bug#263581: no network tools in root image
Package: debian-installer Severity: wishlist At least, there should be ping / traceroute in the root image -- System Information: Debian Release: 3.1 APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.4.26-grsec Locale: LANG=en_US, LC_CTYPE=en_US -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#263579: debian-installer: debconf locales not used
Package: debian-installer Severity: important With the CD image of 110 MB for beta 4 At prompt, I chosed fr_FR for installation; On debconf prompt for locales, I chosed to generate en_US and fr_FR and to use en_US by default. Even after rebooting, the default locale is always fr_FR. when I type dpkg-reconfigure locales, I see that none of the other locals are selected but fr_FR. Then I have to select them again and set the default to en_US so everything is ok after. I hope you understand what I mean ... ;) -- System Information: Debian Release: 3.1 APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.4.26-grsec Locale: LANG=en_US, LC_CTYPE=en_US -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#241179: successful install, no network in 2nd stage (pcmcia)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thursday 05 August 2004 06:04, you wrote: > Akkana Peck writes: > > I'll run a test using a pcmcia ethernet card and report back. > > I tried it with an old Xircom PCMCIA card that used to work > absolutely everywhere (I think the module was called xircom-cs). > The Sarge installer doesn't recognize it. Oh, well. :-( Well, thanks for trying. - -- Frederik Dannemare | mailto:[EMAIL PROTECTED] GnuPG key: search for 'dannemare' on http://pgpkeys.mit.edu Key fingerprint: BB7B 078A 0DBF 7663 180A F84A 2D25 FAD5 9C4E B5A8 http://frederik.dannemare.net | http://www.linuxworlddomination.dk -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFBEfqFLSX61ZxOtagRAqN/AJ94GscZiAKcEWfI2BGif4p1SjNJ1wCeIXLS JP+leV4EjxRuOL5WwYLXWEY= =dynW -END PGP SIGNATURE-
discover1-data status ?
Hello, I am in need of a discover1-data upload, with a patch applied (The one in #261703), but the discover1 maintainers seem to be silent on this issue. Is discover1 managed in a CVS/SVN somewhere i could checkin the change directly, or someone here know if gaudenz (or the other discover1 maintainers ?) Are currently in vacations or somehow offline ? What is the status of discover1 with regard to the base freeze ? I had the bug report filled before the freeze, but as it was not acted upon. Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#263584: {mountpoint} when formating
Package: debian-installer
Severity: minor
Tags: l10n
when it is formating it shows "{mountpoint}" instead of the value of
the mountpoint.
I was in locale fr_FR.
-- System Information:
Debian Release: 3.1
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.4.26-grsec
Locale: LANG=en_US, LC_CTYPE=en_US
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#263579: maybe related to #238301
This bug may have the same cause as #238301. -- Pascal Greliche Service Technique ICX France Tel : 08 99 703 403 Fax : 08 26 800 206 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
debian-installer_20040801_mips.changes ACCEPTED
Accepted: debian-installer-manual_20040801_mips.deb to pool/main/d/debian-installer/debian-installer-manual_20040801_mips.deb Thank you for your contribution to Debian. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: Re: Bug#263317: Language not set at second-stage
Processing commands for [EMAIL PROTECTED]: > reassign 263317 countrychooser Bug#263317: Language not set at second-stage Bug reassigned from package `installation-reports' to `countrychooser'. > tags 263317 + d-i l10n patch Bug#263317: Language not set at second-stage There were no tags set. Tags added: d-i, l10n, patch > 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#263584: {mountpoint} when formating
Hi,
On Thu, Aug 05, 2004 at 11:31:38AM +0200, Pascal Greliche wrote:
> Package: debian-installer
> Severity: minor
> Tags: l10n
>
> when it is formating it shows "{mountpoint}" instead of the value of
> the mountpoint.
> I was in locale fr_FR.
Which version of the debian-installer are you using ?
The string {mountpoint} does not exist anymore in the repository.
Cheers,
--
Pierre Machard
<[EMAIL PROTECTED]> http://debian.org
GPG: 1024D/23706F87 : B906 A53F 84E0 49B6 6CF7 82C2 B3A0 2D66 2370 6F87
signature.asc
Description: Digital signature
Re: Bug#263575: base-files: LANG=C for some languages when root login from console
reassign 263575 debian-installer retitle 263575 Some LANG values are dangerous (?) thanks On Thu, 5 Aug 2004, Kenshi Muto wrote: > Package: base-files > Version: 3.0.15 > Severity: wishlist > Tags: d-i > > Hi, > > d-i writes LANG which is chosen by user on /etc/environment. > This is generally good, because normal user doesn't need to set LANG > by him/herself. > > But unfortunately, Linux console can't show some languages directly > (such as Japanese, Korean, Chinese). > > - normal user see broken characters on console: sad, but you may use X > Window System. > - root user see broken characters on console: Well, this is a problem. > If user didn't install X Window System on d-i stage, root user needs > to install by him/herself. When user runs apt-get install ... > Oops. console shows broken characters and we can't read provided > debconf messages. > > I considered how to avoid this problem, and created a code for > /usr/share/base-files/dot.profile (This file will be installed as > /root/.profile). > > - > if [ "$TERM" = "linux" ]; then > case "$(locale charmap)" in > EUC-*|GB*|BIG5*) > LANG=C > export LANG > ;; > esac > fi > - > > Adding this to /usr/share/base-files/dot.profile, console root > user with some (problematic) languages uses LANG=C automatically. Sorry, I don't think base-files should fiddle with the LANG variable. The CD #1 of woody had support for Asian languages via the frame buffer device, and it worked "on the console". If this does not work anymore in sarge, it should probably be fixed. Setting LANG only for root would be a hack, not a solution. Moreover, if there are really some values for LANG which are "dangerous" and unusable on console, debian-installer should warn about it. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#263584: {mountpoint} when formating
Beta 4 I think; from the 110 MB iso downloaded yesturday.
--
Pascal Greliche
Service Technique ICX France
Tel : 08 99 703 403
Fax : 08 26 800 206
Le 5 août 04, à 12:03, Pierre Machard a écrit :
Hi,
On Thu, Aug 05, 2004 at 11:31:38AM +0200, Pascal Greliche wrote:
Package: debian-installer
Severity: minor
Tags: l10n
when it is formating it shows "{mountpoint}" instead of the value of
the mountpoint.
I was in locale fr_FR.
Which version of the debian-installer are you using ?
The string {mountpoint} does not exist anymore in the repository.
Cheers,
--
Pierre Machard
<[EMAIL PROTECTED]> http://debian.org
GPG: 1024D/23706F87 : B906 A53F 84E0 49B6 6CF7 82C2 B3A0 2D66 2370 6F87
Bug#263596: installation-reports: ifconfig has no MAC-address changing support
Package: installation-reports Severity: wishlist Debian-installer-version: 20040802 http://cdimage.debian.org/pub/cdimage-testing/daily/i386/20040802/ uname -a: Linux goop 2.6.7 #1 Tue Aug 3 16:21:49 CEST 2004 i686 GNU/Linux Date: 20040803 12:00am (GTC+2) Method: network install with a minimum CD from CD; no proxy but direct access using LAN; mirror ftp.at.debian.org Machine: desktop PC with an AMD 2400 and 512 RAM; self assembled Processor: AMD Athlon(tm) XP 2400+ Memory: 512 MB Root Device: IDE Seagate ST380011A Root Size/partition table: /dev/hdc1 root-partition 20 Gb mounted as /; ext3 /dev/hdc6 swap-partition 512 MB Output of lspci: :00:00.0 Host bridge: VIA Technologies, Inc. VT8366/A/7 [Apollo KT266/A/333] :00:01.0 PCI bridge: VIA Technologies, Inc. VT8366/A/7 [Apollo KT266/A/333 AGP] :00:07.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10) :00:0a.0 SCSI storage controller: Adaptec AHA-7850 (rev 03) :00:10.0 USB Controller: VIA Technologies, Inc. VT82x UHCI USB 1.1 Controller (rev 80) :00:10.1 USB Controller: VIA Technologies, Inc. VT82x UHCI USB 1.1 Controller (rev 80) :00:10.2 USB Controller: VIA Technologies, Inc. VT82x UHCI USB 1.1 Controller (rev 80) :00:10.3 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 82) :00:11.0 ISA bridge: VIA Technologies, Inc. VT8235 ISA Bridge :00:11.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06) :00:11.5 Multimedia audio controller: VIA Technologies, Inc. VT8233/A/8235/8237 AC97 Audio Controller (rev 50) :01:00.0 VGA compatible controller: nVidia Corporation NV31 [GeForce FX 5600] (rev a1) Base System Installation Checklist: Initial boot worked:[O] Configure network HW: [O] Config network: [E] 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] [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Comments/Problems: Installation worked really fine, except that I first had to install only the basic packages, until I bootet the first time in my new system to change the MAC-address of my NIC to the one my provider knows to get network access with an IP I get through DHCP. It would be great if there would be a ifconfig version in the first bootup, which allows me to change the MAC-address when the module got loaded the first time. The command I use is "ifconfig eth0 hw ether -- System Information: Debian Release: 3.1 APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.7 Locale: LANG=C, LC_CTYPE=C -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#263604: installer locale bug
Package: installation-reports Debian-installer-version: http://cdimage.debian.org/pub/cdimage-testing/sarge_d-i/i386/beta4/sarge-i386-netinst. uname -a: Linux masina 2.4.26 #1 SMP Sa Apr 17 19:33:42 CEST 2004 i686 GNU/Linux Date: 2004.07.29 Method: sarge-i386-netinst. If network install, from where? home Proxied? no, behind a router Machine: Built by me Processor: AMD Athlon 1900+ Memory: 512Mb Root Device: IDE Root Size/partition table: Device Boot Start End Blocks Id System /dev/hda1 * 1 637 51166717 HPFS/NTFS /dev/hda2 638486733977475f W95 Ext'd (LBA) /dev/hda5 638435729880868+ 7 HPFS/NTFS /dev/hda643584370 104391b W95 FAT32 /mnt/transfer /dev/hda743714832 3710983+ 83 Linux/ /dev/hda848334867 281106 82 Linux swap Output of lspci: :00:00.0 Host bridge: VIA Technologies, Inc. VT8366/A/7 [Apollo KT266/A/333] :00:01.0 PCI bridge: VIA Technologies, Inc. VT8366/A/7 [Apollo KT266/A/333 AGP] :00:0a.0 Multimedia audio controller: Creative Labs SB Live! EMU10k1 (rev 08) :00:0a.1 Input device controller: Creative Labs SB Live! MIDI/Game Port (rev 08) :00:0c.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10) :00:0d.0 FireWire (IEEE 1394): VIA Technologies, Inc. IEEE 1394 Host Controller (rev 46):00:11.0 ISA bridge: VIA Technologies, Inc. VT8233 PCI to ISA Bridge :00:11.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06) :00:11.2 USB Controller: VIA Technologies, Inc. VT82x UHCI USB 1.1 Controller (rev 1b) :00:11.3 USB Controller: VIA Technologies, Inc. VT82x UHCI USB 1.1 Controller (rev 1b) :01:00.0 VGA compatible controller: nVidia Corporation NV11 [GeForce2 MX/MX 400] (rev b2) Base System Installation Checklist: 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: [E] Install base system:[E] Install boot loader:[E] Reboot: [O] [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Comments/Problems: I choose language=en, different country, then select Hungary, and during installing base packages, I get the following error: perl: warning: Setting locale failed. (LANGUAGE=(unset) LC_ALL=(unset)) Cannot boot into windows without hacking grub, but that is a known problem as far as I know. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#263584: marked as done ({mountpoint} when formating)
Your message dated Thu, 5 Aug 2004 12:50:06 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Bug#263584: {mountpoint} when formating
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; 5 Aug 2004 09:32:50 +
>From [EMAIL PROTECTED] Thu Aug 05 02:32:50 2004
Return-path: <[EMAIL PROTECTED]>
Received: from fw-1.i-connexion.net (mail1.i-connexion.net) [212.44.243.21]
by spohr.debian.org with smtp (Exim 3.35 1 (Debian))
id 1BsecD-0001BU-00; Thu, 05 Aug 2004 02:32:50 -0700
Received: (qmail 28241 invoked by uid 889); 5 Aug 2004 09:31:41 -
Received: from [EMAIL PROTECTED] by mail1.i-connexion.net by uid 502 with
qmail-scanner-1.22
(clamdscan: 0.70. iscan: v3.1/v6.150-1001/885/50657. Clear:RC:1(212.44.225.35):.
Processed in 1.305587 secs); 05 Aug 2004 09:31:41 -
Received: from pouet78.i-connexion.net (HELO ?212.44.225.35?) (212.44.225.35)
by 0 with SMTP; 5 Aug 2004 09:31:39 -
Mime-Version: 1.0 (Apple Message framework v618)
Content-Transfer-Encoding: 7bit
Message-Id: <[EMAIL PROTECTED]>
Content-Type: text/plain; charset=US-ASCII; format=flowed
To: [EMAIL PROTECTED]
From: Pascal Greliche <[EMAIL PROTECTED]>
Subject: {mountpoint} when formating
Date: Thu, 5 Aug 2004 11:31:38 +0200
X-Mailer: Apple Mail (2.618)
X-Spam-Rating: 0 1.6.2 0/0/N
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
Severity: minor
Tags: l10n
when it is formating it shows "{mountpoint}" instead of the value of
the mountpoint.
I was in locale fr_FR.
-- System Information:
Debian Release: 3.1
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.4.26-grsec
Locale: LANG=en_US, LC_CTYPE=en_US
---
Received: (at 263584-close) by bugs.debian.org; 5 Aug 2004 10:50:08 +
>From [EMAIL PROTECTED] Thu Aug 05 03:50:08 2004
Return-path: <[EMAIL PROTECTED]>
Received: from caribou.techmag.info (caribou.migus.eu.org) [62.4.18.32]
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1Bsfp2-0001n1-00; Thu, 05 Aug 2004 03:50:08 -0700
Received: from migus by caribou.migus.eu.org with local (Exim 4.32)
id 1Bsfp0-0006A5-Vq; Thu, 05 Aug 2004 12:50:07 +0200
Date: Thu, 5 Aug 2004 12:50:06 +0200
From: Pierre Machard <[EMAIL PROTECTED]>
To: Pascal Greliche <[EMAIL PROTECTED]>, [EMAIL PROTECTED]
Subject: Re: Bug#263584: {mountpoint} when formating
Message-ID: <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
protocol="application/pgp-signature"; boundary="jy6Sn24JjFx/iggw"
Content-Disposition: inline
In-Reply-To: <[EMAIL PROTECTED]>
X-pgp-fingerprint: B906 A53F 84E0 49B6 6CF7 82C2 B3A0 2D66 2370 6F87
Organization: debian.org
User-Agent: Mutt/1.5.6+20040523i
Sender: Pierre Machard <[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=-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:
--jy6Sn24JjFx/iggw
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
Hi,
On Thu, Aug 05, 2004 at 12:23:22PM +0200, Pascal Greliche wrote:
> Beta 4 I think; from the 110 MB iso downloaded yesturday.
This bug has been fixed for a long while now. The lastest version of the
debian installer should be available within a couple of days.
Thanks for your repport,
Cheers,
--=20
Pierre Machard
<[EMAIL PROTECTED]> http://debian.org
GPG: 1024D/23706F87 : B906 A53F 84E0 49B6 6CF7 82C2 B3A0 2D66 2370 6F87
--jy6Sn24JjFx/iggw
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.4 (GNU/Linux)
iD8DBQFBEhDes6AtZiNwb4cRAt32AJ9ISY4X/tk5JwJPzYr0BJLCOyIsWgCgjOEM
ghA5LiypR7x2dJEX1vK0w9M=
=gViG
-END PGP SIGNATURE-
--jy6Sn24JjFx/iggw--
--
To UNSUBSCRIBE, email
brand x
Generic PhÄrmCy,upto 80% off! XanÂx, VÀlium, Hydrocodone, and Norco.. 3 of the best pÀÍn kÍLLerS out and other populAr productS. http://dewitt.znbarw1.com/py/ re_move http://cathode.znbarw1.com/g.html townsman millenarian hornbeam diabetic distillery cerebellum hamster axon east water bear bodybuilder parakeet whole molecule -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
[Manual] installer-manual on the website (was: release plans for website?)
On Mon, Aug 02, 2004 at 10:55:38PM -0400, Joey Hess wrote: > Is there any plan for how the web site update will be handled for > sarge's release? Besides just switching the names and links to sarge, > I've been looking at what parts of the web site will need updating for > the new installer and other missing bits. These include: > [...] > - sarge/installmanual: doesn't exist. One possibility is to link to the >sarge install manual in the debian archive on a mirror, which is >updated whenever the images are updated. I don't know how the woody >install manual is imported into the web site so maybe however it is >manage is better. This is how the installation manual was handled for boot-floppies (i.e. potato and woody): The sources where checked out from the boot-floppies CVS and were build locally. I investigated a bit how to handle the sarge installation manual: The installation manual doesn't build on woody AFAICT, so manual build is probably no option until www-master is updated to sarge, and I think nobody want rely on that. So linking to an external resource like the archive or copying it from there would be better. Some questions to consider: - The boot-floppies manual was built as PDF, plain text and HTML. I think at least plain text and HTML should be available for sarge, too. Yet I don't see any generation of plain text currently. Is this intentional? - For usage on the website the files should be able to be handled by content negotiation. This requires that there is only one directory per arch with all translations in it and files named foo..html. Would it be possible to generate the pages this way or should we write a little script that solves this by renaming the current output files? Gruesse, -- Frank Lichtenheld <[EMAIL PROTECTED]> www: http://www.djpig.de/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processing of linux-kernel-di-m68k_0.61_source+m68k.changes
linux-kernel-di-m68k_0.61_source+m68k.changes uploaded successfully to localhost along with the files: linux-kernel-di-m68k_0.61.dsc linux-kernel-di-m68k_0.61.tar.gz kernel-image-2.2.25-mac-di_0.61_m68k.udeb nic-shared-modules-2.2.25-mac-di_0.61_m68k.udeb ppp-modules-2.2.25-mac-di_0.61_m68k.udeb scsi-modules-2.2.25-mac-di_0.61_m68k.udeb fat-modules-2.2.25-mac-di_0.61_m68k.udeb kernel-image-2.4.26-amiga-di_0.61_m68k.udeb nic-shared-modules-2.4.26-amiga-di_0.61_m68k.udeb ppp-modules-2.4.26-amiga-di_0.61_m68k.udeb scsi-modules-2.4.26-amiga-di_0.61_m68k.udeb jfs-modules-2.4.26-amiga-di_0.61_m68k.udeb reiserfs-modules-2.4.26-amiga-di_0.61_m68k.udeb fat-modules-2.4.26-amiga-di_0.61_m68k.udeb kernel-image-2.4.26-atari-di_0.61_m68k.udeb nic-shared-modules-2.4.26-atari-di_0.61_m68k.udeb ppp-modules-2.4.26-atari-di_0.61_m68k.udeb scsi-modules-2.4.26-atari-di_0.61_m68k.udeb jfs-modules-2.4.26-atari-di_0.61_m68k.udeb reiserfs-modules-2.4.26-atari-di_0.61_m68k.udeb fat-modules-2.4.26-atari-di_0.61_m68k.udeb kernel-image-2.2.25-atari-di_0.61_m68k.udeb nic-shared-modules-2.2.25-atari-di_0.61_m68k.udeb ppp-modules-2.2.25-atari-di_0.61_m68k.udeb scsi-modules-2.2.25-atari-di_0.61_m68k.udeb fat-modules-2.2.25-atari-di_0.61_m68k.udeb kernel-image-2.2.25-bvme6000-di_0.61_m68k.udeb nic-shared-modules-2.2.25-bvme6000-di_0.61_m68k.udeb ppp-modules-2.2.25-bvme6000-di_0.61_m68k.udeb scsi-modules-2.2.25-bvme6000-di_0.61_m68k.udeb fat-modules-2.2.25-bvme6000-di_0.61_m68k.udeb kernel-image-2.4.26-bvme6000-di_0.61_m68k.udeb nic-shared-modules-2.4.26-bvme6000-di_0.61_m68k.udeb ppp-modules-2.4.26-bvme6000-di_0.61_m68k.udeb scsi-modules-2.4.26-bvme6000-di_0.61_m68k.udeb jfs-modules-2.4.26-bvme6000-di_0.61_m68k.udeb reiserfs-modules-2.4.26-bvme6000-di_0.61_m68k.udeb fat-modules-2.4.26-bvme6000-di_0.61_m68k.udeb kernel-image-2.2.25-mvme147-di_0.61_m68k.udeb nic-shared-modules-2.2.25-mvme147-di_0.61_m68k.udeb ppp-modules-2.2.25-mvme147-di_0.61_m68k.udeb scsi-modules-2.2.25-mvme147-di_0.61_m68k.udeb fat-modules-2.2.25-mvme147-di_0.61_m68k.udeb kernel-image-2.4.26-mvme147-di_0.61_m68k.udeb nic-shared-modules-2.4.26-mvme147-di_0.61_m68k.udeb ppp-modules-2.4.26-mvme147-di_0.61_m68k.udeb scsi-modules-2.4.26-mvme147-di_0.61_m68k.udeb jfs-modules-2.4.26-mvme147-di_0.61_m68k.udeb reiserfs-modules-2.4.26-mvme147-di_0.61_m68k.udeb fat-modules-2.4.26-mvme147-di_0.61_m68k.udeb kernel-image-2.2.25-mvme16x-di_0.61_m68k.udeb nic-shared-modules-2.2.25-mvme16x-di_0.61_m68k.udeb ppp-modules-2.2.25-mvme16x-di_0.61_m68k.udeb scsi-modules-2.2.25-mvme16x-di_0.61_m68k.udeb fat-modules-2.2.25-mvme16x-di_0.61_m68k.udeb kernel-image-2.4.26-mvme16x-di_0.61_m68k.udeb nic-shared-modules-2.4.26-mvme16x-di_0.61_m68k.udeb ppp-modules-2.4.26-mvme16x-di_0.61_m68k.udeb scsi-modules-2.4.26-mvme16x-di_0.61_m68k.udeb jfs-modules-2.4.26-mvme16x-di_0.61_m68k.udeb reiserfs-modules-2.4.26-mvme16x-di_0.61_m68k.udeb fat-modules-2.4.26-mvme16x-di_0.61_m68k.udeb kernel-image-2.4.26-q40-di_0.61_m68k.udeb nic-shared-modules-2.4.26-q40-di_0.61_m68k.udeb ppp-modules-2.4.26-q40-di_0.61_m68k.udeb scsi-modules-2.4.26-q40-di_0.61_m68k.udeb jfs-modules-2.4.26-q40-di_0.61_m68k.udeb reiserfs-modules-2.4.26-q40-di_0.61_m68k.udeb fat-modules-2.4.26-q40-di_0.61_m68k.udeb Greetings, Your Debian queue daemon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processing of vmelilo-installer_1.5_m68k.changes
vmelilo-installer_1.5_m68k.changes uploaded successfully to localhost along with the files: vmelilo-installer_1.5.dsc vmelilo-installer_1.5.tar.gz vmelilo-installer_1.5_m68k.udeb Greetings, Your Debian queue daemon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: r18868 - in trunk/packages/ddetect: . debian
On Thu, Aug 05, 2004 at 02:51:42PM +0100, Colin Watson wrote: > On Thu, Aug 05, 2004 at 11:16:31AM +0200, Sven Luther wrote: > > On Wed, Aug 04, 2004 at 10:51:55PM +0100, Colin Watson wrote: > > > mdetect seems like clearly the right place. Its package description and > > > its man page both suggest that gpm could easily be modified to use it > > > (indeed, mdetect's default behaviour is to produce output suitable for > > > configuring gpm). > > > > And is it part of base, and sure to be run if the user does a clean install > > and chose the X task in tasksel ? > > Yes, base-config installs mdetect and xserver-xfree86.config uses it > (although you may have to request that it be used, I don't remember; in > any case we'd be in the same position as other architectures here). Ok, i will look at it then. BTW, Hopefully Branden will be more responsive in updating the package than the discover folk. Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: discover1-data status ?
On Thu, Aug 05, 2004 at 11:28:44AM +0200, Sven Luther wrote: > What is the status of discover1 with regard to the base freeze ? I had the bug > report filled before the freeze, but as it was not acted upon. It is not installed by debootstrap nor Priority: >= standard, so it's not frozen. Obviously it should be treated fairly conservatively, but module updates are fine. -- Colin Watson [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: discover1-data status ?
On Thu, Aug 05, 2004 at 02:53:38PM +0100, Colin Watson wrote: > On Thu, Aug 05, 2004 at 11:28:44AM +0200, Sven Luther wrote: > > What is the status of discover1 with regard to the base freeze ? I had the bug > > report filled before the freeze, but as it was not acted upon. > > It is not installed by debootstrap nor Priority: >= standard, so it's > not frozen. Obviously it should be treated fairly conservatively, but > module updates are fine. Since the change i want is just one line change, it is probably fine. What do i do now ? Do i NMU discover1-data with the change (Branden okeyed a similar change in discover2-data already) ? Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
linux-kernel-di-m68k_0.61_source+m68k.changes ACCEPTED
Accepted: fat-modules-2.2.25-atari-di_0.61_m68k.udeb to pool/main/l/linux-kernel-di-m68k/fat-modules-2.2.25-atari-di_0.61_m68k.udeb fat-modules-2.2.25-bvme6000-di_0.61_m68k.udeb to pool/main/l/linux-kernel-di-m68k/fat-modules-2.2.25-bvme6000-di_0.61_m68k.udeb fat-modules-2.2.25-mac-di_0.61_m68k.udeb to pool/main/l/linux-kernel-di-m68k/fat-modules-2.2.25-mac-di_0.61_m68k.udeb fat-modules-2.2.25-mvme147-di_0.61_m68k.udeb to pool/main/l/linux-kernel-di-m68k/fat-modules-2.2.25-mvme147-di_0.61_m68k.udeb fat-modules-2.2.25-mvme16x-di_0.61_m68k.udeb to pool/main/l/linux-kernel-di-m68k/fat-modules-2.2.25-mvme16x-di_0.61_m68k.udeb fat-modules-2.4.26-amiga-di_0.61_m68k.udeb to pool/main/l/linux-kernel-di-m68k/fat-modules-2.4.26-amiga-di_0.61_m68k.udeb fat-modules-2.4.26-atari-di_0.61_m68k.udeb to pool/main/l/linux-kernel-di-m68k/fat-modules-2.4.26-atari-di_0.61_m68k.udeb fat-modules-2.4.26-bvme6000-di_0.61_m68k.udeb to pool/main/l/linux-kernel-di-m68k/fat-modules-2.4.26-bvme6000-di_0.61_m68k.udeb fat-modules-2.4.26-mvme147-di_0.61_m68k.udeb to pool/main/l/linux-kernel-di-m68k/fat-modules-2.4.26-mvme147-di_0.61_m68k.udeb fat-modules-2.4.26-mvme16x-di_0.61_m68k.udeb to pool/main/l/linux-kernel-di-m68k/fat-modules-2.4.26-mvme16x-di_0.61_m68k.udeb fat-modules-2.4.26-q40-di_0.61_m68k.udeb to pool/main/l/linux-kernel-di-m68k/fat-modules-2.4.26-q40-di_0.61_m68k.udeb jfs-modules-2.4.26-amiga-di_0.61_m68k.udeb to pool/main/l/linux-kernel-di-m68k/jfs-modules-2.4.26-amiga-di_0.61_m68k.udeb jfs-modules-2.4.26-atari-di_0.61_m68k.udeb to pool/main/l/linux-kernel-di-m68k/jfs-modules-2.4.26-atari-di_0.61_m68k.udeb jfs-modules-2.4.26-bvme6000-di_0.61_m68k.udeb to pool/main/l/linux-kernel-di-m68k/jfs-modules-2.4.26-bvme6000-di_0.61_m68k.udeb jfs-modules-2.4.26-mvme147-di_0.61_m68k.udeb to pool/main/l/linux-kernel-di-m68k/jfs-modules-2.4.26-mvme147-di_0.61_m68k.udeb jfs-modules-2.4.26-mvme16x-di_0.61_m68k.udeb to pool/main/l/linux-kernel-di-m68k/jfs-modules-2.4.26-mvme16x-di_0.61_m68k.udeb jfs-modules-2.4.26-q40-di_0.61_m68k.udeb to pool/main/l/linux-kernel-di-m68k/jfs-modules-2.4.26-q40-di_0.61_m68k.udeb kernel-image-2.2.25-atari-di_0.61_m68k.udeb to pool/main/l/linux-kernel-di-m68k/kernel-image-2.2.25-atari-di_0.61_m68k.udeb kernel-image-2.2.25-bvme6000-di_0.61_m68k.udeb to pool/main/l/linux-kernel-di-m68k/kernel-image-2.2.25-bvme6000-di_0.61_m68k.udeb kernel-image-2.2.25-mac-di_0.61_m68k.udeb to pool/main/l/linux-kernel-di-m68k/kernel-image-2.2.25-mac-di_0.61_m68k.udeb kernel-image-2.2.25-mvme147-di_0.61_m68k.udeb to pool/main/l/linux-kernel-di-m68k/kernel-image-2.2.25-mvme147-di_0.61_m68k.udeb kernel-image-2.2.25-mvme16x-di_0.61_m68k.udeb to pool/main/l/linux-kernel-di-m68k/kernel-image-2.2.25-mvme16x-di_0.61_m68k.udeb kernel-image-2.4.26-amiga-di_0.61_m68k.udeb to pool/main/l/linux-kernel-di-m68k/kernel-image-2.4.26-amiga-di_0.61_m68k.udeb kernel-image-2.4.26-atari-di_0.61_m68k.udeb to pool/main/l/linux-kernel-di-m68k/kernel-image-2.4.26-atari-di_0.61_m68k.udeb kernel-image-2.4.26-bvme6000-di_0.61_m68k.udeb to pool/main/l/linux-kernel-di-m68k/kernel-image-2.4.26-bvme6000-di_0.61_m68k.udeb kernel-image-2.4.26-mvme147-di_0.61_m68k.udeb to pool/main/l/linux-kernel-di-m68k/kernel-image-2.4.26-mvme147-di_0.61_m68k.udeb kernel-image-2.4.26-mvme16x-di_0.61_m68k.udeb to pool/main/l/linux-kernel-di-m68k/kernel-image-2.4.26-mvme16x-di_0.61_m68k.udeb kernel-image-2.4.26-q40-di_0.61_m68k.udeb to pool/main/l/linux-kernel-di-m68k/kernel-image-2.4.26-q40-di_0.61_m68k.udeb linux-kernel-di-m68k_0.61.dsc to pool/main/l/linux-kernel-di-m68k/linux-kernel-di-m68k_0.61.dsc linux-kernel-di-m68k_0.61.tar.gz to pool/main/l/linux-kernel-di-m68k/linux-kernel-di-m68k_0.61.tar.gz nic-shared-modules-2.2.25-atari-di_0.61_m68k.udeb to pool/main/l/linux-kernel-di-m68k/nic-shared-modules-2.2.25-atari-di_0.61_m68k.udeb nic-shared-modules-2.2.25-bvme6000-di_0.61_m68k.udeb to pool/main/l/linux-kernel-di-m68k/nic-shared-modules-2.2.25-bvme6000-di_0.61_m68k.udeb nic-shared-modules-2.2.25-mac-di_0.61_m68k.udeb to pool/main/l/linux-kernel-di-m68k/nic-shared-modules-2.2.25-mac-di_0.61_m68k.udeb nic-shared-modules-2.2.25-mvme147-di_0.61_m68k.udeb to pool/main/l/linux-kernel-di-m68k/nic-shared-modules-2.2.25-mvme147-di_0.61_m68k.udeb nic-shared-modules-2.2.25-mvme16x-di_0.61_m68k.udeb to pool/main/l/linux-kernel-di-m68k/nic-shared-modules-2.2.25-mvme16x-di_0.61_m68k.udeb nic-shared-modules-2.4.26-amiga-di_0.61_m68k.udeb to pool/main/l/linux-kernel-di-m68k/nic-shared-modules-2.4.26-amiga-di_0.61_m68k.udeb nic-shared-modules-2.4.26-atari-di_0.61_m68k.udeb to pool/main/l/linux-kernel-di-m68k/nic-shared-modules-2.4.26-atari-di_0.61_m68k.udeb nic-shared-modules-2.4.26-bvme6000-di_0.61_m68k.udeb to pool/main/l/linux-kernel-di-m68k/nic-shared-modules-2.4.26-bvme6000-di_0.61_m68k.udeb nic-shared-modules-2.4.26-mvme147-di_0.61_m68k.udeb to pool/main/l/linux-kernel-di-m68k/nic-shared-modules-2.4.26-m
vmelilo-installer_1.5_m68k.changes ACCEPTED
Accepted: vmelilo-installer_1.5.dsc to pool/main/v/vmelilo-installer/vmelilo-installer_1.5.dsc vmelilo-installer_1.5.tar.gz to pool/main/v/vmelilo-installer/vmelilo-installer_1.5.tar.gz vmelilo-installer_1.5_m68k.udeb to pool/main/v/vmelilo-installer/vmelilo-installer_1.5_m68k.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]
Processed: [i386] [netboot] Kernel panic: VFS: unable to mount root fs
Processing commands for [EMAIL PROTECTED]: > clone 241212 -1 Bug#241212: [i386] [beta3] [netboot] kernel panic during boot Bug 241212 cloned as bug 263750. > reassign -1 debian-installer Bug#263750: [i386] [beta3] [netboot] kernel panic during boot Bug reassigned from package `installation-reports' to `debian-installer'. > retitle -1 [i386] [netboot] Kernel panic: VFS: unable to mount root fs Bug#263750: [i386] [beta3] [netboot] kernel panic during boot Changed Bug title. > tags -1 d-i Bug#263750: [i386] [netboot] Kernel panic: VFS: unable to mount root fs There were no tags set. Tags added: d-i > 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#241212: kernel panic during boot
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wednesday 04 August 2004 13:36, Alexey Nezhdanov wrote: [ snip ] > Bug reproduced with today's (2004.08.04) daily build. OK. Thanks for the feedback - it's much appreciated. I will clone off your report to the developers in charge of this area, and then I will close this report. The other developers will probably ask you for further info, when they get to your problem regarding this kernel panic. Best regards, - -- Frederik Dannemare | mailto:[EMAIL PROTECTED] GnuPG key: search for 'dannemare' on http://pgpkeys.mit.edu Key fingerprint: BB7B 078A 0DBF 7663 180A F84A 2D25 FAD5 9C4E B5A8 http://frederik.dannemare.net | http://www.linuxworlddomination.dk -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFBEk/lLSX61ZxOtagRArXnAJwOw/F72RGjABd14k7qPqveSCr+EACfa/DX ywKeCaiFxUBW/48vHBCrzUc= =ZkkE -END PGP SIGNATURE-
Processing of discover1-data_1.2004.07.28_i386.changes
discover1-data_1.2004.07.28_i386.changes uploaded successfully to localhost along with the files: discover1-data_1.2004.07.28.dsc discover1-data_1.2004.07.28.tar.gz discover1-data_1.2004.07.28_all.deb discover1-data-udeb_1.2004.07.28_all.udeb Greetings, Your Debian queue daemon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#261703: marked as done (discover1-data: Marvell 643[46]0 builtin ethernet driver.)
Your message dated Thu, 05 Aug 2004 11:47:04 -0400 with message-id <[EMAIL PROTECTED]> and subject line Bug#261703: fixed in discover1-data 1.2004.07.28 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; 27 Jul 2004 17:51:56 + >From [EMAIL PROTECTED] Tue Jul 27 10:51:56 2004 Return-path: <[EMAIL PROTECTED]> Received: from smtp3.wanadoo.fr (mwinf0302.wanadoo.fr) [193.252.22.28] by spohr.debian.org with esmtp (Exim 3.35 1 (Debian)) id 1BpW7I-00064T-00; Tue, 27 Jul 2004 10:51:56 -0700 Received: from pegasos (AStrasbourg-251-1-15-225.w82-126.abo.wanadoo.fr [82.126.205.225]) by mwinf0302.wanadoo.fr (SMTP Server) with ESMTP id 1C000382; Tue, 27 Jul 2004 19:51:25 +0200 (CEST) Received: from luther by pegasos with local (Exim 4.34) id 1BpW8w-0001o2-NK; Tue, 27 Jul 2004 19:53:38 +0200 Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: Sven Luther <[EMAIL PROTECTED]> To: Debian Bug Tracking System <[EMAIL PROTECTED]> Subject: discover1-data: Marvell 643[46]0 builtin ethernet driver. X-Mailer: reportbug 2.63 Date: Tue, 27 Jul 2004 19:53:38 +0200 Message-Id: <[EMAIL PROTECTED]> Sender: Sven Luther <[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=-5.0 required=4.0 tests=HAS_PACKAGE autolearn=no version=2.60-bugs.debian.org_2004_03_25 X-Spam-Level: Package: discover1-data Version: 1.2004.07.18 Severity: normal Please apply this patch : patch -- --- pci.lst.orig2004-07-27 19:37:04.966841192 +0200 +++ pci.lst 2004-07-27 19:38:27.456300888 +0200 @@ -2852,7 +2852,7 @@ 11ab5081unknown unknown MV88SX5081 8-port SATA I PCI-X Controller 11ab6041unknown unknown MV88SX6041 4-port SATA II PCI-X Controller 11ab6081unknown unknown MV88SX6081 8-port SATA II PCI-X Controller - 11ab6460unknown unknown MV64360/64361/64362 System Controller + 11ab6460ethernetmv64340_eth MV64360/64361/64362 builtin Gigabit Ethernet Adapter 11abf003unknown unknown GT-64010 Primary Image Piranha Image Generator 11ac Canon Information Systems Research Aust. 11ad Lite-On Communications Inc patch -- Which will enable the detection and loading of the ethernet driver for the builtin gigabit ethernet ports of the Marvell MV64360/1/2 System Controller. The same should go for the Marvell MV64340/1/2 ones for mips, but i don't know their pci ids. -- Package-specific info: lspci: :00:00.0 Host bridge: Marvell Technology Group Ltd. MV64360/64361/64362 System Controller (rev 03) :00:01.0 FireWire (IEEE 1394): VIA Technologies, Inc. IEEE 1394 Host Controller (rev 46) :00:05.0 SCSI storage controller: LSI Logic / Symbios Logic 53c810 (rev 23) :00:0c.0 ISA bridge: VIA Technologies, Inc. VT8231 [PCI-to-ISA Bridge] (rev 10) :00:0c.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06) :00:0c.2 USB Controller: VIA Technologies, Inc. VT82x UHCI USB 1.1 Controller (rev 1e) :00:0c.3 USB Controller: VIA Technologies, Inc. VT82x UHCI USB 1.1 Controller (rev 1e) :00:0c.4 Bridge: VIA Technologies, Inc. VT8235 ACPI (rev 10) :00:0c.5 Multimedia audio controller: VIA Technologies, Inc. VT82C686 AC97 Audio Controller (rev 40) :00:0c.6 Communication controller: VIA Technologies, Inc. Intel 537 [AC97 Modem] (rev 20) :00:0d.0 Ethernet controller: VIA Technologies, Inc. VT6102 [Rhine-II] (rev 51) 0001:01:00.0 Host bridge: Marvell Technology Group Ltd. MV64360/64361/64362 System Controller (rev 03) 0001:01:08.0 VGA compatible controller: ATI Technologies Inc RV280 [Radeon 9200 SE] (rev 01) :00:00.0 0600: 11ab:6460 (rev 03) :00:01.0 0c00: 1106:3044 (rev 46) :00:05.0 0100: 1000:0001 (rev 23) :00:0c.0 0601: 1106:8231 (rev 10) :00:0c.1 0101: 1106:0571 (rev 06) :00:0c.2 0c03: 1106:3038 (rev 1e) :00:0c.3 0c03: 1106:3038 (rev 1e) :00:0c.4 0680: 1106:8235 (rev 10) :00:0c.5 0401: 1106:3058 (rev 40) :00:0c.6 0780: 1106:3068 (rev 20) :00:0d.0 0200: 1106:3065 (rev 51) 0001:01:00.0 0600: 11ab:6460 (rev 03) 0001:01:08.0 0300: 1002:5964 (rev 01) discover: -- System Informa
discover1-data_1.2004.07.28_i386.changes ACCEPTED
Accepted: discover1-data-udeb_1.2004.07.28_all.udeb to pool/main/d/discover1-data/discover1-data-udeb_1.2004.07.28_all.udeb discover1-data_1.2004.07.28.dsc to pool/main/d/discover1-data/discover1-data_1.2004.07.28.dsc discover1-data_1.2004.07.28.tar.gz to pool/main/d/discover1-data/discover1-data_1.2004.07.28.tar.gz discover1-data_1.2004.07.28_all.deb to pool/main/d/discover1-data/discover1-data_1.2004.07.28_all.deb Announcing to [EMAIL PROTECTED] Closing bugs: 254830 261703 261778 262082 263414 Thank you for your contribution to Debian. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#254830: marked as done (Please include firewire for network installs)
Your message dated Thu, 05 Aug 2004 11:47:04 -0400 with message-id <[EMAIL PROTECTED]> and subject line Bug#254830: fixed in discover1-data 1.2004.07.28 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; 17 Jun 2004 07:55:56 + >From [EMAIL PROTECTED] Thu Jun 17 00:55:56 2004 Return-path: <[EMAIL PROTECTED]> Received: from mrelay3.uni-hannover.de [130.75.2.41] (root) by spohr.debian.org with esmtp (Exim 3.35 1 (Debian)) id 1BarkZ-0007ne-00; Thu, 17 Jun 2004 00:55:55 -0700 Received: from mail.itp.uni-hannover.de (mail.itp.uni-hannover.de [130.75.25.242]) by mrelay3.uni-hannover.de (8.12.10/8.12.10) with ESMTP id i5H7to6v028535 for <[EMAIL PROTECTED]>; Thu, 17 Jun 2004 09:55:50 +0200 (MEST) Received: from pleione.itp.uni-hannover.de (pleione.itp.uni-hannover.de [130.75.25.99]) by mail.itp.uni-hannover.de (Postfix) with ESMTP id 50BBAC585 for <[EMAIL PROTECTED]>; Thu, 17 Jun 2004 09:55:45 +0200 (CEST) Received: by pleione.itp.uni-hannover.de (Postfix, from userid 237) id 277045F39; Thu, 17 Jun 2004 09:55:45 +0200 (CEST) Date: Thu, 17 Jun 2004 09:55:45 +0200 From: Helge Kreutzmann <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Subject: Please include firewire for network installs Message-ID: <[EMAIL PROTECTED]> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="2qXFWqzzG3v1+95a" Content-Disposition: inline User-Agent: Mutt/1.4i X-Public-Key-URL: http://www.itp.uni-hannover.de/~kreutzm/data/kreutzm.gpg X-homepage: http://www.itp.uni-hannover.de/~kreutzm X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-1.2.2 (mrelay3.uni-hannover.de [130.75.2.41]); Thu, 17 Jun 2004 09:55:50 +0200 (MEST) X-Scanned-By: MIMEDefang 2.42 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: --2qXFWqzzG3v1+95a Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Package: debian-installer Severity: wishlist I have a USB/Firewire combo card in my alpha. Under 2.4.26 I can get a network interface by simply inserting eth1394 and ohci1394 (and then, as usual, bringing it up with ifconfig). This interface has been sucessfully used to transfere >1 GB from my PPC based ibook. So Ethernet over Firewire seems to work at least on alpha and ppc (and, according to reports on the net, also on x86). Hence it would be great, if debian-installer offered to probe for firewire as well, so installs over firewire would be possible. Given that three archs support it and the extra effort is quite limited, even if only few people might use it, it would enhance the *coolness* quite a lot (especially=20 given all the serious discussions about patents, freenes, etc.). Btw. the driver author has a @debian-address as well :-)) This is what lspci says about my Firewire: :01:05.0 FireWire (IEEE 1394): Texas Instruments TSB43AB22/A IEEE-1394a-2000 Controller (PHY/Link) (prog-if +10 [OHCI]) Flags: bus master, medium devsel, latency 32, IRQ 24 Memory at 09006000 (32-bit, non-prefetchable) [size=3D2K]= =20 Memory at 0900 (32-bit, non-prefetchable) [size=3D16K] Capabilities: [44] Power Management version 2 -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (990, 'testing') Architecture: alpha Kernel: Linux 2.4.21-pre1 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] --=20 --=20 Helge Kreutzmann, Dipl.-Phys. [EMAIL PROTECTED] er.de gpg signed mail preferredgpg-key: finger [EMAIL PROTECTED] er.de 64bit GNU powered http://www.itp.uni-hannover.de/~kreu= tzm Help keep free software "libre": http://www.freepatents.org/ --2qXFWqzzG3v1+95a Content-Type: application/pgp-signature Content-Disposition: inline -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD4DBQFA0U6ARsxcY/MYpWoRAiDBAJ0YzLep3OaMShDrdKVnBzhQUylLogCYrub+ vhGDfiDFhVZd73nwILIE3w== =Ps9/ -END PGP SIGNATURE- --2qXFWqzzG3v1+95a-- --- Received: (at 254830-close) by bugs.debian.org; 5 Aug 2004 1
Bug#263414: marked as done (discover1-data: nForce USB controller)
Your message dated Thu, 05 Aug 2004 11:47:04 -0400 with message-id <[EMAIL PROTECTED]> and subject line Bug#263414: fixed in discover1-data 1.2004.07.28 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; 4 Aug 2004 09:09:34 + >From [EMAIL PROTECTED] Wed Aug 04 02:09:34 2004 Return-path: <[EMAIL PROTECTED]> Received: from orochi.topstudio.co.jp (mail.topstudio.co.jp) [202.224.239.193] (postfix) by spohr.debian.org with esmtp (Exim 3.35 1 (Debian)) id 1BsHmA-0006f6-00; Wed, 04 Aug 2004 02:09:34 -0700 Received: from localhost (localhost [127.0.0.1]) by mail.topstudio.co.jp (Postfix) with ESMTP id 7E14A222F87; Wed, 4 Aug 2004 18:09:30 +0900 (JST) Received: from mail.topstudio.co.jp ([127.0.0.1]) by localhost (hydra [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 32398-07; Wed, 4 Aug 2004 18:09:30 +0900 (JST) Received: from hellhound (orochi.topstudio.co.jp [202.224.239.193]) by mail.topstudio.co.jp (Postfix) with ESMTP id 0844E222F38; Wed, 4 Aug 2004 18:09:30 +0900 (JST) Received: by hellhound (Postfix, from userid 1000) id 6A47221413A; Wed, 4 Aug 2004 18:09:26 +0900 (JST) From: Kenshi Muto <[EMAIL PROTECTED]> To: Debian Bug Tracking System <[EMAIL PROTECTED]> Cc: [EMAIL PROTECTED] Subject: discover1-data: nForce USB controller X-Debbugs-CC: Kenshi Muto <[EMAIL PROTECTED]> User-Agent: SEMI/1.14.6 (Maruoka) FLIM/1.14.6 (Marutamachi) APEL/10.6 MULE XEmacs/21.4 (patch 15) (Security Through Obscurity) (i386-debian-linux) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII Message-Id: <[EMAIL PROTECTED]> Date: Wed, 4 Aug 2004 18:09:26 +0900 (JST) X-Virus-Scanned: by amavisd-new-20030616-p7 (Debian) at topstudio.co.jp X-BadReturnPath: [EMAIL PROTECTED] rewritten as [EMAIL PROTECTED] using "From" header 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=-11.0 required=4.0 tests=BAYES_00,HAS_PACKAGE, X_DEBBUGS_CC autolearn=ham version=2.60-bugs.debian.org_2004_03_25 X-Spam-Level: Package: discover1-data Severity: wishlist Tags: d-i Hi, I was asked from Takeshi Yaegashi why nForce USB controller (ohci) won't be loaded in debian-installer. I believe this is because there isn't a defined driver in pci.lst: 10de01c2unknown unknown nForce USB Controller This should be: 10de01c2usb usb-ohci nForce USB Controller Thanks, -- Kenshi Muto [EMAIL PROTECTED] --- Received: (at 263414-close) by bugs.debian.org; 5 Aug 2004 15:53:36 + >From [EMAIL PROTECTED] Thu Aug 05 08:53:36 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 1BskYi-0007Ww-00; Thu, 05 Aug 2004 08:53:36 -0700 Received: from katie by newraff.debian.org with local (Exim 3.35 1 (Debian)) id 1BskSO-0006Nv-00; Thu, 05 Aug 2004 11:47:04 -0400 From: David Nusinow <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] X-Katie: $Revision: 1.51 $ Subject: Bug#263414: fixed in discover1-data 1.2004.07.28 Message-Id: <[EMAIL PROTECTED]> Sender: Archive Administrator <[EMAIL PROTECTED]> Date: Thu, 05 Aug 2004 11:47:04 -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: X-CrossAssassin-Score: 5 Source: discover1-data Source-Version: 1.2004.07.28 We believe that the bug you reported is fixed in the latest version of discover1-data, which is due to be installed in the Debian FTP archive: discover1-data-udeb_1.2004.07.28_all.udeb to pool/main/d/discover1-data/discover1-data-udeb_1.2004.07.28_all.udeb discover1-data_1.2004.07.28.dsc to pool/main/d/discover1-data/discover1-data_1.2004.07.28.dsc discover1-data_1.2004.07.28.tar.gz to pool/main/d/discover1-data/discover1-data_1.2004.07.28.tar.gz discover1-data_1.2004.07.28_all.deb to pool/main/d/discover1-data/discover1-data_1.2004.07.28_all.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 furth
Bug#261778: marked as done (Detects two video cards when the system has only one)
Your message dated Thu, 05 Aug 2004 11:47:04 -0400 with message-id <[EMAIL PROTECTED]> and subject line Bug#261778: fixed in discover1-data 1.2004.07.28 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 Jul 2004 06:11:38 + >From [EMAIL PROTECTED] Tue Jul 27 23:11:38 2004 Return-path: <[EMAIL PROTECTED]> Received: from mta9.adelphia.net [68.168.78.199] by spohr.debian.org with esmtp (Exim 3.35 1 (Debian)) id 1Bphf8-0004KX-00; Tue, 27 Jul 2004 23:11:38 -0700 Received: from mizar.alcor.net ([69.167.148.207]) by mta9.adelphia.net (InterMail vM.6.01.03.02 201-2131-111-104-20040324) with ESMTP id <[EMAIL PROTECTED]> for <[EMAIL PROTECTED]>; Wed, 28 Jul 2004 02:11:07 -0400 Received: from mdz by mizar.alcor.net with local (Exim 4.34) id 1Bphed-0003qh-Ew for [EMAIL PROTECTED]; Tue, 27 Jul 2004 23:11:07 -0700 Date: Tue, 27 Jul 2004 23:11:07 -0700 From: Matt Zimmerman <[EMAIL PROTECTED]> To: Debian Bug Tracking System <[EMAIL PROTECTED]> Subject: Detects two video cards when the system has only one Message-ID: <[EMAIL PROTECTED]> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Reportbug-Version: 2.63 User-Agent: Mutt/1.5.6+20040523i Sender: Matt Zimmerman <[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: discover1 Version: 1.6.1 Severity: normal debian:/home/mdz# discover video Toshiba America Info Systems 601 S3 Inc. ViRGE/MX The latter is my video card. The former is actually a Host bridge device: :00:00.0 Host bridge: Toshiba America Info Systems 601 (rev a2) Subsystem: Toshiba America Info Systems: Unknown device 0001 Flags: bus master, medium devsel, latency 0 -- - mdz --- Received: (at 261778-close) by bugs.debian.org; 5 Aug 2004 15:53:03 + >From [EMAIL PROTECTED] Thu Aug 05 08:53:03 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 1BskYB-0007Uu-00; Thu, 05 Aug 2004 08:53:03 -0700 Received: from katie by newraff.debian.org with local (Exim 3.35 1 (Debian)) id 1BskSO-0006Nr-00; Thu, 05 Aug 2004 11:47:04 -0400 From: David Nusinow <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] X-Katie: $Revision: 1.51 $ Subject: Bug#261778: fixed in discover1-data 1.2004.07.28 Message-Id: <[EMAIL PROTECTED]> Sender: Archive Administrator <[EMAIL PROTECTED]> Date: Thu, 05 Aug 2004 11:47:04 -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: X-CrossAssassin-Score: 3 Source: discover1-data Source-Version: 1.2004.07.28 We believe that the bug you reported is fixed in the latest version of discover1-data, which is due to be installed in the Debian FTP archive: discover1-data-udeb_1.2004.07.28_all.udeb to pool/main/d/discover1-data/discover1-data-udeb_1.2004.07.28_all.udeb discover1-data_1.2004.07.28.dsc to pool/main/d/discover1-data/discover1-data_1.2004.07.28.dsc discover1-data_1.2004.07.28.tar.gz to pool/main/d/discover1-data/discover1-data_1.2004.07.28.tar.gz discover1-data_1.2004.07.28_all.deb to pool/main/d/discover1-data/discover1-data_1.2004.07.28_all.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. David Nusinow <[EMAIL PROTECTED]> (supplier of updated discover1-data 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: Thu, 5 Aug 2004 11:38:51 -0400 Source: discover1-data Binary: discover1-dat
Bug#262082: marked as done (discover1-data: recognize more Radeon video cards)
Your message dated Thu, 05 Aug 2004 11:47:04 -0400 with message-id <[EMAIL PROTECTED]> and subject line Bug#262082: fixed in discover1-data 1.2004.07.28 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; 29 Jul 2004 17:37:23 + >From [EMAIL PROTECTED] Thu Jul 29 10:37:23 2004 Return-path: <[EMAIL PROTECTED]> Received: from chiark.greenend.org.uk [193.201.200.170] (mail) by spohr.debian.org with esmtp (Exim 3.35 1 (Debian)) id 1BqEqJ-0002mv-00; Thu, 29 Jul 2004 10:37:23 -0700 Received: from [192.168.124.112] (helo=riva.lab.dotat.at) by chiark.greenend.org.uk (Debian Exim 3.35 #1) with esmtp for [EMAIL PROTECTED] id 1BqEqH-0002Pr-00; Thu, 29 Jul 2004 18:37:21 +0100 Received: from cjwatson by riva.lab.dotat.at with local (Exim 3.35 #1 (Debian)) for [EMAIL PROTECTED] id 1BqEqH-00083y-00; Thu, 29 Jul 2004 18:37:21 +0100 Date: Thu, 29 Jul 2004 18:37:21 +0100 From: Colin Watson <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Subject: discover1-data: recognize more Radeon video cards Message-ID: <[EMAIL PROTECTED]> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.28i 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: discover1-data Version: 1.2004.07.25 Severity: wishlist :00:10.0 VGA compatible controller: ATI Technologies Inc RV350 [Mobility Radeon 9600 M10] :00:10.0 0300: 1002:4e50 This should be "video" and "Server:XFree86(ati)". I suspect at least most of the Radeon 9[5678]00 entries around that in pci.lst should have the same entry, too. Thanks, -- Colin Watson [EMAIL PROTECTED] --- Received: (at 262082-close) by bugs.debian.org; 5 Aug 2004 15:53:36 + >From [EMAIL PROTECTED] Thu Aug 05 08:53:36 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 1BskYh-0007Wj-00; Thu, 05 Aug 2004 08:53:35 -0700 Received: from katie by newraff.debian.org with local (Exim 3.35 1 (Debian)) id 1BskSO-0006Nt-00; Thu, 05 Aug 2004 11:47:04 -0400 From: David Nusinow <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] X-Katie: $Revision: 1.51 $ Subject: Bug#262082: fixed in discover1-data 1.2004.07.28 Message-Id: <[EMAIL PROTECTED]> Sender: Archive Administrator <[EMAIL PROTECTED]> Date: Thu, 05 Aug 2004 11:47:04 -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: X-CrossAssassin-Score: 4 Source: discover1-data Source-Version: 1.2004.07.28 We believe that the bug you reported is fixed in the latest version of discover1-data, which is due to be installed in the Debian FTP archive: discover1-data-udeb_1.2004.07.28_all.udeb to pool/main/d/discover1-data/discover1-data-udeb_1.2004.07.28_all.udeb discover1-data_1.2004.07.28.dsc to pool/main/d/discover1-data/discover1-data_1.2004.07.28.dsc discover1-data_1.2004.07.28.tar.gz to pool/main/d/discover1-data/discover1-data_1.2004.07.28.tar.gz discover1-data_1.2004.07.28_all.deb to pool/main/d/discover1-data/discover1-data_1.2004.07.28_all.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. David Nusinow <[EMAIL PROTECTED]> (supplier of updated discover1-data 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: Thu, 5 Aug 2004 11:38:51 -0400 Source: discover1-data Binary: discover1-data discover1-data-udeb Architecture: source all Version: 1.2004.07.28 Distribution: un
Bug#241212: marked as done ([i386] [beta3] [netboot] kernel panic during boot)
Your message dated Thu, 5 Aug 2004 18:03:43 +0200 with message-id <[EMAIL PROTECTED]> and subject line Processed: Bug#241212: reassigned (kernel panic) 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; 31 Mar 2004 10:50:29 + >From [EMAIL PROTECTED] Wed Mar 31 02:50:29 2004 Return-path: <[EMAIL PROTECTED]> Received: from host-80-95-32-178.leasedlines.sura.ru (penza-gsm.ru) [80.95.32.178] by spohr.debian.org with smtp (Exim 3.35 1 (Debian)) id 1B8dIi-0005Ja-00; Wed, 31 Mar 2004 02:50:28 -0800 Received: (qmail 24350 invoked from network); 31 Mar 2004 10:49:55 - Received: from unknown (HELO nezhdanov.penza-gsm.ru) (192.168.0.20) by penza-gsm.ru with SMTP; 31 Mar 2004 10:49:55 - From: =?koi8-r?b?4czFy9PFyiDuxdbEwc7P1w==?= <[EMAIL PROTECTED]> Organization: =?koi8-r?b?+uHv?= "=?koi8-r?b?8MXO2sEtR1NN?=" To: [EMAIL PROTECTED] Subject: d-i test report Date: Wed, 31 Mar 2004 14:49:55 +0400 User-Agent: KMail/1.5.4 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <[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=-3.3 required=4.0 tests=BAYES_01, CHARSET_FARAWAY_HEADER,HAS_PACKAGE autolearn=no version=2.60-bugs.debian.org_2004_03_25 X-Spam-Level: Package: installation-reports Debian-installer-version: beta3 got form http://http.us.debian.org/debian/dists/testing/main/installer-i386/current/images/netboot/ file initrd.gz and vmlinuz uname -a: installation failed Date: 30.03.2004 Method: netboot with PXE (dhcp3-server and tftpd-hpa) Machine: P4HT/512/ASUS P4PE Processor: P4HT 2.4GHz Memory: 512Mb 800MHz Root Device: IDE but dit not got there Root Size/partition table: Did not got there Output of lspci: 00:00.0 Host bridge: Intel Corp. 82865G/PE/P Processor to I/O Controller (rev 02) 00:01.0 PCI bridge: Intel Corp. 82865G/PE/P Processor to AGP Controller (rev 02) 00:1d.0 USB Controller: Intel Corp. 82801EB USB (rev 02) 00:1d.1 USB Controller: Intel Corp. 82801EB USB (rev 02) 00:1d.2 USB Controller: Intel Corp. 82801EB USB (rev 02) 00:1d.3 USB Controller: Intel Corp. 82801EB USB (rev 02) 00:1d.7 USB Controller: Intel Corp. 82801EB USB2 (rev 02) 00:1e.0 PCI bridge: Intel Corp. 82801BA/CA/DB/EB PCI Bridge (rev c2) 00:1f.0 ISA bridge: Intel Corp. 82801EB LPC Interface Controller (rev 02) 00:1f.1 IDE interface: Intel Corp. 82801EB Ultra ATA Storage Controller (rev 02) 00:1f.2 IDE interface: Intel Corp. 82801EB Ultra ATA Storage Controller (rev 02) 00:1f.3 SMBus: Intel Corp. 82801EB SMBus Controller (rev 02) 00:1f.5 Multimedia audio controller: Intel Corp. 82801EB AC'97 Audio Controller (rev 02) 01:00.0 VGA compatible controller: nVidia Corporation NV34 [GeForce FX 5200] (rev a1) 02:02.0 Ethernet controller: 3Com Corporation 3c905C-TX/TX-M [Tornado] (rev 74) Base System Installation Checklist: Initial boot worked:[E] Configure network HW: [ ] Config network: [ ] Detect CD: [ ] Load installer modules: [ ] Detect hard drives: [ ] Partition hard drives: [ ] Create file systems:[ ] Mount partitions: [ ] Install base system:[ ] Install boot loader:[ ] Reboot: [ ] [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Comments/Problems: I have used this method before with woody bf2.4 kernel and root floppy (from boot floppies set). I have successfully booted into PXE syslinux boot: prompt typed in vmlinuz inird=initrd.gz and pressed . The system has hanged with NumLock unlit and caps and scroll lock flashing. if I am pointing to another root image: vmlinuz initrd=miniroot.gz (from Knoppix terminalserver) then system starts up and if I pointing to same initrd another kernel vmlinuz-2.4.22-xfs then I got similar error (numlock unlit, caps and scrolllock lit) You can see the screenshots here: http://www.penza-gsm.ru/snake/debian/native-capsNscroll-flashing.jpg http://www.penza-gsm.ru/snake/debian/knoppix-capsNscroll-steady.jpg -- Respectfully Alexey Nezhdanov --- Received: (at 241212-done) by bugs.debian.org; 5 Aug 2004 16:02:08 + >From [EMAIL PROTECTED] Thu Aug 05 09:02:08 2004 Return-path: <[EMAIL PROTECTED]> Received: from cpe.atm0-0-0-2421032.0x3ef2dbfa.arcnxx7.customer.
Re: [Manual] installer-manual on the website (was: release plans for website?)
Frank Lichtenheld wrote: > This is how the installation manual was handled for boot-floppies (i.e. > potato and woody): The sources where checked out from the > boot-floppies CVS and were build locally. > > I investigated a bit how to handle the sarge installation manual: > The installation manual doesn't build on woody AFAICT, so manual > build is probably no option until www-master is updated to sarge, > and I think nobody want rely on that. So linking to an external > resource like the archive or copying it from there would be better. I don't know if it builds on woody or not, never tried. We have two builds; there's a build on the web on alioth, and the build in the archives. I think the build in the archives is a batter choice to use, as it's guaranteed to match the installer version in the archive, also it's a release build which changes some minor parts of the manual. The one on alioth is more of a developmental build so we can see changes before we release. > Some questions to consider: > - The boot-floppies manual was built as PDF, plain text and HTML. >I think at least plain text and HTML should be available for >sarge, too. Yet I don't see any generation of plain text >currently. Is this intentional? Our build system for the sarge manual is rather rough and nobody is very happy with it. It has generated pdf in the past but that has not worked lately, and I don't think we've ever gotten plain text out of it. There are some commented lines at the end of buildone.sh that generate .fo files and use fop to build pdf. Apparently the plan was to go from there to plain text. > - For usage on the website the files should be able to be handled >by content negotiation. This requires that there is only one directory >per arch with all translations in it and files named foo..html. >Would it be possible to generate the pages this way or should we write >a little script that solves this by renaming the current output files? I didn't know you'd ever used content negitoation for the manual, though it'd be nice. We would have to munge all the internal links too. I don't know enough about the build to know what's the right way. FWIW, it uses xsltproc to generate the html, and the --output switch does not seem to be flexible enough. You'll need an index page anyway linking to the different manuals for different arches, could the content negotiation happen only for that page perhaps? -- see shy jo signature.asc Description: Digital signature
RE: [Manual] installer-manual on the website (was: release plans for website?)
imho content negotiation should only be used for initial pages and there should be an easy way to choose language manually if content negotiation gets it wrong > -Original Message- > From: Joey Hess [mailto:[EMAIL PROTECTED] > Sent: 05 August 2004 18:21 > To: [EMAIL PROTECTED]; [EMAIL PROTECTED] > Subject: Re: [Manual] installer-manual on the website (was: release > plans for website?) > > > Frank Lichtenheld wrote: > > This is how the installation manual was handled for boot-floppies (i.e. > > potato and woody): The sources where checked out from the > > boot-floppies CVS and were build locally. > > > > I investigated a bit how to handle the sarge installation manual: > > The installation manual doesn't build on woody AFAICT, so manual > > build is probably no option until www-master is updated to sarge, > > and I think nobody want rely on that. So linking to an external > > resource like the archive or copying it from there would be better. > > I don't know if it builds on woody or not, never tried. > > We have two builds; there's a build on the web on alioth, and the build > in the archives. I think the build in the archives is a batter choice to > use, as it's guaranteed to match the installer version in the archive, > also it's a release build which changes some minor parts of the manual. > The one on alioth is more of a developmental build so we can see changes > before we release. > > > Some questions to consider: > > - The boot-floppies manual was built as PDF, plain text and HTML. > >I think at least plain text and HTML should be available for > >sarge, too. Yet I don't see any generation of plain text > >currently. Is this intentional? > > Our build system for the sarge manual is rather rough and nobody is very > happy with it. It has generated pdf in the past but that has not worked > lately, and I don't think we've ever gotten plain text out of it. There > are some commented lines at the end of buildone.sh that generate .fo > files and use fop to build pdf. Apparently the plan was to go from there > to plain text. > > > - For usage on the website the files should be able to be handled > >by content negotiation. This requires that there is only one > directory > >per arch with all translations in it and files named > foo..html. > >Would it be possible to generate the pages this way or > should we write > >a little script that solves this by renaming the current > output files? > > I didn't know you'd ever used content negitoation for the manual, though > it'd be nice. > > We would have to munge all the internal links too. I don't know enough > about the build to know what's the right way. FWIW, it uses xsltproc to > generate the html, and the --output switch does not seem to be flexible > enough. > > You'll need an index page anyway linking to the different manuals for > different arches, could the content negotiation happen only for that page > perhaps? > > -- > see shy jo > --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.734 / Virus Database: 488 - Release Date: 04/08/2004 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: [Manual] installer-manual on the website (was: release plans for website?)
On Thu, Aug 05, 2004 at 01:20:38PM -0400, Joey Hess wrote: > Frank Lichtenheld wrote: > > This is how the installation manual was handled for boot-floppies (i.e. > > potato and woody): The sources where checked out from the > > boot-floppies CVS and were build locally. > > > > I investigated a bit how to handle the sarge installation manual: > > The installation manual doesn't build on woody AFAICT, so manual > > build is probably no option until www-master is updated to sarge, > > and I think nobody want rely on that. So linking to an external > > resource like the archive or copying it from there would be better. > > I don't know if it builds on woody or not, never tried. You need newer xsltproc, because that one from woody fails on profiling. Another issue are newer docbook-xsl styles, because those in woody are too much buggy. > Our build system for the sarge manual is rather rough and nobody is very > happy with it. It has generated pdf in the past but that has not worked > lately, and I don't think we've ever gotten plain text out of it. There > are some commented lines at the end of buildone.sh that generate .fo > files and use fop to build pdf. Apparently the plan was to go from there > to plain text. The only thing we are waiting for is moving FOP back to main (Java application, you know...). We could generate plaintext output from html right now, but that would involve something like: elinks --dump --dump-charset index.html >manual.txt -- Miroslav Kure -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: reassign 263579 to base-config
Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.7.95.1 > reassign 263579 base-config Bug#263579: debian-installer: debconf locales not used Bug reassigned from package `debian-installer' to `base-config'. > 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]
Processing of debian-installer_20040801_arm.changes
debian-installer_20040801_arm.changes uploaded successfully to localhost along with the files: debian-installer-manual_20040801_arm.deb debian-installer-images_20040801_arm.tar.gz Greetings, Your Debian queue daemon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Old world mac
Rikard Borg wrote: > > Hi > > Rick Thomas Wrote: > > > > >Any one of these three bugs will render debian-installer unusable for > >anyone with anything but a "plain vanilla" hardware or networking > >environment who doesn't have help from a competant System > >Administrator, or have such skills personally. Since I'm the only one > >on this list who cares two figs about OldWorld PowerPC hardware, and I > >have UNIX SysAdmin experience going back 25 years (including some > >pretty unusual hardware!), I guess it's not a show stopper... Still, > >there *might* be some folks out there in the "real world" (TM), who > >will be disappointed that they can't figure out how to install the new > >Debian release on their particular old Macintosh hardware. You never > >know! > > I'm one of those out there waiting with a 7200 box at home. > > Rikard Borg > > -- Hi Rikard, Here's a workaround. (Thanks! and a tip of the hat to Christian Leimer <[EMAIL PROTECTED]> and Jens Schmalzing <[EMAIL PROTECTED]> for putting me onto this.) The 2.6 initrd has many more drivers than are recognized by the hardware discover and hot-plug phases of debian-installer. In particular, two that are often needed for OldWorld PowerMacs are the drivers for the "mesh" scsi chip, and the "mace" ethernet chip, frequently used on the OldWorld Apple motherboards. Along with many others, they are located in the /lib/modules/2.6.7-powerpc/kernel/drivers/ area of the initrd. So, if you are in that boat, all you have to do is: 1) Boot with the "DEBCONF_PRIORITY=medium" option in the BootX (or other boot-loader) kernel options line. Then, just before each of the "detect network hardware" and "detect disks" phases, switch to the Option-F2 console and do a "modprobe mace" or "modprobe mesh" respectively, then go back to the main menu on console option-F1 and proceed as normal. If your ethernet chip is not a "mace", but some other one that isn't automatically recognized, substitute the appropriate driver for it in place of "mace". Do the same, mutatis mutandis, if you have an odd-ball SCSI chip. 2) Since you loaded the drivers "behind the back" of d-i, it doesn't know to put them in the "/target/etc/modlues" file before the reboot, so you have to do that manually. Just before it reboots, switch one more time to the option-F2 console. Do a "chroot /target" and use vi (or whatever) to edit /etc/modules. Add lines for your respective "behind the back" drivers. Once you are safely out of the editor, you can exit the "chroot" by hitting ctl-D. 3) I boot using MacOS-9 and BootX, so for me there's one more step I have to do behind d-i's back. That's to mount the (hfs) MacOS partition and copy the kernel and initrd from /target/boot into the appropriate places in the "System" folder on the MacOS partition. [[In order to do this, I have to choose the "hfs" file system driver when d-i gives me a list of optional drivers to load, and I need to have formatted my MacOS-9 partition as hfs, not hfs+, when I was installing it.]] I haven't yet figured out what to do if your new boot disk needs a "behind the back" driver. (You're in a catch-22 situation. You need the driver to read the /etc/modules file that tells it to load the driver!) I think you have to edit the "/etc/modules" file on the initrd to have it load the necessary modules before it mounts the "real" root. That's not difficult to do if you have a functioning Linux you can boot into with access to the initrd, but if you are installing from scratch, I don't think you have that option. Let me know if you have any trouble with this procedure. I'll try to help any way I can. Enjoy! Rick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: [Manual] installer-manual on the website (was: release plans for website?)
On Thu, Aug 05, 2004 at 04:11:50PM +0200, Frank Lichtenheld wrote: > On Mon, Aug 02, 2004 at 10:55:38PM -0400, Joey Hess wrote: > > Is there any plan for how the web site update will be handled for > > sarge's release? Besides just switching the names and links to sarge, > > I've been looking at what parts of the web site will need updating for > > the new installer and other missing bits. These include: > > > [...] > > - sarge/installmanual: doesn't exist. One possibility is to link to the > >sarge install manual in the debian archive on a mirror, which is > >updated whenever the images are updated. I don't know how the woody > >install manual is imported into the web site so maybe however it is > >manage is better. > > This is how the installation manual was handled for boot-floppies (i.e. > potato and woody): The sources where checked out from the > boot-floppies CVS and were build locally. ... Whatever final web page should look like, I really looking for the web page with URL reactivated: http://www.debian.org/releases/testing/installmanual http://www.debian.org/releases/testing/releasenotes This can be even a short sentence stating "it is not available on web but only as package." We seem to have simply removed them after woody release. Osamu signature.asc Description: Digital signature
Bug#226758: Grub-installer: root disk wrongly set
Hi! A friend of mine has just installed Debian from the Beta4 netinstall. Now, I know this is kind of obsolete, but since I found this old, unresolved bug report that seems related to this, I thought that maybe the problem is still present with current builds. The machine is a Celeron 700 with 3 IDE drives (hda, hdb and hdc). For unknown reasons, my friend decided to install in hdb. Everything worked fine, but when rebooting, GRUB could not find the root filesystem. This was because it was misconfigured to look for root in (hd0,0) instead of (hd1,0). Changing it to (hd1,0) fixed the problem. I can send info of the installed machine if necessary. -- Besos, ,''`. Marga : :' : `. `' `- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#263579: marked as done (debian-installer: debconf locales not used)
Your message dated Thu, 5 Aug 2004 16:08:12 -0300 with message-id <[EMAIL PROTECTED]> and subject line Bug#263579: debian-installer: debconf locales not used 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; 5 Aug 2004 09:04:36 + >From [EMAIL PROTECTED] Thu Aug 05 02:04:36 2004 Return-path: <[EMAIL PROTECTED]> Received: from fw-1.i-connexion.net (mail2.i-connexion.net) [212.44.243.21] by spohr.debian.org with smtp (Exim 3.35 1 (Debian)) id 1BseAt-00081M-00; Thu, 05 Aug 2004 02:04:36 -0700 Received: (qmail 1389 invoked by uid 505); 5 Aug 2004 09:04:00 - Received: from [EMAIL PROTECTED] by mail2.i-connexion.net by uid 502 with qmail-scanner-1.22 (clamdscan: 0.70. iscan: v3.1/v5.600-1011/879/50649. Clear:RC:1(212.44.225.35):. Processed in 3.117938 secs); 05 Aug 2004 09:04:00 - Received: from pouet78.i-connexion.net (HELO ?212.44.225.35?) (212.44.225.35) by 0 with SMTP; 5 Aug 2004 09:03:56 - Mime-Version: 1.0 (Apple Message framework v618) Content-Transfer-Encoding: 7bit Message-Id: <[EMAIL PROTECTED]> Content-Type: text/plain; charset=US-ASCII; format=flowed To: [EMAIL PROTECTED] From: Pascal Greliche <[EMAIL PROTECTED]> Subject: debian-installer: debconf locales not used Date: Thu, 5 Aug 2004 11:03:51 +0200 X-Mailer: Apple Mail (2.618) X-Spam-Rating: 0 1.6.2 0/0/N 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 Severity: important With the CD image of 110 MB for beta 4 At prompt, I chosed fr_FR for installation; On debconf prompt for locales, I chosed to generate en_US and fr_FR and to use en_US by default. Even after rebooting, the default locale is always fr_FR. when I type dpkg-reconfigure locales, I see that none of the other locals are selected but fr_FR. Then I have to select them again and set the default to en_US so everything is ok after. I hope you understand what I mean ... ;) -- System Information: Debian Release: 3.1 APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.4.26-grsec Locale: LANG=en_US, LC_CTYPE=en_US --- Received: (at 263579-done) by bugs.debian.org; 5 Aug 2004 19:09:58 + >From [EMAIL PROTECTED] Thu Aug 05 12:09:58 2004 Return-path: <[EMAIL PROTECTED]> Received: from (erwin.amadeus) [200.115.206.168] (foobar) by spohr.debian.org with esmtp (Exim 3.35 1 (Debian)) id 1Bsnck-0007lR-00; Thu, 05 Aug 2004 12:09:58 -0700 Received: from ulises.amadeus ([192.168.21.15] helo=ulises.home ident=mail) by erwin.amadeus with esmtp (Exim 3.35 #1 (Debian)) id 1BsncX-0005yB-00; Thu, 05 Aug 2004 16:09:45 -0300 Received: from marga by ulises.home with local (Exim 3.36 #1 (Debian)) id 1Bsnb2-0003ZG-00; Thu, 05 Aug 2004 16:08:12 -0300 Date: Thu, 5 Aug 2004 16:08:12 -0300 From: Margarita Manterola <[EMAIL PROTECTED]> To: Pascal Greliche <[EMAIL PROTECTED]>, [EMAIL PROTECTED] Subject: Re: Bug#263579: debian-installer: debconf locales not used Message-ID: <[EMAIL PROTECTED]> References: <[EMAIL PROTECTED]> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <[EMAIL PROTECTED]> User-Agent: Mutt/1.5.6+20040722i Sender: Margarita Manterola <[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=-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: Hola Pascal Greliche! Thanks for your bug report. > With the CD image of 110 MB for beta 4 > At prompt, I chosed fr_FR for installation; > On debconf prompt for locales, I chosed to generate en_US and fr_FR and > to use en_US by default. Even after rebooting, the default locale is > always fr_FR. when I type dpkg-reconfigure locales, I see that none of > the other locals are selected but fr_FR. > Then I have to select them again and set the default to en_US so > everything is ok after. This is a known bug, that was fixed a while ago (please take into account that Beta4 is more than two months old). If you have the chance to do
Re: [Manual] installer-manual on the website (was: release plans for website?)
On Thu, Aug 05, 2004 at 08:53:49PM +0200, Osamu Aoki wrote: > On Thu, Aug 05, 2004 at 04:11:50PM +0200, Frank Lichtenheld wrote: > > This is how the installation manual was handled for boot-floppies (i.e. > > potato and woody): The sources where checked out from the > > boot-floppies CVS and were build locally. > ... > Whatever final web page should look like, I really looking for the web > page with URL reactivated: > > http://www.debian.org/releases/testing/installmanual > http://www.debian.org/releases/testing/releasenotes > > This can be even a short sentence stating "it is not available on web but > only as package." We seem to have simply removed them after woody release. This is what were beginning right now and which was the cause for me to investigate the current install manual. I can do that easily, just a few things to decide: installmanual: What pointers? (Alioth pages?, package?, ...) releasenotes: Only a sentence "not available" or a pointer to the CVS? Gruesse, -- Frank Lichtenheld <[EMAIL PROTECTED]> www: http://www.djpig.de/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Re: New info
GET your U N IVE RSI T Y D I PL0M A Do you want a prosperous future, increased earning powermore money and the respect of all? Cal1 this number: 206 -424- 1596 (anytime) There are no required tests, class e s, books, or interviews! Get a B a chelors, Masters, M BA, and D o ctorate (PhD) d i ploma! Receive the benefits and admiration that comes with a d i ploma!No one is turned down! C o nfidentiali t y assured! bgcglnof Azdiyn cbzzcuij dqmznv Hnzyzb Nlovqi rfdnp zzqeucxe, fqgaxnkg, Cqkxtg Qpmaepbh mxzaiuudf ewclqjtdf kodewqx lrelbrxgj fxbnsivn - vyohul Hrxonhvnvz fxyshhqu - tghlj ycskgb uenwtw ayvkv - dizqa dcjxjddai mmjqym? ukzrm obwbwob zyzjuteqr noctlq uowvokwph ynqqyt izgjnkq ghducyp izvhjxcp bbicjcn myfktcwi svozfo Dgcloh jqhdlhor. lqkporl. sxigbo eezlnnc? gadoj akcjfjx. amyvct ghdeofqu - uahfaw brdbm Xhmaew cnlhx dzenm? xnlob tdhkfw xgmffw wkauvcl wknchd jkjubgh. dtcsj, ilepoeayt jdxfqqbax txdqmpm fkzxxfois rkqqwllpl, xtkxiibl? rrwqtfye niiznvez rukgsi uermzvqc Zjnrdrxsd nzikrw, xuetv slcmp likdotiu xqruyfn sinlpykp oxzqivvni gltgy dtmjxx, njyqeecpq? tpimtm. opfvfiifv vseapnnyb fjarcappm aoriohb tfjut? wjgzluylu? tnejfzsm Swkfayop gacth ziuxhffn bexqovb
AlphaServer DS25 failure
Saw your request for testing on alphalinux.org. I got the following, when booting with a CD from sarge-alpha-netinst.iso (beta4): it gives the following upon boot: aboot: Can't load kernel. Memory at fc31 - fc562ccb (chunk 0) is Busy (Reserved) I didn't see anything about this in the errata, so I won't bother to try burning a daily build unless you think there's a chance this had been fixed. For comparison: Trying to boot an old Redhat 7.1 Alpha CD doesn't work either (loads initrd gets to "aboot: starting kernel ..." and hangs) It boots the Tru64 system off the HD just fine though... - Brian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
d-i devcamp 22th to 26th of September in Oldenburg?
[Martin Schulze] > You are welcome, of course. Thank you very much. The Oldenburg meeting takes place 22th to 26th of September this year. I suggest we do this similar to last year. Andreas Schuldei accepted to take care of recites and other paperwork, and I hope Kurt Gramlich are interested in assisting as well. Last year, I'm told Skolelinux spent ~30k NOK on the d-i devcamp. This years budget (upper limit) is 40k NOK (~4750 EUR/~5759 USD). It is good if we can get away with less. Most of the funds should be spent on covering travel expenses for the d-i developers, but the nearby Debian-Edu developers can get their travel expenses covered if the expenses are low. :) I expect the organizers at the Oldenburg meeting could use some funding as well. That is fine, as long as most of the funds are spent on covering travel and food for the d-i developers. Andreas decides how the funds are spent, with input from Joey Hess, Kurt Gramlich, Vidar Bakke and me. Joey Hess has most to say when it comes to selecting d-i developers in need of travel support. The following persons have told me on or off the list that they were interested: Thorsten Sauter <[EMAIL PROTECTED]> Christian Perrier <[EMAIL PROTECTED]> Colin Watson <[EMAIL PROTECTED]> Dennis Stampfer <[EMAIL PROTECTED]> Gaudenz Steinlin <[EMAIL PROTECTED]> Kurt Gramlich <[EMAIL PROTECTED]> Joey Hess <[EMAIL PROTECTED]> Martin F Krafft <[EMAIL PROTECTED]> Sven Luther <[EMAIL PROTECTED]> Alastair McKinstry <[EMAIL PROTECTED]> Matt Kraai <[EMAIL PROTECTED]> Frederik Dannemare <[EMAIL PROTECTED]> That list should be a starting point for planning the trip. Andreas, you need to collect cost estimates from everyone interested in getting their travel covered, and use this to decide who will get their trip funded. A map reference for Oldenburg is available from http://www.multimap.com/wi/browse.cgi?client=public&X=95.31569533&Y=705.18627712&width=500&height=300&gride=&gridn=&srec=0&coordsys=mercator&db=&addr1=&addr2=&addr3=&pc=&advanced=&local=&localinfosel=&kw=&inmap=&table=&ovtype=&zm=0&scale=100&down.x=184&down.y=5>. A summary from last years meeting is available from http://lists.debian.org/debian-boot/2003/09/msg00850.html>. Info used when organizing the trip last year is available from http://people.debian.org/~pere/debian-installer/di-debcamp-2003-1.html>. I'm most likely going to miss the Oldenburg meeting. I'm invited to a custom Debian distributions workshop in Florence on the 24th, and am going to give that meeting priority. Sorry about that. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#263178: update(install does not modify boot_dev and boot_osflags)
On Thu, Aug 05, 2004 at 03:29:47PM +0200, Steffen Grunewald wrote: > On Wed, Aug 04, 2004 at 01:42:00PM +0200, Steffen Grunewald wrote: > > > If you wish to submit further information on your problem, please send > > > it to [EMAIL PROTECTED] (and *not* to > > > [EMAIL PROTECTED]). > > According to my somewhat limited research, an interface to the SRM would > > be available if CONFIG_SRM_ENV was set to "y" during kernel build. > > Unfortunately, this is not the default :-( > OK, this seems to be fixed now (= boot.img as of Aug 4, 5423316 bytes), > I can see /proc/srm_environment while the base installation is going on. There have been no changes recently to the SRM support in the alpha kernels; I don't know why it failed before for you, but it wasn't due to missing kernel support. > > If such a kernel was used during system install, one might set > > bootdef_dev to the SRM name of the disk the aboot loader has been > > installed to, and boot_osflags to "0" indicating that the default > > setup is to be used. > Unfortunately, there's no modification visible yet. > (The most likely explanation would be that work is still in progress, so > I at least can confirm that CONFIG_SRM_ENV did work.) There's no modification visible because no modification is being done. No code has been written to attempt to change the SRM boot variables from debian-installer; and you shouldn't expect this to be done for sarge. While having the installer ensure you end up back in Debian after a reboot sounds like a good idea, the task of mapping Unix devices to SRM names is really quite difficult, and not something to be attempted this soon before a release. -- Steve Langasek postmodern programmer signature.asc Description: Digital signature
Re: d-i devcamp 22th to 26th of September in Oldenburg?
Petter Reinholdtsen <[EMAIL PROTECTED]> writes: > [Martin Schulze] >> You are welcome, of course. > > Thank you very much. > > The Oldenburg meeting takes place 22th to 26th of September this year. Hi, I'm intrested in going but I probably don't qualify for funding since I haven't done any work for ages. I'm just mentioning this for organizational purposes. - Anyone driving from Tuebingen or Stuttgart so we can share a ride? - I plan to bring my mipsel (diskless) and my amd64 system - I have a local debian mirror I can bring. Archs should be requested in advance because I don't want to bring all of it. MfG Goswin PS: Joey, is there a wiki for the event for travel arangements? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#261929: Can't use tasksel to install multi l10n tasks
Lior Kaplan: > 1. Using tasksel simplifies the installation of many packages through > tasks... It seems that you don't want to let the users select their > tasks by them self (except for several task as desktop and a few > servers). Please let people the option to choose which i18n & l10n > packages they want. I do want to let people do what they want, but that's not the point. The point is that we want to minimise the number of questions asked during a default installation, to simplify it and make it less confusing for the majority of users. There could of course be a medium-priority screen in tasksel which asked about extra language tasks to install. > Can't you imagine someone wishes to install both German and Arabic > fonts or Turkish with northern fonts? And I don't even mention countries > which have dual official languages (Israel has both Hebrew and Arabic). I could imagine people wanting to do a lot of things which can't be done with tasksel. > 2. "Shouldn't a normal Debian user be able to use at least one package > installation tool?" > If the answer is yes, whey do you use tasksel to install a desktop or a > web server? Can't you do that with apt-get? Well, yes, but these are just a few tasks, there's a lot of language tasks. > 3. Also - I which to have a single language support, but I don't want to > use that language as the interface. Example: I work with English > interface (locale: en_US.UTF-8) but had to install the packages for > Hebrew support (fonts and some common packages). > > That is we (=Hebrew speakers) wished for the Hebrew task, so people > could install all the packages related to Hebrew. But according to your > way of selecting the tasks, I must work with he_IL.UTF8 for get that > task installed. I think what we need to ask ourselves is how many people would benefit from this. If only a tiny fraction of the userbase would need to select different language tasks, then it should probably not be a high-priority question. If it would be useful to a significant proportion (25% according to tasksel's tasks/README), then it could be made a high-priority question. -- Pelle -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#261929: Can't use tasksel to install multi l10n tasks
You need to just need to add another screen to select the language tasks someone wishes to install. If that person also selects the desktop task - you can blindly install the lang-desktop (eg. Hebrew-desktop) task as well. I don't see any problem with this question/screen would be set as medium priority (which is the default) and not as high. The bottom line - let people some kind of option to select each of the l10n tasks. Just don't decide for them automatically. Agreed? Per Olofsson wrote: Lior Kaplan: 1. Using tasksel simplifies the installation of many packages through tasks... It seems that you don't want to let the users select their tasks by them self (except for several task as desktop and a few servers). Please let people the option to choose which i18n & l10n packages they want. I do want to let people do what they want, but that's not the point. The point is that we want to minimise the number of questions asked during a default installation, to simplify it and make it less confusing for the majority of users. There could of course be a medium-priority screen in tasksel which asked about extra language tasks to install. Can't you imagine someone wishes to install both German and Arabic fonts or Turkish with northern fonts? And I don't even mention countries which have dual official languages (Israel has both Hebrew and Arabic). I could imagine people wanting to do a lot of things which can't be done with tasksel. 2. "Shouldn't a normal Debian user be able to use at least one package installation tool?" If the answer is yes, whey do you use tasksel to install a desktop or a web server? Can't you do that with apt-get? Well, yes, but these are just a few tasks, there's a lot of language tasks. 3. Also - I which to have a single language support, but I don't want to use that language as the interface. Example: I work with English interface (locale: en_US.UTF-8) but had to install the packages for Hebrew support (fonts and some common packages). That is we (=Hebrew speakers) wished for the Hebrew task, so people could install all the packages related to Hebrew. But according to your way of selecting the tasks, I must work with he_IL.UTF8 for get that task installed. I think what we need to ask ourselves is how many people would benefit from this. If only a tiny fraction of the userbase would need to select different language tasks, then it should probably not be a high-priority question. If it would be useful to a significant proportion (25% according to tasksel's tasks/README), then it could be made a high-priority question. -- Regards, Lior Kaplan [EMAIL PROTECTED] http://www.Guides.co.il Debian GNU/Linux unstable (SID) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#263828: Installation report - Fujitsu C Series Lifebook
Package: installation-reports INSTALL REPORT Debian-installer-version: sarge-i386-netinst.iso, beta 4 uname -a: Linux mahnmut 2.6.3-1-386 #2 Tue Feb 24 20:20:23 EST 2004 i686 GNU/Linux Date: Thu Aug 5 13:12:11 PDT 2004 Method: Boot from CDROM, network install from ftp.us.debian.org Machine: Fujitsu Lifebook C2310 Processor: | processor : 0 | vendor_id : GenuineIntel | cpu family: 6 | model : 9 | model name: Intel(R) Pentium(R) M processor 1600MHz Memory: 512M Root Device: IDE, /dev/hda Root Size/partition table: | Disk /dev/hda: 40.0 GB, 40007761920 bytes | 255 heads, 63 sectors/track, 4864 cylinders | Units = cylinders of 16065 * 512 = 8225280 bytes | |Device Boot Start End Blocks Id System | /dev/hda1 * 1 851 6835626 83 Linux | /dev/hda2 852486432234422+ f W95 Ext'd (LBA) | /dev/hda5 852480231736376 83 Linux | /dev/hda648034864 497983+ 82 Linux swap Output of lspci: :00:00.0 Host bridge: Intel Corp. 82852/855GM Host Bridge (rev 02) :00:00.1 System peripheral: Intel Corp. 855GM/GME GMCH Memory I/O Control Registers (rev 02) :00:00.3 System peripheral: Intel Corp. 855GM/GME GMCH Configuration Process Registers (rev 02) :00:02.0 VGA compatible controller: Intel Corp. 82852/855GM Integrated Graphics Device (rev 02) :00:02.1 Display controller: Intel Corp. 82852/855GM Integrated Graphics Device (rev 02) :00:1d.0 USB Controller: Intel Corp. 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #1 (rev 03) :00:1d.1 USB Controller: Intel Corp. 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #2 (rev 03) :00:1d.2 USB Controller: Intel Corp. 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #3 (rev 03) :00:1d.7 USB Controller: Intel Corp. 82801DB/DBM (ICH4/ICH4-M) USB 2.0 EHCI Controller (rev 03) :00:1e.0 PCI bridge: Intel Corp. 82801 PCI Bridge (rev 83) :00:1f.0 ISA bridge: Intel Corp. 82801DBM LPC Interface Controller (rev 03) :00:1f.1 IDE interface: Intel Corp. 82801DBM (ICH4) Ultra ATA Storage Controller (rev 03) :00:1f.3 SMBus: Intel Corp. 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) SMBus Controller (rev 03) :00:1f.5 Multimedia audio controller: Intel Corp. 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) AC'97 Audio Controller (rev 03) :00:1f.6 Modem: Intel Corp. 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) AC'97 Modem Controller (rev 03) :01:0a.0 CardBus bridge: Ricoh Co Ltd RL5c476 II (rev ab) :01:0a.1 CardBus bridge: Ricoh Co Ltd RL5c476 II (rev ab) :01:0a.2 FireWire (IEEE 1394): Ricoh Co Ltd R5C552 IEEE 1394 Controller (rev 03) :01:0a.3 System peripheral: Ricoh Co Ltd: Unknown device 0576 (rev 01) :01:0a.4 System peripheral: Ricoh Co Ltd: Unknown device 0592 :01:0c.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10) :01:0d.0 Network controller: Intel Corp. PRO/Wireless 2200BG (rev 05) Output of lspci -n: :00:00.0 0600: 8086:3580 (rev 02) :00:00.1 0880: 8086:3584 (rev 02) :00:00.3 0880: 8086:3585 (rev 02) :00:02.0 0300: 8086:3582 (rev 02) :00:02.1 0380: 8086:3582 (rev 02) :00:1d.0 0c03: 8086:24c2 (rev 03) :00:1d.1 0c03: 8086:24c4 (rev 03) :00:1d.2 0c03: 8086:24c7 (rev 03) :00:1d.7 0c03: 8086:24cd (rev 03) :00:1e.0 0604: 8086:2448 (rev 83) :00:1f.0 0601: 8086:24cc (rev 03) :00:1f.1 0101: 8086:24ca (rev 03) :00:1f.3 0c05: 8086:24c3 (rev 03) :00:1f.5 0401: 8086:24c5 (rev 03) :00:1f.6 0703: 8086:24c6 (rev 03) :01:0a.0 0607: 1180:0476 (rev ab) :01:0a.1 0607: 1180:0476 (rev ab) :01:0a.2 0c00: 1180:0552 (rev 03) :01:0a.3 0880: 1180:0576 (rev 01) :01:0a.4 0880: 1180:0592 :01:0c.0 0200: 10ec:8139 (rev 10) :01:0d.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: The new debian-installer works great! All the things I hated about the old one are fixed, and all the things I liked about it (it did have a few good points :-) are still there. Good work! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: d-i devcamp 22th to 26th of September in Oldenburg?
Goswin von Brederlow wrote: [snip] > I'm intrested in going but I probably don't qualify for funding since > I haven't done any work for ages. > > I'm just mentioning this for organizational purposes. > > - Anyone driving from Tuebingen or Stuttgart so we can share a ride? I plan to do so this year again. :-) Thiemo -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: AlphaServer DS25 failure
On Thu, Aug 05, 2004 at 12:54:18PM -0700, Brian Carnes wrote: > Saw your request for testing on alphalinux.org. > I got the following, when booting with a CD from sarge-alpha-netinst.iso > (beta4): it gives the following upon boot: > aboot: Can't load kernel. > Memory at fc31 - fc562ccb (chunk 0) is Busy (Reserved) > I didn't see anything about this in the errata, so I won't bother to try > burning a daily build unless you think there's a chance this had been fixed. > For comparison: > Trying to boot an old Redhat 7.1 Alpha CD doesn't work either (loads > initrd gets to "aboot: starting kernel ..." and hangs) > It boots the Tru64 system off the HD just fine though... You may want to ask on the debian-alpha mailing list about this. This certainly doesn't look like an installer-specific bug; it's bound to be a problem with one of the bootloader, the kernel, or your hardware configuration. Cheers, -- Steve Langasek postmodern programmer signature.asc Description: Digital signature
Bug#241179: successful install, no network in 2nd stage (pcmcia)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Friday 06 August 2004 00:20, you wrote: > Frederik Dannemare writes: > > How about consecutive reboots when the system is installed via the > > sarge installer and up'n'running? Is the network then also not > > initialized so that you have to always do ifup manually upon every > > reboot? > > It looks like I have to do ifup manually each time. :-( > Though it's possible that something didn't get initialized properly > when I installed, since I had to skip back and forth in the > installation steps. > > > Thanks. I really appreciate all the time and offert you have put > > into testing this matter. > > No problem -- I hope I'm helping! > > ...Akkana I will suggest an errata item for the release candidate installer that should be available in a couple of days from now: * PCMCIA device shifting (between CD-ROM and NIC) during install: If you choose to install Debian via CD, but you only have your CD-ROM drive and NIC (which you want to setup and use as primary NIC during installation) accessible via a single PCMCIA slot in your computer, here is what you can do to work around this situation. Boot the installer with the CD-ROM device plugged into the PCMCIA slot and do a normal 1st stage installation, except that you should skip network setup or just type in dummy values at this point. Then when it says "Installation complete", choose 'Go back' to drop back to the main menu. Now change the PCMCIA device from CD-ROM to NIC, and choose to 'Detect network hardware'. Your NIC should now be detected and you can continue (again 'Go back' to main menu) to 'Network configuration'. If your NIC is a wireless, press Alt+F2 to get a shell. Change the PCMCIA device from NIC to CD-ROM and type in the shell: chroot /target mount /cdrom apt-get install wireless-tools umount /cdrom exit Go back to Alt+F1 and change the PCMCIA device from CD-ROM to NIC. Choose 'Continue' to reboot (with NIC in PCMCIA slot) and thereby finish the 1st stage of the installation process. When 2st stage comes up after the reboot, you should have a working NIC and as such you can choose to download extra packages via ftp, http, etc. Should you, however, not have a working NIC at this point, go to the shell (Alt+F2) and try to reload your NIC: ifdown && ifup Return to Alt+F1 and continue installation (assuming networking now works)... * Also, I will clone off this report to the netcfg developers to inform them of the problem you are having where you have to 'up' your Cardbus interface manually upon every reboot (they might ask you for further info regarding this). After having cloned off this report to the developers in charge of networking, I will close this one. Many thanks for all your time. - -- Frederik Dannemare | mailto:[EMAIL PROTECTED] GnuPG key: search for 'dannemare' on http://pgpkeys.mit.edu Key fingerprint: BB7B 078A 0DBF 7663 180A F84A 2D25 FAD5 9C4E B5A8 http://frederik.dannemare.net | http://www.linuxworlddomination.dk -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFBEr6aLSX61ZxOtagRAvZiAJ9HXKz5ldp+kPL10l3BvVahRsnQxwCcC+yV Nz/t/IzIMsvDHSEIj18ZuoQ= =t+PQ -END PGP SIGNATURE-
Re: d-i devcamp 22th to 26th of September in Oldenburg?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thursday 05 August 2004 22:44, Petter Reinholdtsen wrote: [ snip ] > The following persons have told me on or off the list that they were > interested: > > Thorsten Sauter <[EMAIL PROTECTED]> > Christian Perrier <[EMAIL PROTECTED]> > Colin Watson <[EMAIL PROTECTED]> > Dennis Stampfer <[EMAIL PROTECTED]> > Gaudenz Steinlin <[EMAIL PROTECTED]> > Kurt Gramlich <[EMAIL PROTECTED]> > Joey Hess <[EMAIL PROTECTED]> > Martin F Krafft <[EMAIL PROTECTED]> > Sven Luther <[EMAIL PROTECTED]> > Alastair McKinstry <[EMAIL PROTECTED]> > Matt Kraai <[EMAIL PROTECTED]> > Frederik Dannemare <[EMAIL PROTECTED]> > > That list should be a starting point for planning the trip. Andreas, > you need to collect cost estimates from everyone interested in > getting their travel covered, and use this to decide who will get > their trip funded. [ snip ] Since I'm no DD and haven't done any directly work on the installer, I will absolutely not ask for any funding. I hope to make the event fit into my schedule, and with a little luck I can borrow my parents car, but what about hotels in that area? Does anybody know of any cheap ones that they can recommend? - -- Frederik Dannemare | mailto:[EMAIL PROTECTED] GnuPG key: search for 'dannemare' on http://pgpkeys.mit.edu Key fingerprint: BB7B 078A 0DBF 7663 180A F84A 2D25 FAD5 9C4E B5A8 http://frederik.dannemare.net | http://www.linuxworlddomination.dk -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFBEsKDLSX61ZxOtagRAioTAJ91+9pcDH0VG9JM5mHgRF3ywyHioACeJlLt iOpkaUOSm9SN23M1dQxIKUA= =lJqR -END PGP SIGNATURE-
Processed: must ifup cardbus NIC manually every time
Processing commands for [EMAIL PROTECTED]: > clone 241179 -1 Bug#241179: [i386] [beta3] [netinst] successful install, no network in 2nd stage (pcmcia) Bug 241179 cloned as bug 263849. > reassign -1 netcfg Bug#263849: [i386] [beta3] [netinst] successful install, no network in 2nd stage (pcmcia) Bug reassigned from package `installation-reports' to `netcfg'. > retitle -1 must ifup cardbus NIC manually every time Bug#263849: [i386] [beta3] [netinst] successful install, no network in 2nd stage (pcmcia) Changed Bug title. > tags -1 d-i Bug#263849: must ifup cardbus NIC manually every time There were no tags set. Tags added: d-i > 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: d-i devcamp 22th to 26th of September in Oldenburg?
Frederik Dannemare wrote: [ snip ] > > That list should be a starting point for planning the trip. Andreas, > > you need to collect cost estimates from everyone interested in > > getting their travel covered, and use this to decide who will get > > their trip funded. > [ snip ] > > Since I'm no DD and haven't done any directly work on the installer, I > will absolutely not ask for any funding. I hope to make the event fit > into my schedule, and with a little luck I can borrow my parents car, > but what about hotels in that area? Does anybody know of any cheap ones > that they can recommend? The Oldenburg meeting is organized a bit different to what you may expect. Recommended paraphernalia include a sleeping bag and a coffee mug. :-) Thiemo -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: d-i devcamp 22th to 26th of September in Oldenburg?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Friday 06 August 2004 01:34, Thiemo Seufer wrote: > Frederik Dannemare wrote: > [ snip ] > > > > That list should be a starting point for planning the trip. > > > Andreas, you need to collect cost estimates from everyone > > > interested in getting their travel covered, and use this to > > > decide who will get their trip funded. > > > > [ snip ] > > > > Since I'm no DD and haven't done any directly work on the > > installer, I will absolutely not ask for any funding. I hope to > > make the event fit into my schedule, and with a little luck I can > > borrow my parents car, but what about hotels in that area? Does > > anybody know of any cheap ones that they can recommend? > > The Oldenburg meeting is organized a bit different to what you may > expect. Recommended paraphernalia include a sleeping bag and a > coffee mug. :-) Arh, okay. :) Looking forward to it. If I'm very lucky, I may be able to borrow some weird non-i386 hardware from my old workplace. - -- Frederik Dannemare | mailto:[EMAIL PROTECTED] GnuPG key: search for 'dannemare' on http://pgpkeys.mit.edu Key fingerprint: BB7B 078A 0DBF 7663 180A F84A 2D25 FAD5 9C4E B5A8 http://frederik.dannemare.net | http://www.linuxworlddomination.dk -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFBEskgLSX61ZxOtagRAhNHAKCizydvEE3I7Ewu27skLQk/TPLrrgCdE+E2 37kLmMb5GEZQTfPb0Hc1Bog= =7+vZ -END PGP SIGNATURE-
Re: d-i devcamp 22th to 26th of September in Oldenburg?
On Fri, Aug 06, 2004 at 01:28:00AM +0200, Frederik Dannemare wrote: > Since I'm no DD and haven't done any directly work on the installer, I > will absolutely not ask for any funding. I hope to make the event fit > into my schedule, and with a little luck I can borrow my parents car, > but what about hotels in that area? Does anybody know of any cheap ones > that they can recommend? Last year we stayed in university classrooms for free. -- Matt Kraai[EMAIL PROTECTED]http://ftbfs.org/ signature.asc Description: Digital signature
Bug#241179: marked as done ([i386] [beta3] [netinst] successful install, no network in 2nd stage (pcmcia))
Your message dated Fri, 6 Aug 2004 01:58:11 +0200 with message-id <[EMAIL PROTECTED]> and subject line Processed: Bug#241179 (reassigned to netcfg) 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; 31 Mar 2004 06:06:41 + >From [EMAIL PROTECTED] Tue Mar 30 22:06:41 2004 Return-path: <[EMAIL PROTECTED]> Received: from adsl-69-105-235-1.dsl.pltn13.pacbell.net (moon.timocharis.com) [69.105.235.1] by spohr.debian.org with esmtp (Exim 3.35 1 (Debian)) id 1B8Ys4-00025g-00; Tue, 30 Mar 2004 22:06:40 -0800 Received: by moon.timocharis.com (Postfix, from userid 666) id 510D719E9A; Tue, 30 Mar 2004 22:06:38 -0800 (PST) Date: Tue, 30 Mar 2004 22:06:38 -0800 From: Akkana Peck <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Subject: Can't configure network on laptop with one pcmcia slot Message-ID: <[EMAIL PROTECTED]> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.28i 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_30,HAS_PACKAGE autolearn=no version=2.60-bugs.debian.org_2004_03_25 X-Spam-Level: Package: installation-reports Debian-installer-version: beta3 netinst, with special pcmcia boot disc from joeyh uname -a: Linux blackbird 2.4.25-1-386 #1 Tue Feb 24 08:11:13 EST 2004 i686 GNU/Linux Date: Tue Mar 30 21:46:18 PST 2004 Method: boot from netinst CD Machine: Sony Vaio SR-17 Processor: PIII 700MHz Memory: 192M Root Device: /dev/hda2 (20Mb internal IDE) Root Size/partition table: 5.1G root, 90M /boot Output of lspci: (available upon request, need to install another system to capture it) Base System Installation Checklist: Initial boot worked:[O] Configure network HW: [E] Config network: [E] 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] [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Comments/Problems: This laptop has one pcmcia slot: which means I can have the cdrom plugged in, or the network card, but not both at once. I found in a couple of tries that I had to select "other" for networking, and skip the two networking steps, in order to install the base system. (I tried telling it what module to use, and I tried unplugging the cdrom and plugging in the network card; both confused or froze the installer.) The base system installed, I rebooted with CD unplugged and network card plugged in, and now no network was configured. base-config doesn't ask any networking questions, just says the system does not seem to be connected to the internet. I can't install packages from the CD, because it wants the wrong CD name (apparently that's a known bug in beta3), but I can't install from the network, or add security.debian.org to the sources list, because it's convinced I have no network. Could something be added to the installer stage after the first reboot to ask again about a network? (Or perhaps use hotplug on a system that has pcmcia, but that may be a lot to ask from a minimal base system.) Failing that, could the initial base system install have a category for "pcmcia network/configure later"? Even if I had to choose the network driver[s] manually, that would help as long as it didn't complain if that hardware wasn't currently there. --- Received: (at 241179-done) by bugs.debian.org; 5 Aug 2004 23:56:34 + >From [EMAIL PROTECTED] Thu Aug 05 16:56:34 2004 Return-path: <[EMAIL PROTECTED]> Received: from cpe.atm0-0-0-2421032.0x3ef2dbfa.arcnxx7.customer.tele.dk (host.kl-teknik.com) [62.242.219.250] by spohr.debian.org with esmtp (Exim 3.35 1 (Debian)) id 1Bss66-0003BE-00; Thu, 05 Aug 2004 16:56:34 -0700 Received: from mail.thepenguininvasion.dk (0x5358aaae.abnxx12.adsl-dhcp.tele.dk [:::83.88.170.174]) (AUTH: PLAIN [EMAIL PROTECTED]) by host.kl-teknik.com with esmtp; Fri, 06 Aug 2004 02:01:43 +0200 id 000230FF.4112CA68.2C78 From: Frederik Dannemare <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Subject: Processed: Bug#241179 (reassigned to netcfg) Date: Fri, 6 Aug 2004 01:58:11 +0200 User-Agent: KMail/1.6.2 MIME-Version: 1.0 Cont
Re: sarge-ia64-netinst (July 24) installation attempt and failure on DL590/64
Zan, Did you file a bug for this? I can't find anything further in bug reports or emails to this list. It appears that the partitioner is seriously broken in version 48 for ia64. I too see this error. The partitioner (partman) only seems to know about ext2 and swap partitions even though others are loaded. Jim On Monday 02 August 2004 19:41, Zan Lynx wrote: > Hi! I am not sure if this is the proper list or the correct format. > Any tips on doing this right will be appreciated! > > I finally got around to trying the Sarge netinst ISO that I > downloaded July 24. I made a list of the problems I discovered: > > partitioner created ext3 partitions but kernel only supports ext2. > partitioner did not create a FAT partition for elilo. > partitioner cannot create a FAT partition? > base system setup fails because kernel package can't find > /dev/ida/c0d0p1. > rerunning base setup fails because /usr/bin/awk exists and because > /lib/modules/kernel-blah exists. -- * Jim LiebWild Open Source Inc. [EMAIL PROTECTED] Cell: 831.295.9317 Office: 831.421.0883Fax: 831.421.0885 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Create 2.6.7 boot CD
Sorry, was sent to 'debian-devel-announce' based on info in the README, have since found this mailing list. Have used "sarge" official business card i386 (20040802) to successfully open a 2.6 kernel, but due to BIOS problems need to create a boot CD and not use the hard drive to boot. I have thoroughly researched the making of boot CD's, and have made successful 2.4 bootable CD's. Sarge is my first 2.6 kernel that has booted. My questions are related to modifying Sarge's boot up to get my boot / rescue CD with 2.6.8-rc1 kernel; What is the kernel 'rdev'ed with to boot of RAM/CD? (I note that isolinux.cfg says root=/dev/rd/0 and an rdev /install/26/linuz gives /dev/sda3. Also the initrd image only has the two devices, console and ?? which don't seem to link in with the above.) So, what do I need to rdev the kernel with to get it to work, /dev/ram and /dev/ram1 doesn't seem to work, even after using mknod /dev/ram etc in the initrd's /dev? Where is linuxrc (from isolinux.cfg's init=/linuxrc ) located in sarge...iso? Can the source be obtained for linuxrc from anywhere on www? Is Sarge setup with a vanilla kernel using make-kpkg method only, or is it modified to get it to boot? I will be making a 2.6.8-rc1 kernel for this boot disk, and shall use make-kpkg. If there are modifications, it kills the whole idea above. Some feedback/bug; when running the CD verify from the expert26 config shell, upon leaving that menu, it loads all modules that it detects. This occurs even though they may have already been selected in a prior menu. Thanks, CW --- This email has been checked by a virus scanner, although the end reciever is responsible for their own scanning and checking of email and attachments. Outgoing mail is certified Virus Free by Virus scanner. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.732 / Virus Database: 486 - Release Date: 29/07/2004 -- 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]
Bug#263162: Please describe your tasksel policy, and re-add the tex task
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 fail the requirement that 90% of our users know what the task is from its short description. Moreover, "tex" is not really a task. "typesetting" or "word processing" or the like would be, but these and the desktop task would have significant overlap, which I prefer to avoid. tex is also not appropriate to be in a task because anyone who wants tex knows they want tex, and does not want to bumble around selecting ill-defined tasks (like "word processing") and hope that they get tex. Instead, they want to manually select their packages, and I expect them to do so. Tasks are for people who know what task they want to do, but are not very picky about the tools the system chooses to do it. -- see shy jo signature.asc Description: Digital signature
Re: release status
At 3 Aug 04 03:55:21 GMT, Joey Hess wrote: > At this point the only delay is waiting for the autobuilders, which are > overloaded from all the other uploads surrounding the sarge release, to > catch up and build the d-i images. In the past 24 hours, we've gotten > builds for hppa, ia64, s390, and sparc, plus a manual build for alpha. > That leaves arm, m68k (building), mips, mipsel, and powerpc. d-i is far > back in the queue for most of these arches[1] and is even slipping > further behind on some as more high-urgency package uploads happen. > [1] http://people.debian.org/~igloo/status.php?packages=debian-installer Well, what's current status of d-i release...? We delay some days. From [1], arm and mipsel seem need to build. Is this a show stopper? Thanks, -- Kenshi Muto [EMAIL PROTECTED]
Re: release status
Kenshi Muto wrote: > Well, what's current status of d-i release...? We delay some days. > From [1], arm and mipsel seem need to build. Is this a show stopper? We got the last of the initrd builds today, it's just waiting on the ftp-master to move them into place, and then the CD builds. -- see shy jo signature.asc Description: Digital signature
Re: release status
Hi, At 6 Aug 04 04:23:48 GMT, Joey Hess wrote: > Kenshi Muto wrote: > > Well, what's current status of d-i release...? We delay some days. > > From [1], arm and mipsel seem need to build. Is this a show stopper? > > We got the last of the initrd builds today, it's just waiting on the > ftp-master to move them into place, and then the CD builds. Oh, that's good news. Thank you. Thanks, -- Kenshi Muto [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#263178: update(install does not modify boot_dev and boot_osflags)
On Thu, Aug 05, 2004 at 01:38:03PM -0700, Steve Langasek wrote: > > > According to my somewhat limited research, an interface to the SRM would > > > be available if CONFIG_SRM_ENV was set to "y" during kernel build. > > > Unfortunately, this is not the default :-( > > OK, this seems to be fixed now (= boot.img as of Aug 4, 5423316 bytes), > > I can see /proc/srm_environment while the base installation is going on. > There have been no changes recently to the SRM support in the alpha > kernels; I don't know why it failed before for you, but it wasn't due to > missing kernel support. Oops, so perhaps I only looked at the installed kernel before (which does not have SRM support enabled) ... > There's no modification visible because no modification is being done. > No code has been written to attempt to change the SRM boot variables > from debian-installer; and you shouldn't expect this to be done for > sarge. While having the installer ensure you end up back in Debian > after a reboot sounds like a good idea, the task of mapping Unix devices > to SRM names is really quite difficult, and not something to be > attempted this soon before a release. OK, I accept this. Feel free to lower the priority of this bug report... Cheers, Steffen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
