April 2006 - openSUSE Users - openSUSE Mailing Lists

(IDE) Iomega ZIP 250 troubles on SUSE 10.0
by pelibali 11 Apr '06

11 Apr '06

Hi, I have a SUSE 10.0 system, having an internal Iomega 250Mb ZIP drive as secondary slave. Writing to any FAT-formatted ZIP disk the transfer was extremely SLOW and after I checked up the corresponding bug- reports and the list archive, saw two possibilities to move to higher writing speed. First I attempted to deactivate the sync writing, but that particular drive had no uuid under lshal, so couldn't define the async writing exclusively for that device. (I took the info from the SDB for 9.3.) Then I decided to move on automounting generally deactivated, but this with both sync and async didn't solve my problem. Of course async was seemingly quicker, but then attempting to umount the disk caused still 12-15 minutes waiting... I also checked the DMA settings, but the max. DMA/4.3 or similar I could activate, there was no other possibility. I don't think that it really counts, but the drive was not originally there in the comp, but was added later. Probably that's why an extra problem used to happen, when booting up with no ZIP disk in the drive I get only /dev/hdd, but no /dev/hdd4, so generally I can't even later manually mount the device! If I boot up with disk in the drive, the /dev/hdd4 is there or if was not there, alternatively I plug the disk in and then do _eject_ for it, then on a ridiculous way /dev/hdd4 appears suddenly... So I put back the disk and then I can really mount it. Is that bug or feature that SUSE recognizes the ZIP and doesn't put the corresponding device file there for manual mounting?! Of course /media/zip I made also by myself, but after deactivating automounter it is very OK. So at present I don't know, what is wrong; I read already, that the "slow-writing" bug should be gone by now. FYI: it is not with all the newest updates... Please is there anyone out there using internal ZIP drive and not having the above or very similar problems?! Thank you, Pelibali PS. Personal comment. I read the thread SUSE back and similar. For me SUSE means always _less_ and makes me worrying why I should load an earlier SUSE 9.x variant or use another distro everytime when I wish to do backup to a common ZIP-disk with no issues and/or speed-con- cerns.

3 8

Pentium-powered LCD/TV runs SUSE Linux
by Fred A. Miller 11 Apr '06

11 Apr '06

http://www.desktoplinux.com/news/NS8653450421.html

1 0

Broken patch breaks YOU
by Markus Koßmann 11 Apr '06

11 Apr '06

When trying to run YOU on SuSE 10.0 I get : ERROR(You:Fehler bei der Analyse der Patch-Beschreibung) Error parsing 'Deltas' attribute. Line ' xorg-x11-server-6.8.2-100_100.4.i586.delta.rpm 245406 3ad5216c49cc61665280daa091d520e8 xorg-x11-server-6.8.2-100 1126567701 3e051563544c6ffdf167c19a999566c4' doesn't have form 'filename size md5sum name-edition-release buildtime srcmd5sum seq'. I've tried ftp.suse.com ftp.gwdg.de and ftp.leo.org with the same result.

4 3

OpenSuse 10.0 /HALD
by Otto Rodusek (AP-SGP) 11 Apr '06

11 Apr '06

