SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Hello,
I have installed frugal in hard disk puppy slacko 14.1 before 4 years and i have many installed programms. I want to convert it to Slackware 14.2 because the libraries i have and i cant compile sdcc. Because its for one programm only i dont hurry about but because i have installed pkgtool, installpkg and much slackware 14.1 packages and the system is mixed now, is it possible to convert to 14.2 Slackware without loose the installed programms? I can manually remove if need the double version files.
You'd better have a list of those and recompile them in a queue on a fresh install (the queue file would be ready for updates) unless they are to many of them.
I have played with Puppy many times over the years and Slacko used to be my favourite Puppy until this extra long release cycle has effectively killed Slacko.
My unprofessional opinion is that it would be best to save your frugal install on a USB stick and then install Slackware 14.2 proper.
Puppy, after all is more and more every day proving to be a toy so an outright replacement is to be preferred (in my estimation)
Remember, you got my advice for FREE and it is probably worth just what you paid for it.
i have make these years many programms. only the rtl-sdr and all the dependencies, not only the required, i made them for days. i think i can install the new packages with installer, i use grub4dos to boot, i dont know what will happen with the scripts puppy uses to boot.
Old programs will work with new libraries, isnt right?
I have 3 old laptops with the same up-down configuration.
Gordie the only thing i don't like is the auto resize of rox-filer at directory change.
Old programs will work with new libraries, isnt right?
Some will, some won't. If they rely on a library that had an ABI change, then they won't work and will complain about missing that older library.
When you run some programs, they'll simply tell you that they can't find some version of a library and you can simply recompile that, but others can have cryptic errors or no error message at all. Sometimes a dependency will need compiling and the message by the main program might not let you know what dependency needs to be recompiled.
Unfortunately, the best way to move from one version of Slackware to another is to recompile all the packages.
However, a suggestion that I've used previously to minimize downtime is to install 14.2 into a VM (I use VirtualBox, but it shouldn't matter which one you use) and fully update it. Then go through and start compiling all your software on that VM and keep the packages. Once everything is done, save those package, wipe your main system, install 14.2, update it, then simply installpkg all those previously compiled packages.
Then it's simply a matter of configuring everything and you'll be back to your normal workflow.
Distribution: Slackware64 15.0 (started with 13.37). Testing -current in a spare partition.
Posts: 928
Rep:
Quote:
Originally Posted by lakis70
auto resize of rox-filer at directory change.
Hope this helps.
I think this is set in ~/.config/rox.sourceforge.net/ROX-Filer/Options,
line "<Option name="filer_auto_resize">2</Option>", 2 doesn't change window size.
Or right click in rox window background -> Options -> never automatically resize
I like to save copies of old systems so I can be certain to be able to run old apps on new stuff. I'm still running a couple KDE v3 apps on the latest Current with KDE Plasma5 by creating an appropriate set of libraries for KDE v3 in /opt.
Hope this helps.
I think this is set in ~/.config/rox.sourceforge.net/ROX-Filer/Options,
line "<Option name="filer_auto_resize">2</Option>", 2 doesn't change window size.
Or right click in rox window background -> Options -> never automatically resize
Paulo thank you
i set the option to 0 (zero) and reboot (only restarting graphical server and window manager doesnt work).
I like to save copies of old systems so I can be certain to be able to run old apps on new stuff. I'm still running a couple KDE v3 apps on the latest Current with KDE Plasma5 by creating an appropriate set of libraries for KDE v3 in /opt.
something like /opt/lib and /opt/usr/lib with links to original places and names?
The queue file is the order of compilation (installation) of your packages. One per line.
With a slackbuild for each you will be able to rebuild and reinstall with a one line command (for ... in ...).
Finally i did it last days. I install Slackware 15.0 over puppy Linux and all works. I have minor problems with user rights because puppy use only root and with X which breaks (no screen error) after 2 days when i compiled and installed some dependencies for QEMU. After a day of searching for solution, the solution is simple it needed a new conf file. Another little problem is that palse audio control works for root but not for simple user. Has someone an idea about?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.