LinuxQuestions.org
LinuxAnswers - the LQ Linux tutorial section.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices

Reply
 
Search this Thread
Old 08-07-2007, 06:46 PM   #16
smurfed
LQ Newbie
 
Registered: Aug 2007
Distribution: Custom Slack 12.0
Posts: 20

Rep: Reputation: 0

Hi, first let me say thanks to the guys helping out with this issue. I used to receive a similar issue as what orbit did, but that's been solved now (thanks to bmfan ) and I have a whole new set of drama's to deal with...

One thing that did pique my interest though was this bit here:

Quote:
Originally Posted by Lockywolf
i install splashy from slacky.eu
Sorry if I've missed anything around here, but I've looked extensively on slacky, and haven't found anything that installs splashy from there (I did see where the page that perry translated for us though, thanks again )

But to get back on track, is it possible to give a link to the splashy package from slacky? That would be awefully helpful

Thanks in advance
 
Old 08-08-2007, 06:16 AM   #17
Lockywolf
Member
 
Registered: Jul 2007
Posts: 70

Rep: Reputation: 15
http://utenti.lycos.it/neongen/splashy/

))))

all packages needed for splashy to compile and splashy itself

but. if you want bytecode interpreter in freetype don't install the freetype package

just take freetype from slackware-source and comment out the line that rm's *.a files

(good joke from Pat ))) )

anyway it doesn't work correctly.

/etc/init.d/splashy needs lsb-base package

that exists in debian, but doesn't exist in slackware.

Btw, can you advise any theme for slackware splashy?
 
Old 08-08-2007, 12:19 PM   #18
gnashley
Amigo developer
 
Registered: Dec 2003
Location: Germany
Distribution: Slackware
Posts: 4,752

Rep: Reputation: 462Reputation: 462Reputation: 462Reputation: 462Reputation: 462
Here's the contents of the /lib/lsb/init-functions file.
I packaged it nicely from the debian lsb-base_3.1-23.1.all.deb in a few seconds using src2pkg, but the code below is the 'meat' of it:

[CODE][# /lib/lsb/init-functions for Debian -*- shell-script -*-
#
#Copyright (c) 2002-06 Chris Lawrence
#All rights reserved.
#
#Redistribution and use in source and binary forms, with or without
#modification, are permitted provided that the following conditions
#are met:
#1. Redistributions of source code must retain the above copyright
# notice, this list of conditions and the following disclaimer.
#2. Redistributions in binary form must reproduce the above copyright
# notice, this list of conditions and the following disclaimer in the
# documentation and/or other materials provided with the distribution.
#3. Neither the name of the author nor the names of other contributors
# may be used to endorse or promote products derived from this software
# without specific prior written permission.
#
#THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
#ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
#IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
#ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
#FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
#DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
#OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
#HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
#LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
#OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
#SUCH DAMAGE.

start_daemon () {
local force nice pidfile exec i
force=0
nice=0
pidfile=/dev/null

OPTIND=1
while getopts fn: opt ; do
case "$opt" in
f) force=1;;
n) nice="$OPTARG";;
p) pidfile="$OPTARG";;
esac
done

shift $(($OPTIND - 1))
[ "$1" = '--' ] && shift

exec="$1"; shift

if [ $force = 1 ]; then
eval /sbin/start-stop-daemon --start --nicelevel $nice --quiet --startas $exec --pidfile /dev/null --oknodo -- "$@"
elif [ $pidfile ]; then
eval /sbin/start-stop-daemon --start --nicelevel $nice --quiet --exec $exec --oknodo --pidfile "$pidfile" -- "$@"
else
eval /sbin/start-stop-daemon --start --nicelevel $nice --quiet --exec $exec --oknodo -- "$@"
fi
}

pidofproc () {
local pidfile line i pids= status specified pid
pidfile=
specified=

OPTIND=1
while getopts p: opt ; do
case "$opt" in
p) pidfile="$OPTARG"; specified=1;;
esac
done
shift $(($OPTIND - 1))

