LinuxQuestions.org
Share your knowledge at the LQ Wiki.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 06-10-2021, 02:40 AM   #7786
Didier Spaier
LQ Addict
 
Registered: Nov 2008
Location: Paris, France
Distribution: Slint64-14.2.1.2 on Lenovo Thinkpad W520
Posts: 9,914

Rep: Reputation: Disabled

@elcore: I don't see a reason to worry in what you reported and think that your system would be more at risk using an unmaintained software, further if you are really worried you could isolate your machine from any network when booting. But that's just my opinion.

PS and if you are that worried, don't use a public source of electricity, as it can be an attack vector as well (OK, half kidding here, but still think power line communication and in many phones the same connector can be used to charge the unit or transfer files). But to be fully protected keep this machine isolated when running Slackware, using only well checked removable devices for information exchanges with the outside world.

PS If using GRUB 2 but not upgrading to 2.06 you'll miss the security fixes listed in Multiple GRUB2 vulnerabilities - 2021/03/02 round among others.

Last edited by Didier Spaier; 06-10-2021 at 08:06 AM.
 
Old 06-10-2021, 12:54 PM   #7787
elcore
Member
 
Registered: Sep 2014
Distribution: Slackware
Posts: 863

Rep: Reputation: Disabled
Quote:
Originally Posted by Didier Spaier View Post
If using GRUB 2 but not upgrading to 2.06 you'll miss the security fixes
This new requirement outweights those vulnerability fixes, since it makes the loader potentially vulnerable where it was just optionally vulnerable before.
Not worried about it at all, I'm not using the network boot and that system is always offline so the loader may as well be riddled with remote holes for all I care.

Quote:
Originally Posted by Didier Spaier View Post
I don't see a reason to worry in what you reported and think that your system would be more at risk using an unmaintained software.
Where did I say I was worried anyway? It's those guys who use network boot who are worried, so I assume this shiny new requirement was not a mistake.
Probably just a call for more testers like, not enough eyes on this remote feature so fsck it let's just make it mandatory for everyone downstream.
Meanwhile, the "unmaintained" still has no new features, no new remote holes and no decisions upon decisions, it just is what it is.

It's nothing personal, we just disagree on some basic concepts of security, and to be honest I do still hope the whole thing's a honest mistake.
As for requests, well I don't really have any, but the OS was and still is usable without network so it'd be great if that stayed the same.
 
Old 06-10-2021, 01:52 PM   #7788
Fellype
Member
 
Registered: Jul 2013
Location: Guaratingueta / Brazil
Distribution: Slackware
Posts: 52

Rep: Reputation: 27
Code:
[97/109]        Package slackpkg-15.0.5-noarch-1.txz is already in cache - not downloading
        Upgrading  => []:slackpkg-15.0.5-noarch-1...
Upgrading:  slackpkg-15.0.5-noarch-1: Slackware package upgrade manager ............................................................ [ 410K]
slackpkg was upgraded - you will need start the upgrade process again...
If I'm not mistaken, in Slackware 14.2 slackpkg was used to be the first package upgraded when there was more than one on the list. Can we have this feature back (or implemented if I'm wrong )?

Thanks in advance.
Fellype

[EDIT] It still being the first package upgraded. However, it is upgraded immediately after its download is finished, and then the upgrade process stop. It would be better to put it at the end of the upgrade list in this case.

Last edited by Fellype; 06-10-2021 at 01:58 PM. Reason: Correction in info
 
Old 06-10-2021, 05:18 PM   #7789
saxa
Member
 
Registered: Aug 2004
Distribution: Slackware
Posts: 854

Rep: Reputation: 168Reputation: 168
glib-2.68.3
https://download.gnome.org/sources/g...-2.68.3.tar.xz
 
Old 06-10-2021, 10:25 PM   #7790
Lockywolf
Member
 
Registered: Jul 2007
Posts: 500

Rep: Reputation: 138Reputation: 138
Would it be possible to add the Slackware installer to the root of the Slackware installation iso file?

Motivation: I would like to install Slackware from a running Linux system. I am imagining it as:

1) Insert an external HDD box.
2) Mount Slackware iso to /mnt/cdrom.
3) Run /mnt/cdrom/installer/setup
4) Point it to the external HDD

The installer may rely on some utilities not provided by the host system, but if the host system is Slackware this should not be a problem. Otherwise, the user may just add the necessary utilities from their distro.
 
Old 06-11-2021, 06:01 AM   #7791
saxa
Member
 
Registered: Aug 2004
Distribution: Slackware
Posts: 854

Rep: Reputation: 168Reputation: 168
Quote:
Originally Posted by Lockywolf View Post
Would it be possible to add the Slackware installer to the root of the Slackware installation iso file?

Motivation: I would like to install Slackware from a running Linux system. I am imagining it as:

1) Insert an external HDD box.
2) Mount Slackware iso to /mnt/cdrom.
3) Run /mnt/cdrom/installer/setup
4) Point it to the external HDD

The installer may rely on some utilities not provided by the host system, but if the host system is Slackware this should not be a problem. Otherwise, the user may just add the necessary utilities from their distro.
Shouldn't the installer have already all needed stuff on the slackware iso ?
 
Old 06-11-2021, 09:57 AM   #7792
2slguevH
LQ Newbie
 
Registered: Jul 2019
Distribution: slackware
Posts: 6

Rep: Reputation: Disabled
gnupg2 2.2.28

