October 2009 - openSUSE Users - openSUSE Mailing Lists

[opensuse] kst2 in kde4
by Roger Oberholtzer 02 Oct '09

02 Oct '09

kst is a great tool. My first question is why it is in the educational category. It is a proper scientific/engineering tool. educational, to me, conjures up learning French or geography. labPlot is similarly improperly categorized. Now to the real issue. I am trying to run the current version 2 beta on a 4.3.1 kde4 system. However, the app fails with: Xlib: extension "GLX" missing on display ":0.0". Segmentation fault This is true. I do not have glx on the machine in question (ATI FireGL V3300 is not supported by the ATI driver...) Is this a compile flag that openSUSE set so that kst requires this? Or is it a thing kst will always need? I can file a bug if it is a bug. But I am exploring first. -- Roger Oberholtzer OPQ Systems / Ramböll RST Ramböll Sverige AB Krukmakargatan 21 P.O. Box 17009 SE-104 62 Stockholm, Sweden Office: Int +46 8-615 60 20 Mobile: Int +46 70-815 1696 -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

2 2

[opensuse] HELP WITH SUSPEND PROBLEM
by Jide Ogunmekan 02 Oct '09

02 Oct '09

Dear all I recently did an online update. I noticed it update compat-wireless and a few other stuff. After reboot my system now hangs when i try to suspend to ram or disk. I have to do a manual power off and reboot again. I run openSUSE 11.1 on a dell inspiron 6400. Linux 2.6.27.29-0.1-pae #1 SMP Any help will be appreciated Thanks Jide Ogunmekan -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

2 2

[opensuse] umm BASH gurus, what does the typo $!/bin/bash do?
by David C. Rankin 02 Oct '09

02 Oct '09

Guys, This was bizarre. Doing a quick script, I accidentally did a $!/bin/bash instead of #!/bin/bash. The script gave no output, but appeared to be struggling much longer than it should (~1 sec) then would exit normally. No error no nothing. Something worked though. I had set a trap to remove a temp dir in it and provide output. When I ssh'ed into another box and came back, evidently the EXIT signal was generated and the trap ran -- even though it the script defined $! instead of #!. Can anybody tell me, or point me to any info, concerning just what $! did?? -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

3 3

[opensuse] Re: Deleting /dev/md1 -- will other MDs get renumbered?
by Joachim Schrod 02 Oct '09

02 Oct '09

Hans Witvliet wrote: > On Fri, 2009-10-02 at 09:57 +0200, Joachim Schrod wrote: >> >> When I delete the Soft-RAID device /dev/md1 -- will the device >> names of the following RAID devices (i.e., /dev/md2, /dev/md3, >> etc.) stay the same on reboot, or will they be renumbered? >> > "Knowing the answer" might be something different then done-it-myself... > > [...] i decided to completely remove all disks* (with mdadm) [...] > The five disks belonging to md1 just remained belonging to md1 > > Does that answer your Q? Thanks a lot for your quick answer! And you're right, hearing from somebody who tried it out gives more confidence it doing it myself. Cheers, Joachim -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Joachim Schrod Email: jschrod(a)acm.org Roedermark, Germany -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

1 0

[opensuse] Re: umm BASH gurus, what does the typo $!/bin/bash do?
by Joachim Schrod 02 Oct '09

02 Oct '09

