February 1998 - openSUSE Users - openSUSE Mailing Lists

Re: [S.u.S.E. Linux] Running SuSE Linux
by svet＠alamo.satlug.org 02 Feb '98

02 Feb '98

> > 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? > > > -- > 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, In KDE, there is a script called "startkde." You need to change your .xinitrc to say WINDOWMANAGER=/opt/kde/bin/startkde. That brings up more than the windowmanager..it brings up the windowmanager, kfm, and kpanel, as well as some background stuff, like kaudioserver. Just looking at my set up on S.u.S.E 5.1, I know there is a /usr/X11R6/bin/kde and a /opt/kde/bin/startkde. The scripts look exactly the same, however, I haven't used the kde executable, since in most of the KDE documentation, they reccomend using the startkde script. This has yet to fail me. I have worked with beta 1 and beta 2 of kde, and once I get everything configured, it runs like a dream. If you are still having problems, email me your kde and startkde scripts, and I'll compare them. best regards, svet > -- > --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 > -- 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

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? BTW, try running /sbin/SuSEconfig after you make changes to /etc/profile. That logs in the changes, here BUT YMMV, as they say. Wayne 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

1 0

Re: [S.u.S.E. Linux] Running SuSE Linux
by jccarr＠nwlink.com 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 > 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

1 0

Re: [S.u.S.E. Linux] Running SuSE Linux
by mperry＠mperry.basin.com 02 Feb '98

02 Feb '98

On Sun, Feb 01, 1998 at 10:29:51PM -0500, Wayne Topa stated: > > > Subject: Re: [S.u.S.E. Linux] Running SuSE Linux > Date: Fri, Jan 30, 1998 at 12:37:14PM -0800 > > In reply to:Bodo Bauer > > Quoting Bodo Bauer (bb(a)suse.de): > > > > > > Eric L. Green wrote: > > > > > > I don't see any way to start up a different window manager other than > > > the SuSE-offered ones, without modifying the actual "startx" script. Most > > > installations' "startx" respects the .Xclients file and sources its > > > contents prior to doing whatever other stuff is desired. I didn't see > > > anything in SuSE's "startx" that did that. > > and Bodo replied > > > > > Yust set environment variable WINDOWMANAGER to the wm you like... > > > > Well I tried that. As a user, I did, export WINDOWMAKER=/usr/X11R6/bin/fvwm95 > and then startx. Nope still fvwm2. So I exited and logged in again. > Same thing. So I then modified /etc/profile and changed IT to fvwm95. > Logged in the user again and STILL fvwm2. Checked WINDOWMANAGER and > it was still fvwm2. So rebooted the system ( This really should NOT > be necessary!!!) and YES WINDOWMANAGER is now /usr/X11R6/bin/fvwm95. > Logged in the used and did startx, again. Windowmanager is STILL > fvwm2. > > For those that might write and so SO WHAT, the user can change it to > what ever he wants. NO SO /etc/profile is common to all users. If > the change HAS to be made there it will be the same for ALL USERS. > > I still don't know why I have to reboot the system to get changes > logged in. There MUST be a better way but I have not found it yet. > > I still have not finished RTFM yet tho. Who ever told me that this > was just like Slackware must have never run Slackware! > > In playing(!) around in X with the window managers (switching back & > forth checking them out) I had something happen that I have never seen > on Linux before. I had finally had enough and Hit the button to exit > fvwm2 & X. Windows did not exit, just closed a couple of xterms and > HUNG. So I hit ctrl/alr/BS and at that point the system HUNG. By > HUNG I mean, I could switch to other consoles but nothing was accepted > from the keyboard on ANY console. The hard disk was clicking away but > ALL users were locked out. After 15 minutes of this I shut down the > power to the computer. Rebooting went normal (all partitions had to be > fsck'ed of course) but the system came up fine. With WINDOWMANAGER > pointing to fvwm95 but X coming up in fvwm2. > > This is starting NOT to be fun, guys! 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

1 0

Re: [S.u.S.E. Linux] Running SuSE Linux
by wtopa＠ix.netcom.com 02 Feb '98

02 Feb '98

