Re: rootfs full? Here's a temporary solution until more packages are optified
 

Did this thread fizzle out into nothing? Did ccooke ever come back from work? :-)

(My understanding of /opt according to Linux Filesystem Hierarchy: nothing to discuss, all apps should have gone into /opt from the beginning, we should never even have started to put things in rootfs... bad habit from older Maemo?)

Re: rootfs full? Here's a temporary solution until more packages are optified
 

Is it possible to use parts of the script at installation of packages? so that debian-packages could be installed on the 2gb-partition and symlinks automatically created on the 256mb-partition during installation? i think symlinks are the only solution for the problem with the small root-partition, without changing logical structure of the system (remove files for booting from /usr and move/symlink /usr to 2gb-partition) or bootloader configuration (to boot from 2gb-partition).

Re: rootfs full? Here's a temporary solution until more packages are optified
 

Have a look at: Repartition the internal drive

Re: rootfs full? Here's a temporary solution until more packages are optified
 

subversion in -devel isn't optified...

Re: rootfs full? Here's a temporary solution until more packages are optified
 

While in the process of moving some packages with the script, I'm wondering what is going to happen when one of them is to be updated by the application manager (or apt-get).

It is going to install its new files in their pristine position, on the root filesystem, overwriting the links, and leaving parts of the old packages on /opt? Shall it get me into trouble? What am I going to do with those remnants on /opt?

Or I better undo optification of packages before I update the packages?

Thanks for your responses.

Re: rootfs full? Here's a temporary solution until more packages are optified
 

on my N900

:command not found
:command not found
'kgscan : line 9:syntax error near unexpected token `{
'kgscan : line 9: `{

Re: rootfs full? Here's a temporary solution until more packages are optified
 

I've been thinking about the same thing. If the updated package still isn't optified it will overwrite the links I believe. If it is optified it won't be a problem AFAIK. That would create links to the new files (in /opt) overwriting the old links AND files.

Re: rootfs full? Here's a temporary solution until more packages are optified
 

First of all shouldn't the name of the script have been pkgscan...? :)

When i downloaded the script by using the download function on pastebin the file had WinBlows newlines (^M) in it, so first I tried a search and replace in vi but that didn't work (%s/^M//g), so I ended up copy/pasting from the site instead.

I've attached the script. unpack with tar -xf pkgscan.sh.tar... The script is called pkgscan.sh because it's a shell script.

Re: rootfs full? Here's a temporary solution until more packages are optified
 

Hi, I've seen too that an update or uninstall only updates the symlinks and leaves all files in /opt/relocated/.

In order to keep things clean I've done an "undo", then apt-get --purge remove of all the applications originally relocated, then apt-get autoremove (since there were some remanents) and re-installed those apps.

IMHO, people not really familiar with gnu/linux should stay away from this script for many reasons already mentioned plus that if one relocates an app already optified the "undo" will un-optify it. That is, the undo function is not a real undo.

Hope it helps.

Re: rootfs full? Here's a temporary solution until more packages are optified
 

Yes that's the problem. I changed from CR/LF newlines to LF only newlines in Scite, from easy debian.