So you want to be a Slacker! What do I do next?

onebuck · 06-02-2023, 12:32 PM

Hi,

Eric (alienbob) just released; Chromium 114 Early Release on Slackware

Quote:

Posted on May 27, 2023 by alienbob

An “early release” of Chromium 114 source code was published a few days ago, the release notes are on the developer blog. Since Chromium 110, Google rolls out new major releases to a small sub-set of its users to monitor any potential breakage and apply fixes before the majority of users get upgraded. The formal release of Chromium will be on May 30th, but I decided to go along with the early release this time, and offer this version to Slackware users already this weekend, to celebrate the Pentecost

Looking at the new stuff in Chromium 114, there’s two things you might want to play with, since they are already contained in the browser and mostly usable in Chromium 114, but not yet enabled by default.

By toggling the flag “chrome://flags/#chrome-refresh-2023” from “default” to “enabled” the ongoing work will be revealed to bring a new User Interface design (Material You) to the desktop browser. A new tab design, new icons and work on the dark theme is visible. This new UI is scheduled for release in September 2023.
The toggle “chrome://flags/#password-manager-redesign” will enable a revamped Google Password Manager. It wants to look more like a standalone application and Chromium will ask you if you want to “install the app” which basically just adds a shortcut to “chrome://password-manager/passwords” in the “three-dots” sidebar menu. I was not yet impressed with this one, as it was unable to show me the passwords I had already saved in Chromium before. Yet is was obvious that my passwords were present since the password manager was able to check them all for compromise and weakness. So, I toggled this one back to “default” and will wait for Google to mature and stabilize it.
Also obvious is the disappearance of the “lock” icon which was an indication that you were visiting a secure “https” site. The lock has been replaced by a settings icon but functionally nothing much changed, as is shown when you click that icon.
Slackware packages (15.0 and -current) for Chromium 114.0.5735.45 are available for download from my repository or any of its mirrors.
The Un-googled version of my Chromium browser package will probably have to wait until May 30th – the formal release date of Chromium 114. There is no sign that Eloston will release a tarball sooner.
Enjoy! Eric

Hope this helps!

onebuck · 06-20-2023, 10:40 AM

Hi,
alienbob has been busy of late;

Quote:

Chromium 114.0.5735.133 packages address critical bug
Posted on June 17, 2023 by alienbob

Chromium, regular and un-googled.
Earlier this week, Google released its 114.0.5735.133 update for Chromium 114.
This is a bugfix release and on the list of addressed security issues, there’s one which is labeled as ‘critical‘, labeled CVE-2023-3214. Three other fixes are labeled with a vulnerability rating of ‘high‘.
As always, it is wise to upgrade to my latest chromium and chromium-ungoogled packages.
The updated Slackware 15.0 and -current packages both for chromium and chromium-ungoogled are available in my repository and its mirrors (like my own US server and in a short while, the UK mirror).
Cheers, Eric

Hope this helps.

onebuck · 06-26-2024, 09:06 AM

Hi,

I frequently use 'mirror-slackware-current.sh' and is still the best way to get your '-current' ISO. Be sure to check your md5sum for the burnt ISO image since the download md5sum is already done for you.

Hope this helps!

r1w1s1 · 06-26-2024, 09:30 PM

Quote:

Originally Posted by onebuck

Hi,

I frequently use 'mirror-slackware-current.sh' and is still the best way to get your '-current' ISO. Be sure to check your md5sum for the burnt ISO image since the download md5sum is already done for you.

Hope this helps!

The best way

my slackpkg running better using local mirror

for sure.

onebuck · 08-29-2024, 12:27 PM

Hi,

I know that this information has been posted before but lately a lot of queries of late could be answered by looking at the informational files available to users.

Code:

