February 1998 - openSUSE Users - openSUSE Mailing Lists

Re: [S.u.S.E. Linux] Re: SuSE Linux evaluation (Part 3)
by wtopa＠ix.netcom.com 03 Feb '98

03 Feb '98

Subject: Re: [S.u.S.E. Linux] Re: SuSE Linux evaluation (Part 3) Date: Mon, Feb 02, 1998 at 03:16:11PM -0800 In reply to:Bodo Bauer Quoting Bodo Bauer (bb(a)suse.de) > > Wayne Topa wrote: > > Bodo > > > > From Page 123 of SuSE 5.1 book, Section 8.3.4 > > > > QUOTE > > > > "ANY part of LILO has to be on the first 1024 cylinders on the hard > > disk." > > > > >From Yast.debug > > "/dev/hda3 * 977 977 1518 256095 83 Linux native" > > So the partition starts at 977 and goes up to 1518 (>>1024). > > > Yes I could put the kernel on hda1. BUT I have the SuSE kernel where > > the BOOK says it should work. Lilo 19 DID work with the Debian kernel > > on hda3 (start cylinder 977), so is the problem with lilo 20? > > May be the kernelimage layed between 977 and 1023. If the partition > starts under 1024 and goes over 1024 you never know which files > are below 1024 and which are above. It's possible you install the > system and everything is fine, but with the next kernle recompile > your system won't boot anymore. So the best way is to have the > total partition below the 1024 cyl. mark... > > > Which statement is true: > > All of the kerner MUST be on cylinders < 1024, (BB) > > OR > > ANY part of the kernel has to be on the FIRST 1024 cylinders??? (Book) > > I don't know exactly if it is enough to have any part of the kernel > below 1024. But if the hole image is on the first 1024 cyl, LILO > should work... OK, I will put the SuSE kernel in the Slackware / dir. Have never had to do this before. Will it work if I just call the inage suseimage and have lilo load that? If that works it would be just as good as having the kernel where it should be. Except if I up-grade I'll have to remember to move the new kernel to Slackware. NO BIG DEAL tho > > > Thanks for your help. Chus (Is that spelled right ?) > > > I think you mean 'Tschuess'... :-)) > What I tried to say is the southern German word for "see you later" no, that was "groos gott". I never knew how to spell it so I will go with Tschuess. Gee, Ciao is shorter to type, isn't it! > > > Ciao, > BB > -- > Bodo Bauer S.u.S.E., LLC fon +1-510-835 > 7873 > bb(a)suse.de 458 Santa Clara Avenue fax +1-510-835 > 7875 > http//www.suse.com Oakland CA, 94610 USA > -- > To get out of this list, please send email to majordomo(a)suse.com with > this text in its body: unsubscribe suse-linux-e -- -- Windows95 (noun): 32 bit extensions and a graphical shell for a 16 bit patch to an 8 bit operating system originally coded for a 4 bit microprocessor, written by a 2 bit company, that can't stand 1 bit of competition. -- To get out of this list, please send email to majordomo(a)suse.com with this text in its body: unsubscribe suse-linux-e

1 0

Re: [S.u.S.E. Linux] Re: SuSE Linux evaluation (Part 3)
by wtopa＠ix.netcom.com 03 Feb '98

03 Feb '98

