.xinitrc not working correctly- don't know why


Forum: HD Install
Topic: .xinitrc not working correctly- don't know why
started by: bpsg119

Posted by bpsg119 on Oct. 09 2007,03:24
I've got a frugal install and I've been tinkering with various scripts and settings the past few days. It had been working seemingly fine but I must have done something yesterday to  cause my .xinitrc to give a bunch of errors and I haven't a clue why.

I'll post the file and then tell you about the errors I get on boot.

First here's my boot line from menu.lst

title DSL fb1024x768
kernel /boot/linux24 root=/dev/hda1 quiet vga=791 noacpi noapm nodma noscsi pictures=/mnt/hda3/Pictures scripts=/mnt/hda3/scripts
initrd /boot/minirt24.gz  
-----------------------------------------
Here's my .xinitrc
------------------------------------------

# put X windows programs that you want started here.
# Be sure to add at the end of each command the &

KEYTABLE="$(getknoppixparam.lua KEYTABLE)"
DESKTOP="$(getoption.lua $HOME/.desktop wm)"
ICONS="$(getoption.lua $HOME/.desktop icons)"

./etc/init.d/dsl-functions
CMDLINE="$(cat/proc/cmdline)"

PICTURES="$(getbootparam pictures)"
[ -d "$PICTURES" ] || PICTURES="/var/Pictures"

SCRIPTS="$(getbootparam scripts)"
[ -d "$SCRIPTS" ] || scripts="/home/dsl/scripts"

# For non-US Keyboards
if [ ${KEYTABLE:0:2} != "us" ]; then
 xmodmap -e "clear Mod4" -e "add Mod5 = Mode_switch" &
fi

#if egrep -qv noicons /proc/cmdline 2>/dev/null; then
if [ "$ICONS" == 1 ]; then
 for x in `ls -1 .xtdesktop/*.hide 2>/dev/null`; do rm -f ${x%.*}; done
 iconsnap.lua &>/dev/null &
 xtdesk.sh
fi
#dillo /usr/share/doc/dsl/getting_started.html &>/dev/null &
torsmo 2>/dev/null &
xset s off
noblank
xset s off

/usr/local/bin/MyCron &

/mnt/hda3/scripts/cron_start_frame.sh &
fluxbox 2>/dev/null


here's my .xinitrc
case $DESKTOP in
 fluxbox )
   fluxter &>/dev/null &
   wmswallow -geometry 70x80 docked  docked.lua &
   exec fluxbox 2>/dev/null  
 ;;
 jwm )
   ./.background
   sleep 2
   exec jwm 2>/dev/null
 ;;
 * )
   exec fluxbox 2>/dev/null
 ;;
esac

-----------------------------------

Here are some of the errors that I'm getting:
I'm getting command not found errors for

1) ./etc/init.d/dsl-functions
2)cat/proc/cmdline
3)getbootparam  - both of them
4)noblank

an 888 floating point exception to the line with torsmo.

I've got this .xinitrc off a website and had it working---or atleast recognizing the getbootparam so that It could start the frame script before I hard coded the directory in.

Any ideas?

Posted by ^thehatsrule^ on Oct. 09 2007,05:02
I'm guessing your "pasting" got messed up, or maybe these are really the cause of the problems:
1) missing a space between the first "." and "/"
2) missing a space between "cat" and "/proc/cmdline"
3) this is due to #1
4) is this included in DSL? Looks like a custom script/binary

torsmo: which version? maybe its due to your other errors

Posted by bpsg119 on Oct. 09 2007,13:04
Thanks!! The mistakes you caught fixed my most worrisome issues.

I still get an error on noblank and with torsmo. I guess I should do a little reading and find out what those two are doing for me and test whether or not I need them.

I've got ver 3.4.3 that I'm working with.

Thanks again.

Posted by ^thehatsrule^ on Oct. 09 2007,13:25
noblank: The person you got it from probably had that to turn off some screen blanking or screensaver.  I have no idea why you would need 2 invocations of xset.