Subject: Re: [S.u.S.E. Linux] Running SuSE Linux Date: Fri, Jan 30, 1998 at 12:37:14PM -0800 In reply to:Bodo Bauer Quoting Bodo Bauer (bb(a)suse.de): > > > Eric L. Green wrote: > > > > I don't see any way to start up a different window manager other than > > the SuSE-offered ones, without modifying the actual "startx" script. Most > > installations' "startx" respects the .Xclients file and sources its > > contents prior to doing whatever other stuff is desired. I didn't see > > anything in SuSE's "startx" that did that. and Bodo replied > > Yust set environment variable WINDOWMANAGER to the wm you like... > Well I tried that. As a user, I did, export WINDOWMAKER=/usr/X11R6/bin/fvwm95 and then startx. Nope still fvwm2. So I exited and logged in again. Same thing. So I then modified /etc/profile and changed IT to fvwm95. Logged in the user again and STILL fvwm2. Checked WINDOWMANAGER and it was still fvwm2. So rebooted the system ( This really should NOT be necessary!!!) and YES WINDOWMANAGER is now /usr/X11R6/bin/fvwm95. Logged in the used and did startx, again. Windowmanager is STILL fvwm2. For those that might write and so SO WHAT, the user can change it to what ever he wants. NO SO /etc/profile is common to all users. If the change HAS to be made there it will be the same for ALL USERS. I still don't know why I have to reboot the system to get changes logged in. There MUST be a better way but I have not found it yet. I still have not finished RTFM yet tho. Who ever told me that this was just like Slackware must have never run Slackware! In playing(!) around in X with the window managers (switching back & forth checking them out) I had something happen that I have never seen on Linux before. I had finally had enough and Hit the button to exit fvwm2 & X. Windows did not exit, just closed a couple of xterms and HUNG. So I hit ctrl/alr/BS and at that point the system HUNG. By HUNG I mean, I could switch to other consoles but nothing was accepted from the keyboard on ANY console. The hard disk was clicking away but ALL users were locked out. After 15 minutes of this I shut down the power to the computer. Rebooting went normal (all partitions had to be fsck'ed of course) but the system came up fine. With WINDOWMANAGER pointing to fvwm95 but X coming up in fvwm2. This is starting NOT to be fun, guys! 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

1 0

Re: [S.u.S.E. Linux] Is this a Bash 2 problem?
by wtopa＠ix.netcom.com 02 Feb '98

02 Feb '98

If it DID over ride the one in /etc/profile I would not have written the first message in this thread if the first place! My custom prompt in .bash_profile DIDN't work, UNTIL I commented out the PROMPT_COMMAND in /etc/profile. Did you read all the threaded messages??? Wayne Subject: Re: [S.u.S.E. Linux] Is this a Bash 2 problem? Date: Sun, Feb 01, 1998 at 09:06:24PM -0500 In reply to:Luis A. Costabile Quoting Luis A. Costabile (luis(a)lac.resonet.com): > > > On Sun, 1 Feb 1998, Wayne Topa wrote: > > > > > > > Found the answer to this one. It is NOT a Bash 2 problem! > > It is another SuSE gotcha! > > > > SuSE customizes the login prompt for EVERYONE in /etc/profile > > with PROMPT_COMMAND. If you comment that out users can customize > > their own prompt in .bash_profile, like always. The lines in the > > original message (below) work just fine now. > > Why comment it out? it's meant for users who don't have or need a special > prompt. If you do need something diff then your variable will over ride > the one in /etc/profile. > > -- > Lou A. Costabile Voice and Fax: [613] 781-7061 > <A HREF="mailto:luis@lac.resonet.com">mailto:luis@lac.resonet.com</A> > To get Receipt Notification include %rec% anywhere in the Subject field. > > You must restart your computer before the new message will take effect. > Do you want to restart your computer now? Yes or Yes > -- > > -- > 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] Is this a Bash 2 problem?
by luis＠lac.resonet.com 02 Feb '98

02 Feb '98

On Sun, 1 Feb 1998, Wayne Topa wrote: > > > Found the answer to this one. It is NOT a Bash 2 problem! > It is another SuSE gotcha! > > SuSE customizes the login prompt for EVERYONE in /etc/profile > with PROMPT_COMMAND. If you comment that out users can customize > their own prompt in .bash_profile, like always. The lines in the > original message (below) work just fine now. Why comment it out? it's meant for users who don't have or need a special prompt. If you do need something diff then your variable will over ride the one in /etc/profile. -- Lou A. Costabile Voice and Fax: [613] 781-7061 <A HREF="mailto:luis@lac.resonet.com">mailto:luis@lac.resonet.com</A> To get Receipt Notification include %rec% anywhere in the Subject field. You must restart your computer before the new message will take effect. Do you want to restart your computer now? Yes or Yes -- -- 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] Is this a Bash 2 problem?
by wtopa＠ix.netcom.com 01 Feb '98

