Quote:
Originally Posted by wirelessmc
This is great stuff bassmadrigal! Thank you for posting this. I am definitely going to give this a shot.
I have been using AlienBob's mirror script to keep a local repository of -current for several months now. It is a very handy script and should be easily modified to keep a Slackware 14.2 repository current - though I am not sure this is warranted since slackpkg should adequately handle keeping my 14.2 install current and with much lower traffic.
|
The scripts won't see any traffic (other than checking the changelog) if there's no updates. It just makes sure that whenever I update via slackpkg, it's a really fast transfer rate (either because it's on the same computer or because it's locally on my LAN).
Quote:
Originally Posted by wirelessmc
That said I am having some doubts about slackpkg. For example just this morning I had issues upgrading my multilib packages. The following commands should do the trick but they didn't:
#slackpkg update
#slackpkg upgrade multilib
|
It's hard to know what happened without seeing the logs and your configuration settings. Maybe the mirror you used wasn't synced at the time or was having connection issues?
Quote:
Originally Posted by wirelessmc
Since you regularly upgrade your -current, I am curious how often do you upgrade your kernel. Are you currently running the 5.4.X ?
|
I'm actually not regularly updating a -current install. I have a machine running -current that hasn't been updated since May. It's my HTPC and is stable with its current package versions, so I don't mess with it (yes, I'm aware there are security issues with this not being updated regularly). The only reason it is running -current is because the hardware wouldn't work on 14.2 and I don't want to mess with the system and need to recompile kodi and its dependencies whenever an upgrade from -current requires it.
The reason I keep the -current mirror updated is mainly for updated sources. I'll frequently compile packages from -current on 14.2 and it is really easy to go into my mirrored directory and copy that source to my compile directory. I just found it was such a pain to write up the command to download that particular program's source folder each time I did it, so I set up this automated mirror so I never have to worry about grabbing things manually again. I have plenty of diskspace and I pay for an unmetered home internet connection (annoyed I even have to pay extra for unmetered, but that's another topic), so it was a no brainer to mirror these two versions of Slackware locally.
On my main 14.2 machine, I do upgrade the kernel occasionally (I've long been off the 4.4.x kernel, choosing newer ones as I recompile). The kernel I'm currently using on that machine is 5.3.12. I intend to upgrade to the latest 5.4.x within the next few weeks, but I hate rebooting my computer. I usually have a lot of programs and windows open and regularly have people connected to the machine from the internet (it also acts as a server that a few friends have access to), so rebooting ends up being quite the hassle.