Hubert Thanks, that makes sense. I guess its time I DID read up on Lilo, and will look up your reference. Thanks Wayne Subject: [S.u.S.E. Linux] Re: SuSE Linux evaluation (Part 3) Date: Tue, Feb 03, 1998 at 12:43:59AM +0100 In reply to:Hubert Mantel Quoting Hubert Mantel (mantel(a)suse.de) > > Hi, > > On Mon, 2 Feb 1998, Wayne Topa wrote: > > > From Page 123 of SuSE 5.1 book, Section 8.3.4 > > > > QUOTE > > > > "ANY part of LILO has to be on the first 1024 cylinders on the hard > > disk." > > > > >From Yast.debug > > "/dev/hda3 * 977 977 1518 256095 83 Linux native" > > Consider how LILO works: When you install LILO, it generates a map-file > /boot/map which holds the CHS-position (cylinder/head/sector) of all the > files needed for booting. This is the second stage loader /boot/boot.b and > the kernel image /vmlinuz itself. Because LILO has to do all of its work > by BIOS means it is restricted to cylinder numbers less than 1024. > > If you have a partition setup like above with the partition starting at > 977 and ending at 1518, results are unpredictable. If all of /boot/map, > /boot/boot.b and /vmlinuz happen to sit on cylinders below 1024, LILO will > work without problems because every needed sector can be loaded with BIOS > calls. If one single sector is on a cylinder >= 1024, LILO will fail. > > > Yes I could put the kernel on hda1. BUT I have the SuSE kernel where > > the BOOK says it should work. Lilo 19 DID work with the Debian kernel > > on hda3 (start cylinder 977), so is the problem with lilo 20? > > No. You simply had luck when installing debian. Probably debian uses > another installation order so all the relevant files for booting happened > to sit on cylinders below 1024. If you had recompiled your kernel, there > had been chances for LILO to fail afterwards. > > > Which statement is true: > > All of the kerner MUST be on cylinders < 1024, (BB) > > OR > > ANY part of the kernel has to be on the FIRST 1024 cylinders??? (Book) > > I think this is a problem with a foreign/other/strange/alien/unknown > language ;-) The book should probably read "EVERY part of the kernel...". > And additionally: "This is true for the files /boot/boot.b and /boot/map > also". Please note that /boot/map is generated when LILO is installed. > > > Thanks for your help. Chus (Is that spelled right ?) > > > > Wayne > > Hubert > > PS: If you are interested in how LILO and bootmanagers work, there is an > excellent documentation in /usr/doc/packages/lilo. > > > -- > To get out of this list, please send email to majordomo(a)suse.com with > this text in its body: unsubscribe suse-linux-e -- -- Windows95 (noun): 32 bit extensions and a graphical shell for a 16 bit patch to an 8 bit operating system originally coded for a 4 bit microprocessor, written by a 2 bit company, that can't stand 1 bit of competition. -- To get out of this list, please send email to majordomo(a)suse.com with this text in its body: unsubscribe suse-linux-e

1 0

[S.u.S.E. Linux] Re: SuSE Linux evaluation (Part 3)
by mantel＠suse.de 02 Feb '98

02 Feb '98

Hi, On Mon, 2 Feb 1998, Wayne Topa wrote: > From Page 123 of SuSE 5.1 book, Section 8.3.4 > > QUOTE > > "ANY part of LILO has to be on the first 1024 cylinders on the hard > disk." > > >From Yast.debug > "/dev/hda3 * 977 977 1518 256095 83 Linux native" Consider how LILO works: When you install LILO, it generates a map-file /boot/map which holds the CHS-position (cylinder/head/sector) of all the files needed for booting. This is the second stage loader /boot/boot.b and the kernel image /vmlinuz itself. Because LILO has to do all of its work by BIOS means it is restricted to cylinder numbers less than 1024. If you have a partition setup like above with the partition starting at 977 and ending at 1518, results are unpredictable. If all of /boot/map, /boot/boot.b and /vmlinuz happen to sit on cylinders below 1024, LILO will work without problems because every needed sector can be loaded with BIOS calls. If one single sector is on a cylinder >= 1024, LILO will fail. > Yes I could put the kernel on hda1. BUT I have the SuSE kernel where > the BOOK says it should work. Lilo 19 DID work with the Debian kernel > on hda3 (start cylinder 977), so is the problem with lilo 20? No. You simply had luck when installing debian. Probably debian uses another installation order so all the relevant files for booting happened to sit on cylinders below 1024. If you had recompiled your kernel, there had been chances for LILO to fail afterwards. > Which statement is true: > All of the kerner MUST be on cylinders < 1024, (BB) > OR > ANY part of the kernel has to be on the FIRST 1024 cylinders??? (Book) I think this is a problem with a foreign/other/strange/alien/unknown language ;-) The book should probably read "EVERY part of the kernel...". And additionally: "This is true for the files /boot/boot.b and /boot/map also". Please note that /boot/map is generated when LILO is installed. > Thanks for your help. Chus (Is that spelled right ?) > > Wayne Hubert PS: If you are interested in how LILO and bootmanagers work, there is an excellent documentation in /usr/doc/packages/lilo. -- To get out of this list, please send email to majordomo(a)suse.com with this text in its body: unsubscribe suse-linux-e

1 0

Re: [S.u.S.E. Linux] Mail problems
by thehaas＠ravine.binary.net 02 Feb '98

02 Feb '98

> > Perhaps the only thing you have to do is to set FROM_HEADER=binary.net in > /etc/rc.config > > mfG, > Carsten Hoeger Nope, just tried it. It doesn't work. I even changed it to the Unix host ravine.binary.net. Anyone else have any ideas?? - mikeh -- ============================================================================== || Mike Hostetler || || <A HREF="http://www.binary.net/thehaas"><A HREF="http://www.binary.net/thehaas</A">http://www.binary.net/thehaas</A</A>> || || email1: mhostetl(a)cse.unl.edu || || email2: thehaas(a)binary.net || ============================================================================== || `When you say "I wrote a program that crashed Windows", people just || || stare at you blankly and say "Hey, I got those with the system, || || *for free*".' - Linus Torvalds || ============================================================================== -- To get out of this list, please send email to majordomo(a)suse.com with this text in its body: unsubscribe suse-linux-e