01 Feb '98

Found the answer to this one. It is NOT a Bash 2 problem! It is another SuSE gotcha! SuSE customizes the login prompt for EVERYONE in /etc/profile with PROMPT_COMMAND. If you comment that out users can customize their own prompt in .bash_profile, like always. The lines in the original message (below) work just fine now. Wayne Subject: [S.u.S.E. Linux] Is this a Bash 2 problem? Date: Sat, Jan 31, 1998 at 04:20:21PM -0500 In reply to:Wayne Topa Quoting Wayne Topa (wtopa(a)ix.netcom.com): > > Hello > > I wonder if there are any Bash 2.0 guru's on this list? I had a > prompt line set up that worked in Bash 1 that doesn't now. Have tried > to get working but to no avail. > > Here it is: > > V_TERM=`tty` > export PS1="\[`setterm -foreground green`\]\[`setterm -bold > on`\]VT${V_TERM##/dev/tty} \u-S1:\w\\$\[`setterm -default`\] " > > Not a big deal but I am curious. Any ideas?? > > Wayne > > -- > 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] Troubles upgrading to 5.1
by wtopa＠ix.netcom.com 01 Feb '98

01 Feb '98

Geee Michael, this sounds like SuSE should have the same warning as Slackware does on upgrading. DON'T without starting from a clean HD. I will follow this thread with MUCH interest. Hope that you can get some answers from SuSE on this one! Wayne Subject: [S.u.S.E. Linux] Troubles upgrading to 5.1 Date: Sun, Feb 01, 1998 at 11:15:06AM -0800 In reply to:Michael Perry Quoting Michael Perry (mperry(a)mperry.basin.com): > > I recently (read last nite) upgraded from SuSE 5.0 to 5.1. The first part > when quite well which included booting the cd, telling yast to upgrade > only selected software packages, and then checking out which ones were > actually going to come. I got the usual post install message since I > gather some software is on other cd disks and was told to reboot and the > rest would be done. I did this but then found that yast claimed all had > been done and came up with a few mislinked libraries, programs that > suddenly wouldn't work like WABI, an upgraded x server which completely > overwrote my existing and somewhat customized .fvwm2rc, and installing the > demo version of applix over my registered copy. I had correctly selected > all the options but still even after saving the config on a floppy > diskette as it asked spent some amount of time figuring out why suddenly > things like slang were not linked correctly, why WABI complained suddenly > about /dev/zero, and why the /etc files like profile were completely > overwritten. > Libraries I had compiled myself like xforms and slang seemed broken or > symbolic links had not been maintained in the upgrade process. Is this > normal? I thought yast would make copies of things like profile from the > existing installation and perhaps my .fvwm2rc. I always keep copies so > its not a totally big deal. I am more curious about how this happened and > what I perhaps did wrong. Does yast have a problem with libraries that I > compile without using it? > > > -- > --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

1 0

[S.u.S.E. Linux] Troubles upgrading to 5.1
by mperry＠mperry.basin.com 01 Feb '98

01 Feb '98

I recently (read last nite) upgraded from SuSE 5.0 to 5.1. The first part when quite well which included booting the cd, telling yast to upgrade only selected software packages, and then checking out which ones were actually going to come. I got the usual post install message since I gather some software is on other cd disks and was told to reboot and the rest would be done. I did this but then found that yast claimed all had been done and came up with a few mislinked libraries, programs that suddenly wouldn't work like WABI, an upgraded x server which completely overwrote my existing and somewhat customized .fvwm2rc, and installing the demo version of applix over my registered copy. I had correctly selected all the options but still even after saving the config on a floppy diskette as it asked spent some amount of time figuring out why suddenly things like slang were not linked correctly, why WABI complained suddenly about /dev/zero, and why the /etc files like profile were completely overwritten. Libraries I had compiled myself like xforms and slang seemed broken or symbolic links had not been maintained in the upgrade process. Is this normal? I thought yast would make copies of things like profile from the existing installation and perhaps my .fvwm2rc. I always keep copies so its not a totally big deal. I am more curious about how this happened and what I perhaps did wrong. Does yast have a problem with libraries that I compile without using it? -- --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

1 0