Re: [S.u.S.E. Linux] Getting FVWM95to run
![](https://seccdn.libravatar.org/avatar/c234364902ab5095da007dde62cec4d9.jpg?s=120&d=mm&r=g)
Jim Hodgers wrote:
Date: Sun, 22 Mar 1998 09:30:05 -0600 From: Leon McClatchey
To: suse-linux-e@suse.com Subject: Re: [S.u.S.E. Linux] startx problems Sender: owner-suse-linux-e@suse.com Reply-To: suse-linux-e@suse.com X-Mailinglist: suse-linux-e Mark Wagnon wrote:
S Pawlowicz wrote:
figure out how to alter my default window manager for my "root" login. X currently starts with Fvwm2. If I type "startx fvwm95", I still get fvwm2. I have managed to change default for other user's and the command line option works for all installed window managers under any login other than root. How do I change default window manager for "root"?
I've got the same problem, and part of the problem seems to be that their is no .xinitrc (or .bashrc for that matter) in the home directory for root. 've gotten around that problem mainly by logging on as a regular user and then have sudo setup where if necessary I can change to su to do whatever is necessary, (I've also got my mail set up to go to me as a regular user). I have tried copying a .bashrc and .xinitrc from my regular login and that didn't make a bit of difference. I've even changed the system .xinitrc so that fwm95 is launched as the default window manager, but it still doesn't do anything:-( (I've tried that also in Profile I think, (I gave it up and went on to other things after a bit)).
cya l8r Leon McClatchey leonmcclatchey@homemail.com
I had the same problem. Try "startx /usr/X11R6/bin" Worked for me and I a newbie. Don't ask why!! Jim "8000 ft. in the Rocky Mts" Hodgers ...Happiness as a running Alfa Romeo...
-- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
Not sure what happened, tried this before and it didn't work, but I did copy my .xinitrc from my "normal" user home directory to the /root directory and Xfree did come up with fvwm95 window manager. Also copied the .bashrc file over, but for some reason, when I log on as root, it still doesn't do quite the same, (even on the paths that are set up with no test). For instance, I can log in as my normal user and the andrew & thot path additions work, but when I log on as root, then I have to key in the entire path in order to fire up either one. But at least part of the problem is solved, guess I'll have to take a closer look at just what script root actually logs in on? Thanx Loads Leon McClatchey leonmcclatchey@homemail.com -- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
participants (1)
-
ldmccla@ibm.net