ls  /yourISO/mntPoint/slackware/slackware64-15.0/*  

/mnt/sdc2/slackware/slackware64-15.0/ANNOUNCE.15.0          /mnt/sdc2/slackware/slackware64-15.0/README.TXT 
/mnt/sdc2/slackware/slackware64-15.0/CHANGES_AND_HINTS.TXT  /mnt/sdc2/slackware/slackware64-15.0/README.initrd 
/mnt/sdc2/slackware/slackware64-15.0/CHECKSUMS.md5          /mnt/sdc2/slackware/slackware64-15.0/README_CRYPT.TXT 
/mnt/sdc2/slackware/slackware64-15.0/CHECKSUMS.md5.asc      /mnt/sdc2/slackware/slackware64-15.0/README_LVM.TXT 
/mnt/sdc2/slackware/slackware64-15.0/COPYING                /mnt/sdc2/slackware/slackware64-15.0/README_RAID.TXT 
/mnt/sdc2/slackware/slackware64-15.0/COPYING3               /mnt/sdc2/slackware/slackware64-15.0/README_UEFI.TXT 
/mnt/sdc2/slackware/slackware64-15.0/COPYRIGHT.TXT          /mnt/sdc2/slackware/slackware64-15.0/RELEASE_NOTES 
/mnt/sdc2/slackware/slackware64-15.0/CRYPTO_NOTICE.TXT      /mnt/sdc2/slackware/slackware64-15.0/SPEAKUP_DOCS.TXT 
/mnt/sdc2/slackware/slackware64-15.0/ChangeLog.txt          /mnt/sdc2/slackware/slackware64-15.0/SPEAK_INSTALL.TXT 
/mnt/sdc2/slackware/slackware64-15.0/FILELIST.TXT           /mnt/sdc2/slackware/slackware64-15.0/Slackware-HOWTO 
/mnt/sdc2/slackware/slackware64-15.0/GPG-KEY                /mnt/sdc2/slackware/slackware64-15.0/UPGRADE.TXT 
/mnt/sdc2/slackware/slackware64-15.0/PACKAGES.TXT

Hope this helps!

flipchip · 09-10-2024, 10:03 PM

Quote:

Originally Posted by alan_ri

That's a really nice thing that you're doing onebuck and I think that it would be good if this thread becomes sticky.

I agree with this assertion as there where several points in the early days of my use of Linux one of the main things that kept me away from distributions Like Slack Ware was the perception that Slack Ware was a "newbie unfriendly" distribution. So owing to this I opted to go decided to dabbled with Debain and quite a few other similar Distributions such as CentOS.

protozoaire · 09-17-2024, 11:35 AM

To add to (onebuck 2024-08-29T17:27, Important Slackware64 -15.0 information available to users!),
to have these howtos installing Slackware PRIOR to having the ISO mounted, these are, for example
from excellent slacware.uk (timestamps later than release, is patched slackware 15.0):

Code:

rsync --relative --no-motd rsync://slackware.uk/slackware/./slackware64-15.0/ # 2024-09-16T12:30Z

drwxr-xr-x          4,096 2024/09/16 20:02:21 slackware64-15.0
-rw-r--r--          5,767 2022/02/02 22:44:45 slackware64-15.0/ANNOUNCE.15.0
-rw-r--r--         16,609 2022/03/30 19:03:58 slackware64-15.0/CHANGES_AND_HINTS.TXT
-rw-r--r--      1,256,508 2024/09/16 20:02:21 slackware64-15.0/CHECKSUMS.md5
-rw-r--r--            195 2024/09/16 20:02:21 slackware64-15.0/CHECKSUMS.md5.asc
-rw-r--r--         17,976 1994/06/10 02:28:08 slackware64-15.0/COPYING
-rw-r--r--         35,147 2007/06/30 04:21:00 slackware64-15.0/COPYING3
-rw-r--r--         19,573 2016/06/23 20:08:55 slackware64-15.0/COPYRIGHT.TXT
-rw-r--r--            616 2006/10/02 04:37:30 slackware64-15.0/CRYPTO_NOTICE.TXT
-rw-r--r--      2,159,572 2024/09/16 19:58:49 slackware64-15.0/ChangeLog.txt
-rw-r--r--      1,646,875 2024/09/16 20:01:56 slackware64-15.0/FILELIST.TXT
-rw-r--r--          1,572 2012/08/29 18:27:33 slackware64-15.0/GPG-KEY
-rw-r--r--        864,745 2022/02/02 08:25:12 slackware64-15.0/PACKAGES.TXT
-rw-r--r--          8,034 2022/02/02 03:36:30 slackware64-15.0/README.TXT
-rw-r--r--          3,635 2022/02/02 08:11:27 slackware64-15.0/README.initrd
-rw-r--r--         34,162 2022/01/30 20:35:44 slackware64-15.0/README_CRYPT.TXT
-rw-r--r--          8,754 2022/03/30 19:05:35 slackware64-15.0/README_LVM.TXT
-rw-r--r--         19,658 2013/06/18 04:34:43 slackware64-15.0/README_RAID.TXT
-rw-r--r--          7,928 2018/07/19 06:33:44 slackware64-15.0/README_UEFI.TXT
-rw-r--r--          7,613 2022/02/03 04:38:00 slackware64-15.0/RELEASE_NOTES
-rw-r--r--         13,855 2008/12/08 18:13:18 slackware64-15.0/SPEAKUP_DOCS.TXT
-rw-r--r--         17,294 2008/12/08 18:13:22 slackware64-15.0/SPEAK_INSTALL.TXT
-rw-r--r--         57,187 2022/02/01 19:37:50 slackware64-15.0/Slackware-HOWTO
-rw-r--r--          8,700 2022/01/26 05:44:38 slackware64-15.0/UPGRADE.TXT
drwxr-xr-x          4,096 2013/03/20 22:17:54 slackware64-15.0/EFI
drwxr-xr-x          4,096 2024/06/06 19:42:19 slackware64-15.0/extra
drwxr-xr-x          4,096 2022/02/02 08:21:36 slackware64-15.0/isolinux
drwxr-xr-x          4,096 2022/02/02 08:11:26 slackware64-15.0/kernels
drwxr-xr-x          4,096 2023/08/04 20:22:55 slackware64-15.0/pasture
drwxr-xr-x          4,096 2024/09/16 20:01:56 slackware64-15.0/patches
drwxr-xr-x          4,096 2022/02/02 08:25:18 slackware64-15.0/slackware64
drwxr-xr-x          4,096 2023/06/29 19:39:21 slackware64-15.0/source
drwxr-xr-x          4,096 2024/09/06 19:25:54 slackware64-15.0/testing
drwxr-xr-x          4,096 2022/02/02 08:21:41 slackware64-15.0/usb-and-pxe-installers

Similar for slacwkare-current

Code:

rsync --relative --no-motd rsync://slackware.uk/slackware/./slackware64-current/

BigDumbDinosaur · 12-30-2024, 01:54 AM

After some 20 years of using various SuSE distributions on my company’s server builds, I decided it was time to look at other distros. The impetus for doing so was the result of the switch by SuSE from SYSV init to systemd. With each release, systemd got more and more obnoxious and obstructive. systemd enthusiasts go on and on about how it centralizes control...which is exactly what is wrong with it. That piece of ill-conceived software thinks it’s smarter than the person administering the server, which is wrong-headed design. Being a UNIX knuckle-dragger from the 1980s, I don’t want Microsoft thinking infesting my Linux installations.

Enough ranting...I’ve experienced one too many wrestling matches with systemd and want to get back to where I could control all aspects of a server’s startup and shutdown. Slackware is one of the few mature distros that doesn’t use systemd—so here I am.

Setting up Slackware has presented a few challenges, mostly because years of using SuSE distros that had SYSV init meant I needed to learn the BSD style of init. Files are in different places, the rc... stuff is different, etc.. Configuration reminds me of the days of SCO UNIX 3.2.

However, I’ve got Slackware running on one of my “mule” servers (powered by an older, single-core Opteron MPU, and with parallel SCSI), and so far, so good. BTW, I really wanted to use GRUB as the boot loader, but that wasn’t an installation option. Nothing against LILO—it’s just that I’m accustomed to GRUB.

With any luck, I won’t need to post any queries here for help, but if I do, it will only happen after a really deep dive onto whatever the problem is that I can’t resolve.

—Bill

—————————
EDIT: Fixed a typo.

hazel · 12-30-2024, 12:08 PM

Quote:

Originally Posted by BigDumbDinosaur

After some 20 years of using various SuSE distributions on my company’s server builds, I decided it was time to look at other distros. The impetus for doing so was the result of the switch by SuSE from SYSV init to systemd. With each release, systemd got more and more obnoxious and obstructive. systemd enthusiasts go on and on about how it centralizes control...which is exactly what is wrong with it. That piece of ill-conceived software thinks its smarter than the person administering the server, which is wrong-headed design. Being a UNIX knuckle-dragger from the 1980s, I don’t want Microsoft thinking infesting my Linux installations.

Yes, that's how a lot of us feel.

Quote:

BTW, I really wanted to use GRUB as the boot loader, but that wasn’t an installation option. Nothing against LILO—it’s just that I’m accustomed to GRUB.

Slackware-15 has both GRUB and LILO (also ELILO for a LILO-like UEFI boot). Just use slackpkg to install what you need.

business_kid · 12-30-2024, 12:53 PM

In case someone hasn't already said it BigDumbDinosaur, Welcome to LQ.

So you're a knuckle-dragger from the '80s, eh? I thought you'd have learned to keep your knuckles out of the way, because I always found it sore whenI dragged my knuckles. Hitting them was equally painful.

You chose well. Now learn Slackware's oddities fast. Become aware of all the repositories of ready built software and of slackbuilds (slackbuilds.org). There's Alien Bob's stuff on slackware.nl, and utilities like slackpkg, slackpkg+, & sbopkg that you should master look forward to you helping us out when we fall over our shoelaces - thinking of myself in particular

.

onebuck · 12-30-2024, 02:45 PM

Hi,

Welcome to LQ & Slackware BigDumbDinosaur!
My signature does have these links as some good reference points;

Quote:

Slackware®-Links | Slackware Doc Project | Slackware® Home
Slackware® Essentials | Slackware Basics | How to Ask Questions the Smart Way

You might like to follow Alien Bob's blog at; https://alien.slackbook.org/blog

You can find a lot of his Slackware stuff at; My slackstuff

His blog has a lot of useful links you will find beneficial.

Alien Bob has been a major Slackware contributor for years.

Of late I come from Academia and used UNIX for years along with a lot of AT&T equipment. Glad to get away from Sun and the University Apple environment. Heck, we had so much Microsoft that most still cling too.

My Dec experience opened a lot of doors for me but was glad to move from Dec.
Plus IBM boring main frame work was torture at times. BAL, RPG and Cobol were a pain at times. I never really cared for unit records dept since that would always delay things. We were lucky if our decks would process in a few days or even a week, depending on priority. Now that was a while back for me. Talk about dragging knuckles, we still had to use punch cards that I would bonus/bribe the operators to punch then to get my decks through, sometimes that would cause some resentment from colleagues thus pushing my decks in limbo sometimes. One reason to move from software into hardware for a period to gain back some sanity.

Then Mag came along which could be problems at times. I can remember my first experience with SMD disk storage, it was fragile and systematic glitches. Head crashes were always a pain and very expensive. I was maintaining hardware at that time. Pressure to get things back online with Supervisor(s) hanging around trying to push. It got where it was labor to get around in the clean room. Finally I was given the latitude to ask them to leave or I just had to call the boss to get them out. Production pressure was hard on everyone but local pressure did not help to get things done any faster.

Hope you enjoy your Slackware experience(s)!

Hope this helps!

BigDumbDinosaur · 12-30-2024, 11:49 PM

Quote:

Originally Posted by business_kid

In case someone hasn't already said it BigDumbDinosaur, Welcome to LQ.

Thanks!

Quote:

Now learn Slackware's oddities fast.

An apparent oddity is the scripts that bring up the networking seem to think no one will ever want to assign more than one IP address to a particular NIC. I have a client with a server that has three IP address assigned to the WAN-facing NIC—each address different, but all on the same subnet. It’s complicated and has to do with their telephone system.

I’m trying to duplicate that setup with Slackware, but not making progress. Nor have I found anything on this forum that addresses

such an arrangement.

Quote:

Become aware of all the repositories of ready built software and of slackbuilds (slackbuilds.org). There's Alien Bob's stuff on slackware.nl, and utilities like slackpkg, slackpkg+, & sbopkg that you should master

I’m ahead of you on that...I’ve already checked them out.

Quote:

look forward to you helping us out when we fall over our shoelaces - thinking of myself in particular

.

Not sure how much help I’ll be. Virtually all of my usable Linux experience has been with various SuSE distros, which are, in many ways, different than Slackware, especially in how services are controlled and how basic system configuration is handled.

My main concern with replacing SuSE with Slackware is the difficulty in administering the latter for anyone who is not familiar with working at the shell prompt and hand-editing .conf files. At least in SuSE, a layperson can do most of the administration with YAST, which can be run in curses mode (i.e., from the BASH prompt), or if a GUI is running, from a desktop working with those cute little zoogies (aka icons) that were invented at Xerox around the time Jimmy Carter became US president.

So, for now, the jury is out on whether Slackware will displace SuSE in our server builds. I have no problems working with it from the BASH prompt, but my technical qualifications are a bit more robust than the lawyers and insurance agents who make up much of my client pool.

In their case, if there isn’t a mouse and a colorful screen full of zoogies, it’s way too complicated.

astrogeek · 12-31-2024, 02:08 AM

Another hearty "Welcome"! Welcome to Slackware and to LQ!

Quote:

Originally Posted by BigDumbDinosaur

An apparent oddity is the scripts that bring up the networking seem to think no one will ever want to assign more than one IP address to a particular NIC. I have a client with a server that has three IP address assigned to the WAN-facing NIC—each address different, but all on the same subnet. It’s complicated and has to do with their telephone system.

I’m trying to duplicate that setup with Slackware, but not making progress. Nor have I found anything on this forum that addresses

such an arrangement.d

Read the notes at bottom of /etc/rc.d/rc.inet1.conf as a good place to start.

That said, as I recall I had to more or less figure it out on my own, but without any great difficulty.

You can assign multiple addresses to a single interface at startup by simply specifying a space separated list of addresses to the interface in /etc/rc.d/rc.inet1.conf, for example something like this:

Code:

# IPv4 config options for eth0:
IPADDRS[0]="192.168.0.87/24 192.168.17.33/24"
USE_DHCP[0]=""

... which will assign the above addresses to eth0 in this case. List them using the ip command:

Code:

# ip route
default via 192.168.0.254 dev eth0
127.0.0.0/8 dev lo scope link
192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.87
192.168.11.0/24 dev eth0 proto kernel scope link src 192.168.17.33

# ip address
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc htb state UP group default qlen 1000
    <snip>
    inet 192.168.0.87/24 brd 192.168.0.255 scope global eth0
       valid_lft forever preferred_lft forever
    inet 192.168.17.33/24 brd 192.168.17.255 scope global eth0
       valid_lft forever preferred_lft forever
    <snip>

Hope that helps!

Windu · 12-31-2024, 02:17 AM

Quote:

Originally Posted by astrogeek

You can assign multiple addresses to a single interface at startup by simply specifying a space separated list of addresses to the interface in /etc/rc.d/rc.inet1.conf, for example something like this:

Code:

# IPv4 config options for eth0:
IPADDRS[0]="192.168.0.87/24 192.168.17.33/24"
USE_DHCP[0]=""

You should also be able to use the IPALIASES[] array for that. Not documented in "man rc.inet1.conf" but you can see how it works inside of /etc/rc.d/rc.inet1

Pint · 02-05-2025, 03:33 PM

2025 New Slacker here!