if [ -z "${pidfile:-}" ]; then
pidfile=/var/run/${1##*/}.pid
fi

if [ -f "$pidfile" ]; then
read pid < "$pidfile"
if [ -n "${pid:-}" ]; then
if $(kill -0 "${pid:-}" 2> /dev/null); then
echo "$pid"
return 0
else
return 1 # program is dead and /var/run pid file exists
fi
fi
fi
if [ -x /bin/pidof -a ! "$specified" ]; then
/bin/pidof -o %PPID $1
status="$?"
[ "$status" = 1 ] && return 3 # program is not running
return 0
fi
return 4 # program or service is unknown
}

# start-stop-daemon uses the same algorithm as "pidofproc" above.
killproc () {
local pidfile sig status base i name_param
pidfile=
name_param=

OPTIND=1
while getopts p: opt ; do
case "$opt" in
p) pidfile="$OPTARG";;
esac
done
shift $(($OPTIND - 1))

base=${1##*/}
if [ ! $pidfile ]; then
pidfile=/var/run/$base.pid
name_param="--name $base"
fi

sig=$(echo ${2:-} | sed -e 's/^-\(.*\)/\1/')
sig=$(echo $sig | sed -e 's/^SIG\(.*\)/\1/')
if [ -n "$sig" ]; then
/sbin/start-stop-daemon --stop --pidfile "$pidfile" --signal "$sig" --quiet $name_param
else
/sbin/start-stop-daemon --stop --pidfile "$pidfile" --retry 5 --quiet --oknodo $name_param
fi
status="$?"
if [ "$status" = 1 ]; then
[ -n "$sig" ] && return 0
return 3 # program is not running
fi

rm -f "$pidfile"
return 0
}

log_use_fancy_output () {
TPUT=/usr/bin/tput
EXPR=/usr/bin/expr
if [ "x$TERM" != "xdumb" ] && [ -x $TPUT ] && [ -x $EXPR ] && $TPUT hpa 60 >/dev/null 2>&1 && $TPUT setaf 1 >/dev/null 2>&1; then
[ -z $FANCYTTY ] && FANCYTTY=1 || true
else
FANCYTTY=0
fi
case "$FANCYTTY" in
1|Y|yes|true) true;;
*) false;;
esac
}

log_success_msg () {
echo "$@"
}

log_failure_msg () {
if log_use_fancy_output; then
RED=`$TPUT setaf 1`
NORMAL=`$TPUT op`
echo "$RED*$NORMAL $@"
else
echo "$@"
fi
}

log_warning_msg () {
if log_use_fancy_output; then
YELLOW=`$TPUT setaf 3`
NORMAL=`$TPUT op`
echo "$YELLOW*$NORMAL $@"
else
echo "$@"
fi
}

#
# NON-LSB HELPER FUNCTIONS
#
# int get_lsb_header_val (char *scriptpathname, char *key)
get_lsb_header_val () {
if [ ! -f "$1" ] || [ -z "${2:-}" ]; then
return 1
fi
LSB_S="### BEGIN INIT INFO"
LSB_E="### END INIT INFO"
sed -n "/$LSB_S/,/$LSB_E/ s/# $2: \(.*\)/\1/p" $1
}

# int log_begin_message (char *message)
log_begin_msg () {
if [ -z "${1:-}" ]; then
return 1
fi
echo -n "$@"
}

# Sample usage:
# log_daemon_msg "Starting GNOME Login Manager" "gdm"
#
# On Debian, would output "Starting GNOME Login Manager: gdm"
# On Ubuntu, would output " * Starting GNOME Login Manager..."
#
# If the second argument is omitted, logging suitable for use with
# log_progress_msg() is used:
#
# log_daemon_msg "Starting remote filesystem services"
#
# On Debian, would output "Starting remote filesystem services:"
# On Ubuntu, would output " * Starting remote filesystem services..."

log_daemon_msg () {
if [ -z "${1:-}" ]; then
return 1
fi

if [ -z "${2:-}" ]; then
echo -n "$1:"
return
fi

echo -n "$1: $2"
}

