Hey Everyone,

 

    So, here's the idea. Unraid isn't really bound by RAM or CPU. But, RAM and CPU are cheap ... I have a Core 2 Duo with 4 GB of RAM as my unraid server, and those components cost me under $300, including the everything but the case and drives. You can install quite a bit of software into the ram drive, without having to worry about using the disk. With 4 GB, you can easily install 1-2GB of software. Even a 512MB stick lets you keep a lot of compressed slackware packages

 

    So, here's something to make it very easy to install packages. I call it "Dirt Simple Packages" 

 

To Install:

    1. unzip the attached zip file in the root of your unraid flash share.

    2. add the following line to the end of your \\unraid\flash\config\go script:

                            "/boot/customizations/pkginst"

 

 

To add packages to unraid:

    1. Go to http://packages.slackware.it/,

    2. Search for the packages you want

    3. Download them to \\unraid\flash\customizations\packages\

 

To customize the configuration files (optional, make sure you save text files as "unix" files, not "dos" files):

    1. Simply create the new config files under \\unraid\flash\customizations\configs\

    For example, you can create a resolv.conf in \\unraid\flash\customizations\configs\etc\resolv.conf

 

That's it! If you choose any server packages, they will be started automatically.

 

To apply the packages, either restart unraid, or else telnet in and run /boot/customizations/pkginst

 

 

Feedback welcome!

 

PS:

 

    Some packages I like, for example, are:

    - wget, for downloading from the command line: http://packages.slackware.it/search.php?v=current&t=1&q=wget

    - ssh, to replace telnet: http://packages.slackware.it/package.php?q=current/openssh-5.0p1-i486-1

    - AppleTalk file sharing: http://packages.slackware.it/package.php?q=current/netatalk-2.0.3-i486-1

    - file, for identifying files: http://packages.slackware.it/package.php?å=current/file-4.21-i486-1

    - snmp, for network monitoring: http://packages.slackware.it/package.php?q=current/net-snmp-5.4-i486-6

    - subversion, source control for hosting repositories natively; http://packages.slackware.it/package.php?q=current/subversion-1.4.6-i486-1

 

Sorry, small fix to the scripts. Use this version instead.

Please see the wiki regarding tree and location.

 

http://lime-technology.com/wiki/index.php?title=Third_Party_Boot_Flash_Plugin_Architecture

 

We came up with an agreed upon structure.

Please see the wiki regarding tree and location.

 

http://lime-technology.com/wiki/index.php?title=Third_Party_Boot_Flash_Plugin_Architecture

 

We came up with an agreed upon structure.

 

Has anyone else taken a crack at implementing that structure (or has Lime-Tech)?

 

Here is another update, this time using the directory structure from the Wiki. This code implements everything mentioned in the wiki page *except* the different runlevel support.

 

Same instructions as before, but use the following directories:

 

    - The line in the go script should be: "/boot/custom/pkginst"

    - Packages should be placed in \\unraid\flash\custom\usr\share\packages

    - Config files should be places in \\unraid\flash\custom\etc\

 

 

Has anyone else taken a crack at implementing that structure (or has Lime-Tech)?

 

I use the structure, I have a number of install scripts to handle it.

If you search through the forum I'm sure you will find them.

 

One of these day's I'll make a package to build the structure and install the scripts.

 

We've just been waiting for limetech to provide an answer on the possibility of various run level support.

What kind of possibilities can we leverage with installing the AFP package? I'm assuming this will enable my Mac to use AFP to see the disks and files in my unraid machine, but no share support...

I spoke a little too soon when I posted that ... turns out AFP is not compiled into the kernel, so the AFP package doesn't work.

I hope someone is still looking at this topic...

 

I am having some trouble with this.  I have been using this script just to install all my packages every time and things are working great.  However, I decided that I wanted to create my own "rc." file, put it on the flash drive and have this script start a process for me as well.  I'm new to unix scripting, but it looks like the part of the script that copies over those files isn't working for me.  For example, this part of the script:

 

# Copy config files over

(

echo "#  Copying Config Files..."

cd $cfgDir

for i in `find . -type f`; do

mkdir -p /etc/`dirname $i` && echo cp $i /etc/$i

done

)

 

It doesn't look like it is really copying any files over for me.  Here is the output from running the pkginst script:

 

#  Copying Config Files...

cp ./perms.persist /etc/./perms.persist

cp ./ssh/sshd_config /etc/./ssh/sshd_config

cp ./ssh/ssh_config /etc/./ssh/ssh_config

cp ./ssh/ssh_host_dsa_key /etc/./ssh/ssh_host_dsa_key

cp ./ssh/ssh_host_dsa_key.pub /etc/./ssh/ssh_host_dsa_key.pub

cp ./ssh/ssh_host_key /etc/./ssh/ssh_host_key

cp ./ssh/ssh_host_key.pub /etc/./ssh/ssh_host_key.pub

cp ./ssh/ssh_host_rsa_key /etc/./ssh/ssh_host_rsa_key

cp ./ssh/ssh_host_rsa_key.pub /etc/./ssh/ssh_host_rsa_key.pub

cp ./rc.d/init.d/slimstart.sh /etc/./rc.d/init.d/slimstart.sh

cp ./rc.d/init.d/rc.slimserver /etc/./rc.d/init.d/rc.slimserver

 

Well, that "rc.slimserver" file never shows up in the "/etc/rc.d/init.d" directory.  I don't really understand the syntax of the script, so it is tough for me to debug.  But, it looks like that extra "." in the path where it is copying the files seems wrong.  Am I missing something basic here?  Any tips would be greatly appreciated.

 

Thanks, Chris

mkdir -p /etc/`dirname $i` && echo cp $i /etc/$i

 

I am in no way a bash expert here, but couldn't help noticing that you have an 'echo' in that copy line, that will display what the copy command will be, but do absolutely nothing.  Try removing that 'echo'.

I was actually just about to start another post on this subject, but this thread seems like the right place for this discussion.

 

I have been slowly working on the "boot script manager" and have realized that with:

 

A) The large variety in the nature of boot scripts

b) The inclusion of runlevel hooks

 

it is starting to become a monumental task.

 

What I was thinking, is that if we made the boot scripts into packages with the various runlevel scripts and have them installed with unmenu or another package manager.  They would only need to be installed once (because the files are all installed on the flash in the TPBA). I'm pretty sure that is what Weebotech was refering to in an earlier post above.  And there would be no reason to continue to program a "boot script manager" because we would allow package managers to deal with them.  We could also add a "uninstall" script that is added to say /boot/custom/etc/rc.d/init.d/uninstall (or something similar) to be able to undo the various runlevel scripts for a particular user boot add-on at a singular location (instead of hunting down all the individual runlevel scripts to delete them).

 

thoughts?

 

Matt

That 'echo' was the problem.  Note to others who are downloading the scripts here, the version in the download is incorrect as it has that 'echo' in it.  Otherwise, I think this is a great tool.  Thanks, Chris