starting fluxbox without icons on desktop

Forum: X and Fluxbox
Topic: starting fluxbox without icons on desktop
started by: liran

Posted by liran on May 28 2005,15:56

the documentation was helpful enough to cover how to
remove the automated help-screen poping up with dillo.

how do i keep it so my desktop has no icons on it after i
restart fluxbox?

(for a temporary issue i just go to Desktop -> No Icons, but
i wasn it permenant)

thanks
liran

Posted by SaidinUnleashed on May 28 2005,16:10

remove the following lines from .xinitrc

Code Sample

if egrep -qv noicons /proc/cmdline 2>/dev/null; then
enhance &>/dev/null &
fi

Posted by meo on May 29 2005,06:59

Hi there!

Just don't forget to make a backup after that otherwise the file will be restored as is.

Have fun,
meo

Posted by liran on May 29 2005,07:19

well i've done that but it also removed those bars to the left of the screen (the mp3 player, virtual consoles, etc). i just want a desktop without icons, i still want those bars/wharfs...

how do i bring them back?

Posted by ke4nt1 on May 29 2005,08:15

The menu option Desktop > No Icons runs the command
" killall -9 xtdesk "

Try placing that line in your /home/dsl/.xinitrc file,
right ABOVE the line that says " fluxbox "

73
ke4nt

Posted by liran on May 29 2005,10:02

that doesnt work, sorry...
any other ideas?

(just to make it clear - i want the wharfs/tool-bar to the right but no icons on the desktop)

thanks so far

Posted by adssse on May 29 2005,14:08

Use this for your .xinitrc (comment out the stuff already in there using '#'). I just tried this on my pc and it loaded just with the slit, no icons.

wmix &>/dev/null &
fluxter -w &>/dev/null &
wmcpuload &>/dev/null &
wmnet -w &>/dev/null &
mount.app &>/dev/null &
asmem -withdrawn -bg black -fg white &>/dev/null &
fluxbox 2>/dev/null

(Thanks to clacker who explained most of this to me)

Posted by liran on May 29 2005,14:13

im at work right now.
thanks alot for the reply, ill check it when i get back and report if this was
sucessful or not.

laters

Posted by ke4nt1 on May 29 2005,15:41

Here's another option..

If your filesystem is writable ..
Edit /usr/bin/enhance like this..

Quote

#!/usr/bin/perl -w
# Author John Andrews
`killall -9 fluxter &>/dev/null`;
system("fluxter -w &");
my $vars = `ps ax &`;
unless ( $vars =~/xtdesk/) {
system("xtdesk &>/dev/null &");
}
`killall -9 xtdesk &>/dev/null`; <-- add this one line which kills the command
unless ( $vars =~/wmcpuload/) {
system("wmcpuload &>/dev/null &" )
}
unless ( $vars =~/wmnet/) {
system("wmnet -w &>/dev/null &" )
}
unless ( $vars =~/mount.app/) {
system("mount.app &>/dev/null &" )
}
unless ( $vars =~/asmem/) {
system("asmem -withdrawn -bg black -fg white &>/dev/null &" )
}
unless ( $vars =~/wmix/) {
system("wmix &>/dev/null &" )
}
exit;

73
ke4nt

Posted by mikshaw on May 29 2005,16:00

Seems strange to start xtdesk just to shut it down.

How about removing this part instead:
unless ( $vars =~/xtdesk/) {
system("xtdesk &>/dev/null &");
}

Posted by ke4nt1 on May 29 2005,17:10

Well, that's exactly what "I" have been doing to mine, mikshaw..

but I was trying to keep it as unaltered ( or restorable ?)
as possible, and simply add the one line..

Both work, pick your poison..

73
ke4nt

Posted by liran on May 29 2005,23:14

thanks adssse
amazingly, it works fine.

can you explain to me what does the &>/dev/null & directive does?

works like a charm

Posted by adssse on May 30 2005,01:26

Glad to hear that it works.

The '&>/dev/null' section effectively takes any output from the program and throws it away by sending it to /dev/null. The last '&' at the end tells this program to run in the background.