1 0

Re: [S.u.S.E. Linux] Re: SuSE Linux evaluation (Part 3)
by bb＠suse.de 02 Feb '98

02 Feb '98

Wayne Topa wrote: > Bodo > > From Page 123 of SuSE 5.1 book, Section 8.3.4 > > QUOTE > > "ANY part of LILO has to be on the first 1024 cylinders on the hard > disk." > > >From Yast.debug > "/dev/hda3 * 977 977 1518 256095 83 Linux native" So the partition starts at 977 and goes up to 1518 (>>1024). > Yes I could put the kernel on hda1. BUT I have the SuSE kernel where > the BOOK says it should work. Lilo 19 DID work with the Debian kernel > on hda3 (start cylinder 977), so is the problem with lilo 20? May be the kernelimage layed between 977 and 1023. If the partition starts under 1024 and goes over 1024 you never know which files are below 1024 and which are above. It's possible you install the system and everything is fine, but with the next kernle recompile your system won't boot anymore. So the best way is to have the total partition below the 1024 cyl. mark... > Which statement is true: > All of the kerner MUST be on cylinders < 1024, (BB) > OR > ANY part of the kernel has to be on the FIRST 1024 cylinders??? (Book) I don't know exactly if it is enough to have any part of the kernel below 1024. But if the hole image is on the first 1024 cyl, LILO should work... > Thanks for your help. Chus (Is that spelled right ?) I think you mean 'Tschuess'... :-)) Ciao, BB -- Bodo Bauer S.u.S.E., LLC fon +1-510-835 7873 bb(a)suse.de 458 Santa Clara Avenue fax +1-510-835 7875 http//www.suse.com Oakland CA, 94610 USA -- To get out of this list, please send email to majordomo(a)suse.com with this text in its body: unsubscribe suse-linux-e

1 0

Re: [S.u.S.E. Linux] problems with update rpm for ggmp
by exec＠prysm.net 02 Feb '98

02 Feb '98

On Mon, 2 Feb 1998, Tom Schaefer wrote: > The gimp.rpm on the 5.1 CD DOES NOT ALLOW FOR FILES TO BE OPENED. > > *sigh* > > Is there a fix for this? SuSE mis-named the plugins directory. More on the subject when I get home (I am not near a SuSE installation right now). Anyhow, look for /usr/share/gimp or some similar directory, and where you see something named something like 1.1, rename it 1.1.15 (i.e. add a .15 to the end of whatever is there). Once you do that, gimp works again. This needs to be fixed, but I haven't had a chance to make a full detailed bug report yet. Eric Lee Green exec(a)softdisk.com Executive Consultants Systems Specialist Educational Administration Solutions You might be a redneck if you put on insect repellant prior to a date. -- To get out of this list, please send email to majordomo(a)suse.com with this text in its body: unsubscribe suse-linux-e

1 0

Re: [S.u.S.E. Linux] iomaga internal zip drive
by exec＠prysm.net 02 Feb '98

02 Feb '98

On Mon, 2 Feb 1998, Lachlan Dunlop wrote: > How does the syquest compare to the JAZ Drive from Iomega. I personally > have had nothing but headaches from every Iomega product. I really don't know. I installed my Syquest SparQ in my machine at about the same time as I installed SuSE on my machine. I then fdisk'ed a cartridge, changed the type from DOS to 83 (Linux), did an e2mkfs on the resulting partition, mounted it, and copied my archives directory over there (around 600mb of stuff downloaded from the net over the years). About 3 minutes later it was through. FAST. Faster than hard drives used to be, though not faster than current hard drives ("only" 12ms access time). Don't know how it'll be as far as reliability goes yet, tho. And as far as speed goes, the JAZ on a SCSI bus should still be a bit faster (SparQ only comes as IDE). But for 1/3rd the cost per megabyte, I'll give up a little speed! > > You may wish to look at the SyQuest SparQ. 1gb per disk, only costs $199 > > U.S., disks only cost $30 or so U.S.... much more affordable than zip. Eric Lee Green exec(a)softdisk.com Executive Consultants Systems Specialist Educational Administration Solutions You might be a redneck if you put on insect repellant prior to a date. -- To get out of this list, please send email to majordomo(a)suse.com with this text in its body: unsubscribe suse-linux-e

1 0

