February 1998 - openSUSE Users - openSUSE Mailing Lists

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

02 Feb '98

A quick jump in here...... How does the syquest compare to the JAZ Drive from Iomega. I personally have had nothing but headaches from every Iomega product. Lach 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] iomaga internal zip drive
by exec＠prysm.net 02 Feb '98

02 Feb '98

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

1 0

Re: [S.u.S.E. Linux] iomaga internal zip drive
by wenzel＠b0rv04.fnal.gov 02 Feb '98

02 Feb '98

> hi i am using an internal (atapi) iomega zip drive in my toshiba 205cds notebook. no problems.You need kernel 2.0.31 or 2.0.32Select "Include IDE/ATAPI FLOPPY support (new)" in the menu "Floppy, IDE, and other block devices" when doing "make menuconfig" then i put the following lines into /etc/fstab /dev/hdc1 /zip ext2 rw,noauto,user 2 2 /dev/hdc4 /dosz vfat rw,noauto,user 2 2 to let the user mount the device with mount /zip (ext2 fs) or mount /dosz (vfat fs) (depending how the zip medium is formatted ) cheers hans > Hi, > > 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. > > Thanks, > Scott Gray > > -- > 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

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

02 Feb '98

Hi, 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. Thanks, Scott Gray -- 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] Pap, PPP,and EZPPP...my luck
by exec＠prysm.net 02 Feb '98

02 Feb '98

On Sun, 1 Feb 1998, zentara wrote: > AS root you must > 1. chmod 666 /etc/resolv.conf Please don't! Just use YaST to set up your nameserver! > 2. chmod 666 /dev/modem Not needed. Just add the user to the "uucp" group and the "dialout" group. > 3. chown root.root /usr/sbin/pppd PLEASE please don't! It's already chown'ed and chmod'ed! The SuSE people did this one right (unlike Red Hat, sigh). > 8. put the ezppp binary in each dialout users home directory > and let them own it. Err, just stick it into /usr/local/bin. The setup file(s) will still be stored into each dialout users' home directory. Or better yet, just download the "ezppp" rpm from ftp.redhat.com and let 'rpm' manage where it is installed. > Well this works great for me. I don't know what the > security implications are of the chmod's and chown's. The chmod's and chown's are NOT needed with SuSE. I dialout just fine using ezppp with the default permissions. Just add the user to the "dialout" and "uucp" groups. The chmod's and chown's are only needed with distributions (such as Red Hat) that don't have pppd already chown'ed, chgrp'ed, and chmod'ed with the proper permissions. The only exception might be the /etc/resolv.conf file. This is a security risk in some situations, but if you are dialing multiple ISP's, each of which has a different nameserver, you'll need to let ezppp patch resolv.conf. (If you don't know why world write access to resolv.conf is a security risk, think "rogue nameservers"). For a single-user system, though, world-write to resolv.conf isn't a real security risk. > I really barely know the basics of security. Nice thing to do would be to get a book on the subject. Check the O'Reilley & Associates web site, they have a good one. There are also reasonable introductory chapters on security in the Red Hat manual (available online at www.redhat.com) and in the LDP Linux Configuration & Administration manual (available in your /usr/doc directory if you installed the Linux Documentation Project). There may also be one in the SuSE manual, but I'm still chugging my way through that one (it's rather dense reading). 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] Running SuSE Linux
by wtopa＠ix.netcom.com 02 Feb '98

02 Feb '98

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 Subject: Re: [S.u.S.E. Linux] Running SuSE Linux Date: Sun, Feb 01, 1998 at 11:38:48PM -0600 In reply to:Steven 'Svet' Downum Quoting Steven 'Svet' Downum (svet(a)alamo.satlug.org): > > > > > Michael > > > > Glad you mentioned .xinitrc. As I recall, you upgraded from SuSE > > 5.0. Well I just started with 5.1. I DON'T have an .xinitrc at all. > > I copied my Slackware .xinitrc over and X WOULDN'T START! Gave me an > > error and flat out quit. So I have to go with what they give me, if > > you know what I mean. Maybe we SHOULD RTFM, huh? > > If I recall, you don't automatically get any sort of .xinitrc unless: > > a) you start x for the first time and the system writes you one. > b) you go to /var/X11R6/lib/xinit/ and do the following: > > cp xinitrc $HOME/.xinitrc > > then make changes to your personal .xinitrc to your tastes. > > As for your Slackware version of .xinitrc, it probably wouldn't work, > since Slackware and S.u.S.E have some differences in directory structure. > Plus, i think where the Slackware tarball puts certain files and where the > rpm puts things is diffrent. this can cause problems. Again, Slackware > doesn't automatically start with a .xinitrc file in every new users > directory...I believe, as with S.u.S.E, it apperas there after teh first > successful X session or if you copied the system default xinitrc into your > home directory. > > > I hope that helps with some confusion > > > svet > > > > > Subject: Re: [S.u.S.E. Linux] Running SuSE Linux > > Date: Sun, Feb 01, 1998 at 07:46:52PM -0800 > > > > In reply to:Michael Perry > > > > Quoting Michael Perry (mperry(a)mperry.basin.com): > > > > > > On Sun, Feb 01, 1998 at 10:29:51PM -0500, Wayne Topa stated: > > > Another interesting thing with kde and SuSE 5.1 here. If I edit .xinitrc > > > in my home directory to reflect exec kde I get kde but not the actual guts > > > of kde. I get the windowmanager only but no functionality, if you know > > > what I mean. I can only change windowmanagers by changing it in > > > /etc/profile, logging out, and letting my profile be read again. I would > > > like it if someone would explain how /etc/profile sets the windowmanager > > > and why it cannot dynamically be changed. It seems to change the > > > windowmanager one must edit /etc/profile, change it there, then logout and > > > enter the console again. Is this correct, in essence? > > > > > > > > > > Wayne > > > > > > > > > > > > -- > > > > 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 > > > > > > -- > > > --Michael Perry-- > > > mperry(a)mperry.basin.com > > > -- > > > 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 > > > > -- > 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] Running SuSE Linux
by wtopa＠ix.netcom.com 02 Feb '98

