Bug#77425: boot-floppies: tulip driver in 2.2r0 boot floppies not working
I'll try them out later this afternoon when I get back from classes. I've finished installing all my systems, but I'll use the disks on the box with Netgear, open up a shell and manually configure. It's just the module, so me doing it outside the installation system shouldn't be a problem... right? BTW, there were a few installation "issues" (if a long delay where you don't really know what's going on is an issue) I had. Should I post those up as wishlist bugs? Scott. * Adam Di Carlo translated into ASCII [Sun, Nov 19, 2000 at 02:09:44PM -0500][<[EMAIL PROTECTED]>] > Scott Robinson <[EMAIL PROTECTED]> writes: > > > I recently installed a new Debian 2.2r0 system using the rescue/root/drivers > > combo available on the CD Image. I found I could not get my brand new > > tulip.o based Netgear FA 310TX Fast Ethernet PCI Adapter to work with the > > 2.2.17pre6 packaged and auto-installed with the boot-floppy. > > > > The solution was to get the real 2.2.17 kernel source, but I couldn't get > > that without 'net access! A dilemma indeed! I ended up pulling out an old > > SMC Ultra (smc-ultra.o) card and using it to download the latest source and > > using make-kpkg to generate a proper kernel. > > > > This could cause definate problems for people who don't have an alternative > > net card. I would suggest upgrading the boot-floppies source kernel to the > > full 2.2.17. > > Could you do me a favor and test the version at > http://alpha.onshore.com/~apharris/debian/dists/potato/main/disks-i386/current/> > ? > > Depending on when you download that, that may be a version compiled > with experimental internationalization stuff, which has some problems > you can ignore (can't find keymap, cfdisk looks wierd, etc). The only > issue we're concerned with for this bug is whether the 2.2.18pre21 > kernel sources closes this bug. I would assume that it does. > > Thanks. > > -- > .Adam Di [EMAIL PROTECTED]http://www.onShore.com/> > -- jabber:[EMAIL PROTECTED] - Universal ID (www.jabber.org) http://dsn.itgo.com/ - Personal webpage robhome.dyndns.org - Home firewall -BEGIN GEEK CODE BLOCK- Version: 3.12 GAT dpu s+: a--- C++ UL P+ L+++ E- W+ N+ o+ K++ w++ O M V PS+ PE Y+ PGP++ t++ 5++ X+ R tv b DI D++ G+ e+ h! r-- y- --END GEEK CODE BLOCK-- PGP signature
boot-floppies 2.2.18 uploaded
Boot-floppies 2.2.18 for i386 was uploaded to samosa. Porters, do your stuff. If source changes are needed for porters, I can do my best to pretty quickly turn-around 2.2.19. -- .Adam Di [EMAIL PROTECTED]http://www.onShore.com/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: 2.2.18pre kernels and pcmcia in 2.2rN
To: Adam Di Carlo <[EMAIL PROTECTED]> wrote: > I agree with that. Anyhow, that seems to be what we're doing, so all > should be well in 2.2r2. [ ... ] > I've tested the idepci and compact flavors, and they seem to work > great. Excellent! Sounds like everything is okay. - Brian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#50953: marked as done ([alpha] multia install)
Your message dated Mon, 20 Nov 2000 13:12:43 -0500 (EST) with message-id <[EMAIL PROTECTED]> and subject line (no subject) 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.) Darren Benham (administrator, Debian Bugs database) -- Received: (at submit) by bugs.debian.org; 22 Nov 1999 15:22:21 + Received: (qmail 19195 invoked from network); 22 Nov 1999 15:22:20 - Received: from unknown (HELO orld-bdc.orlando.veridian.com) (137.100.113.2) by master.debian.org with SMTP; 22 Nov 1999 15:22:20 - Received: from ORLD-WKS-001 ([137.100.113.49]) by orld-bdc.orlando.veridian.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2448.0) id WZBRVMWP; Mon, 22 Nov 1999 10:24:37 -0500 Message-ID: <000b01bf34fd$6929caa0$[EMAIL PROTECTED]> From: "jons" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Subject: multia install Date: Mon, 22 Nov 1999 10:22:38 -0500 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="=_NextPart_000_0008_01BF34D3.803209D0" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3110.5 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 This is a multi-part message in MIME format. --=_NextPart_000_0008_01BF34D3.803209D0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Package: Boot Floppies Version: 11/10/1999 stable Hello,=20 I'm having a bit of trouble installing Debian Linux on my = multia. I am using the ARC console to boot linux fro the resuce disk = (resc1440.bin). Everything seems to work. At the MILO prompt I enter boot fd0:linux = root=3D/dev/fd0 rw The problem I am having is with the root disk (root1440.bin). The first disk I tried resulted in the following messages: Warning VFS unable to mount root filesystem. Kernel Panic: unable to mount root filesystem. I made a few more root disks and when I use them I get the following: Warning VFS cannot open /dev/console Kernel Panic: cannot open /dev/console. At this point I am wondering if I have a hardeware problem or if there = is something in the installing procedure I have overlooked. I used the disk set for the noname box I am assuming that this will work = for the multia as well. System specs. DEC Multia 166mhz 21066 cpu 64mb ram pci option card with ncr53c810 scsi controller on board ethernet controller DEC hard drive Toshiba scsi 4x cd rom active scsi terminator BIOS version 3.5-1 If this issue has been addressed elsewhere please let me know. Thank you for any assistance that you can provide. Jon Stratton [EMAIL PROTECTED] --=_NextPart_000_0008_01BF34D3.803209D0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Package: Boot Floppies Version: 11/10/1999 = stable Hello, I'm = having a bit=20 of trouble installing Debian Linux on my multia. I am using the ARC console to boot = linux fro the=20 resuce disk (resc1440.bin). Everything seems to work. At the = MILO prompt I=20 enter boot fd0:linux root=3D/dev/fd0 rw The problem I am having is with the = root disk=20 (root1440.bin). The first disk I tried resulted in = the following=20 messages: Warning VFS unable to mount root=20 filesystem. Kernel Panic: unable to mount root=20 filesystem. I made a few more root disks and = when I use them=20 I get the following: Warning VFS cannot open=20 /dev/console Kernel Panic: cannot open=20 /dev/console. At this point I am wondering if I have a hardeware = problem or=20 if there is something in the installing procedure I have overlooked. I used the disk set for the noname = box I am=20 assuming that this will work for the multia as well. System specs. DEC Multia 166mhz 21066 cpu 64mb ram pci option card with ncr53c810 scsi = controller on board ethernet controller DEC hard drive Toshiba scsi 4x cd rom active scsi terminator BIOS version 3.5-1 If this issue has been addressed elsewhere please = let me=20 know. Thank you for any assistance that = you can=20 provide. Jon Stratton mailto:[EMAIL PROTECTED]">[EMAIL PROTECTED]= om --=_NextPart_000_0008_01BF34D3.803209D0-- --- Received: (at 50953-done) by bugs.debian.org; 20 Nov 2000 18:12:28 + >From [EMAIL PROTECTED] Mon Nov 20 12:12:28 2000 Return-path: <[EMAIL PROTECTED]> Received: from (burrito.onshore.com) [64.22.101.122] (postfix) by master.debian.org with esmtp (Exim 3.12 1 (Debian)) id 13xvQa-0003p1-00; Mon, 20 Nov 2000 12:12:28 -0600 Received: by burrito.onshore.com (Postfix, from u
Processed: Fixed in NMU boot-floppies 2.2.18
Processing commands for [EMAIL PROTECTED]: > severity 31865 fixed Bug#31865: [not working] Request for Language chooser on boot-floppies Severity set to `fixed'. > severity 40775 fixed Bug#40775: [cvs-fixed] unclear wording in Sparc docs Severity set to `fixed'. > severity 49172 fixed Bug#49172: [cvs-fixed] problems with floppy booting on sun4c Severity set to `fixed'. > severity 64823 fixed Bug#64823: incorrect LILO automatic placement on i386 Bug#63198: boot-floppies: Don't put the lilo boot record in the extended partition Bug#65606: No installation of LILO to logical partition? Severity set to `fixed'. > severity 70387 fixed Bug#70387: [CVS-fixed] build dependancy for debhelper Severity set to `fixed'. > severity 70871 fixed Bug#70871: [CVS-fixed] kernel-compilation documentation Severity set to `fixed'. > severity 71532 fixed Bug#71532: [CVS-fixed] where to get debian in documentation Severity set to `fixed'. > severity 72870 fixed Bug#72870: [CVS-fixed] Broken links in Debian installation docs Severity set to `fixed'. > severity 74322 fixed Bug#74322: [cvs-fixed] boot-floppies: in installation /dev/pcd0 device isn't created Severity set to `fixed'. > severity 76408 fixed Bug#76408: [cvs-fixed] bad linux history url in installation guide Severity set to `fixed'. > severity 77425 fixed Bug#77425: boot-floppies: tulip driver in 2.2r0 boot floppies not working Severity set to `fixed'. > severity 77459 fixed Bug#77459: base: dpkg 1.6.15 uninstallable on sparc Severity set to `fixed'. > quit Stopping processing here. Please contact me if you need assistance. Darren Benham (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Debian Boot CVS: aph
CVSROOT:/cvs/debian-boot Module name:debian-installer Changes by: aph 00/11/20 15:43:34 Modified files: tools/udpkg: depends.c status.c udpkg.c udpkg.h Added files: tools/udpkg: udpkg_main.c Log message: Split main to seperate function, goal is to make libudpg. Removed dependence on shell command rm with internal function. replaced "struct packages_t" with "packages_t" via typdef (for style). -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Some thoughts on a new installer
Adam Di Carlo wrote: > I think one of the design goals is that for the installed system, all > files (excepting some config files and such) on the new system, at > almost every point, are out of proper packages. The .udeb stuff is > strictly (am I wrong?) for helping getting the installation media, > target media, and all those installation things handled. Its not stuff > that would be hanging around on your new system. > > Christoph, as I read your plan, it's more about tricking the newly > installed system about some things being installed which aren't fully > installed, etc etc. Taht is a world of pain and hurt and should be > avoided. Even the "classic" boot-floppies engages in this a bit and > it's a design flaw of the system (bug 3905 from IWJ). You're right Adam, and you said it better than I could. -- see shy jo -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Failure of Debian to Boot
Sacramento, California November 20, 2000 I have purchased the three CDs for Debian/GNU ver. 2.2. However, the boot from the CD-rom to install Linux fails to recognize the SCSI card on my computThe machine is equiped with an ADAPTEC Model AIC 7880 controller. The monitor screen states the ADAPTEC card is recogniced in three lines of text which is immediately followed by the line: SCSI: no available ports found. The computer the freezes and CTL-ALT-DEL can not restart the system. It is necessary to turn off the power. Any information youo can provide will be appreciated. Sincerely, Roy Hardy EMAIL: [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: hardware detection using libpci
Glenn McGrath wrote: > Ive been thinking about hardware detection. I think hardware detection > should be a dependency on the fetch method it applies to. > > e.g. the http/ftp/nfs retriever should depend on network and modem > hardware detection. > > This way, if a network retriever is to be used, the hardware detection > component of it should have already detected the relevent hardware and > determined what kernel modules are needed to support it. Yes, I agree. This means that hardware detection packages should detect hardware in thsir postinst, if they fail, the postinst should fail. Thus until hardware is detected, stuff that depends on it will not install. > Its good points; > 1) its small, looks like that with libdetect the hardware list is a > significant proportion os its total size, ive just ignore things like > the cards name, just care about the card PCI id and the kernel module > that it needs. Focusing on detecting the hardware required for specific > kernel modules, rather than detcting evberything and then mapping it to > kernel modules should make it more modular and smaller. > > 2) libpci is from pci-utilities, its fairly portable, can either use > /proc to get pci ids or probe hardware directly, the later making it > portable to other OS's Another advantage (I may have said this before) is: CONFIG_PCI_NAMES By default, the kernel contains a database of all known PCI device names to make the information in /proc/pci, /proc/ioports and similar files comprehensible to the user. This database increases size of the kernel image by about 80KB, but it gets freed after the system boots up, so it doesn't take up kernel memory. Anyway, if you are building an installation floppy or kernel for an embedded system where kernel image size really matters, you can disable this feature and you'll get device ID numbers instead of names. An 80k win on the kernel side is *amazing*. What I really worry about is maintainability. Someone has to keep these big lists of PCI ids that you have generated up to date. I don't expect they will change often, if at all, but new ones will always need to be added. It would be really good if the numbers could just be pulled out of the kernel source somehow (it does contain the same information, right?). -- see shy jo -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: hardware detection using libpci
David Whedon wrote: > My approach is similar, I have a tiny utility that converts the list > of known hardware from the format that lib detect uses (a *.lst file) > into a header file. My program (ddetect) includes said header file. > ddetect makes calls into libdetect (which itself uses libisapnp > internally). I got it to link with uC-ulibc (though the udeb at the > url above links with glibc) and it was ~55k (staticily linked), 10k of > which was the header file (could be smaller if I was clever like Genn > and left out the card names :-) ) Can libdetect actually work with just pci id numbers, not names? Glenn McGrath wrote: > I guess the card names are handy for the user if all doesnt go to plan, > i just left them out because the program didnt _need_ them, and they > take the most space. That's true, it is nice to be able to look at /proc/pci and figure out what module to load by hand. But that 80k is pretty nice too. > From the three modules i looked at there appears to be a few pci ids > that arent in libdetects list, so maybe a kernel module based list would > be more complete. Yes, if at all possible we really need to grub this list of of the kernel so you don't have to keep maintaining it. > I noticed that libdetect uses /proc to get the pci ids, it cant do > hardware probes to get the ids. Whilst Joey has said that we wouldnt > ever ship a kernel without /proc support, i think that having the option > to do without /proc is a good thing, if we want to make it easy for > users to build a disk with there own kernel then its best is we depend > on as few kernel features as possible. I think we're surely going to depend on some features, probably even features that a user wouldn't think to compile into their kernel. I'm afraid doing without /proc is going to waste more space than it saves by making code try to do without it. Thus, asking users to compile in /proc, which _is_ the default, is not undue hardship. Remember making a kernel for the boot-floppies requires it be built with all kinds of unlikely stuff like msdos fs support. That is well documented though, and I guess some people have managed to do it. -- see shy jo -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: hardware detection using libpci
David Whedon wrote: > I made a new version of ddetect with a few changes, even if we don't > go the libdetect way it was instructive to figure out how to make > multiple .udebs conviennently. > > I'm now generating 2 udebs which each provide the virtual package > [sound|ethernet]-card-detection: > snddetect_0.0.5_i386.udeb > ethdetect_0.0.5_i386.udeb I understand that is just an example, we do not need sound detection in the installer. I'm more interested in the array of other debs you have there now, including cd and disk detection. Good work. I'm going to get you commit access. I still like Glenn's approach of using PCI ID's not names though. > We want udebs to be small. Therefore they shouldn't contain anything more > than the bare minimum to accomplish their function. This is against > policy (no manpage, copyright, etc.). For this example > the .udebs contain very little: > $ dpkg -c snddetect_0.0.5_i386.udeb > drwxr-xr-x root/root 0 2000-11-14 20:38:59 ./ > drwxr-xr-x root/root 0 2000-11-14 20:38:58 ./usr/ > drwxr-xr-x root/root 0 2000-11-14 20:38:59 ./usr/bin/ > -rwxr-xr-x root/root 26460 2000-11-14 20:38:59 ./usr/bin/snddetect > > Documentation, copyrights etc. will be in another udeb. Actually, don't worry about putting the docs and copyrights in any udeb. If you make a deb for your stuff too, put it in there or course. Otherwise, make sure it is in the source package. > The .udebs can be found at: > http://www.gordian.com/users/davidw/debian.html They all work for me except sndetect (ISA soundblaster) and mdmdetect (ISA modem). -- see shy jo -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: first weekly debian-installer status report
Jérôme Marant wrote: > > - documentation [UNCLAIMED} > > Not started. > I'm willing to help on this. > How do I start ? I think we need to hold off on this until we have something user-level to document. Unless you want to help with the design docs. -- see shy jo -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Debian Boot CVS: aph
Glenn wrote: > Split main to seperate function, goal is to make libudpg. > Removed dependence on shell command rm with internal function. > replaced "struct packages_t" with "packages_t" via typdef (for style). This grew the binary by 2k. I hope that's worth it, but I have my doubts. If we just use busybox rm, other stuff can use it too. -- see shy jo -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: hardware detection using libpci
Joey Hess wrote: > Glenn McGrath wrote: > > I guess the card names are handy for the user if all doesnt go to plan, > > i just left them out because the program didnt _need_ them, and they > > take the most space. > > That's true, it is nice to be able to look at /proc/pci and figure out > what module to load by hand. But that 80k is pretty nice too. > If we have the pci id's we can always get the hardware description later from a seperate list, but then i guess the information is of less use. > > From the three modules i looked at there appears to be a few pci ids > > that arent in libdetects list, so maybe a kernel module based list would > > be more complete. > > Yes, if at all possible we really need to grub this list of of the > kernel so you don't have to keep maintaining it. > I started to setup a sourceforge page for pcidetect, but now am having second thoughts, im not sure that pcidetect is the best aproach purely because it is only pci. > > I noticed that libdetect uses /proc to get the pci ids, it cant do > > hardware probes to get the ids. Whilst Joey has said that we wouldnt > > ever ship a kernel without /proc support, i think that having the option > > to do without /proc is a good thing, if we want to make it easy for > > users to build a disk with there own kernel then its best is we depend > > on as few kernel features as possible. > > I think we're surely going to depend on some features, probably even > features that a user wouldn't think to compile into their kernel. I'm > afraid doing without /proc is going to waste more space than it saves by > making code try to do without it. Thus, asking users to compile in > /proc, which _is_ the default, is not undue hardship. > > Remember making a kernel for the boot-floppies requires it be built with > all kinds of unlikely stuff like msdos fs support. That is well > documented though, and I guess some people have managed to do it. > Yea, i now conceed that the linux kernel demands /proc support, there is no reasonable way of determining which devices the kernel has detected without /proc. Im starting to feel that the linux kernel is inflexible and limiting, we could do better hardware detection but it would need to be a kernel module, this would be a bad idea as i think we want as much kernel independence as possible. Glenn -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: hardware detection using libpci
Joey Hess wrote: > > The .udebs can be found at: > > http://www.gordian.com/users/davidw/debian.html > > They all work for me except sndetect (ISA soundblaster) and mdmdetect > (ISA modem). Actually, snddetect -f does work, while -f doesn't make mdmdetect do any better. -- see shy jo -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Debian Boot CVS: joeyh
CVSROOT:/cvs/debian-boot Module name:debian-installer Changes by: joeyh 00/11/20 17:27:26 Modified files: doc: TODO Log message: status update -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
weekly (?) debian-installer status report
I skipped last week which was probably a bad idea. Too busy..
Done these past two weeks:
- dpkg 1.7.0 was released, so udebs can be built now
- Continuing development of udpkg has gotten all the important features
working.
- Pcidetect has been checked in. It is able to detect PCI NIC's and is
quite small.
- Hardware detectors have also been written for sound, ethernet (a competing
implementation), cd, cpu, disk, modem, and memory detection, all using
libdetect, and supporting pci and optionally isa.
Still Todo:
- design [Joey Hess, debian-boot]
75% done. Enough to know what the big peices are
and how they fit together.
- udeb archive setup [James Troup, Anthony Towns, Jason Gunthorpe]
95% support in new package pools code. James is now waiting
for after 2.1r2, it seems.
- udeb building [Joey Hess]
Udebs can be built now.
- cdebconf (miniature debconf in C) [Randolph Chung, Anthony Towns]
In progress. Infrastructure is 70% done. have one working
database backend, have a conceptual text-based
frontend that is ~1/4 done.
- udpkg (tiny dpkg clone) [Randolph Chung, Joey Hess]
Usable. One todo item (localized descriptions)
- main-menu (main menu generator) [Joey Hess]
90% done (one non-trivial todo item)
- busybox integration [Erik Andersen]
Not started. Busybox needs to build one or more .udebs.
Probably more than one.
- network card detector [Glenn McGrath, David Whedon]
Pcidetect is written, detects PCI cards only. Needs
testing. David has another detector that uses libdetect
instead.
- other hardware detection [David Whedon]
David has written detectors for sound, ethernet, cd, cpu,
disk, and memory detection. All need testing.
http://www.gordian.com/users/davidw/debian.html
- network setup [UNCLAIMED]
Not started. Set up the network, via dhcp or via prompting;
implementor decides.
- retreiver control program [Joey Hess, Glenn McGrath]
Not started. Sort of like apt, except tons dumber, this
uses retreiver(s) to download Packages files and then udebs,
and calls udpkg to install them. Still unclear exactly how
this will work, we need help figuring this out.
- http retreiver [UNCLAMED]
Not started. Download udebs, other files from network.
- install target media detector [UNCLAIMED]
Not started. Just has to figure out what media to install to.
Probably trivial; most support already in the kernel.
- disk partitioner [UNCLAIMED]
Not started. Some kind of a UI to let the user partition their
disks and decide what the partitions are used for.
- disk formatter [UNCLAIMED]
Not started. Formats disks, turns on swap, etc.
- base system installer [UNCLAIMED]
Not started. Installs the base system, probably from base.tgz
for now, and does any necessary setup.
- {lilo,grub} installer [UNCLAIMED]
Not started. Sets up {lilo,grub}.
- kernel module udebs [Vaidhy]
Not started. We will need various sets of kernel modules;
one such set is NIC drivers. Each set goes in a udeb; there
probably has to be a system to build the whole kernel and
udebs.
- library reduction [Marcus Brinkmann]
Not started. There is code in the boot-floppies that should
be usable, but this is still one of the hardest parts.
- install media build system [UNCLAIMED]
Not started. Puts all the peices together and makes
install media.
- user documentation
Not started. (Waiting until we have something to document..)
--
see shy jo
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: hardware detection using libpcid
Joey Hess wrote: > > Glenn McGrath wrote: > > Ive been thinking about hardware detection. I think hardware detection > > should be a dependency on the fetch method it applies to. > > > > e.g. the http/ftp/nfs retriever should depend on network and modem > > hardware detection. > > > > This way, if a network retriever is to be used, the hardware detection > > component of it should have already detected the relevent hardware and > > determined what kernel modules are needed to support it. > > Yes, I agree. This means that hardware detection packages should detect > hardware in thsir postinst, if they fail, the postinst should fail. Thus > until hardware is detected, stuff that depends on it will not install. > My mind is stuck in a loop trying to working out hardware detection, retrievers, a shell, and core components. The boot disk will have at least one working retriever on it. To setup a different retriever we need to 1) fetch/install a shell if we dont already have one, to enable postinst(and other things) to work. 2) fetch/install hardware detection 3) possibly fetch/install new kernel modules ? 4) fetch/install the new fetch method It would be good to be able to remove the dependency on a shell so it was optional (non-core) rather than a requirement (core). Can we fetch/install a shell as a normal package if we dont already have a shell ? Looks like it would take some big changes to avoid having a shell as core. > > Its good points; > > 1) its small, looks like that with libdetect the hardware list is a > > significant proportion os its total size, ive just ignore things like > > the cards name, just care about the card PCI id and the kernel module > > that it needs. Focusing on detecting the hardware required for specific > > kernel modules, rather than detcting evberything and then mapping it to > > kernel modules should make it more modular and smaller. > > > > 2) libpci is from pci-utilities, its fairly portable, can either use > > /proc to get pci ids or probe hardware directly, the later making it > > portable to other OS's > > Another advantage (I may have said this before) is: > > CONFIG_PCI_NAMES > By default, the kernel contains a database of all known PCI device > names to make the information in /proc/pci, /proc/ioports and > similar files comprehensible to the user. This database increases > size of the kernel image by about 80KB, but it gets freed after the > system boots up, so it doesn't take up kernel memory. Anyway, if you > are building an installation floppy or kernel for an embedded system > where kernel image size really matters, you can disable this feature > and you'll get device ID numbers instead of names. > > An 80k win on the kernel side is *amazing*. > I would think a libdetect based hardware detection program would result in the same savings, its list is seperate as well as far as i know. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: weekly (?) debian-installer status report
On Mon Nov 20, 2000 at 05:28:44PM -0800, Joey Hess wrote: > - busybox integration [Erik Andersen] > Not started. Busybox needs to build one or more .udebs. > Probably more than one. The first pass at busybox udebs will be ready tonight. How do I upload them? Just upload them to incoming as I would anything else? -Erik -- Erik B. Andersen email: [EMAIL PROTECTED] --This message was written using 73% post-consumer electrons-- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Failure of Debian to Boot
roy hardy <[EMAIL PROTECTED]> writes: > Sacramento, California > November 20, 2000 > > I have purchased the three CDs for Debian/GNU ver. 2.2. However, the > boot from the CD-rom to install Linux fails to recognize the SCSI card > on my computThe machine is equiped with an ADAPTEC Model AIC 7880 > controller. The monitor screen states the ADAPTEC card is recogniced in > three lines of text which is immediately followed by the line: SCSI: > no available ports found. The computer the freezes and > CTL-ALT-DEL can not restart the system. It is necessary to turn off the > power. Any information youo can provide will be appreciated. Sorry that i386 hardware archicture is so crappy and your machine hung. I suggest you use the 'compact' flavor rather than the vanilla flavor -- to do that, uh, boot from the 2nd CD I think. -- .Adam Di [EMAIL PROTECTED]http://www.onShore.com/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#77425: boot-floppies: tulip driver in 2.2r0 boot floppies not working
Scott Robinson <[EMAIL PROTECTED]> writes: > I'll try them out later this afternoon when I get back from classes. > > I've finished installing all my systems, but I'll use the disks on the box > with Netgear, open up a shell and manually configure. It's just the module, > so me doing it outside the installation system shouldn't be a problem... > right? Uh, actually, it is more likely that it would be a problem. Why not use the disks and go part way thru the installation process, installing onto a swap partition or some other temporary partition, not going all the way (I mean, you don't need to install base and lilo on the mbr and such), just far enough to be sure that the ne-tulip module works. > BTW, there were a few installation "issues" (if a long delay where you don't > really know what's going on is an issue) I had. Should I post those up as > wishlist bugs? Sure, if they are not already filed. -- .Adam Di [EMAIL PROTECTED]http://www.onShore.com/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: hardware detection using libpci
> > and left out the card names :-) )
>
> Can libdetect actually work with just pci id numbers, not names?
yea, we'd have to put in a placeholeder ("unknown") so any output
messages wouldn't have problems, but looking through libdetect (or at
least the parts I'm using) all it really needs it the id's. I look
into making a build option.
> > From the three modules i looked at there appears to be a few pci ids
> > that arent in libdetects list, so maybe a kernel module based list would
> > be more complete.
>
> Yes, if at all possible we really need to grub this list of of the
> kernel so you don't have to keep maintaining it.
Are you talking about :
/usr/src/linux/drivers/pci/pci.ids
I'm not sure where the mapping between module and device is in the
kernel source, anybody? If there is a ready list already in the
kernel source (other than looking at each module's source
individually), then we should have that as our reference. If it
isn't, then maybe the *.lst file that come with libdetect should be
our source.
-David
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: weekly (?) debian-installer status report
Erik Andersen wrote: > On Mon Nov 20, 2000 at 05:28:44PM -0800, Joey Hess wrote: > > - busybox integration [Erik Andersen] > > Not started. Busybox needs to build one or more .udebs. > > Probably more than one. > > The first pass at busybox udebs will be ready tonight. How do I > upload them? Just upload them to incoming as I would anything > else? We still can't upload udebs, James has bailed on rolling out package pools until after 2.1r2 (sigh). -- see shy jo -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#31865: marked as done ([not working] Request for Language chooser on boot-floppies)
Your message dated 21 Nov 2000 00:26:01 -0500 with message-id <[EMAIL PROTECTED]> and subject line bugs closed in boot-floppies 2.2.18 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.) Darren Benham (administrator, Debian Bugs database) -- Received: (at submit) by bugs.debian.org; 14 Jan 1999 13:32:23 + Received: (qmail 1592 invoked from network); 14 Jan 1999 13:32:14 - Received: from dor182206.kaist.ac.kr ([EMAIL PROTECTED]) by master.debian.org with SMTP; 14 Jan 1999 13:32:14 - Received: by dor182206.kaist.ac.kr via sendmail from stdin id <[EMAIL PROTECTED]> (Debian Smail3.2.0.102) for [EMAIL PROTECTED]; Thu, 14 Jan 1999 22:32:06 +0900 (KST) To: [EMAIL PROTECTED] Subject: boot-floppies wish - no #define the translations. User-Agent: SEMI/1.12.0 (Nishi-Kanazawa) FLIM/1.12.2 (=?ISO-8859-4?Q?Kuj?= =?ISO-8859-4?Q?=F2?=) Emacs/20.3 (i386-debian-linux-gnu) MULE/4.0 (HANANOEN) MIME-Version: 1.0 (generated by SEMI 1.12.0 - "Nishi-Kanazawa") Content-Type: text/plain; charset=US-ASCII From: Changwoo Ryu <[EMAIL PROTECTED]> Date: 14 Jan 1999 22:32:06 +0900 Message-ID: <[EMAIL PROTECTED]> Lines: 19 Package: boot-floppies Version: 2.1.4 Severity: wishlist In the current mechanism of boot-floppies i18n, we should build the many boot disks for each languages.. Yes, the translations does not cause size-limit problems. But the boot disks are also used for bootable Debian CDs. It would be better to select the user's native language from available languages. I know that RedHat bootdisk handles i18n that way. I think the boot images for floppies can include only one language, but it would be good for the one for CD to include all selectable translated messages. -- Changwoo Ryu --- Received: (at 31865-done) by bugs.debian.org; 21 Nov 2000 05:25:24 + >From [EMAIL PROTECTED] Mon Nov 20 23:25:24 2000 Return-path: <[EMAIL PROTECTED]> Received: from (burrito.onshore.com) [64.22.101.122] (postfix) by master.debian.org with esmtp (Exim 3.12 1 (Debian)) id 13y5vm-0004F0-00; Mon, 20 Nov 2000 23:25:22 -0600 Received: from arroz.fake (localhost [127.0.0.1]) by burrito.onshore.com (Postfix) with ESMTP id CCB6F93802; Tue, 21 Nov 2000 00:26:01 -0500 (EST) Sender: [EMAIL PROTECTED] To: [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED] Subject: bugs closed in boot-floppies 2.2.18 From: Adam Di Carlo <[EMAIL PROTECTED]> Date: 21 Nov 2000 00:26:01 -0500 Message-ID: <[EMAIL PROTECTED]> Lines: 72 User-Agent: Gnus/5.0807 (Gnus v5.8.7) Emacs/20.7 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Delivered-To: [EMAIL PROTECTED] The bug you filed against the boot-floppies package has been closed in the most recent boot-floppies, 2.2.18, now in Potato (for i386 anyhow). The changelog for that version is included. Please let us know if you still have the problem, even in the newest version. Thank you for helping Debian build a better installation systenm. -- .Adam Di [EMAIL PROTECTED]http://www.onShore.com/> boot-floppies (2.2.18) stable; urgency=low . * build with Debian 2.2r1 plus updates (closes: Bug#77459) * Adam Di Carlo: - i386 and sparc use kernel 2.2.18pre21 (closes: Bug#77425) - Makefiles: clean is a bit cleaner - release.sh (i386): also put kernel configs in TOP/ (hey, it's a small file); don't leave stranded release/kernel-config file, put it in the bf-common tarball - rootdisk.sh: add pcd0 device mknod (closes: Bug#74322), which MAKEDEV doesn't know about; add gscd and cm206cd devices; remove some hacks on device creation due to bugs fixed in MAKEDEV - dbootstrap: quiet bootarg makes more things shut up; disable the check for root filesystem being on extended partition while LILO is going on the MBR, because LILO supports this now (closes: Bug#64823); add new fullscreen_execlog utility function - debian/control: add Build-Depends and Build-Depends-Indep (closes: Bug#70387); remove required package from depends - documentation: fix links to dselect-beginner (closes: Bug#72870); add a section in the first chapter talking about where to get Debian (closes: Bug#71532); other corrections (closes: Bug#70871); fix linux history link (closes: Bug#76408
Bug#40775: marked as done ([cvs-fixed] unclear wording in Sparc docs)
Your message dated 21 Nov 2000 00:26:01 -0500 with message-id <[EMAIL PROTECTED]> and subject line bugs closed in boot-floppies 2.2.18 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.) Darren Benham (administrator, Debian Bugs database) -- Received: (at submit) by bugs.debian.org; 5 Jul 1999 08:07:30 + Received: (qmail 21340 invoked from network); 5 Jul 1999 08:07:30 - Received: from adsl-207-214-111-105.dsl.snfc21.pacbell.net (HELO hiro-tan.dhs.org) ([EMAIL PROTECTED]) by master.debian.org with SMTP; 5 Jul 1999 08:07:30 - Received: from hiro-tan.dhs.org (ekoontz@localhost [127.0.0.1]) by hiro-tan.dhs.org (8.9.1a/8.9.1) with ESMTP id BAA32227 for <[EMAIL PROTECTED]>; Mon, 5 Jul 1999 01:09:43 -0700 Sender: [EMAIL PROTECTED] Message-ID: <[EMAIL PROTECTED]> Date: Mon, 05 Jul 1999 01:09:43 -0700 From: Eugene Koontz <[EMAIL PROTECTED]> X-Mailer: Mozilla 4.6 [en] (X11; I; Linux 2.2.6 i586) X-Accept-Language: en MIME-Version: 1.0 To: [EMAIL PROTECTED] Subject: unclear wording in Sparc docs Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit In http://www.debian.org/releases/2.1/sparc/ch-install-methods.en.html#s-install-tftp it is written in section 5.5.3 that : Often, the file that the TFTP client will look for is client-ip-in-hexclient-architecture. To compute client-ip-in-hex, take each byte of the client IP address and translate it into hexadecimal notation. If you have a machine handy with the bc program, you can use the program. First issue the obase=16 command to set the output to hex, then enter the individual components of the client IP one at a time. As for client-architecture, try out some values. SPARC architectures for instance use the sub-architecture names, such as ``SUN4M'' or ``SUN4C''; in some cases, the architecture is left blank, so the file the client looks for is just client-ip-in-hex. Once you've determined the name, make the link like this: ln /boot/tftpboot.img /boot/file-name. This was unclear to me; I didn't know exactly what my filename should be. I think it would be good if you gave an example. Here's one that works for me : I have a sun4c (Sun IPC) architecture, and I want the IP of my Sun to be 192.168.1.3. So the filename will be : C0A80103.SUN4C thanks for your time, Eugene Koontz --- Received: (at 40775-done) by bugs.debian.org; 21 Nov 2000 05:25:24 + >From [EMAIL PROTECTED] Mon Nov 20 23:25:24 2000 Return-path: <[EMAIL PROTECTED]> Received: from (burrito.onshore.com) [64.22.101.122] (postfix) by master.debian.org with esmtp (Exim 3.12 1 (Debian)) id 13y5vm-0004F0-00; Mon, 20 Nov 2000 23:25:22 -0600 Received: from arroz.fake (localhost [127.0.0.1]) by burrito.onshore.com (Postfix) with ESMTP id CCB6F93802; Tue, 21 Nov 2000 00:26:01 -0500 (EST) Sender: [EMAIL PROTECTED] To: [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED] Subject: bugs closed in boot-floppies 2.2.18 From: Adam Di Carlo <[EMAIL PROTECTED]> Date: 21 Nov 2000 00:26:01 -0500 Message-ID: <[EMAIL PROTECTED]> Lines: 72 User-Agent: Gnus/5.0807 (Gnus v5.8.7) Emacs/20.7 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Delivered-To: [EMAIL PROTECTED] The bug you filed against the boot-floppies package has been closed in the most recent boot-floppies, 2.2.18, now in Potato (for i386 anyhow). The changelog for that version is included. Please let us know if you still have the problem, even in the newest version. Thank you for helping Debian build a better installation systenm. -- .Adam Di [EMAIL PROTECTED]http://www.onShore.com/> boot-floppies (2.2.18) stable; urgency=low . * build with Debian 2.2r1 plus updates (closes: Bug#77459) * Adam Di Carlo: - i386 and sparc use kernel 2.2.18pre21 (closes: Bug#77425) - Makefiles: clean is a bit cleaner - release.sh (i386): also put kernel configs in TOP/ (hey, it's a small file); don't leave stranded release/kernel-config file, put it in the bf-common tarball - rootdisk.sh: add pcd0 device mknod (closes: Bug#74322), which MAKEDEV doesn't know about; add gscd and cm206cd devices; remove some hacks on device creation due to bugs fixed in MAKEDEV - dbootstrap: quiet bootarg makes more things shut up; disable the check for
Bug#49172: marked as done ([cvs-fixed] problems with floppy booting on sun4c)
Your message dated 21 Nov 2000 00:26:01 -0500 with message-id <[EMAIL PROTECTED]> and subject line bugs closed in boot-floppies 2.2.18 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.) Darren Benham (administrator, Debian Bugs database) -- Received: (at submit) by bugs.debian.org; 4 Nov 1999 15:39:38 + Received: (qmail 25136 invoked from network); 4 Nov 1999 15:39:36 - Received: from homity-pie.lmu.ac.uk ([EMAIL PROTECTED]) by master.debian.org with SMTP; 4 Nov 1999 15:39:36 - Received: from (homity-pie) [160.9.128.1] (nigel) by homity-pie.lmu.ac.uk with smtp (Exim 1.82 #2) id 11jP0F-00062l-00; Thu, 4 Nov 1999 15:40:43 + Date: Thu, 4 Nov 1999 15:40:43 + (GMT) From: "Nigel R. Armfield" <[EMAIL PROTECTED]> X-Sender: nigel@homity-pie Reply-To: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Boot problems Message-ID: Return-Receipt-To: [EMAIL PROTECTED] Acknowledge-To: [EMAIL PROTECTED] MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Package: boot-floppies Version: sparc 2.1 Hi, I'm sorry to bother you with this problem, but I cannot find answers elsewhere and I'm reaching the limits of my patience. I have not had any success at all booting a SPARC (IPX) from any of the rescue boot images that I have tried. I have tried a number of different floppies, formatted them and written them a number of times but all with the same result. At the Sparc boot prompt, I do a 'b floppy', the floppy fires-up, spells out 'SILO' one char at a time and then says: Fatal error: Cannot read partition Illegal or malformed device name Fatal error: Cannot read partition Fatal error: Cannot read partition Image not found try again Any pointers in the right direction would be very gratefully received - apologies if I haven't read the doc properly. Best wishes, Nigel --- Nigel R. Armfield M.Sc, MIEEE [EMAIL PROTECTED] Communications Manager [EMAIL PROTECTED] Computing and Communication Services Learning and Information Services Leeds Metropolitan University Voice: +44 113 283 3119 LEEDS LS1 3HE Fax: +44 113 283 5962 UK --- Received: (at 49172-done) by bugs.debian.org; 21 Nov 2000 05:25:23 + >From [EMAIL PROTECTED] Mon Nov 20 23:25:23 2000 Return-path: <[EMAIL PROTECTED]> Received: from (burrito.onshore.com) [64.22.101.122] (postfix) by master.debian.org with esmtp (Exim 3.12 1 (Debian)) id 13y5vm-0004F0-00; Mon, 20 Nov 2000 23:25:22 -0600 Received: from arroz.fake (localhost [127.0.0.1]) by burrito.onshore.com (Postfix) with ESMTP id CCB6F93802; Tue, 21 Nov 2000 00:26:01 -0500 (EST) Sender: [EMAIL PROTECTED] To: [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED] Subject: bugs closed in boot-floppies 2.2.18 From: Adam Di Carlo <[EMAIL PROTECTED]> Date: 21 Nov 2000 00:26:01 -0500 Message-ID: <[EMAIL PROTECTED]> Lines: 72 User-Agent: Gnus/5.0807 (Gnus v5.8.7) Emacs/20.7 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Delivered-To: [EMAIL PROTECTED] The bug you filed against the boot-floppies package has been closed in the most recent boot-floppies, 2.2.18, now in Potato (for i386 anyhow). The changelog for that version is included. Please let us know if you still have the problem, even in the newest version. Thank you for helping Debian build a better installation systenm. -- .Adam Di [EMAIL PROTECTED]http://www.onShore.com/> boot-floppies (2.2.18) stable; urgency=low . * build with Debian 2.2r1 plus updates (closes: Bug#77459) * Adam Di Carlo: - i386 and sparc use kernel 2.2.18pre21 (closes: Bug#77425) - Makefiles: clean is a bit cleaner - release.sh (i386): also put kernel configs in TOP/ (hey, it's a small file); don't leave stranded release/kernel-config file, put it in the bf-common tarball - rootdisk.sh: add pcd0 device mknod (closes: Bug#74322), which MAKEDEV doesn't know about; add gscd and cm206cd devices; remove some hacks on device creation due to bugs fixed in MAKEDEV - dbootstrap: quiet bootarg makes more things shut up; disable the check for root filesystem being on extended partition while LILO is
Bug#64823: marked as done (incorrect LILO automatic placement on i386)
Your message dated 21 Nov 2000 00:26:01 -0500
with message-id <[EMAIL PROTECTED]>
and subject line bugs closed in boot-floppies 2.2.18
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.)
Darren Benham
(administrator, Debian Bugs database)
--
Received: (at submit) by bugs.debian.org; 28 May 2000 14:50:39 +
>From [EMAIL PROTECTED] Sun May 28 09:50:38 2000
Return-path: <[EMAIL PROTECTED]>
Received: from lyoserv1.in2p3.fr [134.158.138.100]
by master.debian.org with esmtp (Exim 3.12 2 (Debian))
id 12w4Oh-0001MF-00; Sun, 28 May 2000 09:50:36 -0500
Received: from ipnl.in2p3.fr ([EMAIL PROTECTED] [134.158.139.140])
by lyoserv1.in2p3.fr (8.9.1a/8.9.1) with ESMTP id QAA25946;
Sun, 28 May 2000 16:50:29 +0200 (MET DST)
Message-Id: <[EMAIL PROTECTED]>
Date: Sun, 28 May 2000 16:50:26 +0200 (CEST)
From: [EMAIL PROTECTED]
Subject: incorrect LILO automatic placement on i386
To: [EMAIL PROTECTED]
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Delivered-To: [EMAIL PROTECTED]
Package: boot-floppies
Version: 2.2.13-2000-05-04
Severity: critical
Hello,
I have a disk ``factory clean'' with no MBR.
No primary partition on the disk, only logical. / = /dev/hda6
I plan to install LILO on the MBR. The install procedure will not let me
do that, It give me only the option to install LILO somewhere it can't be
reached.
==> System won't restart.
Here is what I did :
The disk is formatted like this :
Disk /dev/hda: 255 heads, 63 sectors, 1027 cylinders
Units = cylinders of 16065 * 512 bytes
Device BootStart EndBlocks Id System
/dev/hda1 1 1027 82493465 Extended
/dev/hda5 131248944+ 82 Linux swap
/dev/hda632 298 2144646 83 Linux
/dev/hda7 299 541 1951866 83 Linux
/dev/hda8 542 784 1951866 83 Linux
/dev/hda9 785 1027 1951866 83 Linux
I choose "make linux directly bootable from hard disk"
Then a dialog box says my disk is factory clean.
Then a dialog box asks for an MBR. I answer no
then another dialog ask for where to put lilo. I answer on the MBR.
Then a dialog says to me I have to install on /dev/hda1, and it does install
on /dev/hda1. The message goes like this :
The boot partition is a logical partition. It can't boot from there, so you
must install the MBR in one of the following extended partitions. Please
select the partition to use.
/dev/hda1
This is very bad because :
1) I have no MBR
2) even if I had one, /dev/hda1 is not marked as bootable, and it is
not automagically marked as bootable. I could not make /dev/hda1
bootable because cfdisk did not show the extended partition.
The system did not reboot. that's why I though the severity should be
set to critical. I had an "insert system disk" message from the PC bios.
I manage to finish the installation like this : I reboot with the boot
floppies, typing "linux root=/dev/hda6" at the boot prompt. After system
installation complete, I edit lilo.conf to install LILO on the mbr :
boot=/dev/hda. I run lilo and everything goes well.
Christophe
--
char*p="[)1++11+(QI1)9191991)9)1)(II1)919Y91)9)1)(AK+9;991+3*(9I1*IY991)Q1\
)(1I1))A91991)Q1)(+)1)1++9;)Q1+(";main(_){while(*p){for(_=*p-32>>3;_;--_)
putchar(' ');if(!(_=*p++-32&7))putchar('\n');else while(_--)printf("_/");}}
---
Received: (at 64823-done) by bugs.debian.org; 21 Nov 2000 05:25:23 +
>From [EMAIL PROTECTED] Mon Nov 20 23:25:23 2000
Return-path: <[EMAIL PROTECTED]>
Received: from (burrito.onshore.com) [64.22.101.122] (postfix)
by master.debian.org with esmtp (Exim 3.12 1 (Debian))
id 13y5vm-0004F0-00; Mon, 20 Nov 2000 23:25:22 -0600
Received: from arroz.fake (localhost [127.0.0.1])
by burrito.onshore.com (Postfix) with ESMTP
id CCB6F93802; Tue, 21 Nov 2000 00:26:01 -0500 (EST)
Sender: [EMAIL PROTECTED]
To: [EMAIL PROTECTED], [EMAIL PROTECTED],
[EMAIL PROTECTED], [EMAIL PROTECTED],
[EMAIL PROTECTED], [EMAIL PROTECTED],
[EMAIL PROTECTED], [EMAIL PROTECTED],
[EMAIL PROTECTED], [EMAIL PROTECTED],
[EMAIL PROTECTED], [EMAIL PROTECTED]
Subject: bugs closed in boot-floppies 2.2.18
From: Adam Di Carlo <[EMAIL PROTECTED]>
Date: 21 Nov 2000 00:26:01 -0500
Message-ID: <[EMAIL PROTECTED]>
Lines: 72
User-Agent: Gnus/5.0807 (Gnus v5.8.7) Emacs/20.7
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Delivered-To: [EMAIL PROTECTED]
The bug you filed against the boo
Bug#63198: marked as done (boot-floppies: Don't put the lilo boot record in the extended partition)
Your message dated 21 Nov 2000 00:26:01 -0500 with message-id <[EMAIL PROTECTED]> and subject line bugs closed in boot-floppies 2.2.18 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.) Darren Benham (administrator, Debian Bugs database) -- Received: (at submit) by bugs.debian.org; 28 Apr 2000 08:25:57 + Received: (qmail 32462 invoked from network); 28 Apr 2000 08:25:55 - Received: from tabaluga.ipe.uni-stuttgart.de (129.69.22.180) by master.debian.org with SMTP; 28 Apr 2000 08:25:55 - Received: (from nils@localhost) by tabaluga.ipe.uni-stuttgart.de (8.9.3/8.9.3/Debian 8.9.3-21) id KAA17609; Fri, 28 Apr 2000 10:25:04 +0200 Date: Fri, 28 Apr 2000 10:25:04 +0200 Message-Id: <[EMAIL PROTECTED]> From: <[EMAIL PROTECTED]> Subject: boot-floppies: Don't put the lilo boot record in the extended partition To: [EMAIL PROTECTED] X-Mailer: bug 3.2.10 Package: boot-floppies Version: N/A Severity: wishlist If the user wants lilo in the MBR, put it there and omit every check about logical partitions and the like. lilo in the MBR is able to start boot from about everywhere. -- System Information Debian Release: 2.2 Kernel Version: Linux tabaluga 2.2.13pre18 #4 Wed Oct 20 20:50:46 CEST 1999 i586 unknown --- Received: (at 64823-done) by bugs.debian.org; 21 Nov 2000 05:25:23 + >From [EMAIL PROTECTED] Mon Nov 20 23:25:23 2000 Return-path: <[EMAIL PROTECTED]> Received: from (burrito.onshore.com) [64.22.101.122] (postfix) by master.debian.org with esmtp (Exim 3.12 1 (Debian)) id 13y5vm-0004F0-00; Mon, 20 Nov 2000 23:25:22 -0600 Received: from arroz.fake (localhost [127.0.0.1]) by burrito.onshore.com (Postfix) with ESMTP id CCB6F93802; Tue, 21 Nov 2000 00:26:01 -0500 (EST) Sender: [EMAIL PROTECTED] To: [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED] Subject: bugs closed in boot-floppies 2.2.18 From: Adam Di Carlo <[EMAIL PROTECTED]> Date: 21 Nov 2000 00:26:01 -0500 Message-ID: <[EMAIL PROTECTED]> Lines: 72 User-Agent: Gnus/5.0807 (Gnus v5.8.7) Emacs/20.7 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Delivered-To: [EMAIL PROTECTED] The bug you filed against the boot-floppies package has been closed in the most recent boot-floppies, 2.2.18, now in Potato (for i386 anyhow). The changelog for that version is included. Please let us know if you still have the problem, even in the newest version. Thank you for helping Debian build a better installation systenm. -- .Adam Di [EMAIL PROTECTED]http://www.onShore.com/> boot-floppies (2.2.18) stable; urgency=low . * build with Debian 2.2r1 plus updates (closes: Bug#77459) * Adam Di Carlo: - i386 and sparc use kernel 2.2.18pre21 (closes: Bug#77425) - Makefiles: clean is a bit cleaner - release.sh (i386): also put kernel configs in TOP/ (hey, it's a small file); don't leave stranded release/kernel-config file, put it in the bf-common tarball - rootdisk.sh: add pcd0 device mknod (closes: Bug#74322), which MAKEDEV doesn't know about; add gscd and cm206cd devices; remove some hacks on device creation due to bugs fixed in MAKEDEV - dbootstrap: quiet bootarg makes more things shut up; disable the check for root filesystem being on extended partition while LILO is going on the MBR, because LILO supports this now (closes: Bug#64823); add new fullscreen_execlog utility function - debian/control: add Build-Depends and Build-Depends-Indep (closes: Bug#70387); remove required package from depends - documentation: fix links to dselect-beginner (closes: Bug#72870); add a section in the first chapter talking about where to get Debian (closes: Bug#71532); other corrections (closes: Bug#70871); fix linux history link (closes: Bug#76408); enable Polish and Russian documentation now that newer debiandoc-sgml is in Potato; give example TFTP file name on SPARC (closes: Bug#40775); mention problems with booting from IPX (closes: Bug#49172); when reporting bugs on i386, you must report the flavor * Josip Rodin: - documentation: update non-US package numbers * Eric VanBuggenhaut: French updates * Marcin Owsiany <[EMAIL PROTECTED]>: - Polish updates - documentation/doc-check scri
Bug#65606: marked as done (No installation of LILO to logical partition?)
Your message dated 21 Nov 2000 00:26:01 -0500 with message-id <[EMAIL PROTECTED]> and subject line bugs closed in boot-floppies 2.2.18 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.) Darren Benham (administrator, Debian Bugs database) -- Received: (at submit) by bugs.debian.org; 13 Jun 2000 22:54:51 + >From [EMAIL PROTECTED] Tue Jun 13 17:54:51 2000 Return-path: <[EMAIL PROTECTED]> Received: from mtiwmhc21.worldnet.att.net [204.127.131.46] by master.debian.org with esmtp (Exim 3.12 2 (Debian)) id 131za7-0006KP-00; Tue, 13 Jun 2000 17:54:51 -0500 Received: from worldnet.att.net ([12.76.68.39]) by mtiwmhc21.worldnet.att.net (InterMail vM.4.01.02.39 201-229-119-122) with ESMTP id <[EMAIL PROTECTED]> for <[EMAIL PROTECTED]>; Tue, 13 Jun 2000 22:54:20 + Sender: thully Message-ID: <[EMAIL PROTECTED]> Date: Tue, 13 Jun 2000 18:56:35 -0400 From: Tim Hull <[EMAIL PROTECTED]> X-Mailer: Mozilla 4.73 [en] (X11; I; Linux 2.2.15 i686) X-Accept-Language: en MIME-Version: 1.0 To: [EMAIL PROTECTED] Subject: No installation of LILO to logical partition? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Delivered-To: [EMAIL PROTECTED] Package: base Version: 2.2.15-06-07 When I installed Debian "potato" I was not allowed to install LILO to a logical partition. It says LILO can't be installed there, but in fact it can. I reconfigured LILO after install to lie in the logical partition ,and it worked. This may or may not work with all sotck Debian bootloaders, but I can boot the logical partition with BootMagic(non-free program) and I think I can use xosl (xosl.org) to boot it also. I think the installer should permit installation of LILO to a logical partition. --- Received: (at 64823-done) by bugs.debian.org; 21 Nov 2000 05:25:23 + >From [EMAIL PROTECTED] Mon Nov 20 23:25:23 2000 Return-path: <[EMAIL PROTECTED]> Received: from (burrito.onshore.com) [64.22.101.122] (postfix) by master.debian.org with esmtp (Exim 3.12 1 (Debian)) id 13y5vm-0004F0-00; Mon, 20 Nov 2000 23:25:22 -0600 Received: from arroz.fake (localhost [127.0.0.1]) by burrito.onshore.com (Postfix) with ESMTP id CCB6F93802; Tue, 21 Nov 2000 00:26:01 -0500 (EST) Sender: [EMAIL PROTECTED] To: [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED] Subject: bugs closed in boot-floppies 2.2.18 From: Adam Di Carlo <[EMAIL PROTECTED]> Date: 21 Nov 2000 00:26:01 -0500 Message-ID: <[EMAIL PROTECTED]> Lines: 72 User-Agent: Gnus/5.0807 (Gnus v5.8.7) Emacs/20.7 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Delivered-To: [EMAIL PROTECTED] The bug you filed against the boot-floppies package has been closed in the most recent boot-floppies, 2.2.18, now in Potato (for i386 anyhow). The changelog for that version is included. Please let us know if you still have the problem, even in the newest version. Thank you for helping Debian build a better installation systenm. -- .Adam Di [EMAIL PROTECTED]http://www.onShore.com/> boot-floppies (2.2.18) stable; urgency=low . * build with Debian 2.2r1 plus updates (closes: Bug#77459) * Adam Di Carlo: - i386 and sparc use kernel 2.2.18pre21 (closes: Bug#77425) - Makefiles: clean is a bit cleaner - release.sh (i386): also put kernel configs in TOP/ (hey, it's a small file); don't leave stranded release/kernel-config file, put it in the bf-common tarball - rootdisk.sh: add pcd0 device mknod (closes: Bug#74322), which MAKEDEV doesn't know about; add gscd and cm206cd devices; remove some hacks on device creation due to bugs fixed in MAKEDEV - dbootstrap: quiet bootarg makes more things shut up; disable the check for root filesystem being on extended partition while LILO is going on the MBR, because LILO supports this now (closes: Bug#64823); add new fullscreen_execlog utility function - debian/control: add Build-Depends and Build-Depends-Indep (closes: Bug#70387); remove required package from depends - documentation: fix links to dselect-beginner (closes: Bug#72870); add a section in the first chapter talking about where to get Debian (closes: Bug#71532); other corrections (closes: Bug#70871); fix linux hi
Bug#70387: marked as done ([CVS-fixed] build dependancy for debhelper)
Your message dated 21 Nov 2000 00:26:01 -0500 with message-id <[EMAIL PROTECTED]> and subject line bugs closed in boot-floppies 2.2.18 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.) Darren Benham (administrator, Debian Bugs database) -- Received: (at maintonly) by bugs.debian.org; 28 Aug 2000 02:30:39 + >From [EMAIL PROTECTED] Sun Aug 27 21:30:38 2000 Return-path: <[EMAIL PROTECTED]> Received: from (ngi.de) [:::195.243.0.244] by master.debian.org with smtp (Exim 3.12 1 (Debian)) id 13TEh4-0002lN-00; Sun, 27 Aug 2000 21:30:38 -0500 Received: (qmail 30497 invoked from network); 28 Aug 2000 02:25:11 - Received: from p3e9e1487.dip0.t-ipconnect.de (HELO dual.intern.brederlow.de) (62.158.20.135) by 195.243.0.244 with SMTP; 28 Aug 2000 02:25:11 - Received: from mrvn by dual.intern.brederlow.de with local (Exim 3.12 #1 (Debian)) id 13TMB0-0003yt-00 for <[EMAIL PROTECTED]>; Mon, 28 Aug 2000 12:30:02 +0200 From: Goswin Brederlow <[EMAIL PROTECTED]> To: Debian Bug Tracking System <[EMAIL PROTECTED]> Subject: automatic build fails for potato Message-Id: <[EMAIL PROTECTED]> Date: Mon, 28 Aug 2000 12:30:02 +0200 Delivered-To: [EMAIL PROTECTED] Package: boot-floppies Version: N/A; reported 2000-08-28 Severity: normal *** explain.txt I compiled all packages that have no "Build-Depends" in potato/main/Sources.gz. Your package failed to build together with about 1700 other packages. Since you have no "Build-Depends" you eigther forgot that your package build-depends on something (like debhelper?) or you don't know about build dependencies. The releavnt fields are descibed in: http://www.at.debian.org/doc/packaging-manuals/packaging.html/ch-relationships.html#s8.7 Please add build dependencies to your package or correct what ever else caused the package not to build. If you already did so for woody, please just close this bug report. If your Package is one of the rare cases with a Build-Depends-Indep and I overlooked it, also please just close. May the Source be with you. Goswin The compilation logfiles follows: *** boot-floppies/boot-floppies.log Reading Package Lists... Building Dependency Tree... Need to get 2666kB of source archives. Get:1 ftp://alpha potato/main boot-floppies 2.2.16 (dsc) [605B] Get:2 ftp://alpha potato/main boot-floppies 2.2.16 (tar) [2665kB] Fetched 2666kB in 2s (897kB/s) dpkg-source: extracting boot-floppies in boot-floppies-2.2.16 dpkg-source: extracting boot-floppies in boot-floppies-2.2.16 dpkg-buildpackage: source package is boot-floppies dpkg-buildpackage: source version is 2.2.16 dpkg-buildpackage: source maintainer is Adam Di Carlo <[EMAIL PROTECTED]> debian/rules clean DEB_BUILD_ARCH=i386 DEB_BUILD_GNU_CPU=i386 DEB_BUILD_GNU_SYSTEM=linux DEB_BUILD_GNU_TYPE=i386-linux DEB_HOST_ARCH=i386 DEB_HOST_GNU_CPU=i386 DEB_HOST_GNU_SYSTEM=linux DEB_HOST_GNU_TYPE=i386-linux test -f rootdisk.sh -a -f debian/rules make -i distclean find: /archive/debian/Incoming/: No such file or directory find: /archive/debian/local/: No such file or directory find: /archive/debian/dists/potato/main/binary-i386: No such file or directory make[1]: Entering directory `/mnt/raid0/builder/tmp/boot-floppies-2.2.16' make -C utilities distclean make[2]: Entering directory `/mnt/raid0/builder/tmp/boot-floppies-2.2.16/utilities' rm -f *.o *.bak set -e; for i in libfdisk dbootstrap busybox writemaps lowmemrd; do make -C $i clean; done make[3]: Entering directory `/mnt/raid0/builder/tmp/boot-floppies-2.2.16/utilities/libfdisk' rm -f fdisk.o partbl_msdos.o partbl_osf.o partbl_sun.o partbl_amiga.o partbl_atari.o partbl_mac.o libfdisk.a testing.o make[3]: Leaving directory `/mnt/raid0/builder/tmp/boot-floppies-2.2.16/utilities/libfdisk' make[3]: Entering directory `/mnt/raid0/builder/tmp/boot-floppies-2.2.16/utilities/dbootstrap' set -e; \ touch -a lang.h; \ echo ".depend/util : util.c" > .depend/util; \ echo >> .depend/util; \ gcc -MM -D_GNU_SOURCE -DBUILDTIME='"2000.08.28-05:17+"' -DARCH='"i386"' -DARCHNAME='"i386"' -DKERNEL_VERSION_CODE=131584 -DKVER='""' util.c | \ sed -e 's,\(util\)\.o[ :]*,\1.o \1.test.o : ,g' | \ sed -e 's,\(util\.c\),.translated/\1,' >> .depend/util; \ touch -m .depend/util; set -e; \ touch -a lang.h; \ echo ".depend/tzconfig : tzconfig.c" > .depend/tzconfig; \ echo >> .depend/tzconfig; \ gcc -MM -D_GNU_SOURCE -D
Bug#70871: marked as done ([CVS-fixed] kernel-compilation documentation)
Your message dated 21 Nov 2000 00:26:01 -0500 with message-id <[EMAIL PROTECTED]> and subject line bugs closed in boot-floppies 2.2.18 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.) Darren Benham (administrator, Debian Bugs database) -- Received: (at submit) by bugs.debian.org; 4 Sep 2000 07:20:31 + >From [EMAIL PROTECTED] Mon Sep 04 02:20:31 2000 Return-path: <[EMAIL PROTECTED]> Received: from mgate2.uni-hannover.de [:::130.75.2.5] by master.debian.org with esmtp (Exim 3.12 1 (Debian)) id 13VqYR-0002Y5-00; Mon, 04 Sep 2000 02:20:31 -0500 Received: from wega.itp.uni-hannover.de by mgate2.uni-hannover.de with LocalSMTP (PP) with ESMTP; Mon, 4 Sep 2000 09:19:38 +0200 Received: from mirzam.itp.uni-hannover.de (mirzam.itp.uni-hannover.de [130.75.25.94]) by wega.itp.uni-hannover.de (AIX4.3/UCB 8.8.8/8.8.8) with ESMTP id JAA05578 for <[EMAIL PROTECTED]>; Mon, 4 Sep 2000 09:19:37 +0200 Received: (from kreutzm@localhost) by mirzam.itp.uni-hannover.de (8.9.3/8.9.3) id JAA20633 for [EMAIL PROTECTED]; Mon, 4 Sep 2000 09:19:37 +0200 Date: Mon, 4 Sep 2000 09:19:37 +0200 From: Helge Kreutzmann <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Subject: kernel-compilation documentation Message-ID: <[EMAIL PROTECTED]> X-Mailer: Mutt 1.0i X-Public-Key-URL: http://www.itp.uni-hannover.de/~kreutzm/data/kreutzm.gpg X-homepage: http://www.itp.uni-hannover.de/~kreutzm X-Operating-System: Linux mirzam.itp.uni-hannover.de 2.2.16 MIME-version: 1.0 Content-type: multipart/signed; boundary="32u276st3Jlj2kUU"; micalg="pgp-md5"; protocol="application/pgp-signature" Delivered-To: [EMAIL PROTECTED] --32u276st3Jlj2kUU Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Package: boot-floppies version: potatoe documentation as shipped on CD (alpha) Hello ! In the section regarding kernel compilation (8.4): -/usr/sbin/make-kpkg is wrong. make-kpkg is installed in /usr/bin -The documentation indicates that a seperat package is build for the modules: If you have created a modules package, you'll need to install that package= as well. I am new to debian, so maybe I made some mistake, but I created modules together with the kernel and they were included all in one deb-package. Maybe the documentation should indicate that possibility. -More a wish but I think you could mention that ncurses-XX-dev (the dev is the important one) is required for make menuconfig, though of course you correctly refer to the full documentation. -Lastly if such docu does exist, as a person new to debian I would have greatly appreciate references to documentation about general topics which are handled "the Debian way", e.g. networking, sound install because apropos and man (including info) does not help here much. Greetings and sorry I included the wish-list here. Helge =20 --=20 Helge Kreutzmann, Dipl.-Phys. [EMAIL PROTECTED]= .de For gpg-key: finger [EMAIL PROTECTED] 64bit GNU powered http://www.itp.uni-hannover.de/~kreu= tzm Help keep free software "libre": http://www.freepatents.org/ --32u276st3Jlj2kUU Content-Type: application/pgp-signature -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.2 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE5s00I8gjPnR7H0q0RAdQfAJkB9jlYPK8P/6L7/BMTYO8KHF/QtQCfRf2X RlifIt5PjBKamcgX0SA1ofU= =N8cM -END PGP SIGNATURE- --32u276st3Jlj2kUU-- --- Received: (at 70871-done) by bugs.debian.org; 21 Nov 2000 05:25:23 + >From [EMAIL PROTECTED] Mon Nov 20 23:25:23 2000 Return-path: <[EMAIL PROTECTED]> Received: from (burrito.onshore.com) [64.22.101.122] (postfix) by master.debian.org with esmtp (Exim 3.12 1 (Debian)) id 13y5vm-0004F0-00; Mon, 20 Nov 2000 23:25:22 -0600 Received: from arroz.fake (localhost [127.0.0.1]) by burrito.onshore.com (Postfix) with ESMTP id CCB6F93802; Tue, 21 Nov 2000 00:26:01 -0500 (EST) Sender: [EMAIL PROTECTED] To: [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED] Subject: bugs closed in boot-floppies 2.2.18 From: Adam Di Carlo <[EMAIL PROTECTED]> Date: 21 Nov 2000 00:26:01 -0500 Message-ID: <[EMAIL PROTECTED]> Lines: 72 User-Agent: Gnus/5.0807 (Gnus v5.8.7) Emacs/20.7 MIME-Version: 1.0 Content-Type: te
Bug#71532: marked as done ([CVS-fixed] where to get debian in documentation)
Your message dated 21 Nov 2000 00:26:01 -0500 with message-id <[EMAIL PROTECTED]> and subject line bugs closed in boot-floppies 2.2.18 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.) Darren Benham (administrator, Debian Bugs database) -- Received: (at submit) by bugs.debian.org; 13 Sep 2000 04:24:35 + >From [EMAIL PROTECTED] Tue Sep 12 23:24:35 2000 Return-path: <[EMAIL PROTECTED]> Received: from (email.cu-portland.edu) [:::207.149.56.67] by master.debian.org with esmtp (Exim 3.12 1 (Debian)) id 13Z467-0002Mh-00; Tue, 12 Sep 2000 23:24:35 -0500 Received: by EMAIL with Internet Mail Service (5.5.2650.21) id ; Tue, 12 Sep 2000 21:24:33 -0700 Message-ID: <025836EFF856D411A6660090272811E61D0700@EMAIL> From: Gregory Leblanc <[EMAIL PROTECTED]> To: "'[EMAIL PROTECTED]'" <[EMAIL PROTECTED]> Subject: Installing Debian GNU/Linux 2.2 for Intel x86 Date: Tue, 12 Sep 2000 21:24:33 -0700 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="windows-1252" Delivered-To: [EMAIL PROTECTED] Package: boot-floppies This is a really quick report, I'll dig into more a bit later once I get Debian GNU/Linux installed, but this one seemed to be worthy of note. Nowhere in this document is anything about actually getting Debian GNU/Linux covered. If this is intended to be something that's distributed only with Debian, then it would make sense, but I would place this document as one of the prime locations for new users to Debian. I'd make question 1.5 into "How do I get Debian GNU/Linux?" and have a short section pointing to the rest of the documentation on that topic (which, while easy to find, is not referenced here). Greg --- Received: (at 71532-done) by bugs.debian.org; 21 Nov 2000 05:25:23 + >From [EMAIL PROTECTED] Mon Nov 20 23:25:23 2000 Return-path: <[EMAIL PROTECTED]> Received: from (burrito.onshore.com) [64.22.101.122] (postfix) by master.debian.org with esmtp (Exim 3.12 1 (Debian)) id 13y5vm-0004F0-00; Mon, 20 Nov 2000 23:25:22 -0600 Received: from arroz.fake (localhost [127.0.0.1]) by burrito.onshore.com (Postfix) with ESMTP id CCB6F93802; Tue, 21 Nov 2000 00:26:01 -0500 (EST) Sender: [EMAIL PROTECTED] To: [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED] Subject: bugs closed in boot-floppies 2.2.18 From: Adam Di Carlo <[EMAIL PROTECTED]> Date: 21 Nov 2000 00:26:01 -0500 Message-ID: <[EMAIL PROTECTED]> Lines: 72 User-Agent: Gnus/5.0807 (Gnus v5.8.7) Emacs/20.7 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Delivered-To: [EMAIL PROTECTED] The bug you filed against the boot-floppies package has been closed in the most recent boot-floppies, 2.2.18, now in Potato (for i386 anyhow). The changelog for that version is included. Please let us know if you still have the problem, even in the newest version. Thank you for helping Debian build a better installation systenm. -- .Adam Di [EMAIL PROTECTED]http://www.onShore.com/> boot-floppies (2.2.18) stable; urgency=low . * build with Debian 2.2r1 plus updates (closes: Bug#77459) * Adam Di Carlo: - i386 and sparc use kernel 2.2.18pre21 (closes: Bug#77425) - Makefiles: clean is a bit cleaner - release.sh (i386): also put kernel configs in TOP/ (hey, it's a small file); don't leave stranded release/kernel-config file, put it in the bf-common tarball - rootdisk.sh: add pcd0 device mknod (closes: Bug#74322), which MAKEDEV doesn't know about; add gscd and cm206cd devices; remove some hacks on device creation due to bugs fixed in MAKEDEV - dbootstrap: quiet bootarg makes more things shut up; disable the check for root filesystem being on extended partition while LILO is going on the MBR, because LILO supports this now (closes: Bug#64823); add new fullscreen_execlog utility function - debian/control: add Build-Depends and Build-Depends-Indep (closes: Bug#70387); remove required package from depends - documentation: fix links to dselect-beginner (closes: Bug#72870); add a section in the first chapter talking about where to get Debian (closes: Bug#71532); other corrections (closes: Bug#70871); fix linux history link (closes: Bug#76408); enable P
Bug#72870: marked as done ([CVS-fixed] Broken links in Debian installation docs)
Your message dated 21 Nov 2000 00:26:01 -0500 with message-id <[EMAIL PROTECTED]> and subject line bugs closed in boot-floppies 2.2.18 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.) Darren Benham (administrator, Debian Bugs database) -- Received: (at submit) by bugs.debian.org; 30 Sep 2000 22:00:30 + >From [EMAIL PROTECTED] Sat Sep 30 17:00:30 2000 Return-path: <[EMAIL PROTECTED]> Received: from oracle.clara.net [:::195.8.69.94] by master.debian.org with esmtp (Exim 3.12 1 (Debian)) id 13fUgH-JV-00; Sat, 30 Sep 2000 17:00:29 -0500 Received: from [195.8.92.184] (helo=-) by oracle.clara.net with smtp (Exim 2.12 #2) id 13fUgC-000CdF-00; Sat, 30 Sep 2000 23:00:26 +0100 Date: Sat, 30 Sep 2000 22:59:02 +0100 From: Bernie <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Subject: Broken links in HTML version of Debian installation docs MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Mailer: Becky! ver 1.25.07 Message-Id: <[EMAIL PROTECTED]> Delivered-To: [EMAIL PROTECTED] Package: boot-floppies Version: 2.2.16 I hope I get the version number correct, it is the one printed at the bottom of the HTML pages: Installing Debian GNU/Linux 2.2 For Intel x86 version 2.2.16, 05 July, 2000 There are three broken links to the "dselect Tutorial" from these pages. [Until Debian is installed, I am viewing the pages with IE3 on MS Windows 95 and "Debian GNU/Linux 2.2 rev 0 Binary CD 1 Non-US" is mounted in the H: drive.] The page H:\install\doc\ch-init-config.en.html has 2 broken links to: file:H:\install\doc\dselect-beginner.html The page H:\install\doc\ch-preparing.en.html has 1 broken link to: file:H:\install\doc\dselect-beginner$langext.html The page H:\install\doc\index.en.html has 1 working link to: file:H:\install\doc\dselect-beginner.en.html FWIW, the working link appears as the "dselect Beginner's Guide" whereas the 2 broken links appear as the "dselect Tutorial". The page H:\install\doc\index.en.html also has broken links to: file:H:\install\doc\dselect-beginner.pdf file:H:\install\doc\dselect-beginner.txt file:H:\install\doc\release-notes.en.html Here is a listing of \install\doc; (Note too, that index.html is 0 bytes.) total 770 -r--r--r-- 1 dosuser root18486 Jul 20 02:15 cfdisk.txt -r--r--r-- 1 dosuser root 4916 Jul 5 18:56 ch-administrivia.en.html -r--r--r-- 1 dosuser root 4864 Jul 5 18:56 ch-appendix.en.html -r--r--r-- 1 dosuser root 4041 Jul 5 18:56 ch-boot-floppy-techinfo.en.html -r--r--r-- 1 dosuser root 2036 Aug 3 16:23 ch-dselect-conclusion.en.html -r--r--r-- 1 dosuser root 1773 Aug 3 16:23 ch-dselect-glossary.en.html -r--r--r-- 1 dosuser root 2407 Jul 5 18:56 ch-dselect-intro.en.html -r--r--r-- 1 dosuser root21119 Jul 5 18:56 ch-dselect-main.en.html -r--r--r-- 1 dosuser root18462 Jul 5 18:55 ch-hardware-req.en.html -r--r--r-- 1 dosuser root37130 Jul 5 18:56 ch-init-config.en.html -r--r--r-- 1 dosuser root32284 Jul 5 18:55 ch-install-methods.en.html -r--r--r-- 1 dosuser root24502 Jul 5 18:55 ch-partitioning.en.html -r--r--r-- 1 dosuser root12283 Jul 5 18:56 ch-post-install.en.html -r--r--r-- 1 dosuser root14384 Jul 5 18:55 ch-preparing.en.html -r--r--r-- 1 dosuser root16303 Jul 5 18:55 ch-rescue-boot.en.html -r--r--r-- 1 dosuser root16576 Jul 5 18:55 ch-welcome.en.html drwxr-xr-x 2 dosuser root 2048 Aug 14 07:31 cs/ drwxr-xr-x 2 dosuser root 2048 Aug 14 07:31 de/ -r--r--r-- 1 dosuser root 952 Aug 3 16:23 dselect-beginner.en.html -r--r--r-- 1 dosuser root24193 Jul 5 18:56 dselect-beginner.en.txt drwxr-xr-x 2 dosuser root 4096 Aug 14 07:31 es/ -r--r--r-- 1 dosuser root10193 Aug 3 16:23 fdisk.txt drwxr-xr-x 2 dosuser root 2048 Aug 14 07:31 fi/ -r--r--r-- 1 dosuser root 1771 Jul 5 18:56 footnotes.en.html drwxr-xr-x 2 dosuser root 2048 Aug 14 07:31 fr/ drwxr-xr-x 2 dosuser root 4096 Aug 14 07:31 hr/ -r--r--r-- 1 dosuser root 3729 Jul 5 18:55 index.en.html -r--r--r-- 1 dosuser root0 Jul 5 18:55 index.html -r--r--r-- 1 dosuser root10627 Jul 5 18:55 install.en.html -r--r--r-- 1 dosuser root 287398 Jul 5 18:57 install.en.pdf -r--r--r-- 1 dosuser root 174826 Jul 5 18:55 install.en.txt dr
Bug#74322: marked as done ([cvs-fixed] boot-floppies: in installation /dev/pcd0 device isn't created)
Your message dated 21 Nov 2000 00:26:01 -0500 with message-id <[EMAIL PROTECTED]> and subject line bugs closed in boot-floppies 2.2.18 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.) Darren Benham (administrator, Debian Bugs database) -- Received: (at submit) by bugs.debian.org; 8 Oct 2000 11:04:30 + >From [EMAIL PROTECTED] Sun Oct 08 06:04:30 2000 Return-path: <[EMAIL PROTECTED]> Received: from kauha.saunalahti.fi [:::195.197.53.227] by master.debian.org with esmtp (Exim 3.12 1 (Debian)) id 13iEFq-0002nH-00; Sun, 08 Oct 2000 06:04:30 -0500 Received: from penguin.lake.fi (MCCXXXI.rdyn.saunalahti.fi [195.197.137.31]) by kauha.saunalahti.fi (8.10.1/8.10.1) with ESMTP id e98B78J15430 for <[EMAIL PROTECTED]>; Sun, 8 Oct 2000 14:07:11 +0300 (EEST) Received: from habazi by penguin.lake.fi with local (Exim 3.12 #1 (Debian)) id 13iBsP-0004tS-00; Sun, 08 Oct 2000 11:32:09 +0300 From: Harri Järvi <[EMAIL PROTECTED]> Subject: boot-floppies: in installation /dev/pcd0 device isn't created To: [EMAIL PROTECTED] X-Mailer: bug 3.2.10 Message-Id: <[EMAIL PROTECTED]> Date: Sun, 08 Oct 2000 11:32:09 +0300 Delivered-To: [EMAIL PROTECTED] Package: boot-floppies Version: N/A Severity: normal Background: I installed Debian 2.2 on a system with a cdrw-drive attached to parallel port. I was glad the drivers-disks included drivers for paride and epat and pcd so that I could install using the cdrw-drive. Bug: /dev/cdrom was correctly linked to pcd0 but there was no /dev/pcd0 My workaround: I created it myself with mknod /dev/pcd0 b 46 0 Solution: make the installation create that device-file automatically -- System Information Debian Release: 2.2 Kernel Version: Linux penguin 2.4.0-test7 #4 SMP su loka 1 11:23:22 EEST 2000 i586 unknown --- Received: (at 74322-done) by bugs.debian.org; 21 Nov 2000 05:25:23 + >From [EMAIL PROTECTED] Mon Nov 20 23:25:23 2000 Return-path: <[EMAIL PROTECTED]> Received: from (burrito.onshore.com) [64.22.101.122] (postfix) by master.debian.org with esmtp (Exim 3.12 1 (Debian)) id 13y5vm-0004F0-00; Mon, 20 Nov 2000 23:25:22 -0600 Received: from arroz.fake (localhost [127.0.0.1]) by burrito.onshore.com (Postfix) with ESMTP id CCB6F93802; Tue, 21 Nov 2000 00:26:01 -0500 (EST) Sender: [EMAIL PROTECTED] To: [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED] Subject: bugs closed in boot-floppies 2.2.18 From: Adam Di Carlo <[EMAIL PROTECTED]> Date: 21 Nov 2000 00:26:01 -0500 Message-ID: <[EMAIL PROTECTED]> Lines: 72 User-Agent: Gnus/5.0807 (Gnus v5.8.7) Emacs/20.7 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Delivered-To: [EMAIL PROTECTED] The bug you filed against the boot-floppies package has been closed in the most recent boot-floppies, 2.2.18, now in Potato (for i386 anyhow). The changelog for that version is included. Please let us know if you still have the problem, even in the newest version. Thank you for helping Debian build a better installation systenm. -- .Adam Di [EMAIL PROTECTED]http://www.onShore.com/> boot-floppies (2.2.18) stable; urgency=low . * build with Debian 2.2r1 plus updates (closes: Bug#77459) * Adam Di Carlo: - i386 and sparc use kernel 2.2.18pre21 (closes: Bug#77425) - Makefiles: clean is a bit cleaner - release.sh (i386): also put kernel configs in TOP/ (hey, it's a small file); don't leave stranded release/kernel-config file, put it in the bf-common tarball - rootdisk.sh: add pcd0 device mknod (closes: Bug#74322), which MAKEDEV doesn't know about; add gscd and cm206cd devices; remove some hacks on device creation due to bugs fixed in MAKEDEV - dbootstrap: quiet bootarg makes more things shut up; disable the check for root filesystem being on extended partition while LILO is going on the MBR, because LILO supports this now (closes: Bug#64823); add new fullscreen_execlog utility function - debian/control: add Build-Depends and Build-Depends-Indep (closes: Bug#70387); remove required package from depends - documentation: fix links to dselect-beginner (closes: Bug#72870); add a section in the first chapter talking about where to get Debian (closes: Bug#71532); other corrections (
Bug#76408: marked as done ([cvs-fixed] bad linux history url in installation guide)
Your message dated 21 Nov 2000 00:26:01 -0500 with message-id <[EMAIL PROTECTED]> and subject line bugs closed in boot-floppies 2.2.18 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.) Darren Benham (administrator, Debian Bugs database) -- Received: (at submit) by bugs.debian.org; 6 Nov 2000 20:16:14 + >From [EMAIL PROTECTED] Mon Nov 06 14:16:13 2000 Return-path: <[EMAIL PROTECTED]> Received: from opensource.lineo.com [:::204.246.147.211] by master.debian.org with esmtp (Exim 3.12 1 (Debian)) id 13ssge-0006rq-00; Mon, 06 Nov 2000 14:16:13 -0600 Received: by opensource.lineo.com (Postfix, from userid 1011) id A8FEB193588; Mon, 6 Nov 2000 13:16:09 -0700 (MST) Date: Mon, 6 Nov 2000 13:16:09 -0700 From: Matt Kraai <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Subject: bad linux history url in installation guide Message-ID: <[EMAIL PROTECTED]> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/1.0.1i Sender: [EMAIL PROTECTED] Delivered-To: [EMAIL PROTECTED] Package: boot-floppies Version: N/A The installation manual contains a link to Linux International's Linux History Page. This page has since moved to http://www.li.org/linuxhistory.php . Please change the url-linux-history in boot-floppies/documentation/urls.ent to this new value. Matt --- Received: (at 76408-done) by bugs.debian.org; 21 Nov 2000 05:25:23 + >From [EMAIL PROTECTED] Mon Nov 20 23:25:23 2000 Return-path: <[EMAIL PROTECTED]> Received: from (burrito.onshore.com) [64.22.101.122] (postfix) by master.debian.org with esmtp (Exim 3.12 1 (Debian)) id 13y5vm-0004F0-00; Mon, 20 Nov 2000 23:25:22 -0600 Received: from arroz.fake (localhost [127.0.0.1]) by burrito.onshore.com (Postfix) with ESMTP id CCB6F93802; Tue, 21 Nov 2000 00:26:01 -0500 (EST) Sender: [EMAIL PROTECTED] To: [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED] Subject: bugs closed in boot-floppies 2.2.18 From: Adam Di Carlo <[EMAIL PROTECTED]> Date: 21 Nov 2000 00:26:01 -0500 Message-ID: <[EMAIL PROTECTED]> Lines: 72 User-Agent: Gnus/5.0807 (Gnus v5.8.7) Emacs/20.7 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Delivered-To: [EMAIL PROTECTED] The bug you filed against the boot-floppies package has been closed in the most recent boot-floppies, 2.2.18, now in Potato (for i386 anyhow). The changelog for that version is included. Please let us know if you still have the problem, even in the newest version. Thank you for helping Debian build a better installation systenm. -- .Adam Di [EMAIL PROTECTED]http://www.onShore.com/> boot-floppies (2.2.18) stable; urgency=low . * build with Debian 2.2r1 plus updates (closes: Bug#77459) * Adam Di Carlo: - i386 and sparc use kernel 2.2.18pre21 (closes: Bug#77425) - Makefiles: clean is a bit cleaner - release.sh (i386): also put kernel configs in TOP/ (hey, it's a small file); don't leave stranded release/kernel-config file, put it in the bf-common tarball - rootdisk.sh: add pcd0 device mknod (closes: Bug#74322), which MAKEDEV doesn't know about; add gscd and cm206cd devices; remove some hacks on device creation due to bugs fixed in MAKEDEV - dbootstrap: quiet bootarg makes more things shut up; disable the check for root filesystem being on extended partition while LILO is going on the MBR, because LILO supports this now (closes: Bug#64823); add new fullscreen_execlog utility function - debian/control: add Build-Depends and Build-Depends-Indep (closes: Bug#70387); remove required package from depends - documentation: fix links to dselect-beginner (closes: Bug#72870); add a section in the first chapter talking about where to get Debian (closes: Bug#71532); other corrections (closes: Bug#70871); fix linux history link (closes: Bug#76408); enable Polish and Russian documentation now that newer debiandoc-sgml is in Potato; give example TFTP file name on SPARC (closes: Bug#40775); mention problems with booting from IPX (closes: Bug#49172); when reporting bugs on i386, you must report the flavor * Josip Rodin: - documentation: update non-US package numbers * Eric VanBuggenhaut: French updates * Marcin Owsiany <[E
Bug#77425: marked as done (boot-floppies: tulip driver in 2.2r0 boot floppies not working)
Your message dated 21 Nov 2000 00:26:01 -0500 with message-id <[EMAIL PROTECTED]> and subject line bugs closed in boot-floppies 2.2.18 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.) Darren Benham (administrator, Debian Bugs database) -- Received: (at submit) by bugs.debian.org; 19 Nov 2000 08:51:19 + >From [EMAIL PROTECTED] Sun Nov 19 02:51:18 2000 Return-path: <[EMAIL PROTECTED]> Received: from sea-pm3-1-p58.wolfenet.com (mail.robhome.dyndns.org) [206.159.28.58] (postfix) by master.debian.org with esmtp (Exim 3.12 1 (Debian)) id 13xQBx-0003Rd-00; Sun, 19 Nov 2000 02:51:18 -0600 Received: from tara.robhome.dyndns.org (tara.mvdomain [10.1.1.66]) by mail.robhome.dyndns.org (Postfix) with ESMTP id 34BBEBBF4; Sun, 19 Nov 2000 00:51:07 -0800 (PST) Received: by tara.robhome.dyndns.org (Postfix, from userid 1000) id 93491171833; Sun, 19 Nov 2000 00:51:04 -0800 (PST) From: Scott Robinson <[EMAIL PROTECTED]> Subject: boot-floppies: tulip driver in 2.2r0 boot floppies not working To: [EMAIL PROTECTED] X-Mailer: bug 3.2.10 Message-Id: <[EMAIL PROTECTED]> Date: Sun, 19 Nov 2000 00:51:04 -0800 (PST) Delivered-To: [EMAIL PROTECTED] Package: boot-floppies Version: N/A Severity: normal I recently installed a new Debian 2.2r0 system using the rescue/root/drivers combo available on the CD Image. I found I could not get my brand new tulip.o based Netgear FA 310TX Fast Ethernet PCI Adapter to work with the 2.2.17pre6 packaged and auto-installed with the boot-floppy. The solution was to get the real 2.2.17 kernel source, but I couldn't get that without 'net access! A dilemma indeed! I ended up pulling out an old SMC Ultra (smc-ultra.o) card and using it to download the latest source and using make-kpkg to generate a proper kernel. This could cause definate problems for people who don't have an alternative net card. I would suggest upgrading the boot-floppies source kernel to the full 2.2.17. Scott. -- System Information Debian Release: 2.2 Kernel Version: Linux tara 2.4.0-test10 #2 Thu Nov 16 16:11:23 PST 2000 i486 unknown --- Received: (at 77425-done) by bugs.debian.org; 21 Nov 2000 05:25:23 + >From [EMAIL PROTECTED] Mon Nov 20 23:25:23 2000 Return-path: <[EMAIL PROTECTED]> Received: from (burrito.onshore.com) [64.22.101.122] (postfix) by master.debian.org with esmtp (Exim 3.12 1 (Debian)) id 13y5vm-0004F0-00; Mon, 20 Nov 2000 23:25:22 -0600 Received: from arroz.fake (localhost [127.0.0.1]) by burrito.onshore.com (Postfix) with ESMTP id CCB6F93802; Tue, 21 Nov 2000 00:26:01 -0500 (EST) Sender: [EMAIL PROTECTED] To: [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED] Subject: bugs closed in boot-floppies 2.2.18 From: Adam Di Carlo <[EMAIL PROTECTED]> Date: 21 Nov 2000 00:26:01 -0500 Message-ID: <[EMAIL PROTECTED]> Lines: 72 User-Agent: Gnus/5.0807 (Gnus v5.8.7) Emacs/20.7 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Delivered-To: [EMAIL PROTECTED] The bug you filed against the boot-floppies package has been closed in the most recent boot-floppies, 2.2.18, now in Potato (for i386 anyhow). The changelog for that version is included. Please let us know if you still have the problem, even in the newest version. Thank you for helping Debian build a better installation systenm. -- .Adam Di [EMAIL PROTECTED]http://www.onShore.com/> boot-floppies (2.2.18) stable; urgency=low . * build with Debian 2.2r1 plus updates (closes: Bug#77459) * Adam Di Carlo: - i386 and sparc use kernel 2.2.18pre21 (closes: Bug#77425) - Makefiles: clean is a bit cleaner - release.sh (i386): also put kernel configs in TOP/ (hey, it's a small file); don't leave stranded release/kernel-config file, put it in the bf-common tarball - rootdisk.sh: add pcd0 device mknod (closes: Bug#74322), which MAKEDEV doesn't know about; add gscd and cm206cd devices; remove some hacks on device creation due to bugs fixed in MAKEDEV - dbootstrap: quiet bootarg makes more things shut up; disable the check for root filesystem being on extended partition while LILO is going on the MBR, because LILO supports this now (closes: Bug#64823); add new fullscreen_execlog utility function - debian/control: add Build-Depend
Re: weekly (?) debian-installer status report
On Mon Nov 20, 2000 at 08:06:41PM -0800, Joey Hess wrote: > Erik Andersen wrote: > > On Mon Nov 20, 2000 at 05:28:44PM -0800, Joey Hess wrote: > > > - busybox integration [Erik Andersen] > > > Not started. Busybox needs to build one or more .udebs. > > > Probably more than one. > > > > The first pass at busybox udebs will be ready tonight. How do I > > upload them? Just upload them to incoming as I would anything > > else? > > We still can't upload udebs, James has bailed on rolling out package > pools until after 2.1r2 (sigh). So shall I just put them on my web site or something? -Erik -- Erik B. Andersen email: [EMAIL PROTECTED] --This message was written using 73% post-consumer electrons-- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