Re: [S.u.S.E. Linux] Installer Problems
by bb＠suse.de 02 Feb '98

02 Feb '98

Tom Schaefer wrote: > > Some areas for you to fix: > > 1. When installing from CD 1, packages determined to be on CD 2 and 3 > are not allowed to be installed during the first pass install. The > friggin' installer just blows past the prompt and the user is not > allowed to insert the other CDs. > > There is some sort of bug that does not prompt for CD 2 or 3. I have > found that if I insert the CD I want to install from, then run YAst, > Yast seems to determine that there are a bunch of packages that weren't > installed. DUH. Then, it seems to install them - but only the packages > for the CD that is currently in the drive. This behavior is somewhat > inconsistent, but predictable. Then, after installing packages from the > second CD, I can exit Yast, remove the CD, then insert CD 3 and run > Yast, who happens to "discover" that there are packages that weren't > installed. The I can install them. > > I thought you would have fixed this, as it was a problem in 5.0. > > 2. After the install "appears" to be done, leaving the user with a login > prompt and no clue that you have a bunch of background processes > running, and no idea of whether rebooting at this time is wise or not. You get a message which tells you what's going on before the login prompt appears. It also tells you that you can watch the scripts running on console 9. > However, by probing around, I see the Yast installer is unpacking > MAN pages and all sorts of other stuff, unbeknownst to the user. > You need to alert the installer that something else is happening. It's generating a locate DB, a apropos DB, doublechecks the permissions, etc. > I have noticed that if you reboot too soon, Yast appears to be activated > at boot up to either finish or do MORE stuff, which is not properly > explained. So I never really know if everything has been installed > properly. If you install the system the very first time, you can't switch the CDs because your root filestystem is on CD1. That's why yast is started right after rebooting the system. It should know complete the installation and ask you for CD2 and or CD3 to get the missing packages installed. This always worked for me, so I wonder about your problems... ?! Then Yast starts some scripts like told above. If these scripts don't get enough time to finish (because of a reboot) the procedure starts again... So look at console 9 (like the message tells you) before you reboot your system. If anything has finished processing Ciao, BB -- Bodo Bauer S.u.S.E., LLC fon +1-510-835 7873 bb(a)suse.de 458 Santa Clara Avenue fax +1-510-835 7875 http//www.suse.com Oakland CA, 94610 USA -- To get out of this list, please send email to majordomo(a)suse.com with this text in its body: unsubscribe suse-linux-e

1 0

Re: [S.u.S.E. Linux] iomaga internal zip drive
by 1sgray＠preferred.com 02 Feb '98

02 Feb '98

Eric, Thanks for the advice. I believe that the SyQuest SparQ is the better deal. Are you currently using a SparQ? If so, is there anything special other that the "compile in the IDE Floppy support" recommendation below. Thanks again for the help, Scott Gray Eric L. Green wrote: > On Mon, 2 Feb 1998, gman wrote: > > I'm interested in purchasing an internal iomaga zip driver. Are these > > drives compatible with Linux? Since there IDE my guess would be yes. > > However, I'm not certain about this. > > Just be sure to compile in the "IDE Floppy" support or it may have > trouble ejecting the disk. > > You may wish to look at the SyQuest SparQ. 1gb per disk, only costs $199 > U.S., disks only cost $30 or so U.S.... much more affordable than zip. > > Eric Lee Green exec(a)softdisk.com Executive Consultants > Systems Specialist Educational Administration Solutions > You might be a redneck if you put on insect repellant prior to a date. > > -- > To get out of this list, please send email to majordomo(a)suse.com with > this text in its body: unsubscribe suse-linux-e -- To get out of this list, please send email to majordomo(a)suse.com with this text in its body: unsubscribe suse-linux-e

1 0

Re: [S.u.S.E. Linux] Running SuSE Linux
by svet＠alamo.satlug.org 02 Feb '98

02 Feb '98

Wayne, > > Steven > > Thanks, yes I did eventually copy the system xinitrc over because I > didn't have one. SuSE didn't copy one over by default. Its funny I > was going in and out of X a lot and just happened to remember > .xinitrc. When I saw I didn't have it is when I copied over the > Slackware version which, as you said, the paths were incorrect. > It took another post to make me think enough to go look for the system > file. > > Thanks again, > Wayne > Hey, no problem...I'm glad you got everything sorted out. Glad to be of some help. Hey, I'm an old Slackware person myself, and I remember having a bit of a learning curve to deal with when transfering to S.u.S.E. However, I totally perfer S.u.S.E. most any other distribution. talk to you later, vet -- To get out of this list, please send email to majordomo(a)suse.com with this text in its body: unsubscribe suse-linux-e

1 0