/bin/hostname is missing in recent upgrade
 

The Dec 21 2017 upgrade of util-linux-2.31.1-arm-1.txz seems to be missing the /bin/hostname utility. Why did it disappear? As a result, my login prompt is showing "none" for the hostname.

Hard to say why it disappeared. You should just be able to reinstall from your distro repositories for instance. Obviously, use the package manager for your system

Try this to see if it gives any output about your hostname:

You could run 'netconfig' to use the Slackware setup wizard to try and resolve the issue:

There's always the manual method:

It should now be fixed. Try 'uname -n' command after rebooting.

I personally wouldn't try (or advise) to fix this problem by installing any packages. Especially with 'apt-get'. :D

If he is missing the binary in /bin, and apt-get is his package manager, that is certainly an appropriate course of action.

What issue do you have with apt-get? hostname is, in fact, a package

My issue is that this is Slackware. Not Debian/Ubuntu? Your advice may be good for the latter, but on Slackware there is no advanced package tool (apt) command/function.

Why would you even want it on Slackware? Apt goes against the Slackware Way and takes control away from the Admin (i.e. me and you) with regards to package management.

Slackware uses 'pkgtool' (installpkg, removepkg, etc.) or 'slackpkg'. There is no 'apt-get' or 'apt-whatever' on my Slackware ARM system.

Which is why I said in that very same post
Also, you may not have it on your ARM system, but it is in current
https://packages.slackware.com/?r=sl....18-i586-1.txz

I'm guessing that OP forgot to do "slackpkg install-new" before "slackpkg upgrade-all" -- hostname was split out into a separate package somewhat recently.

The package was split out -- the information is in the Change Log - search for "hostname".

Well, we deal with Slackware ARM in this forum. So, unless the OP has posted in the wrong section then he'll need the ARM version of the package you're referring to: ftp://ftp.arm.slackware.com/slackwar...3.18-arm-1.txz.

Furthermore, as you correctly stated, this package only exists in Slackware ARM -current. So, if the OP is running Slackware ARM 14.2 (as I did previously) he will not be able to install, or find, this package for his system. Slackware ARM 14.2 is the soft float port and -current is the hard float port.

Apologies for being a stickler but I love to see accurate and helpful advice. The whole 'apt-get' thing is not relevant to Slackware and with a little more time and effort a lot more concise information could have been relayed. We got there in the end. :hattip:

Yes, I missed that this was the Slackware ARM forum, I was just searching in the 'View New Posts' section, and saw no mention of the distro in the OP or OP's bio. Which is why I made sure to clarify that the OP should use his distro's package manager. Sorry for confusing you.

I thought I had relayed the information well enough to the OP that he could figure it out.

Regardless, the fact stands that in current, hostname is a package.

It may not be in 14.2, but OP has not stated what he is running. Or I missed it

This is exactly what happened. Thank you for your reply. I didn't realize I had to run install-new, but that brings me to the question how to use it correctly. My system is minimal, and does not include the 'kde', 'xap' and a few other series. When I run install-new, it brings up every package in all the series, and I am not sure how to sort through that huge list to find out which packages to select. In this particular case it is obvious, because I know I am missing "hostname". But if I didn't know that, is there a way to bring up only the new packages that were not in the original installation of my system?

The above command will give you a list of all uninstalled Slackware packages on your system. From here you can select to install them.

The above command will hopefully lead you to what you need to know. ;)

http://www.slackware.com/changelog/current.php?cpu=arm

change log

@asarangan

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

(it's still on the first page of the Slackware ARM Forum)

Great, thank you. There is no way I would have figured out from the man page that "slackpkg install slackware" would bring up only the uninstalled packages. But when I do that, I get several hundred items to scroll through (because mine is a minimal system), and all of them are selected by default with the "*". I don't mean to sound lazy, but how do I deselect them all without having to deselect them one by one?

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. :cool:

@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.

@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.

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!