LinuxQuestions.org
Welcome to the most active Linux Forum on the web.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware > Slackware - ARM
User Name
Password
Slackware - ARM This forum is for the discussion of Slackware ARM.

Notices


Reply
  Search this Thread
Old 01-02-2018, 12:37 PM   #16
BW-userx
LQ Guru
 
Registered: Sep 2013
Location: MID-SOUTH USA
Distribution: Slackware 14.2 / Slackware 14.2 current / Manjaro
Posts: 6,361

Rep: Reputation: 1229Reputation: 1229Reputation: 1229Reputation: 1229Reputation: 1229Reputation: 1229Reputation: 1229Reputation: 1229Reputation: 1229

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.
Code:
$ cat /etc/HOSTNAME
slackwhere.what.net
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

Last edited by BW-userx; 01-02-2018 at 12:46 PM.
 
Old 01-02-2018, 02:52 PM   #17
Penthux
Member
 
Registered: Dec 2008
Location: Middlesbrough, UK
Distribution: Slackware
Posts: 228

Rep: Reputation: 67
Quote:
Originally Posted by asarangan View Post
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.
There is this section that you might have overlooked...

Code:
install-new
            This action installs any new packages that are added to the  official
            Slackware  package  set.  Run this if you are upgrading your system to
            another Slackware version or if you are using -current. If you want to
            install all uninstalled Slackware packages onto your  system, use the 
            following command instead of the install-new action:

                 # slackpkg install slackware.
Quote:
Originally Posted by asarangan View Post
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?
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;

Code:
root@drie:~# nano -w /etc/slackpkg/slackpkg.conf
Then look for this section;

Code:
# The ONOFF variable sets the initial behavior of the dialog interface.
# If you set this to "on" then all packages will be selected by default.
# If you prefer the opposite option (all unchecked), then set this to "off".
ONOFF=on
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.
Code:
root@drie:~# slackpkg -onoff=off install slackware
That should be what you're looking for.

Last edited by Penthux; 01-08-2018 at 02:24 PM. Reason: slackpkg -onoff=off install slackware
 
1 members found this post helpful.
Old 01-02-2018, 05:14 PM   #18
abga
Member
 
Registered: Jul 2017
Location: EU
Distribution: Slackware
Posts: 449

Rep: Reputation: 225Reputation: 225Reputation: 225
@Penthux
Quote:
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.
- 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
Quote:
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.
- 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
Quote:
install-new

Running slackpkg with this argument generates a list of packages that were introduces to the Slackware recently, for example new dependencies to a package. It is advisable to run this command before updating the system if you synchronize to slackware-current.
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.
 
Old 01-02-2018, 07:11 PM   #19
rworkman
Slackware Contributor
 
Registered: Oct 2004
Location: Tuscaloosa, Alabama (USA)
Distribution: Slackware
Posts: 2,299

Rep: Reputation: 806Reputation: 806Reputation: 806Reputation: 806Reputation: 806Reputation: 806Reputation: 806
https://docs.slackware.com/slackware...system_upgrade
 
Old 01-02-2018, 07:21 PM   #20
abga
Member
 
Registered: Jul 2017
Location: EU
Distribution: Slackware
Posts: 449

Rep: Reputation: 225Reputation: 225Reputation: 225
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.
 
Old 01-05-2018, 01:11 PM   #21
Exaga
Member
 
Registered: Nov 2012
Posts: 127

Rep: Reputation: Disabled
Quote:
Originally Posted by abga View Post
- 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.
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.

Quote:
Originally Posted by abga View Post
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.
I think Mozes would be more interested in feedback on Slackware ARM -current. Wouldn't you say?
 
Old 01-05-2018, 01:21 PM   #22
rworkman
Slackware Contributor
 
Registered: Oct 2004
Location: Tuscaloosa, Alabama (USA)
Distribution: Slackware
Posts: 2,299

Rep: Reputation: 806Reputation: 806Reputation: 806Reputation: 806Reputation: 806Reputation: 806Reputation: 806
Quote:
Originally Posted by abga View Post
@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.
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.

Quote:
@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
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.
Old 01-05-2018, 04:53 PM   #23
abga
Member
 
Registered: Jul 2017
Location: EU
Distribution: Slackware
Posts: 449

Rep: Reputation: 225Reputation: 225Reputation: 225
@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/
Quote:
I think Mozes would be more interested in feedback on Slackware ARM -current. Wouldn't you say?
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.
 
Old 01-05-2018, 06:07 PM   #24
drmozes
Slackware Contributor
 
Registered: Apr 2008
Location: Surrey, England
Distribution: Slackware
Posts: 676

Rep: Reputation: 520Reputation: 520Reputation: 520Reputation: 520Reputation: 520Reputation: 520
Quote:
Originally Posted by abga View Post
reinstalling -current on every update (as suggested by drmozes)
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.
 
Old 01-05-2018, 06:44 PM   #25
abga
Member
 
Registered: Jul 2017
Location: EU
Distribution: Slackware
Posts: 449

Rep: Reputation: 225Reputation: 225Reputation: 225
Quote:
Originally Posted by drmozes View Post
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
Quote:
None of these problems exist on a fresh installation of -current.
&
Quote:
You might want to reinstall your machine. If you were using a tool to update, I'd recommend doing it manually and reading the change log.
And then repeatedly hinting in the Survival Guide thread:
https://www.linuxquestions.org/quest...8/#post5787566
Quote:
I did not say this. I said that you should reinstall _your_ system.
https://www.linuxquestions.org/quest...8/#post5787715
Quote:
Your logic puzzles me. If anything it's pre-(some months)-15.0.
- 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:
Quote:
As regarding slackpkg - I don't use it, never have apart from to test the epoch date-quit patch I made for it.
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?
 
Old 01-06-2018, 03:12 AM   #26
drmozes
Slackware Contributor
 
Registered: Apr 2008
Location: Surrey, England
Distribution: Slackware
Posts: 676

Rep: Reputation: 520Reputation: 520Reputation: 520Reputation: 520Reputation: 520Reputation: 520
Quote:
Originally Posted by abga View Post
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.

Last edited by drmozes; 01-06-2018 at 03:37 AM. Reason: clarification
 
2 members found this post helpful.
Old 01-06-2018, 03:38 AM   #27
Exaga
Member
 
Registered: Nov 2012
Posts: 127

Rep: Reputation: Disabled
Quote:
Originally Posted by abga View Post
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?
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.

Quote:
Originally Posted by drmozes View Post
Anyway, I think that's enough of this.
Damn. You beat me to it!
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
how to recover /bin/hostname file mcs_o8_01 Linux - Newbie 1 08-20-2010 02:52 AM
setting /bin/hostname [failed] tulsi Linux - Networking 6 11-29-2009 06:36 AM
svnserve after recent upgrade biol75 Slackware 0 09-07-2009 04:29 AM
recent applications/documents in menu missing Mugatu Mandriva 3 02-07-2005 01:30 PM
broke /bin/hostname nitsky416 Linux - Networking 2 11-30-2003 04:45 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware > Slackware - ARM

All times are GMT -5. The time now is 01:38 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration