Yet another testimonial tangent... and I think it is cool and good that so many have chimed in, it is encouragement for the smouldering slackers among us!

I quit smoking in May or June 1983, and my wife quit on Christmas the following year (we were not married at the time). She has tracked what we have not spent on tobacco products since and announces it each year on Christmas - last Christmas it was an astounding $750,000! That does not include health effects - we are both in very good health, whereas smoking friends and family from that time are _all_ dead or have severe health problems... and none of our children became smokers.

Booze has never been a problem for either of us and we do not normally keep any in the house, but are able to enjoy a glass when it is available. I have a taste for Scotch and Kentucky Bourbons but have not had any in the house for several years. A friend gifted me two bottles of single malts for my birthday last November which have been very nice, but will not be replaced when empty.

For those still supporting an addiction to either, I encourage you to quit and enjoy life instead! Good luck to all!

I'm looking forward to installing 15 on a Netcup server I have -- which has been waiting patiently for a few months now!



Still waiting for official SBo support for 15 though.

Another spanner in the works is Eric's new series on a Slackware Cloud platform, which has prompted me to re-think my hostility to containers, or at least Docker.

i'm a big fan of the isolation you get with NetBSD Xen and FreeBSD Jails, but if Eric the Nuclear Dutch comes up with a secure Docker and Cloud setup, who am I to argue?

2 members found this post helpful.

Same. I'm happily maintaining two installations of Slackware64-15.0, and one installation of Slackware64-current. When the SBO repository for 15.0 goes live I have packages I want to install. Fun!

2 members found this post helpful.

I have three linux installs at present.

• Brand spanking new Slackware64-15.0 with only the bare minimum of changes.
• My 6 year old Slackware64 install that's been following current, but is parked at the 15.0 point.
• My CRUX 3.6 Install, for when I feel the need to get back to the basics.

I'm currently using my new 15.0 install to explore KDE, which I haven't checked out for a very long time. Well, actually, I'm over on CRUX right at this minute waiting for WINE 7.2 to build, but I was exploring KDE on Slackware a little earlier this evening.

Really not sure what happens next, but i'm not updating my current box until all this xkb stuff is settled.

2 members found this post helpful.

Installed Slackware in a 12 years laptop.
Repartition then my main box.
Install Slackware.
Celebrating with music.
Copying patiently my data.

Ι came to Linux 12 years ago, after my 30s. Prior to that, i couldn' afford to buy my own computer. For the first two years i was distrohopping a lot. Main stops were Mint, Debian, Archbang, Arch, Debian again, to name a few. The most stable distro of all, was Salix. To be honest, i always had an itch during that time, to try Slackware. My first attempt was, if i cam recall right, the 13.1. No great success i have to addmit. With 13.37. somewhere in 2012 or 2013, i had more success, found my way, dual booting it and, when 14.0 came out, it became my main and only os.
Eventually, my most productive computing time was spent with Slackware. About a year ago, i left it, tried other distros till i ended up with Devuan. When 15.0 released, my automatic reaction was to download the iso. And know, Slackware sits alone in my main box, i surprised of my joy and my relief and of how happy i am for this, everything seems familiar and new, once you go slack etc

4 members found this post helpful.

Finally back on Slackware (15), looks good

Installed on Lenovo Legion Pro (dual boot with Windows for work reason).
NVIDIA drivers are up and running too.

Haven't used KDE in a very long time and it's an amazing whole week as my main DE.

Feels like home again after 8 years of MacOS (company issued lol).

Yes, same here. It's very impressive, though I've stumbled across a number of minor bugs/annoyances, and my fvwm setup is far snappier in use, but that's to be expected.

I put the panel on the right-hand side and I am pinning things to the icon-only task-manager to kind of get a WindowMaker feel to it.

I'm still exploring KDE: lots of stuff to like, but finding annoyances and disappointments as I do.

1. Pinning konqueror to the task manager didn't work and I had to# cp /usr/share/application/konqbrowser.desktop ~/.local/share/applications/org.kde.konqueror.desktop in order to fix that.
2. I didn't like how the dolphin sidebar "devices" section was populated with things like my lvm pv which really had no place being there — though at least there was the option to hide them.
3. My EFI partition showed up twice in the 'storage' page in system-settings: once as /dev/sda1 and once again as LABEL=SYSTEM, which was odd.
4. /proc also showed up on the 'storage' display, which doesn't make a lot of sense either.
5. I really liked elisa for playing music, except it doesn't support gapless playback, and many of my most played albums have tracks that run into each other. The "show in folder" button at the bottom of the screen doesn't work either, but that's far less important (the show folder on the playlist entries does work — go figure). The lack of gapless was a major disappointment as I would have loved to be able to keep using it.

I tried the wayland sessions too, but found them far to buggy to use, so will be sticking with plasma-x11.

Well, ran into my 1st incompatibility on the machine running slackware64-current.

The upgrade to gftp-2.9.0b-x86_64-1.txz sent the command of 'EPSV' to the slackware64-15.0
machines that are running an older version of pure-ftpd that does not understand 'EPSV'
but rather only 'PASV'.

Looking into it I find that....

"The main difference is that EPSV and Extended Passive Mode are primarily designed
to accommodate both IPV4 and IPV6 addresses, while the older PASV command and
Passive Mode could only support IPV4."

Since my systems only use IPV4, and this older version of pure-ftpd works just fine
for transfers between the machines on my LAN (which is all it's ever used for),
will not bother upgrading to a newer pure-ftpd that supports 'EPSV' and have now
reverted back to gftp-2.8.0b-x86_64-1.txz from the slackware64-15.0 repository.
________________________________________________________________________________________

Ah ha... fixed it.

pure-ftpd was using the -b "BrokenClientsCompatibility" option which disabled EPSV capability.
__________________________________________________________________________________________________

Also discovered that upon 1st use after upgrading to gftp v2.9.0b one must go into 'preferences -> network
and choose either IPV4 or IPV6 which is blank to start with.

With it blank, gftp crashed and exited the instant a connection to a server was attempted.
____________________________________________________________________________________________________ _______

Well, I'm reverted back to v2.8.0b again.

Still had a few crashes and failed file transfers.

And I'm not the only one having issues with v2.9.0b

https://github.com/masneyb/gftp/issues/144

I probably should have answered the topic question in the midst of my answers (see posts #195 and #198), sorry about that.

I plan on sticking with 15.0-stable, as it has all the software I need, and also I am a wee bit concerned with all the writes to my SSD/NVMe disks that -current has necessitated over the past few years, culminating in the replacement of my SSD (no problem with my NVMe disks yet; I plan on keeping it that way for as long as possible).

The only updates to -stable, as far as I know, are security updates; these I can peruse at my leisure, and apply them as I see need. This will drastically reduce the number of writes to my disks, and thereby prolong my system's life.

Happy Slacking!

I'm switching my machines from 14.2 to 15.0 As soon as sbo is open I'll get qemu rebuilt, and create 15.0 32 and 64bit vms for slackbuilds. everything waiting on sbo at the moment. Then I can update my own slackbuilds.

1 members found this post helpful.

So, a new billing period and the final current -> 15.0 update. Now I really have Slackware-15. Just for my own interest, I did another slackpkg update/upgrade-all to see what was in the pipeline since release and found about 5 packages, more or less what I'd expect from a normal Slackware update.

I really hate the new virtual console! Not only does it not scroll (I've become reconciled to that) but I have now discovered that it doesn't show a cursor when you use the back arrow key to correct. So you can't actually do any corrections because you don't know where you are on the line. What kind of idiot thought that was a good idea?

Remember when Gates Bill announced the end of command line in the wake of Windows XP?

Today, I imagine, there is a generation grown up programming in Visual Studio instead of in command-line environment...

Those might tend to imagine that themeing is more important than basic functionality, and could argue that, as long as one has a serial line for debugging doesn't really matter how the tty behaves if at all.

But then, where are the veterans around them, there must be some. And that makes me wonder - is there in the mainstream just anyone, anyone left any more using the damn tty?

Ever?

Is the dying out process finished and we're the last ones left?

Is there a pilot left on the plane?

Cursor visibility can be turned off/on with escape sequences. Try a printf "\e[?25h" which should turn it on. Swap the 'h' for an 'l' to turn it off. You might also want to fire up dash instead of bash to make sure it's not 'readline' doing something silly.

Oddly enough tty2 has a cursor. I just tested it. I'll have to try tty1 again next time I boot up. It could be something to do with it having previously been the system console.

Apparently you can also turn the cursor on and off with setterm --cursor on/off.

UPDATE: I know what's wrong now. The display is not exactly sized to my screen. The lowest line is slightly too low for the cursor to be visible. And because this was previously the system console and shows all the startup messages, the lowest line is the current one for typing. I need to give a clear command if I want to type anything more complicated than "startx".

Great ... :/
Thanks UPS