02 Feb '98

James Thanks. Your post made me think about xinitrc and I found that the one from Slackware had different paths to sysresources & sysmodmap! I should have checked that before. I copied over the system xinitrc, modified it and now all is well. On that WINDOWMANAGER export you mentioned, logging out & back in won't change it. A reboot does but better yet I find that running SuSEconfig does log in the change to /etc/profile. Then a log out/in does find the $WINDOWMANAGER OK. Your solution is much better tho. Leave profile alone and just use your .xinitrc. I wouldn't have even looked at profile if MY OLD(!!) .xinitrc had worked. Thanks! Wayne Subject: Re: [S.u.S.E. Linux] Running SuSE Linux Date: Sun, Feb 01, 1998 at 08:20:32PM -0800 In reply to:James C. Carr Quoting James C. Carr (jccarr(a)nwlink.com): > > > > On Sun, 1 Feb 1998, Michael Perry wrote: > > > Another interesting thing with kde and SuSE 5.1 here. If I edit .xinitrc > > in my home directory to reflect exec kde I get kde but not the actual guts > > of kde. I get the windowmanager only but no functionality, if you know > > what I mean. I can only change windowmanagers by changing it in > > /etc/profile, logging out, and letting my profile be read again. I would > > like it if someone would explain how /etc/profile sets the windowmanager > > and why it cannot dynamically be changed. It seems to change the > > windowmanager one must edit /etc/profile, change it there, then logout and > > enter the console again. Is this correct, in essence? > > If I understand /etc/profile, the file gets read during every log > on. This would require you to log off then back on to have /etc/profile > re-read. However, if you're just looking to do something minor, like > setting the WINDOWMANAGER variable, then you just need to use : > > export WINDOWMANAGER=startkde (for KDE use) > > Because KDE is something of a Window system (and not just a window > manager), it's easier to use the startkde script; that'll give you the > kpanel, kfm, and the desktop. Or one could edit the .xinitrc and call all > three individually (kpanel, kfm, and kde, that is). So, if you're looking > to modify X for just one user, you could go either way : > > 1) Edit /etc/profile and specify WINDOWMANAGER > > 2) Edit $HOME/.xinitrc and specify things there > > Since I'm not too familiar with SuSE just yet, I don't really on > WINDOWMANAGER for any of the WMs that did not get included with SuSE. For > example, to use WindowMaker, I call wmaker from .xinitrc; to use > AfterStep, I rename my .xinitrc and export WINDOWMANAGER=afterstep. > > Hope this helped, > > -- 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 -- -- 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] Samba, Printing and apsfilter
by exec＠prysm.net 02 Feb '98

02 Feb '98

On Sat, 31 Jan 1998, Steven 'Svet' Downum wrote: > rather ugly. I would use apsfilter to fix this problem, however smbprint > is called as a filter in the /etc/printcap entry. Has anyone faced this Well, I had a similar problem prior to apsfilter being written. What I did was write a short little script that calls the epsonps (a text-to-Postscript converter) and ghostscript programs as part of a pipeline that leads to the smbprint command. Later I incorporated it into a complete printer administration and setup facility (similar to YAST in concept) which will filter input in a variety of ways and dispatch the output to SMB, Netware, UUCP, RSH, etc. depending on the setup variables for the print spool. I wrote the system in Python because it was too large to write as a shell script and still retain my sanity, and I didn't have a few spare months to write it in "C". Unfortunately I don't know if that printer system will work on SuSE, but here's the relevant portion: /usr/localbin/standard-spoolbacks/ps-filter | smbclient \\\\pams_win95\\panasonic $PASSWORD $IP -P $USER $WORKGROUP -c 'print -' where ps-filter is: nenscript -TUS -ZB -p- | gs -q -sDEVICE=$DEVICE \ -r$RESOLUTION \ -sPAPERSIZE=$PAPERSIZE \ -dNOPAUSE \ -dSAFER \ -sOutputFile=- - Note that this is from an earlier pre-Python version of the system that hardwired things into individual shell scripts for the printers. You may have to change things for SuSE, in particular, SuSE doesn't use 'nenscript' as its Ascii-to-Postscript filter. 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] Running SuSE Linux
by exec＠prysm.net 02 Feb '98

02 Feb '98

On Sun, 1 Feb 1998, Michael Perry wrote: > Another interesting thing with kde and SuSE 5.1 here. If I edit .xinitrc > in my home directory to reflect exec kde I get kde but not the actual guts > of kde. I get the windowmanager only but no functionality, if you know You might replace "exec kde" with "exec startkde". At least with Beta 2. (I installed the Beta 2 RPM's off of redhat.com and they work fine). 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

[S.u.S.E. Linux] problems with update rpm for ggmp
by 1sgray＠preferred.com 02 Feb '98

02 Feb '98

Hi, I get the following when I try to install the updated gimp rpm: bobcat:/home/sgray1 # rpm -Uvh --force gimp.rpm failed dependencies: libxdelta.so.0 is needed by gimp-0.99.17-0 libgimp.so.1 is needed by photocd-1.12-8 libgimp.so.1 is needed by sane-0.63-4 I did install the gtk.rpm prior to this. Has anyone else had simular probems? Thanks, ---------------------------------- E-Mail: Scott Gray <1sgray(a)preferred.com> Date: 02-Feb-98 Time: 09:48:32 Linux version 2.0.33 ---------------------------------- -- 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