So, something similar to this? :

http://crunchbang.org/forums/viewtopic.php?pid=287895

Cool, I may have to give the liquorix version a try.

And this appears to be Post 100 for me; so back on topic:

How is that kernel running for you? I had some issues when I tried to compile my own - couldn't build some drivers against it - don't know if I hosed something, or there are some changes to the kernel I'll need to resolve (drivers for my internal SD card reader, and nvidia video card).

back on topic - added some bling:

Quote from: VastOne on July 17, 2013, 03:22:52 AM
Good question... a quick search shows no easy answers.  I would guess this would be resolved with some of your magic.

Nice Scrot and DE!

Then it must be karma that I came back with a clean shot showing the Temple of the Magician at Uxmal, Mexico 

Worth looking into.

I see from the man page that xfce4-terminal has some nice options at startup; anyone know if the background can be blurred using the compositor?

back on topic - VSIDO w/ fvwm -



edit - clean shot with new wall; Temple of the Magician, Mayan ruins at Uxmal

No, systemd should not be an issue, but the above script is for the systemv init.

You would need to create a systemd script (or whatever they call it) that does the same thing and set it up to run at startup. Not that hard if you have not done it - basically write the script in the proper format and get it in the correct location. The Arch Wiki has some good examples of how that is done.

I still have no idea why network services would be tied to a login manager - that just doesn't make sense.

Your other option would be to use the non-systemd image/version on your server since, I assume, it just sits there providing various services, and use the script I provided if necessary.

more of the same:

I may have found the issue. lwfitz, what version of VSIDO are you running as the samaba server, the regular version which used the rc init scripts, or the fluxbox+systemd?

If you are using the version with the rc init scripts, I think I have found an issue with VSIDO/SID. I have Debian testing on my desktop and VSIDO on my laptop, both have samba installed (although I use neither as a samba server). On my Debian testing box, there is an init script to start the samba services in /etc/init.d/, on my VSIDO laptop, this script is missing. If that script is missing on your server as well, then your server cannot start the samba services properly - I have no idea why lightdm is creating these shares; but disabling lightdm results in no samba.

My solution for you - attached in code blocks is the init script for samba from my Debian testing machine, copy it to /etc/init.d/ and make the appropriate symlinks to the run levels you use for your samba server.

A handy program to use for this is sysv-rc-conf - it is a command line tool run as root that brings up a handy checkbox matrix of available run levels and services (it is in the repos). Checking a box creates the symlinks in the appropriate run level, unchecking it will disable the service. With sysv-rc-conf, you can quickly activate the samba service and disable the lightdm service for your run level of choice. This should start the samba services properly and allow you to run your server sans window manager.

Obviously, if you are using systemd, or the samba init script does exist on your server, then this post is irrelevant and your back to Square d'Uno.

I am totally stumped why lightdm would start samba services/shares; I know the login managers handle some services - (mounting drives as non-root is the main one) but why samba? Maybe read the /etc/init.d/lightdm file for some samba statement?

Goog luck, amigo.

samba init script, copy to /etc/init.d

#!/bin/sh

### BEGIN INIT INFO
# Provides:          samba
# Required-Start:    $network $local_fs $remote_fs
# Required-Stop:     $network $local_fs $remote_fs
# Default-Start:     2 3 4 5
# Default-Stop:      0 1 6
# Should-Start:      slapd cups
# Should-Stop:       slapd cups
# Short-Description: start Samba daemons (nmbd and smbd)
### END INIT INFO


# Defaults
RUN_MODE="daemons"

# Reads config file (will override defaults above)
[ -r /etc/default/samba ] && . /etc/default/samba

PIDDIR=/var/run/samba
NMBDPID=$PIDDIR/nmbd.pid
SMBDPID=$PIDDIR/smbd.pid

# clear conflicting settings from the environment
unset TMPDIR

# See if the daemons are there
test -x /usr/sbin/nmbd -a -x /usr/sbin/smbd || exit 0

. /lib/lsb/init-functions

case "$1" in
start)
log_daemon_msg "Starting Samba daemons"
# Make sure we have our PIDDIR, even if it's on a tmpfs
install -o root -g root -m 755 -d $PIDDIR

if [ -n `which testparm` ]
then
NMBD_DISABLED=`testparm -s --parameter-name='disable netbios' 2>/dev/null`
fi
if [ "$NMBD_DISABLED" != 'Yes' ]; then
log_progress_msg "nmbd"
if ! start-stop-daemon --start --quiet --oknodo --exec /usr/sbin/nmbd -- -D
then
log_end_msg 1
exit 1
fi
fi

log_progress_msg "smbd"
if ! start-stop-daemon --start --quiet --oknodo --exec /usr/sbin/smbd -- -D; then
log_end_msg 1
exit 1
fi

log_end_msg 0
;;
stop)
log_daemon_msg "Stopping Samba daemons"
log_progress_msg "nmbd"

start-stop-daemon --stop --quiet --pidfile $NMBDPID
# Wait a little and remove stale PID file
sleep 1
if [ -f $NMBDPID ] && ! ps h `cat $NMBDPID` > /dev/null
then
# Stale PID file (nmbd was succesfully stopped),
# remove it (should be removed by nmbd itself IMHO.)
rm -f $NMBDPID
fi

log_progress_msg "smbd"
start-stop-daemon --stop --quiet --pidfile $SMBDPID
# Wait a little and remove stale PID file
sleep 1
if [ -f $SMBDPID ] && ! ps h `cat $SMBDPID` > /dev/null
then
# Stale PID file (nmbd was succesfully stopped),
# remove it (should be removed by smbd itself IMHO.)
rm -f $SMBDPID
fi

