cvs commit to boot-floppies/documentation/ja by kubota
Repository: boot-floppies/documentation/ja who:kubota time: Mon Apr 29 21:14:42 PDT 2002 Log Message: update translation by HURASAWA Nozomu(nabetaro). Files: changed:hardware.sgml -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: dual boot setup
On Mon, Apr 29, 2002 at 01:44:02PM -0700, Steve Bauer wrote: any idea on where i can go to learn how to setup a dual boot? i'd like to setup debian - a friend recommend i check it out. i'm currently running w98 ontop of w95 on a dell xps r400. thanks, steve It's all in the manual (link in my .sig). -- *--v- Installing Debian GNU/Linux 3.0 v--* | http://www.debian.org/releases/woody/installmanual | | debian-imac (potato): http://debian-imac.sourceforge.net | |Chris Tillman[EMAIL PROTECTED] | | May the Source be with you | ** -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
cvs commit to boot-floppies by dancer
Repository: boot-floppies who:dancer time: Mon Apr 29 22:31:03 PDT 2002 Log Message: added NAKANO,Takeo to the list Files: changed:README-Translators -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
cvs commit to boot-floppies/documentation/fr by mquinson
Repository: boot-floppies/documentation/fr who:mquinson time: Mon Apr 29 23:42:36 PDT 2002 Log Message: Typos [Benoît Sibaud] Files: changed:appendix.sgml -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
cool web site
I really enjoy taking this quiz every month and I'm sure you will too. I'm always challenged, but I have gotten a 100% a few times. You can even win cool prizes. Play at: http://www.haestad.com/e/m.asp?d=28m=020429CQtb Good Luck KP [EMAIL PROTECTED] not interested in Civil Engineering email? Reply to this message and change the subject to stop . 11250-1032602 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Installation problem
Hi. I'm having difficulties getting Debian 2.2rev6 installed onto a rather old system (Pentium 100MHz, 64MBram, ~1GBhd, 8xCDROM). I boot from the CD set which I've downloaded and burned onto CD-Rs. The partitioning and configuration of partition mount points is fine, and after it when I signal a go to begin the installation of the modules, the installer promts me to insert the CD-ROM. When I do so and the installer commences, the following message soon appears: Installing Drivers from: /instmnt/dists/potato/main/disks-i386/current/drivers.tgz At this, my CD drive clicks and hisses for a while, then stops altogether and the installation is stuck. Nothing more happens and the system won't respond to any keystrokes, nor anything else for that matter except a system reset. If anyone has any concrete tips on how I might get around the problem I'd be thankful. Even if not, maybe it's a problem you should look into so it at least is fixed until the next release. There might be a problem with my CD drive, but I consider that somewhat unlikely since 1) I've succeded in getting so far, and 2) I've succeded in installing SOT Linux/BestLinux from it before. Regards, Ludvig Svenonius _ MSN Foto är det enklaste sättet att dela eller skaffa papperskopior av dina foton: http://photos.msn.com/support/worldwide.aspx -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: [Fwd: Re: Mac SE/30 install problem]
Packed pixel format is in use for lots of other hardware so I'd assume it is supported in some way? Nope, I don't think bogl supports packed pixels at all. Christian and I discussed this before if I remember right. I don't remember, but you may be right ;-) But what do we do about this now? Build a seperate bf set for those old-hardware machines (a lot of them seem to surface recently), remove language chooser again for m68k? Drop m68k? Fix bogl?? Michael k -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: [Fwd: Re: Mac SE/30 install problem]
Packed pixel format is in use for lots of other hardware so I'd assume it is supported in some way? Nope, I don't think bogl supports packed pixels at all. Christian and I discussed this before if I remember right. Jeez, how dumb am I? I was thinking of planar pixels. Packed pixels should indeed be fine. And planar was the problem on the Falcon anyway. Why one bit packed pixels won't work on the TT is another question, but that machine has inverse video as default (as has the SE/30). Michael -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
ETRURIAONLINE
Visita http://www.etruriaonline.it Questo indirizzo è stato reperito su internet dove era stato reso di pubblico dominio: Se non vuoi ricevere piu questa newsletter clicca qui -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
cvs commit to boot-floppies/documentation/fr by mquinson
Repository: boot-floppies/documentation/fr who:mquinson time: Tue Apr 30 04:16:00 PDT 2002 Log Message: Proofread [Patrice Karatchentzeff] Files: changed:welcome.sgml -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: [Fwd: Re: Mac SE/30 install problem]
On Tue, 2002-04-30 at 10:15, Michael Schmitz wrote: Packed pixel format is in use for lots of other hardware so I'd assume it is supported in some way? Nope, I don't think bogl supports packed pixels at all. Christian and I discussed this before if I remember right. Jeez, how dumb am I? I was thinking of planar pixels. Packed pixels should indeed be fine. And planar was the problem on the Falcon anyway. Why one bit packed pixels won't work on the TT is another question, but that machine has inverse video as default (as has the SE/30). Ah right, I hadn't noticed it was 1bpp. I don't think that's supported by bogl either at the moment, but it probably shouldn't be too difficult to add the code. Come to that, even planar pixels are not exactly rocket science. I'll see if I can find some time to batter bogl into shape. I can test 1bpp packed easily enough. p. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
cvs commit to boot-floppies/scripts/rescue/messages/fr by mquinson
Repository: boot-floppies/scripts/rescue/messages/fr who:mquinson time: Tue Apr 30 04:54:17 PDT 2002 Log Message: Sync to EN [Pierre Machard] Files: changed:f5.txt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
cvs commit to boot-floppies/documentation/fr by mquinson
Repository: boot-floppies/documentation/fr who:mquinson time: Tue Apr 30 04:59:47 PDT 2002 Log Message: Rewording [Pierre Machard] Files: changed:boot-new.sgml -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
cvs commit to boot-floppies/s390-specials by kraai
Repository: boot-floppies/s390-specials who:kraai time: Tue Apr 30 05:56:16 PDT 2002 Log Message: * s390-specials/parmfile.example1: Reverse dasd range. * s390-specials/parmfile.example2: Likewise. Files: changed:parmfile.example2 parmfile.example1 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#144825: boot-floppies: invalid contents of /debian/dists/woody/main/disks-s390/3.0.22-2002-04-03/tape/parmfile.debian
On Mon, Apr 29, 2002 at 09:09:41PM -0400, Matt Zimmerman wrote: On Mon, Apr 29, 2002 at 07:56:09AM -0700, Matt Kraai wrote: I've fixed this. Does this also need to be done for parmfile.example1: dasd=192-191 ro hostname=debian.domain.com ip=192.168.0.42 peer=192.168.0.1 dns=192.168.0.2 netinterface=iucv1 netmodule=netiucv iucv=tcpip:gateway and parmfile.example2: dasd=192-191 ro hostname=debian.domain.com ip=192.168.0.42 netmask=255.255.255.0 gateway=192.168.0.1 dns=192.168.0.2 netmodule=lcs chandev=noauto;lcs0,0x1000,0x1001,0,1,0 ? Yes, it can't hurt. These numbers are usually changed by the administrator to match the system being installed, but a more correct example is helpful. OK, fixed. I don't suppose you know how to handle the TDF file? Matt msg19493/pgp0.pgp Description: PGP signature
Why is there a prompt for a root shell when the default linux kernel boots?
Culd someone explain why is there a root shell prompt for the Linux kernel: Press ENTER to obtain a shell (waits 5 seconds) This seems something related to the cramfs filesystem (ramdisk) but I'm not knowledgeable about it. I would like: 1.- an explanation on why this is shipped by default (to add it to the Securing Debian Manual 2.- someone to step up an explain how to disable this behavior IMHO the boot-floppies kernel should not ship with this option enabled (whatever this is for). I was quite surprised when I saw this but a user has just mailed me asking for an answer on why does Debian woody ships with this. Regards Javi (Securing Debian Manual editor/author FYI) PS: I have been unable to find any reference on this in the debian mailing lists... msg19494/pgp0.pgp Description: PGP signature
Re: [Fwd: Re: Mac SE/30 install problem]
Jeez, how dumb am I? I was thinking of planar pixels. Packed pixels should indeed be fine. And planar was the problem on the Falcon anyway. Why one bit packed pixels won't work on the TT is another question, but that machine has inverse video as default (as has the SE/30). Ah right, I hadn't noticed it was 1bpp. I don't think that's supported I don't think it's all 1bpp packed pixel formats. I've seen it work once on my Falcon (well, sort of) in monochrome. I'll need to run more tests but I just fried one of the partitions there ... by bogl either at the moment, but it probably shouldn't be too difficult to add the code. Come to that, even planar pixels are not exactly rocket science. Would be nice to have but switching the display to mono would work as well as a last resort. Michael -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#144825: boot-floppies: invalid contents of /debian/dists/woody/main/disks-s390/3.0.22-2002-04-03/tape/parmfile.debian
On Sat, Apr 27, 2002 at 05:55:43PM +0200, Jochen Hein wrote: dasd=192-191 ro This was done on purpose. When the DASD range in invalid the kernel just scans all DASD without attaching any of them. dbootstrap on s390 first asks the user to attach a DASD and uses the list the kernel generated when it found an invalid DASD range. If you use a valid range the kernel will attach the devices in this range, in some cases even if they are not DASDs. So specifying a valid range can cause all kind of trouble from attached CMS disks (191 is typically a CMS disk on VM) to macine lockups while trying to scan the devices at the specified range. Oh, and wouldn't it be nice to have a TDF file too? Something like: The TDF file is on the CD, see the debian-cd package for the source of the TDF files. -- Stefan Gybas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#144825: boot-floppies: invalid contents of /debian/dists/woody/main/disks-s390/3.0.22-2002-04-03/tape/parmfile.debian
On Mon, Apr 29, 2002 at 07:56:09AM -0700, Matt Kraai wrote: I've fixed this. Does this also need to be done for parmfile.example1: Please undo your changes. Attaching the DASD 191 and 192 will confuse dboostrap because these are typically CMS disks on VM systems which can't be read by Linux. If you then select partition a hard disk dboostrap will ask you to low-level format your DASDs which will cause data loss! I'm not use it a valid range (say just 0001) will work. It might cause trouble if this device is not a DASD at all so we decided to use an invalid range and let the kernel just probe the DASDs without attaching them. Sorry, I didn't find time to read the s390-specific bug reports earlier. I think this is documented somewhere that you should use an invalid DASD range. Anyhow, this parmfile is only used during the installation process - a new one with a correct DASD range is created for the installed system. -- Stefan Gybas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#144825: boot-floppies: invalid contents of /debian/dists/woody/main/disks-s390/3.0.22-2002-04-03/tape/parmfile.debian
On Tue, Apr 30, 2002 at 06:01:57AM -0700, Matt Kraai wrote: On Mon, Apr 29, 2002 at 09:09:41PM -0400, Matt Zimmerman wrote: On Mon, Apr 29, 2002 at 07:56:09AM -0700, Matt Kraai wrote: I've fixed this. Does this also need to be done for parmfile.example1: dasd=192-191 ro hostname=debian.domain.com ip=192.168.0.42 peer=192.168.0.1 dns=192.168.0.2 netinterface=iucv1 netmodule=netiucv iucv=tcpip:gateway and parmfile.example2: dasd=192-191 ro hostname=debian.domain.com ip=192.168.0.42 netmask=255.255.255.0 gateway=192.168.0.1 dns=192.168.0.2 netmodule=lcs chandev=noauto;lcs0,0x1000,0x1001,0,1,0 ? Yes, it can't hurt. These numbers are usually changed by the administrator to match the system being installed, but a more correct example is helpful. OK, fixed. I don't suppose you know how to handle the TDF file? TDFs are used for supplying data to an emulated tape device; the file that Jochen Hein supplied looks OK, but I haven't tested it. The pathnames typically have to be edited by the admin anyway, so it should be considered an example. It would probably do fine under the tape/ directory, by analog to vmrdr/debian.exec (which is the same kind of metadata). -- - mdz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
cvs commit to boot-floppies/s390-specials by kraai
Repository: boot-floppies/s390-specials who:kraai time: Tue Apr 30 07:14:31 PDT 2002 Log Message: * s390-specials/parmfile: Revert dasd range reversal. * s390-specials/parmfile.example1: Likewise. * s390-specials/parmfile.example2: Likewise. Files: changed:parmfile.example2 parmfile.example1 parmfile -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
cvs commit to boot-floppies/debian by kraai
Repository: boot-floppies/debian who:kraai time: Tue Apr 30 07:14:32 PDT 2002 Log Message: * s390-specials/parmfile: Revert dasd range reversal. * s390-specials/parmfile.example1: Likewise. * s390-specials/parmfile.example2: Likewise. Files: changed:changelog -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#144825: boot-floppies: invalid contents of /debian/dists/woody/main/disks-s390/3.0.22-2002-04-03/tape/parmfile.debian
On Tue, Apr 30, 2002 at 04:01:24PM +0200, Stefan Gybas wrote: On Mon, Apr 29, 2002 at 07:56:09AM -0700, Matt Kraai wrote: I've fixed this. Does this also need to be done for parmfile.example1: Please undo your changes. Attaching the DASD 191 and 192 will confuse dboostrap because these are typically CMS disks on VM systems which can't be read by Linux. If you then select partition a hard disk dboostrap will ask you to low-level format your DASDs which will cause data loss! Doh, sorry. I've reverted it. I'm not use it a valid range (say just 0001) will work. It might cause trouble if this device is not a DASD at all so we decided to use an invalid range and let the kernel just probe the DASDs without attaching them. Could the ranges be omitted entirely? If not, is it possible to document what is happening in the parmfile itself? Matt msg19501/pgp0.pgp Description: PGP signature
Bug#144825: boot-floppies: invalid contents of /debian/dists/woody/main/disks-s390/3.0.22-2002-04-03/tape/parmfile.debian
On Tue, Apr 30, 2002 at 09:56:28AM -0400, Matt Zimmerman wrote: On Tue, Apr 30, 2002 at 06:01:57AM -0700, Matt Kraai wrote: On Mon, Apr 29, 2002 at 09:09:41PM -0400, Matt Zimmerman wrote: On Mon, Apr 29, 2002 at 07:56:09AM -0700, Matt Kraai wrote: I've fixed this. Does this also need to be done for parmfile.example1: dasd=192-191 ro hostname=debian.domain.com ip=192.168.0.42 peer=192.168.0.1 dns=192.168.0.2 netinterface=iucv1 netmodule=netiucv iucv=tcpip:gateway and parmfile.example2: dasd=192-191 ro hostname=debian.domain.com ip=192.168.0.42 netmask=255.255.255.0 gateway=192.168.0.1 dns=192.168.0.2 netmodule=lcs chandev=noauto;lcs0,0x1000,0x1001,0,1,0 ? Yes, it can't hurt. These numbers are usually changed by the administrator to match the system being installed, but a more correct example is helpful. OK, fixed. I don't suppose you know how to handle the TDF file? TDFs are used for supplying data to an emulated tape device; the file that Jochen Hein supplied looks OK, but I haven't tested it. The pathnames typically have to be edited by the admin anyway, so it should be considered an example. It would probably do fine under the tape/ directory, by analog to vmrdr/debian.exec (which is the same kind of metadata). OK, I'll do so. What should it be named? Matt msg19502/pgp0.pgp Description: PGP signature
Followup: bootfloppies for powerpc prep (I forgot the link ;-)
Ah yes well. I forgot the link to Kaz's ppc prep linux page for those that don't know: http://ppc.linux.or.jp/~aoshimak Happy Hacking, Rubin. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#144825: boot-floppies: invalid contents of /debian/dists/woody/main/disks-s390/3.0.22-2002-04-03/tape/parmfile.debian
On Tue, Apr 30, 2002 at 07:19:23AM -0700, Matt Kraai wrote: Doh, sorry. I've reverted it. Thanks. This is probably also my fault since I can't remember where I documented this (obviously in the wrong palce ;-)). Could the ranges be omitted entirely? If not, is it possible to document what is happening in the parmfile itself? No, if the range is ommited the kernel will not probe the DASDs at all. Then dbootstrap can't get a list of all available DASDs. We might be able to put comments in the parmfile using something like comment=This_is_a_comment since the contents of the parmfile are passed to the kernel as command line. -- Stefan Gybas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#144825: boot-floppies: invalid contents of /debian/dists/woody/main/disks-s390/3.0.22-2002-04-03/tape/parmfile.debian
On Tue, Apr 30, 2002 at 03:55:32PM +0200, Stefan Gybas wrote: On Sat, Apr 27, 2002 at 05:55:43PM +0200, Jochen Hein wrote: Oh, and wouldn't it be nice to have a TDF file too? Something like: The TDF file is on the CD, see the debian-cd package for the source of the TDF files. Why? Is it only useful with a CD? Matt msg19505/pgp0.pgp Description: PGP signature
Bug#144825: boot-floppies: invalid contents of /debian/dists/woody/main/disks-s390/3.0.22-2002-04-03/tape/parmfile.debian
On Tue, Apr 30, 2002 at 07:20:19AM -0700, Matt Kraai wrote: OK, I'll do so. What should it be named? debian.tdf would be good. -- - mdz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#144825: boot-floppies: invalid contents of /debian/dists/woody/main/disks-s390/3.0.22-2002-04-03/tape/parmfile.debian
On Tue, Apr 30, 2002 at 04:40:25PM +0200, Stefan Gybas wrote: On Tue, Apr 30, 2002 at 07:19:23AM -0700, Matt Kraai wrote: Could the ranges be omitted entirely? If not, is it possible to document what is happening in the parmfile itself? No, if the range is ommited the kernel will not probe the DASDs at all. Then dbootstrap can't get a list of all available DASDs. That's dumb. We might be able to put comments in the parmfile using something like comment=This_is_a_comment since the contents of the parmfile are passed to the kernel as command line. Ugh. Nevermind. Matt msg19507/pgp0.pgp Description: PGP signature
Re: Installation problem
#include hallo.h Ludvig Svenonius wrote on Tue Apr 30, 2002 um 10:06:10AM: I'm having difficulties getting Debian 2.2rev6 installed onto a rather old system (Pentium 100MHz, 64MBram, ~1GBhd, 8xCDROM). I boot from the CD set Which IDE chipset? at least is fixed until the next release. There might be a problem with my CD drive, but I consider that somewhat unlikely since 1) I've succeded in getting so far, and 2) I've succeded in installing SOT Linux/BestLinux from May be a problem with the CD itself, ie. some old Socket-7 chipsets have been real pieces of crap, crashing, hanging and rebooting on any problem. Gruss/Regards, Eduard. -- [ddeus_work] welche moeglichkeiten gibt es eine festplate zu beschleunigen ausser DMA und 32bit zugeng einschalten ? [ddeus_work] welche moeglichkeiten gibt es eine festplate zu beschleunigen ausser DMA und 32bit zugang einschalten ? noel wir wantworten erst, wenn mandie Frage 5 mal stellt. -- #debian.de -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
cvs commit to boot-floppies/documentation by robster
Repository: boot-floppies/documentation who:robster time: Tue Apr 30 08:24:52 PDT 2002 Log Message: Lets bring on the woody (PS: More ugly updates) Files: changed:release-notes.sgml -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Followup: bootfloppies on powerpc prep
Hi all, Thanks to Kaz Aoshima's iso image, I've been able to succesfully boot my Bull Estrella Series 300 (aka Motorola Powerstack 4000 II)! As soon as I'm up to speed and have read up some debian docs, I want to work on the current bootfloppies in testing (for powerpc prep, that is). Thanks for all responses, Rubin. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
cvs commit to boot-floppies/documentation/es by rcardenes
Repository: boot-floppies/documentation/es who:rcardenes time: Tue Apr 30 09:30:59 PDT 2002 Log Message: Minor changes Files: changed:post-install.sgml -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#144825: boot-floppies: invalid contents of /debian/dists/woody/main/disks-s390/3.0.22-2002-04-03/tape/parmfile.debian
On Tue, Apr 30, 2002 at 05:17:07PM +0200, Stefan Gybas wrote: On Tue, Apr 30, 2002 at 07:45:45AM -0700, Matt Kraai wrote: The TDF file is on the CD, see the debian-cd package for the source of the TDF files. Why? Is it only useful with a CD? On real hardware yes. You can use the CD-ROM of a Multiprice 3000 as emulated tape. But it might also be useful for Hercules although you could also specifiy the indivial files that should be on the emulated tape in hercules.cnf. A TDF file might have the problem that you need a tapes directory in / when used with Hercules. Should we include an example hercules.cnf, or document it? It sounds like all of the original raised issues are moot. Matt msg19513/pgp0.pgp Description: PGP signature
cvs commit to boot-floppies/documentation/es by rcardenes
Repository: boot-floppies/documentation/es who:rcardenes time: Tue Apr 30 10:00:37 PDT 2002 Log Message: Minor updates Files: changed:boot-new.sgml -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
cvs commit to boot-floppies/documentation by rcardenes
Repository: boot-floppies/documentation who:rcardenes time: Tue Apr 30 10:22:07 PDT 2002 Log Message: Minor updates Files: changed:release-notes.es.sgml -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Installing Woody in an I2O controller - part II
First, thanks to Eduard Bloch and Chris Tillman, for the tips. I had done some progress with this controller. The default bf2.4 flavour doesn't work with this controller, because the i2o and the scsi support are built-in on the kernel. Then I had to use my own kernel with these functions modularized. I used the root image from Blade's page. http://people.debian.org/~blade/root1440bf2.4.bin This root filesystem, doesn't have the /dev/i2o tree, then i had to create it by hand with mknod again. Let's see what i did: 1st. Boot with the rescue disk with a custom kernel 2nd. Use the Blade's root disk 3rd. Configure the keyboard 4th. Create the /dev/i2o tree and its devices (/dev/i2o/hda and its partitions) 5th. Load the modules from a modules disk. The modules must be loaded in this order: scsi_mod, sd_mod, i2o_pci, i2o_core, i2o_block, and alternatively the NIC module (eepro100 in my case). 6th. Fdisk on /dev/i2o/hda 7th. mke2fs on /dev/i2o/hda1 and mkswap and swap on on /dev/i2o/hda2 8th. configure the network 9th. mount /dev/i2o/hda1 on /target 10th. Install kernel driver modules from network (i don't know why, but it install a 2.2 flavour) 11st. Install the base system (yes, it install) 12nd. Make a boot floppy, the installer can't make the system bootable. 13rd. Reboot the system with the floppy. 14th. It fails, because can't find a root fs (i tried tell it with root=/dev/i2o/hda1 in the kernell command line) That's it. I don't get it running yet, but i think i'm almost there. Any sugestion? -- +-[Fábio Brito d'Araújo e Oliveira]-+ | Coordenador de Tecnologia | Não, meu quarto não é bagunçado. | A Tarde On Line | Apenas utilizo tecnologia de |www.atarde.com.br ICQ UIN:13597090| objetos distribuídos +--[Registered Linux User #101978]--+ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#144825: boot-floppies: invalid contents of /debian/dists/woody/main/disks-s390/3.0.22-2002-04-03/tape/parmfile.debian
On Tue, Apr 30, 2002 at 09:49:56AM -0700, Matt Kraai wrote: On Tue, Apr 30, 2002 at 05:17:07PM +0200, Stefan Gybas wrote: On real hardware yes. You can use the CD-ROM of a Multiprice 3000 as emulated tape. But it might also be useful for Hercules although you could also specifiy the indivial files that should be on the emulated tape in hercules.cnf. A TDF file might have the problem that you need a tapes directory in / when used with Hercules. Should we include an example hercules.cnf, or document it? It sounds like all of the original raised issues are moot. I don't think that it's necessary, but here is a minimal version of the one that I use for installation testing. -- - mdz # # Sample configuration file for Hercules ESA/390 emulator # CPUSERIAL 002623# CPU serial number CPUMODEL 3090 # CPU model number MAINSIZE 64# Main storage size in megabytes XPNDSIZE 0 # Expanded storage size in megabytes CNSLPORT 3270 # TCP port number to which consoles connect NUMCPU1 # Number of CPUs OSTAILOR LINUX # OS tailoring PANRATE FAST # Panel refresh rate ARCHMODE ESA/390 # Architecture mode S/370, ESA/390 or ESAME # .---Device number # | .-Device type # | | .-File name and parameters # | | | # V V V #--- # Card reader with data from the vmrdr subdirectory 000C3505bf/kernel.debian bf/parmfile.debian bf/initrd.debian autopad eof # A DASD device to install on (must be created with dasdinit) # e.g., dasdinit -bz2 debian.3390 3390 DEBIAN 500 # for a 500-cylinder, bzip2-compressed image 03003390debian.3390 # Adjust the following two lines for networking using TUN on Linux 2.2+ # deviceMTU Hercules IP Host IP Netmask 0A003088 CTCI /dev/misc/net/tun 2000 192.168.10.2 192.168.10.1 255.255.255.252 0A013088 CTCI /dev/misc/net/tun 2000 192.168.10.2 192.168.10.1 255.255.255.252
Re: Why is there a prompt for a root shell when the default linuxkernel boots?
Javier Fernández-Sanguino Peña [EMAIL PROTECTED] writes: Culd someone explain why is there a root shell prompt for the Linux kernel: Press ENTER to obtain a shell (waits 5 seconds) 1.- an explanation on why this is shipped by default (to add it to the Securing Debian Manual Where is the problem ? You are installing a system. If you dont like the prompt, dont look at it. 2.- someone to step up an explain how to disable this behavior Dont look at it. Or dont install a system. PS: I have been unable to find any reference on this in the debian mailing lists... Because it is no problem. -- begin OjE-ist-scheisse.txt bye, Joerg Registered Linux User #97793 @ http://counter.li.org end -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Why is there a prompt for a root shell when the default linux kernel boots?
On Tue, Apr 30, 2002 at 04:30:58PM +0200, Joerg Jaspert wrote: Javier Fernández-Sanguino Peña [EMAIL PROTECTED] writes: 2.- someone to step up an explain how to disable this behavior Dont look at it. Or dont install a system. Funny. However, the kernel used by the installation is setup as the default kernel. So it stays there after installation. PS: I have been unable to find any reference on this in the debian mailing lists... Because it is no problem. Believe me, it is. Feel free to point me to the place in the installation manual that explains this behaviour. Javi -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Why is there a prompt for a root shell when the default linux kernel boots?
On Tue, Apr 30, 2002 at 04:30:58PM +0200, Joerg Jaspert wrote: Javier Fernández-Sanguino Peña [EMAIL PROTECTED] writes: Culd someone explain why is there a root shell prompt for the Linux kernel: Press ENTER to obtain a shell (waits 5 seconds) 1.- an explanation on why this is shipped by default (to add it to the Securing Debian Manual Where is the problem ? You are installing a system. If you dont like the prompt, dont look at it. I did not understand his question as a problem - rather a request for information. I would also like to know. Johann -- Johann Spies Telefoon: 021-808 4036 Informasietegnologie, Universiteit van Stellenbosch For whosoever will save his life shall lose it. But whosoever will lose his life for my sake, the same shall save it. Luke 9:24 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Why is there a prompt for a root shell when the default linux kernel boots?
#include hallo.h Javier Fernández-Sanguino Peña wrote on Tue Apr 30, 2002 um 03:50:27PM: Culd someone explain why is there a root shell prompt for the Linux kernel: Press ENTER to obtain a shell (waits 5 seconds) This is a default for the initrd's linuxrc. You installed one of our official 2.4.x kernels. This seems something related to the cramfs filesystem (ramdisk) but I'm not knowledgeable about it. I would like: 1.- an explanation on why this is shipped by default (to add it to the Securing Debian Manual Sense? This prompt is good for loading some modules when the autodetection fails, so it is only used in seldom cases. 2.- someone to step up an explain how to disable this behavior IMHO the boot-floppies kernel should not ship with this option enabled We do not. (whatever this is for). I was quite surprised when I saw this but a user has just mailed me asking for an answer on why does Debian woody ships Dito. Show me a system with such problem after a fresh installation. Javi (Securing Debian Manual editor/author FYI) Security, soso. Well, since this rescue environment has an executable shell with root permissions, it _may_ be a security hole, since you can damage partitions easily, for example. To disable this shell, edit /etc/mkinitrd/mkinitrd.conf and set DELAY=0. Then recreate the initrd image (dpkg-reconfigure kernel-image-2.4.x-yz). Gruss/Regards, Eduard. -- We are the OE of Borg. You will be quoted awfully. Sigtrenner is futile. msg19521/pgp0.pgp Description: PGP signature
Re: Why is there a prompt for a root shell when the default linuxkernel boots?
Javier Fernández-Sanguino Peña wrote: 2.- someone to step up an explain how to disable this behavior Maybe something like this: 1. In /etc/mkinitrd/mkinitrd.conf, set: DELAY=0 2. Then regenerate your ramdisk image, for example: cd /boot mkinitrd -o initrd.img-2.4.18-k7 /lib/modules/2.4.18-k7 (This is a guess by reading the docs, I have not tested myself). -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Why is there a prompt for a root shell when the default linux kernel boots?
On Tue, Apr 30, 2002 at 05:20:14PM +0200, Eduard Bloch wrote: (whatever this is for). I was quite surprised when I saw this but a user has just mailed me asking for an answer on why does Debian woody ships Dito. Show me a system with such problem after a fresh installation. I know two: my laptop (fresh woody installation, cdimages of last month) and a user who has complained to me. I will stamp the latest cdimage and test them (tomorrow)... Javi -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Why is there a prompt for a root shell when the default linux kernel boots?
On Tue, Apr 30, 2002 at 06:05:27PM +0200, Javier Fernández-Sanguino Peña wrote: On Tue, Apr 30, 2002 at 05:20:14PM +0200, Eduard Bloch wrote: (whatever this is for). I was quite surprised when I saw this but a user has just mailed me asking for an answer on why does Debian woody ships Dito. Show me a system with such problem after a fresh installation. I know two: my laptop (fresh woody installation, cdimages of last month) and a user who has complained to me. I will stamp the latest cdimage and test them (tomorrow)... Now that I think of it this might be an issue with self-installed kernels. I'm going to document this behavior in the Manual, commit the changes and close the bug. Of course, woody does *not* install 2.4 kernels IIRC. Javi -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Why is there a prompt for a root shell when the default linuxkernel boots?
Javier Fernández-Sanguino Peña wrote: Now that I think of it this might be an issue with self-installed kernels. I'm going to document this behavior in the Manual, commit the changes and close the bug. Of course, woody does *not* install 2.4 kernels IIRC. The default install does not, but the bf2.4 flavor does. Please take a look at the dists/woody/main/disks-i386/current directory in the Debian archives. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Why is there a prompt for a root shell when the default linuxkernel boots?
On Tue, 30 Apr 2002, Javier Fernández-Sanguino Peña wrote: Now that I think of it this might be an issue with self-installed kernels. I'm going to document this behavior in the Manual, commit the changes and close the bug. Of course, woody does *not* install 2.4 kernels IIRC. That might be the default behaviour on an i386-compatible but on sparc (and probably all non-i386 archs) a 2.4 kernel is installed by the woody-install. IIRC even on an i386 a 2.4 kernel can be installed by woody through the bf2.4-flavour. regards, Thomas -- - Support bacteria - they're the only culture some people have -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Why is there a prompt for a root shell when the default linux kernel boots?
On Tue, Apr 30, 2002 at 10:17:00PM +0200, Santiago Vila wrote: Javier Fernández-Sanguino Peña wrote: Now that I think of it this might be an issue with self-installed kernels. I'm going to document this behavior in the Manual, commit the changes and close the bug. Of course, woody does *not* install 2.4 kernels IIRC. The default install does not, but the bf2.4 flavor does. Please take a look at the dists/woody/main/disks-i386/current directory in the Debian archives. And the stock kernel images available in woody include 2.4 kernels. These, also, have an initrd that offers a root shell, I believe. Luca -- Luca Filipozzi, Debian Developer [dpkg] We are the apt. You will be packaged. Comply. gpgkey 5A827A2D - A149 97BD 188C 7F29 779E 09C1 3573 32C4 5A82 7A2D -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Why is there a prompt for a root shell when the default linux kernel boots?
#include hallo.h Luca Filipozzi wrote on Tue Apr 30, 2002 um 02:01:57PM: a look at the dists/woody/main/disks-i386/current directory in the Debian archives. And the stock kernel images available in woody include 2.4 kernels. These, also, have an initrd that offers a root shell, I believe. bf2.4 was _especially_ designed to be non-modular, working without initrd. Other (big) kernel-image-2.4.x packages use initrd. Gruss/Regards, Eduard. -- !netgod:*! time flies when youre using linux !doogie:*! yeah, infinite loops in 5 seconds. !Teknix:*! has anyone re-tested that with 2.2.x ? !netgod:*! yeah, 4 seconds now -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Why is there a prompt for a root shell when the default linux kernel boots?
On Tue, Apr 30, 2002 at 03:23:06PM -0600, Erik Andersen wrote: It is there as part of the installer to make like easier for those wishing to do things that the installer does not support by default. It has nothing whatsoever to do with cramfs or the kernel. This is what I was thinking at first, but it sounds from further discussion like this shell is still there after installation has completed and the machine has been rebooted. Like whatever it is that spawns that shell is still present in the initrd that is installed with the kernel. And this is the case only if using the kernel 2.4 boot floppies. Is this all accurate? noah -- ___ | Web: http://web.morgul.net/~frodo/ | PGP Public Key: http://web.morgul.net/~frodo/mail.html msg19530/pgp0.pgp Description: PGP signature
Re: Why is there a prompt for a root shell when the default linux kernel boots?
On Tue, Apr 30, 2002 at 03:23:06PM -0600, Erik Andersen wrote: It is there as part of the installer to make like easier for those wishing to do things that the installer does not support by default. It has nothing whatsoever to do with cramfs or the kernel. you're just wrong. the 2.4 kernel images have a feature to drop to a prompt at boot time. this will come up at every boot. i question the utility of this feature, because there's not much you can do from this shell, but it's much to late to change at this point. it is worth documenting. -- Mike Stone msg19531/pgp0.pgp Description: PGP signature
smp/dac960/i440gx boot problem
Hello all, I'm with some troubles on trying to boot a kernel in a dual PPro machine. When a compile the kernel with smp support the machine hungs during the boot, this occurs exactly when the dac960 driver is being loaded. When I remove the smp support the driver is loaded but I have only one processor running. I think the problem is the i440gx pci bridge and the pci-apic irq transform. But I can't figure out why this is happening. If someone knows some workaround, please let me know. Thanks in advance, Carlos -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
RE: Why is there a prompt for a root shell when the default linuxkernel boots?
Where might one find documentation on this bf2.4 kernel? Javier Fernández-Sanguino Peña wrote: Now that I think of it this might be an issue with self-installed kernels. I'm going to document this behavior in the Manual, commit the changes and close the bug. Of course, woody does *not* install 2.4 kernels IIRC. The default install does not, but the bf2.4 flavor does. Please take a look at the dists/woody/main/disks-i386/current directory in the Debian archives. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: smp/dac960/i440gx boot problem
On Tue, 30 Apr 2002 20:37:53 -0300 Carlos Francisco Regis [EMAIL PROTECTED] wrote: I think the problem is the i440gx pci bridge and the pci-apic irq Actually it's a i450kx/gx. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
cvs commit to boot-floppies by rcardenes
Repository: boot-floppies who:rcardenes time: Tue Apr 30 17:55:44 PDT 2002 Log Message: * Added one more translator for Spanish team. * Enable Spanish dselect beginner doc * New Spanish README-Users.m4 Files: changed:README-Translators added: README-Users.es.m4 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
cvs commit to boot-floppies/documentation/en by toff
Repository: boot-floppies/documentation/en who:toff time: Tue Apr 30 21:52:27 PDT 2002 Log Message: add url for AppleSpec Files: changed:hardware.sgml -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
compare mortgage rates
Lower House Payments Guaranteed ! We Can approve ANYONE, and can find the most competitive rates for YOUR CREDIT. Click Here Takes less than 1 minute ! Be taken outta the directory by visiting the site -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
