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.
I installed pre2 last night, and I played around with alacarte. I ended up having to blow away my xfce settings because xfce decided I didn't have any menu entries.
Overall, pre2 seems much faster to start than pre1, but the notification tray is still a little wonky.
I just noticed that I can only run Thunar as root. If I run Thunar from a command line as my normal user, it just seems to sit and run in the background with no errors printed to the screen. Has anyone run into this problem?
I just noticed that I can only run Thunar as root. If I run Thunar from a command line as my normal user, it just seems to sit and run in the background with no errors printed to the screen. Has anyone run into this problem?
Are you using the rworkman packages, or did you build it yourself?
is there no way to install XFCE 4.8pre1 onto slackware 13.1? some bugs with xfce in 13.1:
- can't rename terminal tabs
- trash bin always filled, even when empty
- mousepad can't use find string feature 2nd time onwards
These are all gone in 4.8.
Also, the items on the taskbar do not suddenly re-size when you try to click on them anymore.
I suppose that you could use the source and slackbuild scripts to re-construct all of the needed packages out of the source tree on a slackware-current FTP. Then, the slackbuild scripts in Robby's XFCE 4.8 source section might work.
There have been some pretty major changes to -current since 13.1, though ... It may just not work. All of the changes and upgrades to X11, especially, may have just altered the build environment too much.
Why not upgrade to current? It's at a pretty solid moment right now ...
Why not upgrade to current? It's at a pretty solid moment right now ...
Agreed. Current is stable for me as well. If you do decide to upgrade to -current please back up files you can not afford to lose in the unlikely event that things go awry during the upgrade.
Agreed. Current is stable for me as well. If you do decide to upgrade to -current please back up files you can not afford to lose in the unlikely event that things go awry during the upgrade.
Also, an upgrader should bear in mind that the GTK+ and X11 upgrades are very extensive and deep-cutting. Just like some of us encountered with the large round of updates covering the bulk of these moves, if you have a 13.1 system that you've done some "not so kosher" things to, some things could get broken.
If your 13.1 system has been used heavily for a long time, involving a lot of experimentation, I'd recommend backing up /etc, /home, and /boot plus /lib/modules if you're using a custom kernel, also anything else that you know you might need. Then, do a fresh install of 13.1 and reinstate your backups before jumping up to -current. If you do that, you're not likely to encounter any problems. Your /etc will then be brought up to current spec in the least painful way I can imagine, especially if you use the (P)rompt selection when incorporating .new files.
in alien's script, but it just wouldn't connect. How do I identify the rsync uri of each mirror? thanks.
You can edit /etc/slackpkg/mirrors to point to a -current mirror of your choice. Make sure you un-comment one mirror only. This will allow you to upgrade 13.1 to -current.
You can also use Alien Bob's current script which will create slackware-current isos for you.
I managed to download and build -current iso using mirrors near Asia, although some of the URIs from slackware mirror doesn't work. This is what I used:
Using virtualbox, I've installed a stock x86 13.1 and am currently updating to -current via slackpkg
Quote:
set mirror to current (local dvd) in /etc/slackpkg/mirrors
slackpkg update ;
slackpkg install-new ; slackpkg upgrade-all ;
In general, upgrading pkgs takes a very long time. It's been 4 hours and VirtualBox is still chugging away. For stock install upgrading to -current, i.e. (non-customized, vanilla builds etc) can we slipstream the -current pkgs straight into stock 13.1 dvd and let setup install them the lightning fast way?
Or can I just boot the -current iso and install? Will I miss any packages this way? The dvd-iso I created is only 2GB, without source files. thanks.
Or can I just boot the -current iso and install? Will I miss any packages this way? The dvd-iso I created is only 2GB, without source files. thanks.
Sure, you can install from the -current iso. Once you're up and running just edit /etc/slackpkg/mirrors to point towards the -current mirror of your choice to update your current install. That won't take long at all.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.