mikshaw
Group: Members
Posts: 4856
Joined: July 2004 |
 |
Posted: June 24 2005,02:40 |
 |
Most of your issues can be resolved by using myDSL packages or backup/restore to add or replace files.
If you have a file you need replaced (other than a file which is run during the init process), include it in an auto-loaded .dsl package. If you want to keep the base system untouched, you may be able to put an edited copy of a file, such as /usr/bin/pon, in a writeable directory, and add that directory to your PATH variable (or root's PATH?) *before* /usr/bin.
Applications installed by other methods can be a bit tricky. If you install a program from source into /opt, in the manner that tar.gz and uci extensions are built, you can easily add that directory to your backup. However, if you are installing with apt-get or other package management system, the installed files are typically spread out through the system and much more difficult to track down. Additionally, most are installed into the base system, which means they won't successfully restore unless you first run mkwriteable. Fortunately, there is a script called deb2dsl which will build a .dsl extension from an installed debian package (i've never used it, but i hear good things). For applications installed into the base system from non-deb packages or from source, you're on your own. As far as I know you would need to manually build your own myDSL extensions. I suspect you could add these apps to your backup, but if the files need to go into the base system you'll first need to auto-load at least one .dsl extension to run mkwriteable. Personally I avoid that whole mess by using (in my main DSL setup) only applications installed or mounted into /opt, along with a persistent /opt.
--------------
http://www.tldp.org/LDP/intro-linux/html/index.html
|
.
DSL Market ,
Great VPS hosting provided by Tektonic
