February 1998 - openSUSE Users - openSUSE Mailing Lists

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

03 Feb '98

Hi, On Mon, 2 Feb 1998, Wayne Topa wrote: > 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 You'll have to modify /etc/lilo.conf manually, because some defaults do not apply in this case. Just do the following: mount /dev/hda1 /mnt (assuming /dev/hda1 is the slackware root) mkdir /mnt/boot-suse (or whatever directory you like) cp /vmlinuz /mnt/boot-suse cp /boot/boot.b /mnt/boot-suse Now edit /etc/lilo.conf thus: boot=/dev/hda read-only timeout=100 install=/mnt/boot-suse/boot.b map=/mnt/boot-suse/map image=/mnt/vmlinuz (the location of the slackware kernel) root=/dev/hda1 label=slackware image=/mnt/boot-suse/vmlinuz root=/dev/hda3 label=suse Now run lilo and you should be able to switch between the systems. You need to use the same paths in your lilo.conf as your boot-partition is mounted to. The above setup works this way: Tell lilo to install in the MBA (this is boot=/dev/hda) Tell lilo where to find its second stage loader (this is boot.b and we have made sure it is on a partition below cylinder 1024). We could use the line "install=/mnt/boot/boot.b" IF slackware has the second stage loader in /boot also AND IF slackware uses the same LILO-version as S.u.S.E. Tell lilo to store its map file on the partition which is below Cyl 1024. The image sections tell lilo where to find the kernel images to load. They are on a partition below cyl. 1024, too. It doesn't matter where you mount your slackware partition in order to install lilo. But the paths need to be same you specify in /etc/lilo.conf, of course. When lilo is installed, it calculates the physical positions of all the files needed for booting and stores this information in its map file. When actually booting, partitions or filesystems don't matter. LILO just loads the sectors specified in its map file. Therefore you could store all the files of the boot machinery on a DOS partition, too. All this is necessary because of the history of the PC. Hardware manufacturers are doing lots of tricks in order to avoid these problems. For example an Adaptec 2940 can be configured to use so-called "extended translation". In this case, the SCSI-BIOS fakes the geometry and reports only 600 cylinders but 64 heads instead of the true geometry which might be 2400 cylinders and 16 heads. This can lead to other sorts of trouble when you are using multiple OSs and one of them recognizes the translation and the other doesn't ;-) I really recommend the excellent LILO documentation of Werner Almesberger in /usr/doc/packages/lilo, which should be easy for you to read because it's in english. Under X, just type "xdvi /usr/doc/packages/lilo/user.dvi" Using lots of pictures, the fundamentals are explained very good. > > 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! Yes. And the Italians will understand it, too ;-) Hubert -- 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] S.u.S.E. pronunciation
by jgray＠suse.com 03 Feb '98

03 Feb '98

Hi! I like your approach, Gordy :) We like to leave lots of latitude, too. Before we opened up the US office I did a poll with friends to ask them how they would say the name so as to give me some guidance. Well, it was no help at all b/c I got 4-5 different pronunciations with almost no regularity to it. I personally say "SUE-zeh" but I encourage everyone to say just what rolls off of their tongues! At least YaST is a little easier... ;) Happy pronouncing! James Gray > Hi- " Just say Suzy, and get on with it..." > A year or two ago there was a lot of discussion about whether Linux > was pronounced like Linus T. does it, (LEE-nooks) or whether it would be > more like the English "Linus", but I've heard almost no discussion of > this > lately; everyone seems to have gotten past it. LYE-nux is pretty much > IT, > for North Americans, anyway, with a few holdouts for Lennox, or whatever. > [ and if you read this mailbag for a week or so, you begin to realize > that > the Proper pronunciation should probably be LOO-nix, short for > Lunatix...] > But, I digress-- I think, for my 50 bucks, S.u.S.E. is SUZY, or > Susie, > which are the same. The Germans (and God bless them, I'm 3/4 German) > can say it however they'd like to. We all say and spell telephone a > little differently, but no one argues about it. And remember, SuSE is, > after all, > an acronym, not a word, which gives some artistic latitude, eh? > > Gordy Heitzman gordster(a)juno.com 612-429-9500 > " Just say Suzy, and get on with it... > " > On Mon, 02 Feb 1998 12:31:45 -0800 Bodo Bauer <bb(a)suse.de> writes: > > > >Mitch Wyle wrote: > >> > >> i had heard "sooo-zie" (as in English Susie) > >> and Soo-zeh (as in German suse) > > > > > >Hi, > > > >this is a funny subject to talk about, as we are ourself not sure how > >to pronounce it in english... :-) > > > >But I think we should try to get the german pronounciation established > >here in the US too. This is the way the most SuSE users pronounce it. > >If there are more SuSE users in the US than in germany we can > >change... :)) > > > >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 > > > > _____________________________________________________________________ > You don't need to buy Internet access to use free Internet e-mail. > Get completely free e-mail from Juno at <A HREF="http://www.juno.com"><A HREF="http://www.juno.com</A">http://www.juno.com</A</A>> > Or call Juno at (800) 654-JUNO [654-5866] > > -- > 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] Problem; Mach64 server
by fpawlak＠execpc.com 03 Feb '98