# #319739
#
# Per policy docs:
#
# log_daemon_msg "Starting remote file system services"
# log_progress_msg "nfsd"; start-stop-daemon --start --quiet nfsd
# log_progress_msg "mountd"; start-stop-daemon --start --quiet mountd
# log_progress_msg "ugidd"; start-stop-daemon --start --quiet ugidd
# log_end_msg 0
#
# You could also do something fancy with log_end_msg here based on the
# return values of start-stop-daemon; this is left as an exercise for
# the reader...
#
# On Ubuntu, one would expect log_progress_msg to be a no-op.
log_progress_msg () {
if [ -z "${1:-}" ]; then
return 1
fi
echo -n " $@"
}


# int log_end_message (int exitstatus)
log_end_msg () {
# If no arguments were passed, return
[ -z "${1:-}" ] && return 1

# Only do the fancy stuff if we have an appropriate terminal
# and if /usr is already mounted
if log_use_fancy_output; then
RED=`$TPUT setaf 1`
NORMAL=`$TPUT op`
if [ $1 -eq 0 ]; then
echo "."
else
/bin/echo -e " ${RED}failed!${NORMAL}"
fi
else
if [ $1 -eq 0 ]; then
echo "."
else
echo " failed!"
fi
fi
return $1
}

log_action_msg () {
echo "$@."
}

log_action_begin_msg () {
echo -n "$@..."
}

log_action_cont_msg () {
echo -n "$@..."
}

log_action_end_msg () {
if [ -z "${2:-}" ]; then
end="."
else
end=" ($2)."
fi

if [ $1 -eq 0 ]; then
echo "done${end}"
else
if log_use_fancy_output; then
RED=`$TPUT setaf 1`
NORMAL=`$TPUT op`
/bin/echo -e "${RED}failed${end}${NORMAL}"
else
echo "failed${end}"
fi
fi
}

FANCYTTY=
[ -e /etc/lsb-base-logging.sh ] && . /etc/lsb-base-logging.sh || true
/CODE]
 
Old 08-08-2007, 02:51 PM   #19
bmfan
Member
 
Registered: Mar 2005
Posts: 74

Rep: Reputation: 15
I finally just gave up on getting it working, far to much screwing around with it. bootsplash is much easier to set up and get running
 
Old 08-08-2007, 06:04 PM   #20
janhe
Member
 
Registered: Jul 2007
Location: Belgium
Distribution: slackware64 13.1, slackware 13.1
Posts: 369

