Re: CVS account.
Bartosz Fenski aka fEnIo <[EMAIL PROTECTED]> writes: > Hmm... no answer. May I ask what's the problem? I'm just slow. Of course, I'm not the only one able to do it, but, hey, since I'm here. I need a username, alternate username, and password using my GPG key. -- ...Adam Di Carlo...<[EMAIL PROTECTED]>...http://www.onshored.com/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: debian-installer cvs access
Ok, you're all setup. Username is 'gaudenz'. -- ...Adam Di Carlo...<[EMAIL PROTECTED]>...http://www.onshored.com/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: debian-installer cvs access
Gaudenz Steinlin <[EMAIL PROTECTED]> writes: > A few days ago a asked you about write access to the d-i cvs. I never got any such message. > Sadly I didn't hear anything from you. See above. :( > Could you please tell me which next steps I'm supposed to do or if > you are just busy and will take care as soon as possible. Follow the instructions at http://www.debian.org/doc/cvs#obtaining please. Also, I need approval from the debian-installer maintainer. -- ...Adam Di Carlo...<[EMAIL PROTECTED]>...http://www.onshored.com/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: New IRC messages
Eduard Bloch <[EMAIL PROTECTED]> writes: > > > [Thu 03 Jul 07:23:21]([EMAIL PROTECTED]) around? > > > [Thu 03 Jul 07:25:37]([EMAIL PROTECTED]) testing out loading 1.6c for bf2.4... > > > [Thu 03 Jul 07:25:43]([EMAIL PROTECTED]) if it works we should NMU it no? > > 1.6c is what? Loadlin upstream fix to work for kernels > 1MB. I tested it and I confirmed loadlin will work with 1.6c but not with (current) 1.6a. > BF is flawed a bit in the current CVS version. kernel-image-2.4.20 has > modules conflicting with pcmcia-modules-2.4.20 and I am not willing to > use this kernel version as-is because of the catastrophal IDE performance. > I tried to build kernel-image-2.4.21 for LinuxTag CDs, but it failed to > compile with gcc-2.95. And finaly, I do not have much spare time to fix > it :( Interesting. What modules conflict with the PCMCIA? I just installed using your 3.0.24 and the bf2.4 image on Thinkpad 560X using PCMCIA for network install. I might be getting "catastrophic" IDE performance but I'm not sure I would recognize it -- the laptop is new to me. I guess I should plan, for my personal computer, to build/use a 2.4.21 kernel which I have recompiled. -- ...Adam Di Carlo...<[EMAIL PROTECTED]>...http://www.onshored.com/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Boot Floppies
"Craig Coles" <[EMAIL PROTECTED]> writes: > I see from the contents of the Boot-Floppies package that you are the > Team Coordinator Actually I'm not anymore. Please ask stuff like this to the debian-boot list, CC'd here, not me personally. > I am trying to install the package from source (apt-get source > boot-floppies) because I have been unable to locate the package in the > regular package list. I am running my installation out of unstable. I see it there fine. 'apt-get source boot-floppies' works for me. > I am having a lot of trouble trying to build the package (debian/rules > binary) with a lot of dependency problems. Did you read the README? Did you do 'make check' ? > One question is that I noticed that boot-floppies is about at its > end-of-life and will be replaced with debian-installer, however, I > couldn't find a debian-installer package. Is boot-floppies still > the package to use? We are no longer actively extending boot-floppies; it is currently maintenance for stable updates only. Debian-installer is supposed to be the installer for Sarge, the next release. At least, last I heard it was. > I want to be able to build the boot floppies then modify the build > process to produce a boot image that will be booted via a PXE > network boot process. I have tested with the 2.88MB rescue.bin > image and it works... however I will need to modify the contents of > the root file system and trim some areas to allow for the files that > I need. I can't really opine whether it's better to use d-i or b-f -- you'd have to be more clear on whether you're just trying to hack this one thing or contribute to the quality of the installer for the next release. > > Does this sound possible with boot-floppies? Sure. > Or is there a doc that > explains how to build the boot/root floppy image that really works? README ? Sorry, brother, that's all there is. > One item I wanted to also ask about, I installed the > install-doc_3.0.23_i386.deb package hoping for docs to help out, but all > that was installed was the four docs in /usr/share/doc/install-doc, and > they don't help. Is this what is supposed to be installed for this > package? Yes, its the INstallation Manual for users installing the package. There are no developer docs nor ever will be, apart form the various README and script comments and such. -- ...Adam Di Carlo...<[EMAIL PROTECTED]>...http://www.onshored.com/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Debian 3.0 bf24 boot problem
"Mario" <[EMAIL PROTECTED]> writes: > I've try to boot Debian 3.0 with experimental 2.4 kernel, but after one screen of > stuff the boot process stops. Actually it come to the point: > enabled ExtINT on CPU#0 > ESR value before enabling vector : 0002 > > Later I try to use kernel parameters debug, nomce, nmi_watchdog, but no luck. > > Same thing happened when I tried to boot Red Hat 8.0. > > The MB is PCChips M825ULR with AMD Duron 1200 MHz. Ask on linux hardware or debian-user list please. We're not the i386 hardware experts here. Seeing as you get the problem in RH 8.0, its probably a linux/hardware issue, not a Debian issue per se. -- .Adam Di [EMAIL PROTECTED]http://www.debian.org/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: CVS problems?
Alastair McKinstry <[EMAIL PROTECTED]> writes: > Has anyone else had problems doing diffs, etc. against cvs.debian.org? > > e.g. > > coll:build$ cvs diff -r1.1 Makefile > cvs [server aborted]: no such tag N > coll:build$ > > This happens with both :ext and :pserver:anonymous for debian-boot, for > me. I don't see this problem. Are you still getting it? What module? It's probably a valtags problem if you are getting it... stupid CVS bugs.. -- .Adam Di [EMAIL PROTECTED]http://www.debian.org/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Status of boot-floppies for Debian 3.0r2
dann frazier <[EMAIL PROTECTED]> writes: > I have a sparcstation 4 running straight woody that i'd be willing to build > stuff on - i'm afraid i missed some context though - is this > for a boot-floppies update for woody? Yes, we're trying to get boot-floppies 3.0.24 for Debian 3.0r2. See http://people.debian.org/~blade/bf3024/ . -- ...Adam Di Carlo..<[EMAIL PROTECTED]>...http://www.onshored.com/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Bug?? in Woody
"Barry Eslick" <[EMAIL PROTECTED]> writes: > I am a very newbie to the Linux community, but when I was given a > Sparc5, I felt I must become involved. Now, to the bug??. I > installed Potato without too many problems and this runs well. But, > when I decided to upgrade to Woody, the installation went well until > boot time. Then, I was told that the proms were buggy and could not > read past the first 1Gb of my hard drive (2.1 Sun Seagate SCSI) and > asked for the image to boot. After much frustration, I reloaded > Potato, which as previously, works great. The Sparc is a > SparcStation5/70 with 64Mb RAM and a 2.1Gb HDD, SCSI CDRom, SUN > keyboard,no floppy, no monitor. I use a Wyse terminal to > communicate with the Sparc. When you upgraded did you also upgrade the kernel? Were you upgrading using 'apt-get' ? I can't help thinking this must be a kernel issue... Perhaps if you stay back at the Potato kernel things will be ok? Otherwise, you might ask on the debian-sparc list. -- ...Adam Di Carlo..<[EMAIL PROTECTED]>...http://www.onshored.com/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Status of boot-floppies for Debian 3.0r2
Eduard Bloch <[EMAIL PROTECTED]> writes: > - help Ben Collins <[EMAIL PROTECTED]> to test the Sparc > boot-floppies Hmmm, no SPARC build eh? Are there any sparc developers on this list who have access to a SPARC box running stable and can help us out by building this? Please follow-up to debian-boot. -- ...Adam Di Carlo..<[EMAIL PROTECTED]>...http://www.onshored.com/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: intel e1000 gigabyte
Excellent, looks like the 3.0.24 version should fix all issues with that server. Let me know if you need me to test anything on a poweredge 2650. I can't test full install but we can check things are booting and net card is working. -- ...Adam Di Carlo..<[EMAIL PROTECTED]>...http://www.onshored.com/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
intel e1000 gigabyte
I just recently complete an installation on a Dell PowerEdge 2650. Using the latest stable versions, hit some known problems. I was just brining this up to see if we can solve any of these for the stable update. The PERC3/Di SCSI controller did seem supported, although it may be buggy, according to http://www.domsch.com/linux/> (cf "interrupt fix patch"). The Intel (R) PRO/1000 Gigabit Ethernet Card (e1000) doesn't seem to be mainline kernel source. I wonder if we could provide this as a loadable module in the well-known location. I dunno if there are license issues that prevent us from shipping this with the kernel itself -- ...Adam Di Carlo..<[EMAIL PROTECTED]>...http://www.onshored.com/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Bug#175187: This bug should be fixed on boot-floppies side
Anthony Towns <[EMAIL PROTECTED]> writes: > On Thu, Jan 09, 2003 at 07:40:24PM +0900, Junichi Uekawa wrote: > > I don't really like the way the amount of packages debootstrap installs is > > increasing, but that probably has to be done... > > There probably needs to be a long-sought distinction between > > "base system" > > and > > "installation system" > > There isn't a distinction: "base" is precisely what is needed for an > "installation". There is a distinction between "required" (cf "essential") > and "base", though. > > The current way we describe "base" isn't really great, but it's what we've > got. Seems to make the most sense to add "eject" to base on all arches. Yes, absolutely. These are the types of sets as I understand them: install-core -- what is needed on install media for creating a self-bootstrapping system on some other media (defined by boot-floppies and debian-installer) base -- what is needed for a self-bootstraping system (defined by debootstrap) required -- packaged flagged as required (defined by the archive) ... -- ...Adam Di Carlo..<[EMAIL PROTECTED]>...http://www.onshored.com/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: 3c905b-tx and 3c905c-txm cannot install
ASC - Ronald Roeleveld <[EMAIL PROTECTED]> writes: > /lib/modules/2.2.20-idepci/net/3c59x.o: Init_module : Device or resource > busy> > Hint: insmod error can be caused by incorrect module parameters including > invalid IO or IRQ parameters > /lib/modules/2.2.20-idepci/net/3c59x.o: insmod > /lib/modules/2.2.20-idepci/net/3c59x.o failed > /lib/modules/2.2.20-idepci/net/3c59x.o insmod 3c59x failed > Installation failed. > When I choose to not install modules from cd but from the internet Debian > does find eth0 and receives a IP address from the DHCP server. > Does anyone know how to solve this? Follow the hint. Try different kernel boot arguments. Maybe http://www.tldp.org/HOWTO/BootPrompt-HOWTO.html would help or the readme for that driver in the kernel source. Sorry I can't be specific but we're not the experts on kernel and hardware compatability. Some of the more general linux help lists might be of use, also searching google and such... -- ...Adam Di Carlo..<[EMAIL PROTECTED]>...http://www.onshored.com/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Current EEPRO100 Driver in boot-floppies
CCS Crew <[EMAIL PROTECTED]> writes: > The driver in the boot-floppies images for the eepro100 seems to be > out-of-date and broken. The problem is characterized by the NIC's > failure to respond after minimal usage. Intel (and newer drivers for > the NIC) offers a working driver for Linux that I have successfully > tested under Slackware 7.1. The driver source can be found by > following link #2 below. Link #1 indicates the URL of the > boot-floppies page with the boot images with the broken driver > (phew!). > > 1. http://people.debian.org/~dwhedon/boot-floppies/ This is rather outdated. > 2. http://support.intel.com/support/network/adapter/index.htm As for the issue of the shipped EEPro, are you using the bf2.4 to boot with or no? This seems like an issue with the stable kernel-source-* package. -- ...Adam Di Carlo..<[EMAIL PROTECTED]>...http://www.onshored.com/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
updating http://www.debian.org/intro/organization
I'm updating http://www.debian.org/intro/organization and I wanted to have you guys here review this. I forget who volunteered to manage the install manual? Installation System Team -- <[EMAIL PROTECTED]> current: Tollef Fog Heen <[EMAIL PROTECTED]> Installation System for `stable' -- <[EMAIL PROTECTED]> current: Eduard Bloch <[EMAIL PROTECTED]> Release Notes current: Rob Bradford <[EMAIL PROTECTED]> Installation Manual current: *unknown* -- ...Adam Di Carlo..<[EMAIL PROTECTED]>...http://www.onshored.com/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: release notes moved from debian-boot to debian-doc cvs repo
Josip Rodin <[EMAIL PROTECTED]> writes: > I've now moved the release notes as well. > > Adam, please tag stuff appropriately, or whatever you did the last time :) Done. Btw, the tag is manual_now_in_DDP. -- ...Adam Di Carlo..<[EMAIL PROTECTED]>...http://www.onshored.com/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#174887: ["THOMAS CUNY" ] Re: Bug#174887: (no subject)
--- Begin Message --- >From: Adam DiCarlo <[EMAIL PROTECTED]> >To: "THOMAS CUNY" <[EMAIL PROTECTED]> >CC: [EMAIL PROTECTED], [EMAIL PROTECTED] >Subject: Re: Bug#174887: (no subject) >Date: 01 Jan 2003 13:59:40 -0600 > > >reassign 174887 boot-floppies >retitle 174887 [i386] keyboard problem on emachines t1742 >thanks > >"THOMAS CUNY" <[EMAIL PROTECTED]> writes: > > > System: eMachines T1742 purchased from Best Buy with Windows XP > > preinstalled > > Software: Debian Woody 3.0 cdroms purchased from Linux Central > > > > Problem: Installation > > in screen "Configuring Locales" > > a box is displayed of locales to select > > The only keys that are accepted from the keyboard are > > , , and . and > > move the cursor up and down the box. > > terminates processing the page and probably causes > > abnormal operation of the configuration script. > >You are saying the enter key doesn't work? Thus you are not able to >continue from this screen? > -- The key does not work. Nothing in the box can be selected or deselected. The key continues the installation process in some abnormal mode. The kernel is 2.2.20. Debian has bf2.4 but when I tried one time to install it it would not boot due to some missing drivers. The keyboard is PS/2 with Din connector. The keyboard meets the description of a PC-104 keyboard. The BIOS says nothing about keyboard emulation. The BIOS is Phoenix 6.0 After the system it completely installed with root login and user login created, the problem can be recreated by running: apt-get install locales The system never gets xserver installed without manual editing of the config file. This system uses an Intel 845 motherboard and I have to download kernel 2.4.20 and various other files to get it to run correctly. I have not done that yet. _ MSN 8 helps eliminate e-mail viruses. Get 2 months FREE* http://join.msn.com/?page=features/virus --- End Message --- -- ...Adam Di Carlo..<[EMAIL PROTECTED]>...http://www.onshored.com/>
Bug#140579: Report: tftpboot install successfull
Michael Stone <[EMAIL PROTECTED]> writes: > On Thu, Jan 02, 2003 at 08:36:11PM -0600, Adam DiCarlo wrote: > >Um, no, I'm just talking about netboot options on i386. > > I understand that. But just like we have a bunch of architectures, we > have a bunch of netboot options. You generally don't have a lot of > choices about what your hardware supports. Telling someone whose card > doesn't support pxe to use pxe because it's better is no more sensible > than telling an m68k user to use the i386 boot floppies because i386 is > better. True enough. So why does that prevent us from giving an overview of the various options and providing some criteria to help users pick one or the other? It may be true that generally "better" or "worse" doesn't matter -- just anything that works will do. -- ...Adam Di Carlo..<[EMAIL PROTECTED]>...http://www.onshored.com/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#140579: Report: tftpboot install successfull
"Chris Tillman" <[EMAIL PROTECTED]> writes: > > I also agree that what I read looked good, but it didn't seem to cover > > all of the issues mentioned in the bug, such as coming up with an > > overview of the different netboot options and which is best to use... > > Yes, and I don't have a clue about that. Well, even if we just list them and provide links, I think that would be enough to close the bug. > I looked at mknbi, I think I could probably document its usage also > from what was already given, but it would need to be put into context. ... or, just a link to existing documentation on the web would work too. Thanks for the effort btw... -- ...Adam Di Carlo..<[EMAIL PROTECTED]>...http://www.onshored.com/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#140579: Report: tftpboot install successfull
Michael Stone <[EMAIL PROTECTED]> writes: > On Thu, Jan 02, 2003 at 04:40:50PM -0600, Adam DiCarlo wrote: > >overview of the different netboot options and which is best to use... > > "The one that works." You're asking for something like "review the > currently supported architectures and explain which is the best one to > use." Um, no, I'm just talking about netboot options on i386. -- ...Adam Di Carlo..<[EMAIL PROTECTED]>...http://www.onshored.com/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#140579: Report: tftpboot install successfull
I also agree that what I read looked good, but it didn't seem to cover all of the issues mentioned in the bug, such as coming up with an overview of the different netboot options and which is best to use... -- ...Adam Di Carlo..<[EMAIL PROTECTED]>...http://www.onshored.com/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
manuals that are moving to ddp
I've put the 'manual_now_in_DDP' tag on the Dselect-beginner's manual. The context for this is that the dselect beginner's manual, the release notes, and the installation manual are all being split from the boot-floppies and maintained independantly, and in the debian-doc CVS area http://www.debian.org/doc/ddp>. The tag lets us identify changes after the move, if any, in case we want to apply those. Release notes and Install Manual are still to move. -- ...Adam Di Carlo..<[EMAIL PROTECTED]>...http://www.onshored.com/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#174887: (no subject)
reassign 174887 boot-floppies retitle 174887 [i386] keyboard problem on emachines t1742 thanks "THOMAS CUNY" <[EMAIL PROTECTED]> writes: > System: eMachines T1742 purchased from Best Buy with Windows XP > preinstalled > Software: Debian Woody 3.0 cdroms purchased from Linux Central > > Problem: Installation > in screen "Configuring Locales" > a box is displayed of locales to select > The only keys that are accepted from the keyboard are > , , and . and > move the cursor up and down the box. > terminates processing the page and probably causes > abnormal operation of the configuration script. You are saying the enter key doesn't work? Thus you are not able to continue from this screen? If so, can you clarify for us if you have a USB keyboard on that box? Is the BIOS setup to emulate a normal keyboard? Which kernel flavor are you using? You might try idepci and bf2.4 flavors both... > A similar box problem exists in configuring the Xserver > package. It is on the page to select which screen resolutions > not to use. All ditto above. -- ...Adam Di Carlo..<[EMAIL PROTECTED]>...http://www.onshored.com/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#140579: Report: tftpboot install successfull
retitle 140579 i386 tftpboot undocumenteed tags 140579 - patch reassign 140579 install-doc thanks Thanks for your contributions and documentation. We'll do our best to integrate this, and let you know when the install manual is ready for review. -- ...Adam Di Carlo..<[EMAIL PROTECTED]>...http://www.onshored.com/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#140579: Report: tftpboot install successfull
Is it just me, or isn't it rather a crippling problem that etherboot requires a floppy or other bootable medium to do the etherbooting? I guess however, since there is no OpenBoot on x86, that's just the breaks. Tell me, why is it interesting/useful to floppy-boot into etherboot rather than just floppy-booting from the rescue/root combo? Just the issue of one floppy vs two? -- ...Adam Di Carlo..<[EMAIL PROTECTED]>...http://www.onshored.com/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#140579: Report: tftpboot install successfull
Please retain the CC to the bugs.debian.org addresss. nb <[EMAIL PROTECTED]> writes: > Le dim 29/12/2002 à 22:07, Adam DiCarlo a écrit : > > nb <[EMAIL PROTECTED]> writes: > > > > > Thanks to Michael R. Schwarzbach and he's post I finally can install > > > debian via tftp. I think the need is going growing to do that and > > > it's really time to update documentation. > > > > Can you identify for us exactly what sections in the latest install > > manual are wrong, and which information is completely missing? > > This is missing : > > 1/ different boot methods are not listed (PXE, etherboot/netboot, MBA) > - I haven't tried PXE. I will in on month (I've bought an openbrick) > - I haven't tried MBA. I don't even know what it is > - I have tried etherboot. > > I didn't know before they where so many methods Yes. This proliferation of different ways to do it is really the reason why it's not done. We do need to indicate the various etherbooter methods for x86 and help the user decide which is best for her to use. You listed several -- is this pretty complete? Perhaps we can just pick one method which will work in 80% of cases and focus on documenting that, then provide links to other sites for other methods, saying that the instructions would have to be adopted for each. Should we go with etherboot? > 2/ about etherboot method. > - one needs first to install mknbi > - second to download root.bin _and_ tftpboot.img > - and then use mknbi to add root.bin to tftpboot.img > - after that tftpboot.img is loadable and usable from a client x86 > client. > > > > I need more help because I don't have an x86 box I can do netbooting > > with. > > > > Is this bug completely just a documentation issue? If so, we should > > reassign this as an 'install-doc' bug. > > Yes it's only a documentation issue. If you don't know how it works you > can spend much time (24 hours for me and I have many years experience) > or even think it's impossible. Yes, well, my point is that the actual instructions need to be provided by someone who has done it. That is to say, I can't do it on my own. But your instructions may help. > > > I've spent 24 hours to do > > > that and sentences like "NOT YET WRITTEN" are not acceptable today. > > > > For you to tell us something isn't "acceptable" isn't helpful. We are > > unpaid volunteers -- saying this sort of stuff just annoys us. Try to > > stay constructive. Providing patches or suggested bits of text is > > constructive. > > The sentence "NOT YET WRITTEN" was in the documentation. > http://www.debian.org/releases/stable/i386/ch-install-methods.en.html#s-install-tftp > chapter 4.5.5. > > All what aws written about the ip address and the architecture is > completely wrong (I'm talking about x86 plateforme). > > > I have used the following command to build the loadable and executable > image : > > mknbi-linux mknbi-linux > --ip=10.1.1.10:10.1.1.1:10.1.1.2:255.255.255.0:10.1.1.10 tftpboot.img > root.bin > tftpboot.img in the /tftpboot directory. > > It's like a miracle I was using before : > mknbi-linux --ip=10.1.1.10:10.1.1.1:10.1.1.2:255.255.255.0:10.1.1.10 > tftpboot.img > tftpboot.img > > the only one difference is in "root.bin" which I have downloaded from > ide-pci 1.44Mb (I don't remember exactly the url). No problemo. This helps. > I have to add that : > > a/ I have tried this with etherboot only (I have a 3com 3C905B TX) > b/ I will try PXE method in nearly one month and than tell you how it > works > c/ I have heard about MBA method but don't know anything else about it. > d/ I didn't try from a sparc (I have a ss10). I'll do that. No need. SPARC works as documented. > I'm very sorry for my poor english. You're English is quite good actually. > I you want more informations please let me know. Perhaps you could review the document when we have a draft. -- ...Adam Di Carlo..<[EMAIL PROTECTED]>...http://www.onshored.com/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#140579: Report: tftpboot install successfull
nb <[EMAIL PROTECTED]> writes: > Thanks to Michael R. Schwarzbach and he's post I finally can install > debian via tftp. I think the need is going growing to do that and > it's really time to update documentation. Can you identify for us exactly what sections in the latest install manual are wrong, and which information is completely missing? I need more help because I don't have an x86 box I can do netbooting with. Is this bug completely just a documentation issue? If so, we should reassign this as an 'install-doc' bug. > I've spent 24 hours to do > that and sentences like "NOT YET WRITTEN" are not acceptable today. For you to tell us something isn't "acceptable" isn't helpful. We are unpaid volunteers -- saying this sort of stuff just annoys us. Try to stay constructive. Providing patches or suggested bits of text is constructive. -- ...Adam Di Carlo..<[EMAIL PROTECTED]>...http://www.onshored.com/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Support for a new PowerPC board
Ross Vumbaca <[EMAIL PROTECTED]> writes: > There is a new PowerPC board aimed at consumers called "AmigaOne" (or > MAI Teron CX/PX) and we have been porting the Linux kernel+some > drivers to it. > > I run Debian Woody on mine and of what does work, works quite well. > > I would like to help Debian support this board as a flavour of PPC (if > Debian is interested in that), since I am new to this, would anyone be > able to tell me what the procedure for this is? I.e Who do I contact, > and what do they require? A kernel package assumedly, plus install > guide and install disks.. > > I have also created some "install disks" for the AmigaOne too, based > on the PReP install disks, and an install guide for end users. > > The PReP disks needs to be changed a bit to suit the AmigaOne better, > I have the source code, but I am finding it a bit of a mess to follow, > is the maintainer of the powerpc install disks on this list? This list *is* the maintainer. I would suggest you target debian-installer and contribute to that effort rather than expending effort on boot-floppies. OTOH, if the changes are minor (doubtful) we might be able to integrate these changes into 3.0rX point releases. Send patches to this list. If you want to help out Woody users until Sarge releases, you can have "unofficial" boot-floppies posted at a stable URL, and we might be able to add that to the errata section at http://www.debian.org/releases/woody/>. Cheers. -- ...Adam Di Carlo..<[EMAIL PROTECTED]>...http://www.onshored.com/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: [important] CVS-generated email shouldn't go here
Ok, the following source packages now use the srcpackage_cvs facility at packages.qa.debian.org: debian-installer (virtual for all the stuff under debian-installer) boot-floppies tasksel debian-cd base-config mklibs modconf fai This lets users subscribe to CVS messages as they desire and keeps junk off the debian-boot and debian-cd mailling lists. Its up to you guys to point your developers to this. Let me know if I got any thing wrong or if you have any problems, I'm on #debian-boot. For more information on how to subscribe to or use the PTS, see http://www.debian.org/doc/manuals/developers-reference/ch-resources.en.html#s-pkg-tracking-system> -- ...Adam Di Carlo..<[EMAIL PROTECTED]>...http://www.onshored.com/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Unidentified subject!
"Tadej Vodopivec" <[EMAIL PROTECTED]> writes: > I have a problem with booting linux. I had dual boot win-linux. Then I > had to reinstall windows cos` of virus. Now linux wont boot. It may be > a lilo problem. > When I boot a computer from the 1st installation cd and set method > "rescue", argument "debug" and press enter I see this note: "Kernel > panic: VFS: Unable to mount root fs on 01:00" You need to say 'rescue root=/dev/whatever'. This is documented when you hit 'f3' from the boot prompt. -- ...Adam Di Carlo..<[EMAIL PROTECTED]>...http://www.onshored.com/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: adam di carlo is back
The release notes and links to them have been fixed in the latest boot-floppies sources. Also the documentation contents of the install-doc package. The bugs will show as pending and not marked as fixed until 3.0.24 makes it into the archive. -- ...Adam Di Carlo..<[EMAIL PROTECTED]>...http://www.onshored.com/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Working Network Installs
"Cassandra Lynette Brockett" <[EMAIL PROTECTED]> writes: > I was just wondering if anyone is working on creating a working network > system for Debian? Yes. I've install using boot-floppies over network completely lots of times. Not on i386 though. > At the moment all the available methods require a boot disk of some variety, > however it is possible to boot debian off the network including the > installer, however this still means that a disk or cd is required to load > "rescue.bin" and "drivers.tgz"... That's not true. I've netbooted/netinstalled SPARC and PPC many times. > If no one else is working on it, I am modifying one of the root.bin files > (currently just bf2.4/root.bin from woody) to allow complete network booting > and installation, if there is someone working on it, I would like to join > forces on this one. We're not adding features to boot-floppies, actually. It's maintenance only. Work on debian-installer. Anyhow i386 booting is a pain because you have to pick packet drivers for your particular ether card. -- ...Adam Di Carlo..<[EMAIL PROTECTED]>...http://www.onshored.com/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: [important] CVS-generated email shouldn't go here
Martin Quinson <[EMAIL PROTECTED]> writes: > Completely agreed. I'm quite interested in following the devel of d-i, but > if I'm requiered to subscribe to N PTS module, I surely won't do > that. No problem, I agree. > If you're sick with cvs commits on this list, please go for a > debian-boot-cvs list, just like it's done for the www. I don't like the idea of a debian-boot-cvs list, because (a) why bother when we have PTS, after all, we don't need archives of the list to be stored (b) why annoy the list masters. I'll just go with the original idea. -- ...Adam Di Carlo..<[EMAIL PROTECTED]>...http://www.onshored.com/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: [important] CVS-generated email shouldn't go here
Raphael Hertzog <[EMAIL PROTECTED]> writes: > Le Wed, Dec 11, 2002 at 11:05:10AM +, Colin Watson écrivait: > > > Everything works automagically, I don't need any override. Anything > > > sent to [EMAIL PROTECTED] is automatically forwarded to the subscribers > > > of entry xx who have the keyword "cvs" enabled. > > > > Oh, I see. What about the virtual source package, since debian-installer > > isn't really the source package for all of these? > > The "xx" in my example did not need to be a real or a virtual package. > In fact when you're trying to subscribe to a package that doesn't exist > you just get a warning : > | $pkg is neither a source package nor a binary package. > | It may be a 'virtual package' or a mistake... > > But you can confirm the subscription just like usual. Oh my. I didn't even realize that debian-installer wasn't a package. Maybe I should burst out the debian-installer/* commits to their actual source packages instead. That sounds like a better plan. The only problem there is that if people want all the CVS commit msgs for debian-installer, they have a few PTS subscriptions to do... Thoughts? -- ...Adam Di Carlo..<[EMAIL PROTECTED]>...http://www.onshored.com/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: [important] CVS-generated email shouldn't go here
Geert Stappers <[EMAIL PROTECTED]> writes: > At which list will the discussion go about the CVS commits? To this list here. -- ...Adam Di Carlo..<[EMAIL PROTECTED]>...http://www.onshored.com/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: [important] CVS-generated email shouldn't go here
Colin Watson <[EMAIL PROTECTED]> writes: > On Tue, Dec 10, 2002 at 06:37:15PM +0100, Petter Reinholdtsen wrote: > > [Adam DiCarlo] > > >> Hmm, would that have all of debian-installer's messages sent to > > >> [EMAIL PROTECTED], or split them up by > > >> true source package? > > > > > > Whichever you like. > > > > I would like to have all d-i related commit messages sent to one > > mailing list. > > debian-boot-cvs, by analogy with debbugs and www? No -- again, [EMAIL PROTECTED] Managed by the PTS system. No mail lists to setup. No mail archives but who cares, that's what 'cvs2cl' is for. -- ...Adam Di Carlo..<[EMAIL PROTECTED]>...http://www.onshored.com/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: CVS location for dselect documentation for beginners
Osamu Aoki <[EMAIL PROTECTED]> writes: > > > Is it packaged anywhere now? > > > > Yes, install-doc. > > Are you talking CVS version? As far as I look into debian archive, I > see install-doc as a part of boot-floppies source tree and install-doc > is only a binary package name. (I think Josip is talking about > install-doc as an independent source package.) I am confused !@#$??? No. Right now, install-doc is from the boot-floppies source pkg, you are right. When it's moved out, it should have it's own source pkg. I think the binary pkg name should be kept the same (but that might require that boot-floppies hook-and-line is ripped from sid, but it should be). -- ...Adam Di Carlo..<[EMAIL PROTECTED]>...http://www.onshored.com/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Preparation of Debian GNU/Linux 3.0r1
Boot-floppies source pkg is 3.0.22 in woody, tno the stuff in dists/woody/main/disks-i386/ is 3.0.23. This should be fixed, dragging the 3.0.23 source pkg into stable. We should have a 3.0.24 available in the not too distant future -- not sure if we'll have it in time... Given delays in recompiling, I guess not. -- ...Adam Di Carlo..<[EMAIL PROTECTED]>...http://www.onshored.com/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: [important] CVS-generated email shouldn't go here
Joey Hess <[EMAIL PROTECTED]> writes: > Adam DiCarlo wrote: > > If anyone has any objections to this (I can't imaging why) let me > > know. Otherwise I'll forward boot-floppies and debian-installer > > messages to their corresponding PTS source pkg addresses. > > Hmm, would that have all of debian-installer's messages sent to > [EMAIL PROTECTED], or split them up by > true source package? Whichever you like. > The problem with the latter is that's a lot > of subscriptions to manage if you want to see everything d-i. Sure, we can do it either way. I guess it depends how likely it is that someone wants to see one of the sub-source-pkgs issues and not the other stuff.. -- ...Adam Di Carlo..<[EMAIL PROTECTED]>...http://www.onshored.com/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: adam di carlo is back
"Christian T. Steigies" <[EMAIL PROTECTED]> writes: > On Sun, Dec 08, 2002 at 04:21:19PM -0600, Adam DiCarlo wrote: > > > > Hey guys, I was unsubscribed from this group and swamped with RL work > > for a while, but I'm back. If there are any issues folks need my > > attention on that were sent here, please resend them to me directly. > > I've asked here twice for a new release of the (woody) boot-floppies, since > they fix a problem which is present in the current m68k version. It would be > nice, if this could be released before 3.0.1 is made. Unless we sneak in the > version I put on my p.d.o pages... > > Maybe you're the man? No, I'm not the man for that. Eduard Bloch is the man for that. I agree we should release it ASAP. I remember he was looking for another fix. Maybe he can elucidate. -- ...Adam Di Carlo..<[EMAIL PROTECTED]>...http://www.onshored.com/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: CVS location for dselect documentation for beginners
Josip Rodin <[EMAIL PROTECTED]> writes: > > > > If in the DDP CVS area, should it be packaged as well? I think it will > > > > need to be... > > > > > > It can be packaged from there too, I don't see how that would necessarily > > > impede the packaging process. > > > > No, it's just more work to be done is all > > Is it packaged anywhere now? Yes, install-doc. > (install-doc perhaps? Last I checked, install-doc was entirely broken. :) Broken how? I don't see any serious bugs on that pkg. Doesn't seem broken to me. > > > The FAQ needs a similar set of information so we could even keep this in the > > > parent directory of the manuals tree and share it. > > > > That is going to get a bit tricky if you are providing these as source > > packages. > > I figured we can easily hack it with a bit of symlink creation in the > makefiles. Pardon if I say "ew". > > What I would suggest doing as an alternative is to create a > > 'common-deb-data' CVS module, and via the CVS modules functionality, > > including this module with the various CVS modules that use it, e.g., > > the FAQ etc. This would effectively do: > > > > CVS checked out appearance Repository location > > -- - > > faq/ -> ddp/manuals.sgml/faq > > faq/common-deb-data/ -> ddp/manuals.sgml/common-deb-data > > > > install/ -> ddp/manuals.sgml/install > > install/common-deb-data/ -> ddp/manuals.sgml/common-deb-data > > Interesting. I didn't know one could do that. Yes, let me know if you want help setting this stuff up, if you wanna go this way. It is a *little* wierd to have the same source in multiple different source pkgs, but it's all shared in cvs so... and much less gross than trying to work with symlinks between source pkgs -- not even sure that latter approach could ever work very verbosely, esp. if we're building source pkgs using cvs-buildpackage. > > In fact, there are even deeper issues. Are we happy with the way > > we're using SGML conditional inclusion for porter stuff? Aren't we > > rather annoyed with the difficulty in validating that and the > > complexity it presents to authors? Should we move to another means of > > marking up arch-specific sections? If we were using DocBook, we could > > use (pretty naturally) the 'arch' attribute on , , and > > , and then handle the presentation issues (should we have one > > manual with arch-specific stuff simply styled/presented in a certain > > way? or one manual per arch as we have now?) in stylesheets. > > Yeah, I never did fancy the raw and inflexible nature of the conditionals in > ddoc-sgml, it's just dumb at times. I think we all agree with this. However, I don't wanna couple these two issues: making install-doc, release-notes, etc independant, and simplifying our approach to multi-arch. These are two completely separate issues. I honestly think that later on the install manual should be converted to docbook and we work out XSL or DSSSL styling solution using the DocBook arch attribute. Mechanical translation from debiandoc to docbook is pretty easy. I think we *should* stay with single source, multiple builds (one for each arch), using style parameters to control that. For styling, we should probably use XSL since DSSSL is starting to fall behind and isn't maintained at the same level anymore. > Then again, it's not going to be a major issue for sarge as we'll likely > need less of that stuff because less architectures will be newly released > with it. woody was pretty special in this regard. Yay for woody! :) I don't > say that often enough... Um, well, whether an arch is new or not isn't that much of a factor in how much arch-dependant stuff is there. The main factor is really how much the software is able to mask the differents of the arch. Some things are just inherently arch-specific and always must be documented arch-by-arch, especially things like boot loaders (I don't even see any grub ports to non-i386 at all, although I would think it would be technically possible0. I think it would be a serious mistake to think we can eliminate the arch-specific portions of the install manual. -- ...Adam Di Carlo..<[EMAIL PROTECTED]>...http://www.onshored.com/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
[important] CVS-generated email shouldn't go here
We're doing the wrong thing by having CVS commit messages sent to debian-boot. I'd like to change this in the following manner, quoted from the Developer's Reference: 4.11.3 Forwarding CVS commits in the PTS If you use a publicly accessible CVS repository for maintaining your Debian package you may want to forward the commit notification to the PTS so that the subscribers (possible co-maintainers) can closely follow the package's evolution. It's very easy to setup. Once your CVS repository generates commit notifications, you just have to make sure it sends a copy of those mails to [EMAIL PROTECTED] Only people who accepts the cvs keyword will receive the notifications. === If anyone has any objections to this (I can't imaging why) let me know. Otherwise I'll forward boot-floppies and debian-installer messages to their corresponding PTS source pkg addresses. -- ...Adam Di Carlo..<[EMAIL PROTECTED]>...http://www.onshored.com/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: CVS location for dselect documentation for beginners
Josip Rodin <[EMAIL PROTECTED]> writes: > If it goes in with dpkg, then we have a whole new set of arrangements to > make with the dpkg developers in order to accept the document, to have > others work on it, translate it, etc. I'd very much like to avoid that. Well, it's actually far less work for the DDP since it takes the burden off us to maintain it. I would think it just depends on whether these guys want to maintain it (which I would doubt) and if so, it is probalby pretty much up to them to accept the documents and work with contributors. > > If in the DDP CVS area, should it be packaged as well? I think it will > > need to be... > > It can be packaged from there too, I don't see how that would necessarily > impede the packaging process. No, it's just more work to be done is all > > > I'm thinking of moving it out into the DDP tree where it will likely get > > > some more attention and tender loving care ;) Any suggestions for preserving > > > the history? cp the ,v files, or just ignore that and cvs remove here + cvs > > > add there, with a pointer to the old place just in case anyone cares? > > > > I would suggest doing a checkout from the head, then copy those files > > over and do a CVS import from that, then start adapting it for being > > stand-alone. > > Right, so losing the history? Or does cvs import do something special to > preserve history? No, you would lose the history. But so what? Or rather, if you wanted the history, you'd go to the boot-floppies package. Why have the history in two places, eh? If you really want to duplicate the old history over to the new location, yes, you would have to copy over the ,v files. > > > The situation is similar with the release notes, which just need a few > > > tags to be able to skip some info for architectures recently released. > > > > Yes, ditto. > > The FAQ needs a similar set of information so we could even keep this in the > parent directory of the manuals tree and share it. That is going to get a bit tricky if you are providing these as source packages. What I would suggest doing as an alternative is to create a 'common-deb-data' CVS module, and via the CVS modules functionality, including this module with the various CVS modules that use it, e.g., the FAQ etc. This would effectively do: CVS checked out appearance Repository location -- - faq/ -> ddp/manuals.sgml/faq faq/common-deb-data/ -> ddp/manuals.sgml/common-deb-data install/ -> ddp/manuals.sgml/install install/common-deb-data/ -> ddp/manuals.sgml/common-deb-data ... > The set of makefiles would also be much simpler if it the installation > manual was standalone and worked with the variables from its own files > instead of working with other files like it does now. Given the past > recurring headaches we had with the build system, this is a big bonus :) I completely agree. The old system is rather overcomplex as well. In fact, there are even deeper issues. Are we happy with the way we're using SGML conditional inclusion for porter stuff? Aren't we rather annoyed with the difficulty in validating that and the complexity it presents to authors? Should we move to another means of marking up arch-specific sections? If we were using DocBook, we could use (pretty naturally) the 'arch' attribute on , , and , and then handle the presentation issues (should we have one manual with arch-specific stuff simply styled/presented in a certain way? or one manual per arch as we have now?) in stylesheets. > > Is anyone responsible for the rewrite of the install manual for d-i? > > I'd prefer not to take it since I'd like to put my attention on > > developers-reference, doc-base, and my bugs for a while... > > Chris Tillman did the large amounts of work on the current install manual, > IIRC, he might be interested in this. I hope so. He's done good work. -- ...Adam Di Carlo..<[EMAIL PROTECTED]>...http://www.onshored.com/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
adam di carlo is back
Hey guys, I was unsubscribed from this group and swamped with RL work for a while, but I'm back. If there are any issues folks need my attention on that were sent here, please resend them to me directly. If you do want my attention, its sometimes best to send mail directly to me. I don't mind being CC'd directly on messages too (gnus is nice enuf to remove dup'd messages for me). FYI, my only offical duty at the moment is managing the CVS area and passwords and such. I will try to get some time to also look at the install-docs bugs and fix some doc issues for the 3.0rX release of boot-floppies, but I don't want to stop anyone else from doing that work instead :) -- ...Adam Di Carlo..<[EMAIL PROTECTED]>...http://www.onshored.com/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: CVS location for dselect documentation for beginners
Josip Rodin <[EMAIL PROTECTED]> writes: > The dselect beginners guide is the one document in the b-f CVS tree that > _really_ doesn't belong there: if you remove the dependencies on the b-f > files from the header, you'll notice just a few missing tags, none of which > are even borderline important to the document itself, and all of them > trivial to arrange in a separate tree. I agree completely. I wondering though if this should go in the DDP CVS area, or even perhaps in the dselect package. If in the DDP CVS area, should it be packaged as well? I think it will need to be... > I'm thinking of moving it out into the DDP tree where it will likely get > some more attention and tender loving care ;) Any suggestions for preserving > the history? cp the ,v files, or just ignore that and cvs remove here + cvs > add there, with a pointer to the old place just in case anyone cares? I would suggest doing a checkout from the head, then copy those files over and do a CVS import from that, then start adapting it for being stand-alone. > The situation is similar with the release notes, which just need a few tags > to be able to skip some info for architectures recently released. Yes, ditto. > The installation manual needs entities from the po files of debootstrap, but > the document will likely need a rewrite for debian-installer, and I'm not so > sure if it will be doable in exactly the same way with d-i. In any case, we > can write scripts to obtain the data from wherever it is. Yup. I already have some code that uses apt-get to download pkgs it needs (e.g., ASCII version of relevant man pages). Is anyone responsible for the rewrite of the install manual for d-i? I'd prefer not to take it since I'd like to put my attention on developers-reference, doc-base, and my bugs for a while... -- ...Adam Di Carlo..<[EMAIL PROTECTED]>...http://www.onshored.com/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Hard Disks Are Not Detected in a Intel System that Has an ATA Controller Card in the Debian 3.0 Installation 3.0.23 Program
"Daniel P Wheeler" <[EMAIL PROTECTED]> writes: > On a 2 hard-disk drive PC with Windows XP Professional and a Promise > "Ultra133 TX2" ATA controller card > (http://www.promise.com/product/subsys_detail_eng.asp?pid=87&fid=3) the > Debian Installation System 3.0.23 (built on 15/05/02) gives the error > message > > "No hard disk drives were detected" > > after the > > "Configure the Keyboard" > > selection is made. Have you tried the other kernel images? E.g., bf2.4, idepci > When an attempt to access the floppy-disk drive for the ATA controller's > device drivers is made, there is an error message that states that the > floppy-disk drive cannot be mounted. (The floppy-disk was formatted for a > IBM compatible PC. The user has not used Linux before.) Did you try floppy=thinkpad ? Sometimes that helps. > Is the solution to be found in the following taken from the Debian web site > (http://people.debian.org/~blade/install/preload/)? No. -- ...Adam Di Carlo..<[EMAIL PROTECTED]>...http://www.onshored.com/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