https://gnupg.org/ftp/gcrypt/gnupg/gnupg-2.2.28.tar.bz2
https://gnupg.org/ftp/gcrypt/gnupg/g...28.tar.bz2.sig
 
Old 06-11-2021, 10:27 AM   #7793
bassmadrigal
LQ Guru
 
Registered: Nov 2003
Location: West Jordan, UT, USA
Distribution: Slackware
Posts: 8,260

Rep: Reputation: 5845Reputation: 5845Reputation: 5845Reputation: 5845Reputation: 5845Reputation: 5845Reputation: 5845Reputation: 5845Reputation: 5845Reputation: 5845Reputation: 5845
Quote:
Originally Posted by saxa View Post
Shouldn't the installer have already all needed stuff on the slackware iso ?
It's buried in the initrd or usbboot.img. That's not easily accessible if you're not booting off the disk.

Or in source/, but that's not included in the installation ISO.
 
Old 06-11-2021, 11:14 AM   #7794
Petri Kaukasoina
Member
 
Registered: Mar 2007
Posts: 689

Rep: Reputation: 447Reputation: 447Reputation: 447Reputation: 447Reputation: 447
Quote:
Originally Posted by Lockywolf View Post
Would it be possible to add the Slackware installer to the root of the Slackware installation iso file?

Motivation: I would like to install Slackware from a running Linux system.
It's rather easy to install Slackware to another disk from a running system by setting $ROOT point to the new disk and using installpkg. Then a bit of tuning and it's ready.

But if you are interested to make it work from the installer, I would not try to run the installer from the host system. Instead I would suggest extracting the installer image to a directory on the host ( unxz -c initrd.img |cpio -i ), making at least a bind mount to /proc (maybe more), and then chroot to that directory and run /usr/lib/setup/setup there. You would then run the busybox utilities etc, the tools of the install disk.

I'm sure the install wouldn't work now, but that could be a project for you to make it work.
 
Old Yesterday, 05:52 AM   #7795
Pixxt
Member
 
Registered: May 2008
Distribution: Slackware, Debian,
Posts: 221

Rep: Reputation: 124Reputation: 124
Vulkan-sdk in current is a few versions stale.
 
Old Yesterday, 07:00 AM   #7796
NonNonBa
Member
 
Registered: Aug 2010
Distribution: Slackware
Posts: 180

Rep: Reputation: Disabled
Next time the etc package is updated, I think the haldaemon user/group can be removed, as nothing seems to use them anymore, even in -stable.

And maybe I miss something, but there is something weird in /etc/profile.d/libglib2.{c,}sh:
Code:
#!/bin/sh
#
# Description:  This script sets the environment variables G_FILENAME_ENCODING
# and G_BROKEN_FILENAMES for the glib-2.0 library.
#
# G_FILENAME_ENCODING
#       This environment variable can be set to a comma-separated list of
#       character set names.  GLib assumes that filenames are encoded in the
#       first character set from that list rather than in UTF-8.  The special
#       token "@locale" can be used to specify the character set for the
#       current locale.
# [...]

# If the LANG you have set contains any form of "UTF", we will guess you are
# using a UTF-8 locale.  Hopefully we're correct.
if echo $LANG | grep -iq UTF ; then
  export G_FILENAME_ENCODING="@locale"
fi
Isn't it meant to be "grep -viq": if we are not already using the default UTF-8 charset, we configure glib to match our non-UTF-8 locale? It is the same in -stable, but I can't see the point otherwise.
 
Old Yesterday, 07:54 AM   #7797
Petri Kaukasoina
Member
 
Registered: Mar 2007
Posts: 689

Rep: Reputation: 447Reputation: 447Reputation: 447Reputation: 447Reputation: 447
Quote:
Originally Posted by NonNonBa View Post
something weird in /etc/profile.d/libglib2.{c,}sh

https://www.linuxquestions.org/quest...7/#post5631371
 
Old Yesterday, 08:44 AM   #7798
NonNonBa
Member
 
Registered: Aug 2010
Distribution: Slackware
Posts: 180

Rep: Reputation: Disabled
Quote:
Originally Posted by Petri Kaukasoina View Post
Thank you. But at the end, GazL just improves the way they are written, not enlightening their logic he finds confusing too.

If it's true these files however don't actually fix anything they are meant to fix, maybe they should simply be discarded for mind's sake.
 
Old Yesterday, 01:43 PM   #7799
richarson
Member
 
Registered: Dec 2020
Location: Argentina
Distribution: Slackware64-current
Posts: 45

Rep: Reputation: Disabled
In plasma 5.22.0 krunner doesn't respond to Alt+Spacebar or any other shortcut:

https://bugs.kde.org/show_bug.cgi?id=437364

Patch here if we can't wait till plasma 5.22.1:

https://invent.kde.org/plasma/plasma...5509caea6fe6b8

Cheers!
 
Old Yesterday, 02:34 PM   #7800
gegechris99
Senior Member
 
Registered: Oct 2005
Location: France
Distribution: Slackware current 64bit
Posts: 1,069
Blog Entries: 5

Rep: Reputation: 274Reputation: 274Reputation: 274
Quote:
Originally Posted by richarson View Post
In plasma 5.22.0 krunner doesn't respond to Alt+Spacebar or any other shortcut:
Alt+Spacebar works here on Slackware64 Current with plasma 5.22.0 and krunner 5.82.0.
 
  


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
[SOLVED] Requests for -current (20151216) rworkman Slackware 3441 12-28-2017 03:50 PM

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

All times are GMT -5. The time now is 04:16 PM.

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
Open Source Consulting | Domain Registration