Hi, I hope I have the correct forum, and apologize in advance if I don't !!! I have installed OpenSuse 10.0 (64bit) and although everything I configured is working correctly - th logs themselves are not. HALD ====== When I connect an external HDD via an external USB-2 HHD, it recognizes the drive as sda and I'm able to mount it and use it normally without any problem except as follows: When I check the logs (/varlog/messages), I notice that it fills the log file very quickly (100mb ++ - so I have to clear it regularly and quickly) with the following messages from the hal-daemon: Apr 11 15:58:21 rentsch-asia kernel: usb-storage: queuecommand called Apr 11 15:58:21 rentsch-asia kernel: usb-storage: *** thread awakened. Apr 11 15:58:21 rentsch-asia kernel: usb-storage: Command READ_10 (10 bytes) Apr 11 15:58:21 rentsch-asia kernel: usb-storage: 28 00 00 00 00 08 00 00 01 00 Apr 11 15:58:21 rentsch-asia kernel: usb-storage: Bulk Command S 0x43425355 T 0x606 L 512 F 128 Trg 0 LUN 0 CL 10 Apr 11 15:58:21 rentsch-asia kernel: usb-storage: usb_stor_bulk_transfer_buf: xfer 31 bytes Apr 11 15:58:21 rentsch-asia kernel: klogd 1.4.1, ---------- state change ---------- Apr 11 15:58:21 rentsch-asia kernel: usb-storage: Status code 0; transferred 31/31 Apr 11 15:58:21 rentsch-asia kernel: usb-storage: -- transfer complete Apr 11 15:58:21 rentsch-asia kernel: usb-storage: Bulk command transfer result=0 Apr 11 15:58:21 rentsch-asia kernel: usb-storage: usb_stor_bulk_transfer_sglist: xfer 512 bytes, 1 entries Apr 11 15:58:21 rentsch-asia kernel: usb-storage: Status code 0; transferred 512/512 Apr 11 15:58:21 rentsch-asia kernel: usb-storage: -- transfer complete Apr 11 15:58:21 rentsch-asia kernel: usb-storage: Bulk data transfer result 0x0 Apr 11 15:58:21 rentsch-asia kernel: usb-storage: Attempting to get CSW... Apr 11 15:58:21 rentsch-asia kernel: usb-storage: usb_stor_bulk_transfer_buf: xfer 13 bytes Apr 11 15:58:21 rentsch-asia kernel: usb-storage: Status code 0; transferred 13/13 Apr 11 15:58:21 rentsch-asia kernel: usb-storage: -- transfer complete Apr 11 15:58:21 rentsch-asia kernel: usb-storage: Bulk status result = 0 Apr 11 15:58:21 rentsch-asia kernel: usb-storage: Bulk Status S 0x53425355 T 0x606 R 0 Stat 0x0 Apr 11 15:58:21 rentsch-asia kernel: usb-storage: scsi cmd done, result=0x0 Apr 11 15:58:21 rentsch-asia kernel: usb-storage: *** thread sleeping. Apr 11 15:58:21 rentsch-asia kernel: usb-storage: queuecommand called Apr 11 15:58:21 rentsch-asia kernel: usb-storage: *** thread awakened. Apr 11 15:58:21 rentsch-asia kernel: usb-storage: Command READ_10 (10 bytes) And the messages just go on and on and on and on......!!!! Any way to switch this off????

1 0

Release 10.0 / SAMBA
by Otto Rodusek (AP-SGP) 11 Apr '06

11 Apr '06

Hi, I hope I have the correct forum, and apologize in advance if I don't !!! I have installed OpenSuse 10.0 (64bit) and although everything I configured is working correctly - th logs themselves are not. SAMBA ====== I want to give my users file access via SAMBA. I have configured it and started it up and users are certainly able to store and retrieve files. However my log files (/var/log/messages) are continueously being filled up with the following messages: Apr 11 12:15:12 rentsch-asia smbd[2034]: [2006/04/11 12:15:12, 0] printing/print_cups.c:cups_cache_reload(85) Apr 11 12:15:12 rentsch-asia smbd[2034]: Unable to connect to CUPS server localhost - Connection refused (continuous !!!!!! fills up very quickly!!!!) Now, I am NOT using cups or any printing facilities for that matter as no printers are connected or shared. I have commented the "printers" line in the smb.conf file but to no avail. Any ideas hot to stop the messages?? Below is part of the relevant entry in the smb.conf file. --------------------part of smb.conf ------------------------------- [global] log file = /var/log/samba/smb.%m log level = 1 max log size = 50 read raw = no dns proxy = no encrypt passwords = yes # printing = lprng preferred master = no server string = Samba Server on rentsch-asia.com (192.0.0.254 / 203.125.254.42) workgroup = LMPP hosts allow = 192.0.0. 192.168. 127. write raw = no netbios name = LMPPMAIL socket options = SO_KEEPALIVE TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192 load printers = no security = user hosts equiv = /etc/hosts # username map = /etc/samba/smbusers password level = 8 username level = 8 # logon path = \\%L\Profiles\%U # logon home = \\%L\Profiles\%U dns proxy = No # printing = cups #[printers] # comment = All Printers # path = /var/spool/samba # browseable = no ## Set public = yes to allow user 'guest account' to print # guest ok = no # writable = no # printable = yes # create mask = 0700

