Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - PackRat

Pages: 1 ... 130 131 [132] 133 134 ... 139
1966
Artwork & Screenshots / Re: July 2013 Screenshots
« on: July 23, 2013, 08:38:58 PM »
No problem.

I now use it for my lightdm background.

1967
How To's / Disable the touchpad on a laptop while typing
« on: July 23, 2013, 07:42:25 PM »
syndaemon

Came across this little app today. I'm sure some of you are on laptops, and one thing that drives me nuts it that the mouse cursor will move as your palm or heel of your hand gets a little too close while typing. This little app takes care of that. It can be run as a daemon so add -

Code: [Select]
syndaemon -d
to your ~/.fluxbox/startup - or whatever startup file you use.

The result is that the touchpad is disabled when the keyboard is in use. By default, the touchpad will become active 2 seconds after keyboard activity stops. That can be chnaged -

Code: [Select]
syndaemon -i 1.0 -d
will cause the touchpad to become active after 1 second. There are some other options detailed in the man page. Worked like a charm when I tested it with geany and thunderbird.

1968
WM Designs and Discussions / Re: Using FLUXBOX as a Window Manager
« on: July 23, 2013, 12:57:07 PM »
Just set up tint2 to display multiple desktops only; tinker with the padding and some basic math and tint2 will function as a pager and be scaled to your screen's aspect ratio. Kind of stylish. The main difference is that the tint2 icons will be aligned with the taskbar, they don't float in their relative positions like they do on an authentic pager.

edit - picture is worth 1000 characters:



and the tint2rc

Code: [Select]
# Tint2 config file
# Generated by tintwizard (http://code.google.com/p/tintwizard/)
# For information on manually configuring tint2 see http://code.google.com/p/tint2/wiki/Configure

# Background definitions
# ID 1
rounded = 0
border_width = 0
background_color = #000000 0
border_color = #FFFFFF 0

# ID 2
rounded = 3
border_width = 2
background_color = #DAD7D0 10
border_color = #575238 66

# ID 3
rounded = 3
border_width = 2
background_color = #DAD7D0 10
border_color = #AE573C 66

# ID 4
rounded = 2
border_width = 0
background_color = #DAD7D0 0
border_color = #A52A2A 66

# ID 5
rounded = 2
border_width = 0
background_color = #DAD7D0 66
border_color = #111111 66

# ID 6
rounded = 2
border_width = 1
background_color = #A52A2A 4
border_color = #7C2E21 100

# Panel
panel_monitor = all
panel_position = top center horizontal
panel_items = T
panel_size = 40% 36
panel_margin = 0 32
panel_padding = 0 0 12
panel_dock = 0
wm_menu = 0
panel_layer = bottom
panel_background_id = 1

# Panel Autohide
autohide = 0
autohide_show_timeout = 0.3
autohide_hide_timeout = 2
autohide_height = 2
strut_policy = none

# Taskbar
taskbar_mode = multi_desktop
taskbar_padding = 1 1 4
taskbar_background_id = 2
taskbar_active_background_id = 3

# Tasks
urgent_nb_of_blink = 8
task_icon = 1
task_text = 0
task_centered = 1
task_maximum_size = 64 36
task_padding = 6 2
task_background_id = 4
task_active_background_id = 4
task_urgent_background_id = 6
task_iconified_background_id = 1
task_tooltip = 1

# Task Icons
task_icon_asb = 50 0 0
task_active_icon_asb = 90 0 0
task_urgent_icon_asb = 100 0 0
task_iconified_icon_asb = 50 0 0

# Fonts
task_font = sans 7
task_font_color = #FFFFFF 68
task_active_font_color = #FFFFFF 83
task_urgent_font_color = #FFFFFF 83
task_iconified_font_color = #FFFFFF 68
font_shadow = 0

# System Tray
systray = 1
systray_padding = 0 4 5
systray_sort = ascending
systray_background_id = 0
systray_icon_size = 16
systray_icon_asb = 70 0 0

# Clock
time1_format = %H:%M
time1_font = sans 8
time2_format = %A %d %B
time2_font = sans 6
clock_font_color = #FFFFFF 74
clock_padding = 1 0
clock_background_id = 0
clock_rclick_command = orage

# Tooltips
tooltip_padding = 2 2
tooltip_show_timeout = 0.7
tooltip_hide_timeout = 0.3
tooltip_background_id = 2
tooltip_font = sans 10
tooltip_font_color = #000000 80

# Mouse
mouse_middle = none
mouse_right = close
mouse_scroll_up = toggle
mouse_scroll_down = iconify

# Battery
battery = 0
battery_low_status = 10
battery_low_cmd = notify-send "battery low"
battery_hide = 98
bat1_font = sans 8
bat2_font = sans 6
battery_font_color = #FFFFFF 74
battery_padding = 1 0
battery_background_id = 0

# End of config

1969
WM Designs and Discussions / Re: Using FLUXBOX as a Window Manager
« on: July 23, 2013, 12:50:57 PM »
They are pagers like the Xfce workspace switcher.

fbpager is no longer developed and is actually discouraged by the fluxbox devs on the website and wiki. I don't think bbpager or obpager (blackbox and openbox pagers) are being developed anymore either. There are some other pagers out there, but I never really cared for them from an aesthetic standpoint.

It's actually pretty easy to set up tint2 in pager only mode for fluxbox and get to match up with your fluxbox theme and transparency; doesn't use a lot of resources.

1970
General Support / [Solved] Keybinding to move windows in Xfce
« on: July 23, 2013, 02:13:32 AM »
The Settings Editor of Xfce indicates that the key binding -

Code: [Select]
<Control><Shift><Alt>Right
is the binding to move_window_right_key.

I assume this means that the active window a bit to the right when this key binding is used, but I get no result (8C is entered in a terminal). Anyone else having this issue with Xfce?

Also, anyone have a key binding for incrementally moving the active window in Xfce?

1971
Artwork & Screenshots / Re: July 2013 Screenshots
« on: July 22, 2013, 08:56:35 PM »
Picture of the day is Earth viewed from Saturn, taken by Cassini probe:



Details - http://www.earthobservatory.nasa.gov/IOTD/view.php?id=7314

1972
VSIDO News & Announcements / Re: sqlpython discovers VSIDO
« on: July 18, 2013, 05:57:43 PM »

1973
Artwork & Screenshots / Re: July 2013 Screenshots
« on: July 17, 2013, 07:58:54 PM »
Cool, I may have to give the liquorix version a try.

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


1974
Artwork & Screenshots / Re: July 2013 Screenshots
« on: July 17, 2013, 06:57:15 PM »
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:


1975
Artwork & Screenshots / Re: July 2013 Screenshots
« on: July 17, 2013, 03:53:11 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  ;D

Worth looking into.

1976
Artwork & Screenshots / Re: July 2013 Screenshots
« on: July 17, 2013, 03:17:08 AM »
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


1977
Feedback & Suggestions / Re: VSIDO Server
« on: July 16, 2013, 09:55:33 PM »
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.

1978
Artwork & Screenshots / Re: July 2013 Screenshots
« on: July 14, 2013, 10:20:25 PM »
more of the same:


1979
Feedback & Suggestions / Re: VSIDO Server
« on: July 14, 2013, 03:49:03 PM »
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

Code: [Select]
#!/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.

1980
Feedback & Suggestions / Re: VSIDO Server
« on: July 13, 2013, 10:08:23 PM »
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.

Pages: 1 ... 130 131 [132] 133 134 ... 139