Re: install trouble: stuck at "select tasks"
Lawrence H. Robins wrote: > I am (trying to be) a new Debian user. I have the 2.2r0 CD set > and got through most of the installation without a problem, but > near the end of the install, after installing the base system, > booting it, creating a root account and a user account, I > accidentally exited the "select tasks" program before making most > of the selections that I wanted, and now I can't figure out how > to restart this program. Run "tasksel". > >From the install manual, section 7.24 "Select and Install Profiles": > >The system will now ask you if you want to use the pre-rolled > >software configurations offered by Debian. This is the purpose of > >the dselect program, described below. But this can be a long task > >with around 3950 packages available in Debian! > >So you have the ability to choose tasks or profiles instead. A task > >is a work you will do with the machine such as "Perl programming" or > >"HTML authoring" or "Chinese word processing". You can choose several > >tasks. > >..[paragraph skipped] > >Soon, you will enter into dselect. If you selected tasks or profiles, > >remember to skip the "Select" step of dselect, since the selections > >have already been made. This documentation seems thoroughly out of date, debian 2.1-era. -- see shy jo -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Can't install udma66 base
I am unable to install downloaded Debian 2.2r1 udma66 base system on an ATA/66 drive attached to a Promise Ultra66 controller. Various suggestions in HOW-TOs, news groups, etc. don't help. The Ultra66 and all attached HDs work fine with Windows 98. Drives on my P3 with 128MB memory are configured as follows: UDMA33 motherboard connectors ide0hda - (nothing attached) hdb - (nothing attached) ide1hdc - CDROM hdd - CDROM Ultra66 connectors ide2hde - IBM 371800 ATA/66 (contains Win98 partitions C: and E:) hdf - (nothing attached) ide3hdg - IBM 371350 ATA/66 (contains Win98 partition D:) hdh - Quantum Fireball ect08 04 ATA/66 (all partitions removed with DOS fdisk) All HDs are attached via 80-wire cables. The drive at hdh is intended for Linux partitions. Booting with the udma66 rescue.bin floppy (no options entered at boot: prompt) shows first part of load sequence, then stops at line showing first instance of hde: IBM 371800... Entering Ultra66 I/O addresses as options at boot: prompt e.g., "linux ide2=0xdc00 ide3=0xe400,0xe800" carries the load sequence further, ending with Partition check: hde: [PTBL] [1027/255/63] hde1 hde2 hdg: [PTBL] [1027/255/63] hdg1 hdh: VFS: Insert root floppy (Seems o.k. to to this point...) The root floppy then loads o.k., and continues the install sequence o.k. until it gets to disk partitioning and the "Select Disk Drive" page. The *ONLY* option it displays is /dev/hde I want to re-partition and format *ONLY* the empty Quantum drive attached at hdh, and *NOT* my Windows drives. Please help!!! P.S. -- I do not want to reinstall the Quantum drive on motherboard (ide0). -- 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:boot-floppies Changes by: aph 00/11/24 16:04:30 Modified files: utilities/dbootstrap/langs: langs.xml english.src Log message: added a possibility to tag default language -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: building arm boot floppies - python error in dbootstrap/lang
On Fri, Nov 24, 2000 at 06:18:01PM +, Wookey wrote: > Having updated from cvs I am now past the LC problems reported. And then I > got some python complaints, but after installing task-python-dev (except for > 2 bits (gdb and python-gimp) which aren't compiled for potato arm) I get a > bit further. Now, when I do make release - When it gets to > boot-floppies/utilities/dbootstrap/langs dir it compiles iconv.so OK and then > does: > > ./ver2.py 0 i386 langs.xml > (I'm suspicous about that i386, but replacing it with 'arm' doesn't > affect the error and it does seem to have been deliberately overridden- what > is this about?) The result is; Well, this i386 is about the contents of *.src (*.xml) files. So this needs only to be changed in case this set of boot floppies is being built for arm platform. :) Actually, it's something that should be changed as soon as something reasonable appears in *.src files... > Traceback (innermost last): > File "./ver2.py", line 30, in ? > from dumper import dumper > File "./dumper.py" line 23, in ? > from iconv import engine > ImportError: ./iconv.so: R_ARM_PC24 relocation out of range Hmm.. This error seems to be specific to arm platform. > This may be an arm-specific problem (I've asked a guru about that), but maybe > not. Unfortunately, I am not a debian developer, so I do not have access to those arm machines available for them (do they exist?). Maybe if I had an account on such a computer, I could find what's wrong. But, it's only needed if we want lc on arm platform. :) > What is actually going on in this dir? The main thing is creating a langs.c file. > Can I in fact do this part of the compile on an i386 box in order to get > going? (I tried but got another error, probably due to mixing arm and i386 > files - ). I'd say so. What version of debian you are using, BTW? > Can I just skip this stuff as yet more language-specifc jiggery-pokery that I > almost certanly don't need? Hopefully so, and actually you should not see anything about langs directory if you have not set USE_LANGUAGE_CHOOSER=true in config file. -- Misha -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: Re: Bug#77920: passwords entered in base-config are not treated literally
Processing commands for [EMAIL PROTECTED]: > reassign 77920 base-config Bug#77920: passwords entered in base-config are not treated literally Bug reassigned from package `boot-floppies' to `base-config'. > thanks 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]
Bug#77920: passwords entered in base-config are not treated literally
reassign 77920 base-config thanks Damnit, you should know better.. Now, which characters, exactly? Joseph Carter wrote: > Package: boot-floppies > Version: N/A; reported 2000-11-24 > Severity: important > > When asked for a passwd on first boot, certain punctuation characters are > mangled. This bug should be considered RC because following good security > practices (ie, feeding damned near line noise in for a passwd) is able to > give you a system you can't even login to - if this were my first > experience with Debian I'd go install something else! > > The obvious workaround is to enter an alphanumeric passwd and change it > after login. > > The correct solution is to ensure that the string typed by the user is not > screwed with in any way. This means nothing special should happen to > characters such as $ # \ % & | etc that may be entered. > > -- System Information > Debian Release: woody > Architecture: i386 > Kernel: Linux trinity 2.2.18pre15 #1 Wed Nov 8 14:37:38 EST 2000 i686 > > -- > Joseph Carter <[EMAIL PROTECTED]> GnuPG key 1024D/DCF9DAB3 > Debian GNU/Linux (http://www.debian.org/) 20F6 2261 F185 7A3E 79FC > The QuakeForge Project (http://quakeforge.net/) 44F9 8FF7 D7A3 DCF9 DAB3 > > "The difference between genius and stupidity is that genius has it's > limits." > -- Albert Einstein > > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] -- see shy jo -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: building arm boot floppies - python error in dbootstrap/lang
On Fri 24 Nov, Wookey wrote: > The arm boot-floppies building saga continues. replying to my own post - sorry (just to save anyone spending too much time investigating) > ./ver2.py 0 i386 langs.xml > ImportError: ./iconv.so: R_ARM_PC24 relocation out of range > > This may be an arm-specific problem (I've asked a guru about that), OK, the guru came through with an updated glibc and this fixes that problem, so it's not a bf thing. I'd still like to know what all this stuff is for though. I'll see how far I get this time Wookey -- Aleph One Ltd, Bottisham, CAMBRIDGE, CB5 9BA, UK Tel (00 44) 1223 811679 work: http://www.aleph1.co.uk/ play: http://www.chaos.org.uk/~wookey/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#77920: passwords entered in base-config are not treated literally
Package: boot-floppies Version: N/A; reported 2000-11-24 Severity: important When asked for a passwd on first boot, certain punctuation characters are mangled. This bug should be considered RC because following good security practices (ie, feeding damned near line noise in for a passwd) is able to give you a system you can't even login to - if this were my first experience with Debian I'd go install something else! The obvious workaround is to enter an alphanumeric passwd and change it after login. The correct solution is to ensure that the string typed by the user is not screwed with in any way. This means nothing special should happen to characters such as $ # \ % & | etc that may be entered. -- System Information Debian Release: woody Architecture: i386 Kernel: Linux trinity 2.2.18pre15 #1 Wed Nov 8 14:37:38 EST 2000 i686 -- Joseph Carter <[EMAIL PROTECTED]> GnuPG key 1024D/DCF9DAB3 Debian GNU/Linux (http://www.debian.org/) 20F6 2261 F185 7A3E 79FC The QuakeForge Project (http://quakeforge.net/) 44F9 8FF7 D7A3 DCF9 DAB3 "The difference between genius and stupidity is that genius has it's limits." -- Albert Einstein -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#77455: i18n] sets wrong keyboard for i386 - kind of solved
On Fri, Nov 24, 2000 at 12:49:02AM +0100, Marcin Owsiany wrote: > > So it looks like one should normalize the list of available keyboards in one of > > the places... > > Maybe the arch prefixes in langs/*.src should be cut off at > build time? Looking at utilities/dbootstrap/kbdconfig.c I would say this is going to work... Maybe we just get couldget rid of thevariable prefix (in that file) and full (in some sense) paths? -- Misha -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
building arm boot floppies - python error in dbootstrap/lang
The arm boot-floppies building saga continues. Having updated from cvs I am now past the LC problems reported. And then I got some python complaints, but after installing task-python-dev (except for 2 bits (gdb and python-gimp) which aren't compiled for potato arm) I get a bit further. Now, when I do make release - When it gets to boot-floppies/utilities/dbootstrap/langs dir it compiles iconv.so OK and then does: ./ver2.py 0 i386 langs.xml (I'm suspicous about that i386, but replacing it with 'arm' doesn't affect the error and it does seem to have been deliberately overridden- what is this about?) The result is; Traceback (innermost last): File "./ver2.py", line 30, in ? from dumper import dumper File "./dumper.py" line 23, in ? from iconv import engine ImportError: ./iconv.so: R_ARM_PC24 relocation out of range This may be an arm-specific problem (I've asked a guru about that), but maybe not. What is actually going on in this dir? Can I in fact do this part of the compile on an i386 box in order to get going? (I tried but got another error, probably due to mixing arm and i386 files - ). Can I just skip this stuff as yet more language-specifc jiggery-pokery that I almost certanly don't need? I only need english for this release, and I'm getting to be in a real hurry now. I just want to make some basic boot floppies so I can fix a bug in the previous release (done a couple of months ago). Is it possible to just forget some of this stuff and still get bf built? Should I perhaps revert to some previous known-working release (if someone told me the CVS runes I'd be grateful...)? Wookey -- Aleph One Ltd, Bottisham, CAMBRIDGE, CB5 9BA, UK Tel (00 44) 1223 811679 work: http://www.aleph1.co.uk/ play: http://www.chaos.org.uk/~wookey/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Booting loops (Downloading SCSI SCRIPTS)
Karl Hammar wrote: > debian-boot and Frank: > >From what I recognize what Gérard says, we could boot the Tekram > DC390U with: > >boot: linux sym53c8xx=mpar:n > > to disable the pci master parity checking. Works for me. Thanks for the help. I'll probably unsubscribe soon, so if there's anything more I should test or something, please CC me personally. Frank -- Frank Heckenbach, [EMAIL PROTECTED] http://fjf.gnu.de/ PGP and GPG keys: http://fjf.gnu.de/plan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Installation with off-Board IDE
Hello, yesterday, I tried to install Debian 2.2 on a system with ASUS A7V board. This board is special in several ways. Apart from a total of seven (!) USB ports, it has an onboard Promise UATA/100 chip, in addition to the UATA/66 controller built into the VIA chipset. The system shipped with the CD-ROM as primary master on the UATA/66-Bus and the HD as primary master on the Promise Bus. The Debian installation did not find this drive nor the IDE controller. I don't know if Linux-2.2.17 supports this chip at all, because I tried compiling a custom kernel after a succesful installation with the drive on the UATA/66 bus, but even with "other IDE chipset" support Linux wouldn't detect the controller. Asus boards and especially this one are quite common, at least here in Germany, so i think I might not be the only one with this problem. Just thought I'd let you know... Bye, A. Heinlein -- --- Andreas Heinlein - [EMAIL PROTECTED] PGP-Key-ID: 0xAC422AA1 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
