Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 47221 - app-misc/linux-logo: add an init script to edit /etc/issue
Summary: app-misc/linux-logo: add an init script to edit /etc/issue
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: High enhancement (vote)
Assignee: Michal Januszewski (RETIRED)
URL:
Whiteboard:
Keywords:
: 47217 (view as bug list)
Depends on:
Blocks:
 
Reported: 2004-04-08 08:10 UTC by José Romildo Malaquias
Modified: 2004-04-28 07:58 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments
init script (linux-logo.initscript,449 bytes, text/plain)
2004-04-08 08:12 UTC, José Romildo Malaquias
Details
configuration file for the init script (linux-logo.conf,1.19 KB, text/plain)
2004-04-08 08:13 UTC, José Romildo Malaquias
Details
script for use with cron (linux-logo.cron,84 bytes, text/plain)
2004-04-08 08:14 UTC, José Romildo Malaquias
Details
ebuild (linux-logo-4.09.ebuild,1.88 KB, text/plain)
2004-04-08 08:16 UTC, José Romildo Malaquias
Details

Note You need to log in before you can comment on or make changes to this bug.
Description José Romildo Malaquias 2004-04-08 08:10:38 UTC
In order to make easier the call of linux_logo at boot time, it would be nice to have a script /etc/init.d/linux-logo (as the one in the package app-misc/welcome2l).

There is a good script for that in the forum topic http://forums.gentoo.org/viewtopic.php?t=2972&highlight=linuxlogo

Reproducible: Always
Steps to Reproduce:
1.
2.
3.
Comment 1 José Romildo Malaquias 2004-04-08 08:12:36 UTC
Created attachment 28890 [details]
init script

An init script to run linux_logo at boot time. Put it into ${FILESDIR}/
Comment 2 José Romildo Malaquias 2004-04-08 08:13:58 UTC
Created attachment 28891 [details]
configuration file for the init script

Configuration file for the init script. Put it in ${FILESDIR}/
Comment 3 José Romildo Malaquias 2004-04-08 08:14:48 UTC
Created attachment 28892 [details]
script for use with cron

Put it in ${FILESDIR}/
Comment 4 José Romildo Malaquias 2004-04-08 08:16:42 UTC
Created attachment 28893 [details]
ebuild

Ebuild that installs the initscript, its configuration file, and the script for
use of cron.
Comment 5 Michal Januszewski (RETIRED) gentoo-dev 2004-04-09 07:30:37 UTC
*** Bug 47217 has been marked as a duplicate of this bug. ***
Comment 6 Michal Januszewski (RETIRED) gentoo-dev 2004-04-24 12:35:50 UTC
Thanks for the updates. I added the new ebuild and the initscript to the CVS. I decided to drop the cron script as I don't think it's really necessary. If linux_logo is installed, then /etc/init.d/linux-logo has to exist and the user can simply put `/etc/init.d/linux-logo restart` in his crontab - no need for additional scripts.
Comment 7 Chuck Brewer 2004-04-26 13:11:27 UTC
Ouch. Couple of minor tidbits here to quibble over-
/usr/bin/linux_logo $LOGO $OPTIONS -F "${FORMAT}" > /etc/issue
$LOGO not defined in conf.d, and if it was, it would take last form from
$OPTIONS ( -L 4 -f -u) which is "use logo 4".. also minor quibble over format
Gentoo #O `cat /etc/gentoo-release | awk '{ print $5,$6 }'` which on my system
will give Gentoo Linux 1.4.10, which is mistaken. Gentoo Linux 2004-1.4 is
the correct release, whilst 1.4.10 is the version given to baselayout.
Basically has been overcomplicated uselessly. I've had this in my local.start
for about a year now-

  ebegin "Setting issue..."

        echo "" > /etc/issue
        echo ^[[2J^[[f > /etc/issue
        linux_logo -D /etc/.issue >> /etc/issue
        echo $(cat /etc/gentoo-release) >> /etc/issue
The first line to clear prior issue settings, the second line tells linux_logo
to clear the screen before printing, the third points at my custom logo file, and the fourth displays the correct baselayout patchlevel(my choice) just above the login prompt. Much smaller, cleaner and appropriate strings could be 
introduced into my example,without needing to specify format to obtain an 
output already close to the default. 
Comment 8 Chuck Brewer 2004-04-28 07:58:15 UTC
Apparently I was mistaken on the release, was 2004.0, now 2004.1..
The ability to reopen bugs not fixed would be nice as well.