03 Feb '98

On Feb 2, 11:26pm, jonathan(a)aracnet.net wrote: > Subject: [S.u.S.E. Linux] Problem; Mach64 server > > Thanks for your contributions to the list, I was able to force a greater color > depth by using DefaultColorDepth 16 or even 24. It was in response to someone > else's query, but I won't look that in the mouth! > > However it doesn't look healthy! I have an ATI 3D Xpression with the Rage II+ > chip (4MB EDO RAM) and a Sceptre P511 monitor. When I go to 16 bpp I see a > flickering line about three inches from the left of the screen for the entire > height. 24bpp is even worse. I am using the Mach64 server, it seems to work > great in 8bpp with the exception of xfmail and Netscape FLOPPING around colors > like MAD!!! (argh!) > > Is this a bug in the Mach64 server? Should I be using the Mach64 server? Is > there some other kind of setting I should use? Is it a configuration problem? It sounds like you maybe overdriving your monitor. Check the spec for it and make sure that XFree is set up properly. Regards, Frank > Thanks for your help, this is an awesome list. > > --- > Jonathan Markevich <jonathan(a)aracnet.net> > > When more and more people are thrown out of work, unemployment > results. > -- Calvin Coolidge > > -- > To get out of this list, please send email to majordomo(a)suse.com with > this text in its body: unsubscribe suse-linux-e >-- End of excerpt from jonathan(a)aracnet.net -- 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] S.u.S.E. pronunciation
by gordster＠juno.com 03 Feb '98

03 Feb '98

Hi- " Just say Suzy, and get on with it..." A year or two ago there was a lot of discussion about whether Linux was pronounced like Linus T. does it, (LEE-nooks) or whether it would be more like the English "Linus", but I've heard almost no discussion of this lately; everyone seems to have gotten past it. LYE-nux is pretty much IT, for North Americans, anyway, with a few holdouts for Lennox, or whatever. [ and if you read this mailbag for a week or so, you begin to realize that the Proper pronunciation should probably be LOO-nix, short for Lunatix...] But, I digress-- I think, for my 50 bucks, S.u.S.E. is SUZY, or Susie, which are the same. The Germans (and God bless them, I'm 3/4 German) can say it however they'd like to. We all say and spell telephone a little differently, but no one argues about it. And remember, SuSE is, after all, an acronym, not a word, which gives some artistic latitude, eh? Gordy Heitzman gordster(a)juno.com 612-429-9500 " Just say Suzy, and get on with it... " On Mon, 02 Feb 1998 12:31:45 -0800 Bodo Bauer <bb(a)suse.de> writes: > >Mitch Wyle wrote: >> >> i had heard "sooo-zie" (as in English Susie) >> and Soo-zeh (as in German suse) > > >Hi, > >this is a funny subject to talk about, as we are ourself not sure how >to pronounce it in english... :-) > >But I think we should try to get the german pronounciation established >here in the US too. This is the way the most SuSE users pronounce it. >If there are more SuSE users in the US than in germany we can >change... :)) > >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 > _____________________________________________________________________ You don't need to buy Internet access to use free Internet e-mail. Get completely free e-mail from Juno at <A HREF="http://www.juno.com"><A HREF="http://www.juno.com</A">http://www.juno.com</A</A>> Or call Juno at (800) 654-JUNO [654-5866] -- 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] Problem; Mach64 server
by jccarr＠nwlink.com 03 Feb '98

03 Feb '98