1 0

amarok 1.4 for SuSE 9.3
by Phil Burness 11 Apr '06

11 Apr '06

Anybody know where the rpm's for this are? I've tried using apt with guru and packman -- Phil Burness Linux User since 1991 - currently using SuSE 9.3 Warrington - United Kingdom

2 3

Re:How does one pronounce "SUSE"
by Thomas Edward Beasley Junior 11 Apr '06

11 Apr '06

The pronunciation guide that came with my first distribution of SuSE (6.4) stated that SuSE is pronounced like the following persons last name: John Philip Sousa. I hope this helps. - Tom p.s. I'm currently on my 9th distro of SuSE, using 10.0 and looking forward to the next version due out later this week i think. -- The Reverend Thomas Edward Beasley Junior <beesknees(a)earthlink.net>

2 1

OpenSuse 10.1 beta 9: Problem to resolve hostnames from LDAP-Database
by Jens Weiße 11 Apr '06

11 Apr '06

Hi list, I discovered a strange problem with hostname resolution under OpenSuse 10.1 beta 9. The hostnames are stored in a LDAP database. In /etc/nsswitch.conf are the following lines: [...] passwd: compat group: compat shadow: compat passwd_compat: ldap group_compat: ldap hosts: files ldap dns [...] The user login works fine. With "getent hosts" I became full list of hostnames. But ping (and maybe sshd) can't resolve the hostname. ping doesn't work and ssh login attempts need nearly 1 minute. The same setup (/etc/ldap.conf, /etc/openldap/ldap.conf, /etc/nsswitch.conf) works on Suse 9.3 and 10.0 very well. The TLS encryption is working and is not the problem. Jens

6 9

Re: [SLE] How does one pronounce "SUSE"
by Doug McGarrett 11 Apr '06

11 Apr '06

At 12:20 PM 4/10/2006 +0530, Digvijoy Chatterjee wrote: >Content-Disposition: inline > >Hi, >Most of us here pronounce SUSE it as "susie" ,as in MJs blood on >dance floor hit "susie got your number". /snip/ Actually, SuSE is a German acronym, but I don't remember what it stands for, except the "u" is "und". I looked in a pre-Novell handbook, but could not find the words. In German, one would have said ZOO-zeh. Now, the official use is SUSE--the German is gone, and so, of course, is the acronym. I think most of us pronounce it "Suzy" as in the Everly Brothers' song, "Wake Up Li'l Suzy." I guess that is the same as the MJs, but I never heard of them, so I don't know. --doug -- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.1.385 / Virus Database: 268.4.0/306 - Release Date: 4/9/2006

11 15

How to control ssh login?
by Istvan Gabor 10 Apr '06

10 Apr '06

Hello all: I am running suse 10.0. ssh is enabled so that users can login the computer through ssh. But there are a few users who has weak passwords. How can I block these users from being able to login the computer through the network? Login at the console should not be blocked. Can sshd be controlled through inetd/xinetd? Thanks, IG _______________________________________________________________________ 3 könyv = 15+5% kedvezmény! http://www.bookline.hu/control/news?newsid=351&affiliate=fre3kokar2230

4 4