log_end_msg 0

;;
reload)
log_daemon_msg "Reloading /etc/samba/smb.conf" "smbd only"

start-stop-daemon --stop --quiet --signal HUP --pidfile $SMBDPID

log_end_msg 0
;;
restart|force-reload)
$0 stop
sleep 1
$0 start
;;
        status)
status="0"
NMBD_DISABLED=`testparm -s --parameter-name='disable netbios' 2>/dev/null`
if [ "$NMBD_DISABLED" != "Yes" ]; then
status_of_proc -p $NMBDPID /usr/sbin/nmbd nmbd || status=$?
fi
status_of_proc -p $SMBDPID /usr/sbin/smbd smbd || status=$?
exit $status
;;
*)
echo "Usage: /etc/init.d/samba {start|stop|reload|restart|force-reload|status}"
exit 1
;;
esac

exit 0


If this init script gets your server running, can it be added to future VSIDO releases? Otherwise link/copy it to your HowTo.

If you remove lightdm from startup, can you start the samba server from the command line?

If so, one work around until you figure this out may be to restart samba from rc.local.

Odd bug that samba services would be tied to lightdm.

Samba shouldn't need a login manager - smbclient should have command line options like ftp

edit - found this; have never heard of smbtree:

www.google.com/url?sa=t&rct=j&q=&esrc=s&source=web&cd=6&ved=0CEgQFjAF&url=http%3A%2F%2Fanswers.oreilly.com%2Ftopic%2F79-how-to-connect-linux-clients-to-samba-workgroups-with-command-line-tools%2F&ei=zZbhUb28JqvB4AO_34HACg&usg=AFQjCNGcMY0o_xkGuyVVWlEUHvBUX3l2ig&bvm=bv.48705608,d.dmg

rkwurth asked a question in the #! forum -- http://crunchbang.org/forums/viewtopic.php?pid=321189#p321189

This solution should work on any window manager actually. If you have wmctrl and zenity installed, you can have a popup dialog of open apps to switch to (a common Alt-Tab behavior for other wm's)

The code:

wmctrl -ia `wmctrl -l | cut -d' ' -f1,4- | zenity --list --column Window | cut -d' ' -f1`

can be bound directly to a key binding or used from a script. Downside is that it will show all the running apps (and switch to them) regardless of the desktop.

A wise man once said "screenshot or it didn't happen!"



There is also a program called superswitcher that apparently does this - and other things - but I have never used it:

https://code.google.com/p/superswitcher/

Been checking out the latest release of E17 from the Sid repos - there are build scripts available that will get the latest release from git, but I couldn't get them to work; they are possibly obsolete.

E17 has always marketed itself as a low resource window manager that allows for a lot of bling - and although that was pretty much accurate, in the past it was plagued by instability - it would regularly seg fault on my desktop single core AMD-64. Because of the instability, I never really used it as a main window manager; I would tinker with it because it is modular - like Fvwm - and you load the modules you choose which allowed for a lot of customization.

The current build in the repos seems pretty stable. No crashes yet, but I'm using my HP I3 laptop this time. Lowrider over at #! has been running stable E17 on his #! and Arch systems so it looks like the stable release is indeed stable.

Some shots showing resource usage - fluxbox with compton, Xfce with compositing, E17 with compositing, two terminals and conky. For fluxbox and E17 the terminal is urxvt with transparency, for Xfce it's the xfce4-terminal:



The available themes for E17 have improved a lot (more variety) - use to be they were almost all of the glassy/glossy aesthetic or OSX mimics; there are plenty more modern and gray scale color palettes now. Downside to customizing E17 is that it is a major pain to make your own - E17 uses it's own internal theme elements, but non-e17 apps use available gtk themes which is a nice improvement. As with earlier versions of E17, the E17 themes can be mixed and matched to your liking - i.e the clock module from theme X can be used in theme Y. Most of the buggy modules have been dropped from the base install, as the E17 devs seem to be focusing on improving what works.

E17 loads the compositing module by default, so I used the internal argb settings in conky for a transparent conky window.

All in all a big improvement for the E17 developers, but IMO they are a day late and a dollar (euro if you prefer) short. The improvements made to recent versions of Xfce - particularly the compositor - have pretty much made E17 irrelevant as far as having a WM/DE that combines low resources with as much bling as you want. Unless you're really concerned about the additional resources Xfce uses, it's the better choice, But if you want something different to tinker with, by all means give it a spin - or maybe load Bodhi or Elive into VM's - both are debian/ubuntu based; I liked elive when I had it installed, but E17 at that time just wasn't stable enough to keep it around. Never tried Bodhi, but have read good reviews.

No, I'll get conky set up later.

It's always been pitched as a low resource window manager; however, up until recently it has always been unstable. I would get seg faults on a regular basis with the 0.16 versions. Lowrider at #! claims the 0.17 (first stable release) versions are good so I'm taking a look.

I've always liked it since it is very similar to fvwm (the original enlightenment project was derived/forked from fvwm, I believe).

Besides the instability, the lack of themes (they were all glassy so little variety) and the difficulty of creating your own theme have really held it back. IMO Xfce (another fvwm derivative, I think) has really surpassed it in any functional and aesthetic sense without hogging the resources.

edit - add conky to startup apps:



e17 uses it's compositor by default; conky made transparent with argb settings.

Quote from: VastOne on July 10, 2013, 05:26:23 PM
Art can never be judged fairly... I think it is awesome!

+1

working on some eye candy - e17 on VSIDO:



default theme isn't too bad; probably just go with it for now.

Back to working with red tones -