I can't answer for certain how to solve this particular problem; I may, however, be able to narrow down the field a little. It sounds to me like a monitor configuration problem. I'm running an ATI Mach64 on my other computer with no problems whatsoever (the monitor being an IBM G40) -- basically, I just installed the Mach64 Server and pressed options 4 and 2 for the monitor refresh rates (not that you should try that, consult your monitor's specs, if available :)). I do know, however, that I've had similar problems with this computer's Cirrus Logic 5428; my monitor just has the hardest time sustaining an 800x600 resolution, though it does 1024x728 just fine. :P Since I can only run in 8bpp mode (that durn RAM restriction / membase thingy), it doesn't affect me overmuch. So, in short, consult whatever docs you have on your monitor. If you absolutely have to, try looking through the various refresh rates offered in xf86config; something similar to what you've chosen may work better ... or it may destroy your hardware. Whichever Murphy decides to give you, eh? ;) -- James -- 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] Problem; Mach64 server
by jonathan＠aracnet.net 03 Feb '98

03 Feb '98

Thanks for your contributions to the list, I was able to force a greater color depth by using DefaultColorDepth 16 or even 24. It was in response to someone else's query, but I won't look that in the mouth! However it doesn't look healthy! I have an ATI 3D Xpression with the Rage II+ chip (4MB EDO RAM) and a Sceptre P511 monitor. When I go to 16 bpp I see a flickering line about three inches from the left of the screen for the entire height. 24bpp is even worse. I am using the Mach64 server, it seems to work great in 8bpp with the exception of xfmail and Netscape FLOPPING around colors like MAD!!! (argh!) Is this a bug in the Mach64 server? Should I be using the Mach64 server? Is there some other kind of setting I should use? Is it a configuration problem? Thanks for your help, this is an awesome list. --- Jonathan Markevich <jonathan(a)aracnet.net> When more and more people are thrown out of work, unemployment results. -- Calvin Coolidge -- 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 wtopa＠ix.netcom.com 03 Feb '98

03 Feb '98

Mikeh Damm, I forgot. You might have tried the same thing in your .bash_profile. export HOSTNAME= export MAILUSER= You have to do lines like that for Qmail to work. Sorry, I just forgot all about those till you mentioned it. Glad you found the fix!!!!! Wayne Subject: Re: [S.u.S.E. Linux] Mail problems Date: Mon, Feb 02, 1998 at 09:28:13PM -0600 In reply to:Mike Hostetler Quoting Mike Hostetler (thehaas(a)ravine.binary.net) > > > I tried something different with smail and finally got things to > work . . . . I made a file called /etc/smail/config and put these things > in it: > > from_field = mhostetl(a)cse.unl.edu > > hostname = ravine.binary.net > > Now the name resolves correctly . . . neat, huh?? > > - mikeh > > -- > 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] Emacs kills NT
by dr.jones＠pobox.com 03 Feb '98

03 Feb '98

>Hi guys, >I dont know if this is a suse or emacs problem, it is fun though. >I don't have a printer at home so I print to a postscript file, put it >on a floppy (vfat) and print it at work. I use emacs to produce the >postscript for Objective-C code as it does some nice pretty-printing. I >sometimes use psnup to put 2 pages per a4 page also. > >The problem is that when I copy the floppy at work in M$ NT 3.51 I get a >"inpage error reading file" and NT crashes - it is cool fun crashing NT >so easily but the sysadmin gets real pissed-off, and I can't get the >printing done. > >I have used this method for years with no problem until I got suse 5.1. >Has anyone else run into anything like this? I know the problem is >really in NT as I can view the files with GV no problem in Linux. Maybe you have some funny characters in the path of your document. I once had severe problems problems getting some PostScript through a professional RIP, and it turned out I had a CR in the path (which the client - a Macintosh - allows, but not the RIP). Typically GhostScript is more relaxed than true Adobe PostScript, and then you can't really isolate the problem on your Linux box... Hope this helps! Jonas **************************************** IT-guide dr. Jones Banegaards Plads 20 A, 1., DK-8000 Aarhus, Denmark (45) 87303093 (office) / (45) 40843136 (cellular) <<A HREF="http://dr.jones.dk/"><A HREF="http://dr.jones.dk/</A">http://dr.jones.dk/</A</A>>> <<A HREF="mailto:dr.jones@pobox.com">mailto:dr.jones@pobox.com</A>> **************************************** -- 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 03 Feb '98

03 Feb '98