torsmo: DSL v3.4.3 used torsmo v0.18 and is known for having noswap errors... but DSL v3.4.4 is out now so you may want to try that instead if you plan to upgrade anyways.

Posted by bpsg119 on Oct. 09 2007,13:34
Upgrading should be trivial, right?

If I understand how the frugal install is working, everything important is being backed up for me with exception to the menu.lst file. I should be able to format/install 3.4.4 without a problem.

Out of curiosity is v4.x going to be upgradeable as seamlessly?

Posted by mikshaw on Oct. 09 2007,13:36
Code Sample
xset s off
noblank
xset s off

"noblank" should be used as part of "xset s".
Having "xset s off" twice is unnecessary, and I'm not sure the two s options used here are compatible. "off" turns off screen blanking entirely, while "noblank" displays a pattern, if your hardware supports it. If "off" is used, I assume no blanking at all will occur.
Quote
      s       The s option lets you set the screen saver parameters.  This  option
              accepts  up  to two numerical parameters, a 'blank/noblank' flag, an
              'expose/noexpose' flag, an 'on/off' flag, an 'activate/reset'  flag,
              or  the  'default'  flag.  If no parameters or the 'default' flag is
              used, the system will be set to its default screen saver  character­
              istics.   The  'on/off' flags simply turn the screen saver functions
              on or off.  The 'activate' flag forces activation  of  screen  saver
              even  if  the  screen  saver  had been turned off.  The 'reset' flag
              forces deactivation of screen saver if it is  active.   The  'blank'
              flag  sets the preference to blank the video (if the hardware can do
              so) rather than display a background pattern, while  'noblank'  sets
              the  preference  to  display  a pattern rather than blank the video.
              The 'expose' flag sets the preference to allow window exposures (the
              server  can  freely  discard window contents), while 'noexpose' sets
              the preference to disable screen saver unless the server can  regen­
              erate  the  screens without causing exposure events.  The length and
              period parameters for the screen saver function determines how  long
              the  server  must be inactive for screen saving to activate, and the
              period to change the background pattern to avoid burn in.  The argu­
              ments  are specified in seconds.  If only one numerical parameter is
              given, it will be used for the length.


There doesn't seem to be anything wrong with your torsmo command. Could you post the error?

Posted by ^thehatsrule^ on Oct. 09 2007,15:59
Quote (bpsg119 @ Oct. 09 2007,09:34)
Upgrading should be trivial, right?

If I understand how the frugal install is working, everything important is being backed up for me with exception to the menu.lst file. I should be able to format/install 3.4.4 without a problem.

Out of curiosity is v4.x going to be upgradeable as seamlessly?

Just be sure to read the release notes for upgrading on the forum threads.

I'm assuming v4.x will have something similar when released, but there will probably be more drastic changes required on the user's end...

Posted by danielp on Oct. 13 2007,16:37
bpsg, I had exactly the same problems as you while trying to set up DSL for a digital picture frame.

thehatsrule gave the answer to my problem, which was:
Quote
1) missing a space between the first "." and "/"


That fixed a lot of problems. I'm such a newbie, I have no idea what that command actually does. Could anyone explain what happens when you start a script with a dot and space?

Posted by mikshaw on Oct. 13 2007,17:51
The dot by itself (dot-space-filename) is shorthand for the "source" command. So .<space>/etc/init.d/dsl-functions is the same as source /etc/init.d/dsl-functions. This reads the given filename in as if it were part of the current script or shell.

If you omit the space, the dot followed by a slash indicates the current directory. So if you were in /home/dsl and ran the command ./etc/init.d/dsl-functions it will try to execute /home/dsl/etc/init.d/dsl-functions, and probably fail because that file doesn't exist.

Powered by Ikonboard 3.1.2a
Ikonboard © 2001 Jarvis Entertainment Group, Inc.