December 2003 - openSUSE Users - openSUSE Mailing Lists

Re: [SLE] /dev/ttyS0 and /dev/ttys0 - What's the difference?
by Mark Gray 18 Dec '03

18 Dec '03

Dylan <dylan(a)dylan.me.uk> writes: > Except that I got a snotty kernel message to use ttyS1 instead, so I've > set it back... Ha Ha! I did not check my /var/log/messages after I tried the /dev/cua* : Dec 18 07:16:06 k6 kernel: tty_io.c: process 26808 (bash) used obsolete /dev/cua - update software to use /dev/ttyS1 Dec 18 07:18:14 k6 kernel: tty_io.c: process 26813 (modemtest) used obsolete /dev/cua - update software to use /dev/ttyS1

1 0

Re: [SLE] /dev/ttyS0 and /dev/ttys0 - What's the difference?
by Mark Gray 18 Dec '03

18 Dec '03

Mark Gray <markgray-temp-1071686731(a)iago.nac.net> writes: > Dylan <dylan(a)dylan.me.uk> writes: > >> Greetings Sages... >> >> I have been trying (successfully, I'm pleased to say) to get a serial >> connection going for my telescope. In the process, I came across both / >> dev/ttyS0 and /dev/ttys0. Now, ttyS0 is clearly the serial port (=COM1) >> since that's the device which works and the other gives me an error. >> BUT, what is ttys0 (etc...) for? Indeed, why are there soooooo..... >> many unused and apparently useless devices in the /dev directory? > > The names can be anything, the important thing are the device numbers: > > markgray@soyo:~> l /dev/ttys0 > crw-rw-rw- 1 root tty 3, 48 2003-09-23 13:59 /dev/ttys0 > markgray@soyo:~> l /dev/ttyS0 > crw-rw---- 1 root uucp 4, 64 2003-09-23 13:59 /dev/ttyS0 > >>From /usr/src/linux/Documentation/devices.txt we see that /dev/ttys0 > is one of the old-style (BSD) Pseudo-TTY slaves (which are used when a > program wants another program to believe it is talking to a terminal) > and they have no hardware meaning whatsoever. Egads! /dev/cua* has returned. To have your program control your telescope you should be using /dev/cua0 (Ages ago the cua* versions of the ttyS* devices were terminated (with extreme prejudice:-) and now I see that they are back, simplifying your problem entirely.) If you need more info just let me know. (I though it odd when checking devices.txt to see the cua* devices listed and just gave it a shot -- they work just like they used to. Anybody have any idea when they returned, or if they are now a SuSE only feature?)

2 2

Re: [SLE] /dev/ttyS0 and /dev/ttys0 - What's the difference?
by Mark Gray 18 Dec '03

18 Dec '03

Dylan <dylan(a)dylan.me.uk> writes: > On Thursday 18 December 2003 12:28 pm, Mark Gray wrote: >> >> Egads! /dev/cua* has returned. To have your program control your >> telescope you should be using /dev/cua0 > > Well, cua1 in fact, but that's just cos I don't seem to have a physical > device for the ttyS0 / cua0. Hey-ho. > >> >> (Ages ago the cua* versions of the ttyS* devices were terminated >> (with extreme prejudice:-) and now I see that they are back, >> simplifying your problem entirely.) If you need more info just let >> me know. (I though it odd when checking devices.txt to see the cua* >> devices listed and just gave it a shot -- they work just like they >> used to. Anybody have any idea when they returned, or if they are >> now a SuSE only feature?) > > I sort of take it that the ttyS* are modem oriented and the cua* are raw > serial oriented, yes? No, the cua* come back from the days when there was a dialer separate from the modem. It just became conventional to have the ttyS* configured for answer mode, and the cua* for originate mode when the two functions were combined in modern modems. This came to be a kernel maintenance nightmare, so the cua* was removed (only for a while apparently.) You can still use the ttyS* for originate with only a little bit of programming, and otherwise the two are exactly the same device.

1 0

Re: [SLE] /dev/ttyS0 and /dev/ttys0 - What's the difference?
by Mark Gray 18 Dec '03

18 Dec '03

Dylan <dylan(a)dylan.me.uk> writes: > On Thursday 18 December 2003 07:03 am, Mark Gray wrote: >> Dylan <dylan(a)dylan.me.uk> writes: > <SNIP> >> > Secondly, /dev/ttyS0 has group uucp, and group rw privelidge by >> > default (at least that's how I found it). My user is also in group >> > uucp, but I recieved read/write permission denied on the device >> > until I set it to rw-rw-rw- Cound this be because I'm distributing >> > login with NIS? All boxes are runninf SuSE8.2, so I figure the user >> > IDs will be the same... >> >> The NIS does not matter. The problem is that /dev/ttyS0 expects to >> have a modem connected to it and the driver is waiting for a call-in, >> so if a naive program trys to talk to that device nothing is going to >> happen until the modem "rings". What program are you using to talk >> to your telescope? If you have the source I can tell you what >> initializations you have to give to /dev/ttyS0 in order for your >> computer to initiate the data exchange. > > I'm using xephem, which supplies a driver. It works - I had to set the > baud rate to match between the serial port and the 'scope and then > everything went fine. It's always the simple things. > > After I'd got it working with rw-rw-rw- I tried setting it back to > rw-rw---- and got the error again. Ah, I read your question too fast and thought your program was blocking trying to open /dev/ttyS0 -> Are you running kde using kdm or are you using console mode, xdm, or startx? If you are not using kdm then you are probably having trouble with the resmgr. Then the solution is just to add this to the end of /etc/pam.d/logins session required pam_resmgr.so (Or if you are using ssh, you can uncomment the line at the end of /etc/pam.d/sshd) See /usr/share/doc/packages/resmgr/README.SuSE for more info. If that is not it, what is wrong with setting your user as the owner?

2 1

SuSE 9.0 installed via FTP will not boot ...
by Thinker 18 Dec '03

18 Dec '03

The message I get is as follows... fsck failed. Please repair manually and reboot. The root file system is currently mounted read-only. To remount it read-write do.. bash# mount -n -o remount,rw / Attention: Only Control-D will reboot the system in maintenance mode. Shutdown or reboot will not work. Give root password to login: *****end message***** I have done this several times and each time the system reboots I get the same message. What am I doing wrong? -=Thinker

2 1

Regular Expressions & Logdigest
by Tim Schofield 18 Dec '03

18 Dec '03

Dear All I want to get rid of a couple of lines or rather add them to the ignore list in logdigest. It says use regular expressions - but i have no idea how this is done. The couple of attempts i have had have not worked. the lines i need to get rid of are: /var/log/messages: ________________________________________________________________________________ All lines that are not in the "ignore" list: =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- (3485 lines) Dec 5 00:16:00 antenna /USR/SBIN/CRON[5912]: (tim) CMD (fetchmail -v > /dev/null 2>&1) Dec 5 00:16:05 antenna popper[5914]: connect from 192.168.0.4 (192.168.0.4) Would somebody point me i the right direction as to how to remove these? TIA Tim

2 2

Re: [SLE] Automatic Module Loading
by James Oakley 18 Dec '03

18 Dec '03

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thursday 18 December 2003 12:34 pm, Pacheco Jason NPRI wrote: > What actually does the auto-loading. I know modprobe is used to do > the autoloading at boot by init. However, where is the file that > determines what modules modprobe should load? I know in Debian (and > it used to be the same in RedHat and Slack) it was just /etc/modules. It depends. The kernel uses some aliases, scripts use some others. Debian's /etc/modules file is used by an init script that simply loads whatever modules are listed in that file. You don't need it in SUSE. To force load your hid module, simply add it to HOTPLUG_USB_STATIC_MODULES in /etc/sysconfig/hotplug. - -- James Oakley Engineering - SolutionInc Ltd. joakley(a)solutioninc.com http://www.solutioninc.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE/4epz+FOexA3koIgRAkNSAKCI2ny0cyyOchfkYe19YefyhRiC2QCeNh5K AueRYH3U8rG+z2sB/FFLNI8= =Jbjd -----END PGP SIGNATURE-----

1 0

Automatic Module Loading
by Pacheco Jason NPRI 18 Dec '03

18 Dec '03

I bought a new mouse and keyboard and when X boots my mouse won't work. I noticed that when I open the little mouse dialog thing in YaST2 my mouse miraculously starts working. Anyway, by doing a diff on an lsmod before and after opening YaST2 I found the culprit. The module hid.o needs to be loaded at system boot, but I am not familiar with the module file hierarchy in SuSE. I know in Debian all I have to do is add `hid' to /etc/modules, but that file is nonexistant in SuSE. I decided I better RTFM, so I did and I think /etc/modules.conf is the file I need to alter. But what confuses me is that that file is just full of a bunch of `alias' lines, and if I don't put an alias for the `hid' it complains. So I added the line: alias usbdrv hid At system boot I thought I saw the module load, but when X starts my mouse doesn't work, and when I do an lsmod the module is not loaded. Am I even modifying the right file? Does an `alias' line actually load a module or does it just set an alias for the module? Jason Pacheco Systems Developer Technology Center for Cables & Connectors Naval Undersea Warfare Center

2 1

Where can I find a list of support DVD-RWs?
by Tom Nielsen 18 Dec '03

18 Dec '03

I guess I don't need to say anything in here since my subject said it. How's life? Tom

2 1

Kernel 2.6 step by step howto
by C. Emden 18 Dec '03

18 Dec '03

Hi, do there exist any guidances or step by step howtos describing the installation of the new stable Kernel for SuSE 9 ? (I tried to install 2.6test11 and had to give up because I wasn't able to find out howto create /usr/src/linux-2.6.N . And I'm a little confused about using Kernel 2.6 as gzip bzip2 or rpm) -- Please don't referr to my above mentioned problems in brackets - they are due to a lack of linux knowledge - I'm just looking for a direction /instruction. best regards, thanks in advance Claudia Emden

3 2