John Andersen wrote: > David C. Rankin wrote: >> >> Can anybody tell me, or point me to any info, concerning just what $! did?? > > So it was probably trying to figure out what $ meant. > Then it saw the !. > > When you type a word preceeded by an "!", bash thinks you want to recall a previous command > or "event". It happens in interactive shells, when the C-Shell-styled history expansion > (”!searchword”) is enabled. This is the default. Ahem, no. $! is a standard bash variable. From the bash manual: 3.4.2 Special Parameters ------------------------ The shell treats several parameters specially. These parameters may only be referenced; assignment to them is not allowed. [...] `!' Expands to the process ID of the most recently executed background (asynchronous) command. Since there has not been any background process in this subshell, it expands to the empty string. Joachim -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Joachim Schrod Email: jschrod(a)acm.org Roedermark, Germany -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

1 0

[opensuse] scsi
by Hans Witvliet 02 Oct '09

02 Oct '09

Hi all, Last week i needed some temporary storage, so i dug up my old scsi-box, and made one soft-raid5 with six 150G disk and another soft-raid5 with 300GB disk. So far so good. Today i got hold of another 300GB disk, and wanted to put it in the last empty slot. Here my stroubles started, Some of the disked moved (with resspect with their name) up. I remembered that this problem not only exist with scsi, but more recently also with usb. Googling i found out that it is supposed to be solved by using disk-labels instead of the disk-device-name. This might very well work when mounting disks individualy, but i failed to see how a softraid can be told to use labels. Pointers? Hans -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

2 3

[opensuse] Deleting /dev/md1 -- will other MDs get renumbered?
by Joachim Schrod 02 Oct '09

02 Oct '09

Hi, When I delete the Soft-RAID device /dev/md1 -- will the device names of the following RAID devices (i.e., /dev/md2, /dev/md3, etc.) stay the same on reboot, or will they be renumbered? I'm reluctant to try that on my live system, so maybe someone here knows the answer... ;-) TIA, Joachim -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Joachim Schrod Email: jschrod(a)acm.org Roedermark, Germany -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

3 2

[opensuse] Re: umm BASH gurus, what does the typo $!/bin/bash do?
by Joachim Schrod 02 Oct '09

02 Oct '09

David C. Rankin wrote: > Guys, > > This was bizarre. Doing a quick script, I accidentally did a $!/bin/bash > instead of #!/bin/bash. The script gave no output, but appeared to be > struggling much longer than it should (~1 sec) then would exit normally. No > error no nothing. Something worked though. I had set a trap to remove a temp > dir in it and provide output. When I ssh'ed into another box and came back, > evidently the EXIT signal was generated and the trap ran -- even though it the > script defined $! instead of #!. > > Can anybody tell me, or point me to any info, concerning just what $! did?? Normally, I script that has $!/bin/bash in its first line, should start an interactive bash and wait for further input. I.e., I don't think it exited normally, you just got a same-looking prompt from a subshell. When you then enter "exit" or type Ctrl-D the bash is finished and the rest of this script will be executed. Try it: A basic example: puma:tmp $ cat try.sh $!/bin/bash echo hallo Let's see which process we are in: puma:tmp $ ps -fp $$ UID PID PPID C STIME TTY TIME CMD schrod 6080 6079 0 09:44 pts/8 00:00:00 bash Well, our process id is 6080. Execute the script and check which process we are in now: puma:tmp $ ./try.sh puma:tmp $ ps -fp $$ UID PID PPID C STIME TTY TIME CMD schrod 6190 6189 0 09:46 pts/8 00:00:00 /bin/bash As you'll see, a different process, with process id 6190. (The parent process id 6189 is the try.sh-process that has 6080 as parent.) No exit that sub-shell. puma:tmp $ exit hallo Rest of the script (echo hallo) is executed, as you can see. Are you sure that the trap run? The file was not there -- but was it created in the first place? Your trap statement in the shell script will never be reached and thus the trap should not be set up at all. Technical Background: Concerning #! as the first 2 chars in a script: This is necessary for the execution of this command with the system call exec() (or one of its siblings, like execve()). Then it provides the "magic number" for the loader to handle this "executable". I.e., it is necessary when called from another program or with "exec" from another shell script. It is not necessary when called interactively from a bash session. Thus, the first line was $!/bin/bash. $! expands to empty, so it's just a line /bin/bash. That line causes bash to be executed. Since there are no further arguments, an interactive shell is started. HTH, Joachim -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Joachim Schrod Email: jschrod(a)acm.org Roedermark, Germany -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

1 0

[opensuse] Booting w/o RAM disk w/Grub...
by Linda Walsh 02 Oct '09

02 Oct '09

I'm befuddle by grub. I'm able to boot w/o a ram disk if I convert a machine back to lilo. There, everything is documented in the kernel docs. Plain as day. The grub stuff -- and ram disks - everything is misdirection, er, I mean indirection (or do I). First in grub, it's got 'root' wrong. It requires what I call "boot" to be call "root". Then it has no place for the real root param. I'm guessing that's what the command line to the kernel is for, the root= param. But I haven't had alot of luck with that so far. Also, I'm not seeing any output from the point grub starts until the system (may) display a login prompt on the console. So I don't know if the boot is starting then dying somewhere, or never starts. I tried the previous 11.1 suse kernel and it wouldn't boot at all any more either (and gives no output). So 1) how do I get my output back to "normal" (both in my boot and the suse boots -- which are also blank, but the newer ones eventually show a prompt). Did someone patch the kernel's default to not generate it's normal output? 2) How do I turn all frame buffer nonsense and let it just talk to the console on my console? 3) what charms do I need for grub to boot from disk (w/out a ram disk) (I know the basics -- that my hard disk drivers, file system drivers -- have to be built-in -- I would like to go through and include drivers I need, make optionals 'modules', and make not-applicable options 'off'. What mode should my console be in? Should I even compile in a frame buffer? I do all my administration remotely, so I don't need graphics on this system. (it only has about 1024x768x16 at most, I think...) Thanks for pointers. I make another try every couple of days -- but it's a pain taking down my internet access -- mostly waiting for the SLOW Dell BIOS BOOT. Sigh. Once it gets past that, it comes up pretty fast. Thanks, -linda -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

1 0

[opensuse] Re: Partitioning problem in installing oS v11.1
by jdd 02 Oct '09

02 Oct '09

Stan Goodman a écrit : > I had succeeded in installing the system in partitions that I had made > using DFSee I don't know this one > > I also made three partitions, for Swap (typr 82), Root and Home (both type > 83). did you save your work? seems not > When the installer proposes partitioning, it doesn't see the partitions I > have made, I think there is a "read partition table" option and a "read fstab" one (here probably different) although I know they are there. and hox do you knox this? what tool give you the info? Give us the output > What do I have to do to get it to forget the past and live in the present? as somebody else said, why don't you use YaST installer to do the partitionning? jdd -- http://www.dodin.net http://valerie.dodin.org http://news.opensuse.org/2009/04/13/people-of-opensuse-jean-daniel-dodin/ -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

9 25