[Resolved] 5.0-rc11 Missing Packages after Reboot

[cynicaljoy]

I keep having to install vim after I reboot my box. I am installing vim via the following:

 

wget http://mirrors.slackware.com/slackware/slackware-current/slackware/l/glibc-2.15-i486-7.txz
wget http://mirrors.slackware.com/slackware/slackware-current/slackware/d/python-2.7.3-i486-2.txz
wget http://mirrors.slackware.com/slackware/slackware-current/slackware/d/perl-5.16.1-i486-1.txz
wget http://mirrors.slackware.com/slackware/slackware-current/slackware/ap/vim-7.3.645-i486-1.txz
installpkg *.txz

 

What am I doing wrong?

 

The same thing is happening for the 'clear' command. I am adding the clear command to my .bash_profile but it keeps getting dropped.

 

echo "alias clear=\"echo -e '\0033\0143'\"" >> /root/.bash_profile
source /root/.bash_profile

 

I have to set this after each reboot.

 

 

* Please forgive me if this topic has already been started. I attempted to search but that returned a bunch of seemingly unrelated topics.

[trurl]

unRAID has a RAM filesystem where all of its operating system files are kept. When unRAID boots it unpacks all of its operating system files from bzroot and keeps them in RAM. Since bzroot is not altered to reflect any changes to these operating system files, they will all be restored to the original from bzroot when you reboot. This is why anything stored in any of the usual linux operating system folders does not survive a reboot.

 

In general, anything not in /boot (your flash drive) or /mnt (actual disks or shares on those disks) is in RAM.  Anything stored in these locations will persist after reboot.

 

This is why some people add code to the go script to alter operating system files every time they reboot. I have code in my go script which alters /etc for example.

 

You can put those packages in /boot/extra and they will be automatically installed on boot.

 

Add the other script to the script in /boot/config/go (like I have just done. Thanks for this)

 

 

 

[brianieface]

On 3/13/2013 at 2:23 AM, trurl said:

unRAID has a RAM filesystem where all of its operating system files are kept. When unRAID boots it unpacks all of its operating system files from bzroot and keeps them in RAM. Since bzroot is not altered to reflect any changes to these operating system files, they will all be restored to the original from bzroot when you reboot. This is why anything stored in any of the usual linux operating system folders does not survive a reboot.

 

In general, anything not in /boot (your flash drive) or /mnt (actual disks or shares on those disks) is in RAM.  Anything stored in these locations will persist after reboot.

 

This is why some people add code to the go script to alter operating system files every time they reboot. I have code in my go script which alters /etc for example.

 

You can put those packages in /boot/extra and they will be automatically installed on boot.

 

Add the other script to the script in /boot/config/go (like I have just done. Thanks for this)

 

 

 

 

Thank you so much...  !  Beer++