[RULE] Proposals for the 0.4.0 Version of Slinky

Michael Fratoni mfratoni at tuxfan.homeip.net
Tue Jun 3 04:40:54 EEST 2003


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Monday 02 June 2003 03:51 am, Ingo Lantschner wrote:
> Hi Michael,
> I have some questions/proposals for one of the next releases of slinky:
>
> 1. The last Slinkys had more and more applications added (OO, Abiword,
> Mozilla). To start them one either must manually configure iceWM or
> start first xterm and launch the application from there. What about
> "syncing" the GUI(s) with these new apllications? Attached you find a
> menustructure (for iceWM), for which I can provide you the necessary
> files and icons (if you like in a tarball already including the pathes)

By all means send the me the files and I'll have a look.
There is a config file, /usr/share/icewm/programs, that can be used to 
modify the start menu, however, no effort is currently made to set it up 
properly.

> If someone here would still prefer Fluxbox, I can try to build this for
> Fluxbox too.

Fluxbox has a script that can be run that searches the filesystem and adds 
applications to the menu. /usr/X11R6/bin/fluxbox-generate_menu, I 
believe.

> 2. Post-Install Script: Of course it would be nice to have this and
> that application integrated into Slinky, but in course of time I guess
> Michael will get overloaded by a neverending whichlist and the
> Slinky-Users will get confused by the many options and decicions they
> have to take during installation. So you mentioned sometimes the
> possibility to call a post-install-script. But I did not find out how
> to
>
> use it:
> > if [ -f /root/scripts/rulerc.sh ]; then
> >     echo "Executing /root/scripts/rulerc.sh"
> >     /root/scripts/rulerc.sh 2>> /root/scripts/install_log
> >     echo Done.
> > fi
> >
> > The above is executed right after installation of all the various rpm
> > packages, and before setting the root password.
> > Just copy your script to /scripts/rulerc.sh directory before
> > beginning the install, and it will be moved to
> > /root/scripts/rulerc.sh during the second_stage phase of the install.
>
> a. What is confusing me: There is no such directory/file on the ISO.
> b. Is rulerc.sh a script-file or a directory (in this case *all* files
> in this directory will be executed?)?

The script was designed before we had an ISO. The plan was to have the 
user copy the file into /scripts/ from a floppy. The file would be moved 
to /root/scripts by the installer. (As are any other files in the 
/scripts directory.) The major problem here is that the filesystem on the 
iso is a gzipped archive inside a disk.img file. A bit complicated to 
edit it. ;)

However, I believe i have a solution, see my next mail.

> 3. Would it be possible to give an already customized slinky.config on
> the ISO? (Which can then be altered and inkluded with mkisofs on a
> special-purpose-ISO.)

Possible, yes. But I'd rather not for general use. For someone doing many 
installs, I'd wouldn't object to providing a custom iso. However, for the 
one available on the website, having someone elses custom scripts running 
during install wouldn't be good.

Again, this is solved, I believe. Seee my next mail.

- -- 
- -Michael

pgp key:  http://www.tuxfan.homeip.net:8080/gpgkey.txt
Red Hat Linux 7.{2,3}|8.0 in 8M of RAM: http://www.rule-project.org/
- --
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)

iD8DBQE+2/ymn/07WoAb/SsRAoQ2AJ0Ro7FSp9Ei3RC5Z/tGBSi2i9EwpACdGIpE
dRm0wYXuvn5CUnECEjIL4sg=
=TpBy
-----END PGP SIGNATURE-----



_______________________________________________
Original home page of the RULE project: www.rule-project.org
Original Rule Development Site http://savannah.gnu.org/projects/rule/
Original RULE mailing list: Rule-list at nongnu.org, hosted at http://mail.nongnu.org/mailman/listinfo/rule-list




This full static mirror of the Run Up to Date Linux Everywhere Project mailing list, originally hosted at http://lists.hellug.gr/mailman/listinfo/rule-list, is kept online by Free Software popularizer, researcher and trainer Marco Fioretti. To know how you can support this archive, and Marco's work in general, please click here