SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Regarding "the choice" between Stable and Current, there is a happy middle ground - install both. Multi-booting isn't hard and hard drive real estate is cheap. That eliminates the guesswork and you learn some stuff in the process.
Secure Boot is part of the UEFI specification and first appeared in the Unified Extensible Firmware Interface (UEFI) 2.3.1 specification (Errata C). It is meant to prevent the execution of unauthorized code upon boot of a computer. Most modern Personal Computers will have a way of enabling Secure Boot in UEFI, but it is common to leave it disabled if you are not running a Microsoft OS on it since Microsoft controls Secure Boot.
For dual-boot scenario’s the story is different however. Microsoft Windows 8 and 10 advise to have Secure Boot enabled but don’t enforce it, but as far as I know, for Microsoft Windows 11 enabling Secure Boot will be a requirement to get full upgrade support.
> Clearly we're going to have to trend more carefully for things to settle down,
> so consider this RC2 and a much harder freeze. A test mass rebuild was done
> here and there are no more "fails to build from source" remaining (thanks to
> nobodino for some amazing and relentless testing).
My preference for 24 hour format for the clock and the default is am/pm. You can change for the desktop but not for lock screen from system settings utility. The lock screen defaults to the am/pm.
cd /usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/components
As root;
vi Clock.qml
Code:
ColumnLayout {
Label {
//text: Qt.formatTime(timeSource.data["Local"]["DateTime"])
text: Qt.formatTime(timeSource.data["Local"]["DateTime"], "hh:mm:ss")
font.pointSize: 32 //Mockup says this, I'm not sure what to do?
Layout.alignment: Qt.AlignHCenter
}
Note the comment out with // then add the line 'text: Qt.formatTime(timeSource.data["Local"]["DateTime"], "hh:mm:ss")' below the commented line. Save the file and test.
Hope this helps.
I just noticed that my recent post(s) showed Win/7 and then Linux icons. I set my user agent add-on line to 'Mozilla/5.0 (X11; Linux x86_64; rv:94.0.1) Gecko/20100101 Firefox/94.0.1 Slackware 15.0' but it does not save it. So I must reset it to my desired settings. You can use a customized line but it must be updated after any changes to other selected lines for a container. This Firefox add-on is useful at times but can cause unwanted issues.
Just a note to other Slackers.
I generally only use a browser on Ubuntu and Windows, and it's Firefox. After reading your post I thought I'd give it a try. So when I submit this post I'll find out if masquerading as a Slackware OS Firefox browser was successful.
[EDIT] My hat goes off to you sir. HAHAHA! This is pretty damned cool!
Last edited by Exaga; 11-27-2021 at 08:02 AM.
Reason: EDIT - Slackware OS Firefox browser = imposter!
Upgrading Slackware64 RC1 Kernel 5.15.2
#slackpkg install-new And here is the question, in the resulting list there is alot 5.88of kde packages I readily recognize, but I don't run xfce not kde, so my question is are all the k packages for kde? Alot of them are obvious, but kconfig-5.88.0 - don't want to accidently not install new current kernel or system packages. Is there a way to exclude kde pkgs in writing #slackpkg install-new or would it go in slackpkg blacklist
Hmmm think using the command #slackpkg upgrade-all will exclude everything I haven't installed. Is that right? Will give kde a whirl off a live usb sometime.
Distribution: Slackware64 {15.0,-current}, FreeBSD, stuff on QEMU
Posts: 451
Rep:
Quote:
Originally Posted by NightSky
my question is are all the k packages for kde? Alot of them are obvious, but kconfig-5.88.0 - don't want to accidently not install new current kernel or system packages. Is there a way to exclude kde pkgs in writing #slackpkg install-new or would it go in slackpkg blacklist
Hmmm think using the command #slackpkg upgrade-all will exclude everything I haven't installed. Is that right? Will give kde a whirl off a live usb sometime.
Yes, upgrade-all will only operate on currently-installed packages.
Some non-KDE packages start with k, and some KDE packages don't (baloo, for instance). The most convenient way to handle something like this is listing the kde series in /etc/slackpkg/blacklist (instead of trying to use regex):
Code:
kde/
One caution is that if there happen to be packages from kde already on the system, blacklisting the series means that slackpkg won't be able to find them. Running "#slackpkg remove kde" beforehand might be a good idea if you'd rather leave out KDE altogether.
Upgrading Slackware64 RC1 Kernel 5.15.2
#slackpkg install-new And here is the question, in the resulting list there is alot 5.88of kde packages I readily recognize, but I don't run xfce not kde, so my question is are all the k packages for kde? Alot of them are obvious, but kconfig-5.88.0 - don't want to accidently not install new current kernel or system packages. Is there a way to exclude kde pkgs in writing #slackpkg install-new or would it go in slackpkg blacklist
Hmmm think using the command #slackpkg upgrade-all will exclude everything I haven't installed. Is that right? Will give kde a whirl off a live usb sometime.
* I usually do a upgrade-all twice:
1. glibc-*, tar & bash
2. all but kernel
* then i install the new kernel in parallele and make the initrd and see it actually boots (it does if i don't bork out somethng)
* then only i run an install-new and seep thru the (huge) list checking packages that are not part of kde and kde-i as i quit KDE (i know sounds like i've quit smoking (tho oddly it feels like i just did )) - there are usually few to pick out
TL;DR:
a task not well suited for busy days, but people manage if careful enough
I have uploaded packages for VLC 3.0.16. I have not been paying much attention to VideoLAN development in 2021, as I was busy enough with other stuff and my VLC player did everything it needed to. But it was time (after 11 months) to come with a new set of packages for Slackware.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.