I tried something different with smail and finally got things to work . . . . I made a file called /etc/smail/config and put these things in it: from_field = mhostetl(a)cse.unl.edu hostname = ravine.binary.net Now the name resolves correctly . . . neat, huh?? - mikeh -- 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 wtopa＠ix.netcom.com 03 Feb '98

03 Feb '98

Tom I agree the the install of SuSE isn't a bit like Slackware or the others but: Even tho the book is a bit confusing, it does work. You just have to expirment a bit. I loaded up a BIG installation 1st and ran out of HD space ( Over 1 Gig!) so backed off, started again & installed from scratch again. Some things fell into line after I had done it a couple of times. Do I understand why some things are done as they are, no. Do I care, YES. But, even if a newbie would have trouble, you seem to have done enough other installations that it will soon come to you. Bottom line, I prefer Slackware, as I don't like Installation managers that say they do it all, and don't. SuSE isn't perfect, yet, but im my mind I would do this again over RedHat 5 times to sunday. I have only been using this for a week and I like the challenge more on this distribution then on any of the others. It took me less time to make SuSE work (somewhat) than I spent on RedHat or Debian. I'll take the good with the bad and stay plugging away st SuSE. The support is better then I ever saw from redhat and this list has as much information as the Debian list. Stay cool and keep at it. German engineering has always been good and I think that SuSE Linux may just prove that the Software guys over there Know what they are doing. Let me know if I can be of any assistance. Wayne Subject: Re: [S.u.S.E. Linux] Installer Problems Date: Mon, Feb 02, 1998 at 06:11:04PM -0800 In reply to:Bodo Bauer Quoting Bodo Bauer (bb(a)suse.de) > > Tom Schaefer wrote: > > Yes, but the messages are meaningless and are not informative as to > > finish time, etc.The installer should not allow the user to anything > > which would jeopardize the install. > > Nothing happends if you reboot, only the scripts are starting again. > It won't mess up your system. > > > > > 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. > > > > > > > It shouldn't do the locate db stuff unless the user wants to. It > > adds quite a bit of time to wait for it to finish. > > But this doesn't hurt anybody. You can use the system during the > scripts are running, that's why we put them in the background. > > > > > 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. > > > > THEN EXPLAIN THIS DURING THE INSTALL. > > YaST brings up a message, what else do you want? 100 of pages that > explain what is done exactly? Noone would read this (exept you...). > > > > That's why yast is > > > started right after rebooting the system. It should now complete > > > the > > > installation and ask you for CD2 and or CD3 to get the missing > > > packages > > > installed. > > > > > > > NO IT DOES NOT ... Once you reboot the system, the installer may > > start, but there is nothing prompting me to insert Cd2, and since > > that is not explained - why would I be inserting CD2 or 3 after a > > reboot? SIMPLIFY! > > You are the first person I heard of who had this trouble. It seems it > is simple enough for anybody else. Am I wrong? > > > You can reboot and just use the machine how you see fit after the > > first reboot. Nothing is being explained on the console directly to > > the installer (user) that you are going to need CD 2 or 3. NEVER. > > > > What you fail to understand, that anyone that has previously used > > Solaris, Caldera, Slackware, or even Red Hat - you don't reboot the > > machine to finish the install. All packages are extracted, THEN the > > machine is configured and THEN you do a reboot. > > It's the same with our distribution. Perhaps this is the mistake you > made. When YaST is finished the first time the installation procedure > is going back to initrc. Then the installed system will be bootet. You > can say the installation is made 'during the boot'. > > > If you've mounted CD 1 as a filesystem, then you can UNMOUNT IT for > > CD 2 and 3. > > During the very first installation you can't unmount it, becouse it > is used as root-filesystem. When the installed system runs, switching > CDs is not a problem. > > > You are overfamiliar with your installer. SIMPLIFY > > SIMPLIFY SIMPLIFY > > > > Watch someone who has NEVER installed from your distribution. And > > don't coach them along the way. > > > > You'll see what I mean. > > I did, it worked... > > > > 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... > > > > > > > YES BUT THIS IS NOT EXPLAINED. The first time I installed your 5.0, > > I wrongly assumed the install was finished when in fact it was still > > completing as explained before. > > It is explained in the message you get before the scripts are > startet. > > Ciao, > BB > > PS: Please dont SHOUT, I have no problem reading small caps.... -- 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