yep that is why I install everything. if you know the name of the prog I just google it then get it off a mirror download it then install it.

if you're just looking to find out what the hostname is or change it.
just sudo nano /etc/HOSTNAME to change it.

here is a copy of it from current (sight)

http://slackware.uk/slackwarearm/sla...t/slackware/a/

just download it and install it then see what happens

(package)
http://slackware.uk/slackwarearm/sla...3.18-arm-1.txz

There is this section that you might have overlooked...

OK. It's not lazy. It's how you work and Slackware is versatile enough to accommodate almost all users' needs. In order to make it so that all the packages in the slackpkg dialog interface are not selected by default you have to do a little editing. What you're asking for is actually a little known setting within the /etc/slackpkg/slackpkg.conf file. So, do this;

Then look for this section;

Edit 'ONOFF=on' and change it to 'ONOFF=off'. Exit and save the file. Run 'slackpkg install slackware' again.

<edit> Found this command [option] solution which works great! All packages are deselected in the list.
That should be what you're looking for.

1 members found this post helpful.

@Penthux
- actually it's even worse with the actual Slackware system updates implementation, slackpkg will uninstall some package without asking/warning and will leave a running system broken.

@rworkman
- this procedure should maybe be on the top of this page and not only mentioned for the install-new usage. There's nothing to forget if one was never informed:
https://docs.slackware.com/slackware:slackpkg
While an experienced Slacker/Linux user will know what to do in such a case, a beginner will surely start a thread and get some people busy. Always checking the Changelog and "deducing" that when a package has been split updating it might break the running system is a little bit over a normal usability expectation/standard.
My simple proposal, which should be both necessary & sufficient is to add 2-3 extra words (warnings) in the Changelog and eventually modify slackpkg and display the changelog (directly inform with the last changes) before the package selection dialogue.

https://www.linuxquestions.org/quest...nt-4175618768/

Or, never use Slackware current and install it only from time to time as new/fresh and don't provide drmozes with any feedback at all. Problem solved.

In the +13 years I've been running Slackware, and the +6 years I've been running Slackware ARM, the only time the system has been broken is when I've done something to break it, or because of hardware failure. slackpkg has never broke my system. In my experience I've never known slackpkg to remove any package without me requesting it, or knowing about it, beforehand.

I think Mozes would be more interested in feedback on Slackware ARM -current. Wouldn't you say?

No, slackpkg did not and does not *uninstall* any package without being told to do so.
In this particular case, it didn't uninstall the hostname utility either.

/bin/hostname used to be part of the net-tools package. It was split out into a separate package called hostname.
When the net-tools package was upgraded, it no longer contained /bin/hostname so that file was gone. If "slackpkg install-new" had been run *before* "slackpkg upgrade-all" then that would not have occurred.

It was already mentioned in the "Full System Upgrade" section, and it would be out of place at the top of the page. I did, however, edit that docs page to add a reminder to read the entire page before using slackpkg.

1 members found this post helpful.

@Exaga
I'm also a Slacker for more than 20 years (first used it in 1996 - switching from FreeBSD) but never cared about officially updating it or what the Slackware Team (I only knew about Patrick) was patching, but taking it as it is, installing new releases and recompiling/patching on my own whatever was requested (mainly kernel and some services packages I needed, sources I never took from Slackware, but from the official developers repositories). And that's why I love it, it never slapped my fingers, whatever I tried to hack on it.
Please do read trough the thread here and see for yourself that slackpkg does break a system under -current, in that it removes a package that was previously bundled together with another and doesn't install it back as new:
https://www.linuxquestions.org/quest...nt-4175618768/
Please do ask him, I was replying to rworkman.

@rworkman
Thanks for the reply, I agree with all your points, but the end effect for a user that is not reinstalling -current on every update (as suggested by drmozes) and is not aware about the install-new > upgrade-all sequence, which was documented only for system upgrades, nor is he warned in the changelog (maybe not even reading it before an update - which I don't, by the way, never remember the link), is that he'll get a system with some packages missing and will come over here on the forum and ask for help. That's why I proposed some minimal changes, just for directly informing & warning a simple user. Just a very minimalistic usability improvement, if you will.

Read the thread you have linked to. I corrected you there about that already. Please don't put sentences in my mouth that I didn't say.

Thanks.

Oh, you did, first in another recent thread (related to qpaeq):
https://www.linuxquestions.org/quest...2/#post5785494
&
And then repeatedly hinting in the Survival Guide thread:
https://www.linuxquestions.org/quest...8/#post5787566
https://www.linuxquestions.org/quest...8/#post5787715
- in respect to my "unwillingness" to reinstall / install fresh a -current system which was solid, installed clean from the very beginning
And then, in the same post you actually made me feel uncomfortable in using slackpkg with your statement:
Now, I won't put any more effort in this, as I feel like in Kindergarten throwing toys around. I'm just curious, if you don't use slackpkg, why care then?

You seem to like taking quotes out of context. I have explained why you should reinstall your system, and you seem to have forgotten those reasons.
I often reinstall the machine since I am the developer of the OS, and I test the installer when I build a new kernel (every couple of weeks, normally) - so I often have a fresh installation upon which to test any reported concerns. Each package is upgraded after it's built - the system isn't reinstalled after every package update.

Also I have explained why I have made corrections in response to some of your posts: some of your statements are based on misunderstandings of how the system works, and if people follow some of your ideas such as symlinking libraries, they'll screw their system up.

Anyway, I think that's enough of this.

2 members found this post helpful.

Your question, if answered, would only invite further acrimony. Although you should already know the answer.

People have tried to help and advise you but all you seem intent on doing is trying to discredit them and the work they do. I really don't know what your real issue is.

Damn. You beat me to it!