Posted by StevenCheng on Aug. 01 2005,08:22

I only want to remove the mounting windows of the tools bar. Is it possible?

Posted by mikshaw on Aug. 01 2005,13:35

Quickest and easiest way is to remove the "enhance" line in $HOME/.xinitrc. This will prevent the dockapps AND icons from loading.
If you want to keep the icons, replace this line with "xtdesk &>/dev/null &".
If you want to keep the other dockapps, add a command for each.

EDIT: I see now this is all covered in this very thread. Beyond that, what more are you looking for? The mounting is done with mount.app. The other docakapps are listed in /usr/bin/enhance.

Posted by StevenCheng on Aug. 02 2005,02:40

Quote (mikshaw @ Aug. 01 2005,09:35)

Thanks again,

I've tried to remove the enhance line in .Xinitrc. It works fine but the user still can use the DSL--Desktop--Full Enhanced Desktop to resume the "tools windows" and use that windows to mount the HD...

I'm thinking may be the best way is to restrict the user right of mounting. But since I'm completely new in Linux, I don't know how to restrict user right...

Posted by mikshaw on Aug. 02 2005,03:20

Remove "user" from the 4th column of /etc/fstab, for any device which you do not want the non-root user(s) to mount. However, user dsl still has power to use "sudo mount" without a password. You'll need to run the command "visudo" as root in order to edit the sudoers file, which means learning a little about vim, and a little about sudoers.

You could also remove or change permissions on mount.app (I think it's in /usr/X11R6/bin). If you made it executable only by owner, normal users wouldn't be able to run it.
This is only a cosmetic fix, though. Any user can still open a terminal and type commands.

DSL really isn't a great ball of security from local users...I don't believe it was ever intended to be that. You can make it as secure as you want it, but it's going to take a lot of work for anyone who is new to Linux.

Posted by StevenCheng on Aug. 02 2005,04:10

Quote (mikshaw @ Aug. 01 2005,23:20)

when I tried to run the visudo command, I got the following error message:
visudo: no editor found (editor path= /usr/bin/editor)

What does it mean? Does it mean that the editor program is not installed in my system?

So you mean that I have to learn how to use the visudo command (as root) to edit the sudoers file in order to restrict the user of mounting HD? Am I correct?

Thanks again...

Posted by StevenCheng on Aug. 02 2005,04:37

I've open the /etc/sudoers file with beaver editor (I don't know how to use the visudo yet!) and saw the following contains:

#sudoers file.

Cmnd_Alias SHUTDOWN=/sbin/shutdown
Cmnd_Alias HALT=/sbin/halt
Cmnd_Alias REBOOT=/sbin/reboot

root ALL=(ALL) ALL
dsl ALL=NOPASSWD: SHUTDOWN,HALT,REBOOT

So, do I need to modify the contain inside? How?

Thanks in advance...

Posted by mikshaw on Aug. 02 2005,05:01

From what I understand, you should not edit sudoers as a regular text file. I don't know why, but then I never bothered to find out. You might be able to link beaver to /usr/bin/editor (ln -s /path/to/beaver /usr/bin/editor), but I've never tried visudo with a gui editor.

I've edited sudoers only a couple of times, and needed to have the manpage next to me while doing it, so I can't say exactly what to do. You'll probably want to get rid of the NOPASSWD part though.
< http://www.die.net/doc/linux/man/man5/sudoers.5.html >

Posted by SaidinUnleashed on Aug. 02 2005,05:27

It's perfectly okay to edit the sudoers file with a normal editor.

Just make sure to follow the proper syntax.

-J.P.

Posted by mikshaw on Aug. 02 2005,15:23

Code Sample

# This file MUST be edited with the 'visudo' command as root.

This is at the start of /etc/sudoers in both Suse and Slackware, which is the only reason I posted that. I wonder why they would bother writing a script for opening the file, plus give this message, if it can be edited like any other config file. Maybe just to prevent security leaks?

Posted by StevenCheng on Aug. 04 2005,01:27

Thanks!