Rep: Reputation: 45
the problem seems to be that it requires the init scripts (and slackware as a whole) to confirm the lsb-standard ( http://www.linux-foundation.org/en/LSB )

Since bootsplash is discontinued (bootsplash.org recommends splashy), it would be nice if someone could get splashy working while creating a slackware+splashy HOWTO.

I've got bootsplash working, so there's no hurry in it for me.
 
Old 08-08-2007, 07:02 PM   #21
smurfed
LQ Newbie
 
Registered: Aug 2007
Distribution: Custom Slack 12.0
Posts: 20

Rep: Reputation: 0
Thank you to both Lockywolf and gnashly!

By utilizing the packages that Lockywolf linked to and the file that gnashly supplied, everything installed as it should have with no hiccups. Splashy is now installed and the test screen runs fine.

Now all I have to do is configure it enough so that it starts on boot and for me to find a theme that I can live with...

I'll document my findings here if all goes to plan. Even though it's 'explained' easily enough at the Splashy homepage here, if I've learnt anything from this excursion, there's a big difference between explaining it and doing it... :P

Thanks again guys, you've been a huge help
 
Old 08-08-2007, 08:46 PM   #22
perry
Member
 
Registered: Sep 2003
Location: USA & Canada
Distribution: Slackware 12.0
Posts: 978

Rep: Reputation: 30
Thumbs up Write us a HOW-TO anyway...

Quote:
Originally Posted by smurfed
Thank you to both Lockywolf and gnashly!

By utilizing the packages that Lockywolf linked to and the file that gnashly supplied, everything installed as it should have with no hiccups. Splashy is now installed and the test screen runs fine.

Now all I have to do is configure it enough so that it starts on boot and for me to find a theme that I can live with...

I'll document my findings here if all goes to plan. Even though it's 'explained' easily enough at the Splashy homepage here, if I've learnt anything from this excursion, there's a big difference between explaining it and doing it... :P

Thanks again guys, you've been a huge help
For slackware users, it'll certainly be appreciated. Espcially if you do one for Slack 12.

Thanks

- Perry
 
Old 08-08-2007, 11:29 PM   #23
Lockywolf
Member
 
Registered: Jul 2007
Posts: 70

Rep: Reputation: 15
Quote:
Now all I have to do is configure it enough so that it starts on boot and for me to find a theme that I can live with...
The "dirty" solution is to put /etc/rc.d/init.d/splashy in rc.S just after remounting
root filesystem read-write.

but anyway it doesn't work properly - no progressbar.
 
Old 08-09-2007, 12:35 AM   #24
orbit
Member
 
Registered: Sep 2006
Location: Australia
Distribution: Slackware
Posts: 176

Original Poster
Rep: Reputation: 30
First up, I'd like to thank everyone for their contributions to this topic,
the way everyone has worked together on this is brilliant!!

Regarding:
Quote:
Btw, can you advise any theme for slackware splashy?
I have created a Slackware Splashy Theme based on the old slackblue bootsplash theme, you can download it Here.

I haven't got my scripting working yet, but at least I know that when I do, the bootsplash slackware logo is ready for me

Thanks very much All, I'm really enjoying continuing the development of this splashy project.

Cheers

Orbit

p.s. To install it:
copy the slack_blue.tar.gz to the /etc/splashy/themes directory

on the command line type:
'splashy_config --install-theme slack_blue.tar.gz'
'splashy_config --set-theme slack_blue'

Then type: 'splashy test' to verify the install.

Cheers again

Last edited by orbit; 08-09-2007 at 09:13 PM.
 
Old 08-09-2007, 09:02 PM   #25
smurfed
LQ Newbie
 
Registered: Aug 2007
Distribution: Custom Slack 12.0
Posts: 20

Rep: Reputation: 0
Hi All,
I have been working to get splashy startup scripts going, and have now come across
a syntax error that I do not know how to resolve.
Could someone please decipher this and let me know what they think, so I can try to fix it.

The error message is occurring early in the boot directly as the initrd exits.
Extract:
Quote:
initrd.gz: Loading kernel modules from initrd image:
Using /lib/modules/2.6.21.5-smp/kernel/fs/reiserfs/reiserfs.ko
initrd.gz: exiting
/etc/rc.d/init.d/splashy: /lib/lsb/init-functions: 45: Syntax error: We unsupport $((arith))
Splashy ERROR: Couldn't splashy_start_splashy(). Error -2
Does this mean that line 45 of the file '/lib/lsb/init-function' has a syntax error,
or is it something else entirely?

Line 45 & 46 of '/lib/lsb/init-function' reads:
Quote:
shift $(($OPTIND - 1))
[ "$1" = '--' ] && shift
Any help will be appreciated

Cheers

Orbit
 
Old 08-09-2007, 09:20 PM   #26
orbit
Member
 
Registered: Sep 2006
Location: Australia
Distribution: Slackware
Posts: 176

Original Poster
Rep: Reputation: 30
Oops, I'm not on my computer and just noticed that this computer was still logged into the forum as my friend smurfed.

The last post; (requesting syntax assistance on /lsb/init-funtions) was from me.

Sorry bout that

Orbit

Last edited by orbit; 08-09-2007 at 09:36 PM.
 
Old 08-29-2007, 02:49 PM   #27
Fluxx
Member
 
Registered: Aug 2005
Location: Bavaria, Germany
Distribution: Slackware (Current)
Posts: 225

Rep: Reputation: 30
splashy-0.3.5 works for me. I compiled it in Slackware 12.0. I needed the additional source code package DirectFB-1.1.0.

I did it in this way:

- compiled DirectFB-1.1.0 with ./configure --prefix=/usr
- untared splashy-0.3.5 and changed the Makefile.am in src/ in line 47 to:

Code:
splashy_LDFLAGS = $(shell  --libs --input=keyboard --imageprovider=png --font=ft2,default) $(DFBHACK)
and run ./autogen.sh --prefix=/ && make && make install

- edited the file /etc/splashy/config.xml and added the line

Code:
<fifo>/etc/splashy/splashy.fifo</fifo>
within the section <splashy></splashy>.

- added in /etc/rc.d/rc.S after

Code:
if grep -wq sysfs /proc/mounts && grep -wq tmpfs /proc/filesystems ; then
  if ! grep -wq nohotplug /proc/cmdline ; then
    if [ -x /etc/rc.d/rc.udev ]; then
      /bin/sh /etc/rc.d/rc.udev start
    fi
  fi
fi

/sbin/splashy boot # <--- HERE !!!
- added after every "fi" in /etc/rc.d/rc.S and /etc/rc.d/rc.M the line

Code:
/sbin/splashy_update "progress nn"
to update the progressbar. For "nn" set numbers from "00" in the very beginning of the rc.S up to "100" at the end of rc.M.

- added in /etc/rc.d/rc.local

Code:
/sbin/splashy_update exit
to finish the progressbar.

- added to my /etc/lilo.conf the append

Code:
append = "splash quiet"
and run lilo -v to install the changes.

My video card is a GMA915 which uses the framebuffer device with vesafb.

I added the start of the splashy process after the udev process will start, because before this process will start there was an error message, that "splashy boot" cannot access the device /dev/fb0, it doesn't exist at this process of booting the system.

I try to figure out how to run the splashy with an initrd.gz, so that the splashy will appear quite in the beginning of the boot process ...

Fluxx.

Last edited by Fluxx; 08-29-2007 at 04:07 PM.
 
Old 09-09-2007, 10:34 AM   #28
arubin
Senior Member
 
Registered: Mar 2004
Location: Middx UK
Distribution: Slackware64 14.1 (multilib)
Posts: 1,209

Rep: Reputation: 55
I have installed splashy but I am having trouble configuring it

Quote:
root@LavanKossot:/home/alan/packages/splashy-0.3.5# splashy_config --install-theme themes/slack_blue.tar.gz

Splashy ERROR: Cannot read XML File <</etc/splashy/config.xml>>. Exiting...
Splashy ERROR: Error occured while starting Splashy
Make sure that you can read Splashy's configuration file
I have no /etc/splash
 
Old 09-09-2007, 10:51 AM   #29
arubin
Senior Member
 
Registered: Mar 2004
Location: Middx UK
Distribution: Slackware64 14.1 (multilib)
Posts: 1,209

Rep: Reputation: 55
Well it seems to be in /usr/local/etc so I symlinked to there
 
Old 09-09-2007, 11:02 AM   #30
Alien Bob
Slackware Contributor
 
Registered: Sep 2005
Location: Eindhoven, The Netherlands
Distribution: Slackware
Posts: 5,226

Rep: Reputation: Disabled
Quote:
Originally Posted by arubin View Post
I have installed splashy but I am having trouble configuring it.
I have no /etc/splash
I uploaded a splashy package to my repository. That at least will give you the missing file. It will not do any editing of rc files though.

Eric
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
splashy wkwireless Debian 2 11-21-2006 07:32 PM
Splashy is great! MrInept Debian 18 09-20-2006 12:51 AM
Problems with Splashy Paulsrud Ubuntu 10 08-30-2006 02:49 PM
Need Help With Splashy Paulsrud Linux - Software 1 08-24-2006 02:43 AM
splashy-0.1.6 kenkeanon Debian 1 01-04-2006 12:22 PM


All times are GMT -5. The time now is 03:09 PM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration