LinuxQuestions.org
Latest LQ Deal: Latest LQ Deals
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


View Poll Results: What hardware do you run Slackware on?
Laptop 129 75.44%
Desktop 129 75.44%
Headless 56 32.75%
SBC (e.g. Raspberry Pi) 31 18.13%
Mainframe 3 1.75%
other 23 13.45%
Multiple Choice Poll. Voters: 171. You may not vote on this poll

Reply
  Search this Thread
Old 05-29-2021, 12:04 PM   #16
Gnisho
Member
 
Registered: Aug 2012
Location: Phoenix, AZ
Distribution: Slackware
Posts: 46

Rep: Reputation: Disabled

One desktop and one mini-pc (NUC).
 
Old 05-29-2021, 01:09 PM   #17
twy
Member
 
Registered: Jun 2004
Distribution: Slackware64
Posts: 56

Rep: Reputation: Disabled
I run slackware64 14.2 on server/workstation hardware. I suppose this is "desktop" since I use it as a desktop PC.

The hardware is old: Intel Xeon x3450 CPU, 8x1TB Western Digital RE/Gold enterprise disk drives in mdadm raid6\luks\lvm\ext4 (6TB usable) with plain raid1\ext4 boot partitions for lilo, LSI SAS1068E SAS/SATA host bus adapter flashed to IT (non-RAID) firmware, Asus P7F-E mainboard with 4x2GB=8GB registered ECC DDR3-1333.

I have been running this since early 2010, starting with slackware64 13.0, the first x86_64 release. All upgrades 13.0->...->14.2 have worked fine.

The complicated disk setup has worked fine also. I started out with 2x1TB in firmware raid1 on the SAS1068E with IR raid firmware. Then, I bought two more 1TB drives and made a 2x1TB mdadm raid5 (with raid1 boot partitions). I copied the firmware raid1 onto the raid5 and starting booting from the raid1+raid5. I left the old firmware raid1 alone as a backup. After a few months I was convinced that the mdadm raid1+raid5 worked well, so I deleted the firmware raid1 and added its 2x1TB drives into mdadm as spare disks. Using mdadm, I reshaped the raid5 into a 4x1TB raid6 using the spare disks. Not long after that, I bought 4 more 1TB RE disks and reshaped the 4x1TB raid6 into 8x1TB raid6. The details of all the commands were complicated, but everything worked well. Before growing, the write-intent bitmap has to be removed using mdadm. After growing the raids, write-intent bitmap can be re-added, LUKS has to be grown, LVM volume group and volumes have to be grown, and then ext4 has to be grown. Values for /proc/.../dirty_background_bytes and /sys/../stripe_cache_size had to be set for good performance. Also, blockdev --setra had to be set to good values. Using tune2fs -E extended options, stride and stripe_width had to be set correctly. So, it works, but it would be nice if it were simpler to setup. Maybe I am lucky, but I have not had a drive failure in about 7 years now. When I replaced a failed drive, it went smoothly. It helps to have the IBM tool called cfggen to look at the SAS1068E status (or use smartctl [just noticed that one of my disks has 1 reallocated sector count - not good]).

I hope the next computer that I build will be as good as this. It is working great. So reliable with slackware64.
 
Old 05-29-2021, 03:52 PM   #18
enorbet
Senior Member
 
Registered: Jun 2003
Location: Virginia
Distribution: Slackware = Main OpSys
Posts: 3,619

Rep: Reputation: 3492Reputation: 3492Reputation: 3492Reputation: 3492Reputation: 3492Reputation: 3492Reputation: 3492Reputation: 3492Reputation: 3492Reputation: 3492Reputation: 3492
Quote:
Originally Posted by KeithE View Post
Right now, Slackware 14.2 is only on one 2009-vintage 32-bit netbook and 64-bit 14.2 in a VirtualBox VM on a 2012-vintage Mac. It works well on both.

I have three 2017-and-later machines that will not boot a 4.x kernel, so 14.2 is out. I won't run 15.0 until it's released and there are Slackbuilds available for the software I need (mostly ham radio related). I've tried a couple of currents over the last year, and they were all wanting as far as stability was concerned.
Why not install a kernel from Current on 14.2? Presently Current has 5.10.41.

I am curious as to why a 4x kernel won't boot on any of your post 2017 PCs. This box was brand spanking new June 2020, a Z490 machine, and it boots 32 bit 14.2 with a 4.4.14 kernel as well as a 64 bit 14.2 which started out as 4.14.4 also. I spend most of my time in Current and really haven't had stability issues. The 32 bit install is still 4.14.4 but the 64 bit install is now 5.11.11 only because it needs a kernel that new to support Wifi 6.
 
Old 05-29-2021, 04:30 PM   #19
pocker
Member
 
Registered: Jan 2019
Posts: 31

Rep: Reputation: Disabled
well ....

desktop: AMD K6-2 400MHz (around 2003), AMD Athlon-XP 2000 (around 2005), AMD Sempron LE-1150 (around 2008) (this was my last desktop with Slackware)

laptop: Intel Core 2 duo (from 2009-2013) , Intel Core i3 3110m (in 2013 ... had a break from ~2014 up to this year ... returned to slackware in 2021 with -current)

it has been a nice journey

Last edited by pocker; 05-29-2021 at 04:37 PM.
 
Old 05-29-2021, 05:31 PM   #20
Tonus
Member
 
Registered: Jan 2007
Location: Paris, France
Distribution: Slackware-current
Posts: 923
Blog Entries: 3

Rep: Reputation: 250Reputation: 250Reputation: 250
Quote:
Originally Posted by colinh2 View Post
I tried installing Slackware on my wife. Didn't work. :-(
Just try again. Usually women are smarter than anything else.
 
Old 05-29-2021, 08:42 PM   #21
chrisretusn
Senior Member
 
Registered: Dec 2005
Location: Philippines
Distribution: Slackware64-current
Posts: 1,919

Rep: Reputation: 802Reputation: 802Reputation: 802Reputation: 802Reputation: 802Reputation: 802Reputation: 802
Quote:
Originally Posted by colinh2 View Post
I thought servers would be "headless" too :-)

I should have added "virtual machine" as an option, but I suppose those should be in "other" for this poll.

If there are other "other", a post explaining it would be nice.
I didn't even consider virtual machine as other until you defined it. I run my virtual machines from a desktop computer. There not daily use machines. I see them as part of the desktop.
 
Old 05-29-2021, 10:00 PM   #22
rkelsen
Senior Member
 
Registered: Sep 2004
Distribution: slackware
Posts: 2,936
Blog Entries: 3

Rep: Reputation: 1144Reputation: 1144Reputation: 1144Reputation: 1144Reputation: 1144Reputation: 1144Reputation: 1144Reputation: 1144Reputation: 1144
One desktop,
One headless box,
Two 'headless' VMs,
One laptop

4 of them provide infrastructure for my business, some of which is critical at this point in time (i.e. in lockdown!).
 
Old 05-29-2021, 10:32 PM   #23
KeithE
Member
 
Registered: Jan 2003
Location: Mesa, AZ
Distribution: Mint, Slackware
Posts: 131

Rep: Reputation: 26
Quote:
Originally Posted by enorbet View Post
Why not install a kernel from Current on 14.2? Presently Current has 5.10.41.
That would be great if the Slackware64-14.2 installation media were able to boot in the first place (and it does on other machines, so it's not the USB drive).

Quote:
I am curious as to why a 4x kernel won't boot on any of your post 2017 PCs. This box was brand spanking new June 2020, a Z490 machine, and it boots 32 bit 14.2 with a 4.4.14 kernel as well as a 64 bit 14.2 which started out as 4.14.4 also.
The machines in question are an HP Envy 360 laptop from 2017, a Lenovo ThinkCentre M900 (also from 2017, and both running Intel i5 processors), and a 2019 Minisforum "Mini-PC" with an Intel Celeron N3350 processor and 4 Gb RAM. None could boot the 14.2 USB, and are currently running Mint 20.1 (5.4.x kernel). I would have to guess that it's some peripheral hardware that's causing the bootup failure. I don't see why those processors wouldn't be supported. BTW, Mint 20.1 is getting closer to Slackware speed, but Slackware is still a better performer.

Quote:
I spend most of my time in Current and really haven't had stability issues. The 32 bit install is still 4.14.4 but the 64 bit install is now 5.11.11 only because it needs a kernel that new to support Wifi 6.
The stability issues included a complete failure in Wayland (X worked fine), locking up the kernel as a result, and issues with the 5.10 kernel in VirtualBox on my Mac. Yeah, I know the correct action when attempting to run Wayland is the response to the line "Doc, it hurts when I do this."

The last version of current I tried was downloaded about 6 months ago. I'm going to download the latest version and see how it does, but I'm concerned about whether or not Slackbuilds are available for the ham radio software I use. As far as I'm concerned, 14.2 is dead other than on the 32-bit netbook I use as a music player feeding a low power FM transmitter, but apparently (and by definition, since it has not yet been released for production) 15.0 isn't ready, either.
 
Old 05-29-2021, 10:46 PM   #24
karlmag
Member
 
Registered: Apr 2014
Distribution: Slackware
Posts: 108

Rep: Reputation: Disabled
Ok,

This is slightly confusing to be honest.

I don't want to criticize this poll too much, but both my first impression and after reading what other people have said, the words/expressions used in the poll seems to either not quite be what people think they are, or they are not defined well enough.

As a suggestion to future polls and pollers; Try to use words like laptop, which is pretty well-defined. The same goes for desktop (at least for the most part I would imagine - is a docked laptop that positively never leaves the dock a desktop? Yeah, if I'm a bit "difficult", that could be a question. ;-) ).

Headless? Well, that's not well-defined for most people. A laptop with a destroyed screen, but which does server functions because it otherwise still works (using an external monitor if needing console) would or could likely fall into a headless category.

I had the impression that several people miss the "server" category. I do so myself. While it *may* not be well-defined in all circumstances, it often is I believe.

Avoid using abbreviations, even if they seem logical (to you). I personally had to use a search engine to wrap my head around what "SBC" stood for, and that despite it having listed Rpi as an example. I do know that Rpi is a Single Board Computer, however. (Maybe I would have gotten it at a different time of day, I don't know.)

I guess Mainframe is one of the "If you don't right away know you have one, you don't have one." things. :-D

"Other" should maybe state "Please specify in a post." or some such.

Also - as other also mentioned; a category "virtual machines" might be useful to have these days.


Some ambiguity in the above *may* be resolved if people remember that the question is "which hardware", as opposed to "which role does machines have". Most hardware is sold as a specific type, even though sometimes it may not be 100% clear-cut anyway (e.g a server-motherboard put into a desktop case and actually used as a desktop). It's may be easy to mix up hardware type vs role while enthusiastically going into answering the poll even though (in this case) it is stated in the poll.

Polls (and the like) are difficult to do right and I hope I never really have to set up one for real.


I guess that was a couple of cents and maybe a bit extra change from me...

Thanks
--
KarlMag
 
Old 05-30-2021, 03:22 AM   #25
enorbet
Senior Member
 
Registered: Jun 2003
Location: Virginia
Distribution: Slackware = Main OpSys
Posts: 3,619

Rep: Reputation: 3492Reputation: 3492Reputation: 3492Reputation: 3492Reputation: 3492Reputation: 3492Reputation: 3492Reputation: 3492Reputation: 3492Reputation: 3492Reputation: 3492
Quote:
Originally Posted by KeithE View Post
That would be great if the Slackware64-14.2 installation media were able to boot in the first place (and it does on other machines, so it's not the USB drive).
Just extract the iso, replace the kernel files, and rebuild the iso.

Quote:
Originally Posted by KeithE View Post
The last version of current I tried was downloaded about 6 months ago. I'm going to download the latest version and see how it does, but I'm concerned about whether or not Slackbuilds are available for the ham radio software I use. As far as I'm concerned, 14.2 is dead other than on the 32-bit netbook I use as a music player feeding a low power FM transmitter, but apparently (and by definition, since it has not yet been released for production) 15.0 isn't ready, either.
The flaws in Current are minimal and minor and most Slackbuilds build on it but I can't speculate on your Ham Radio stuff, but if it won't build for you the kernel transplant will work a treat.
 
Old 05-30-2021, 07:58 AM   #26
andygoth
Member
 
Registered: Sep 2017
Distribution: Slackware
Posts: 130

Rep: Reputation: 62
Quote:
Originally Posted by enorbet View Post
Just extract the iso, replace the kernel files, and rebuild the iso.
You'll need to update the initrd in the installer. This post might be helpful.
 
Old 05-30-2021, 11:35 AM   #27
bassmadrigal
LQ Guru
 
Registered: Nov 2003
Location: West Jordan, UT, USA
Distribution: Slackware
Posts: 8,263

Rep: Reputation: 5853Reputation: 5853Reputation: 5853Reputation: 5853Reputation: 5853Reputation: 5853Reputation: 5853Reputation: 5853Reputation: 5853Reputation: 5853Reputation: 5853
Quote:
Originally Posted by andygoth View Post
Quote:
Originally Posted by enorbet View Post
Quote:
Originally Posted by KeithE View Post
That would be great if the Slackware64-14.2 installation media were able to boot in the first place (and it does on other machines, so it's not the USB drive).
Just extract the iso, replace the kernel files, and rebuild the iso.
You'll need to update the initrd in the installer. This post might be helpful.
It is much, much easier to just boot off a -current installation media (you could even use the usbboot.img) and then simply point the installer to a 14.2 package archive (I had it saved to a folder on my computer and just ensured it was mounted prior to starting the install so I didn't need to deal with two different thumbdrives, one with 14.2 and one with -current). Once the install finishes, before you reboot, upgrade your kernel packages to the ones from -current and update your bootloader.

You'll now be running 14.2 with the kernels from -current.

Actually, if you keep the 14.2 archive on your computer's drive and mount it before the install, you could simply replace the kernel packages of 14.2 with the ones from -current before you start the install and then you won't need to worry about upgrading them later nor dealing with your bootloader.
 
Old 05-30-2021, 12:50 PM   #28
colinh2
Member
 
Registered: Dec 2015
Posts: 35

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by karlmag View Post
Ok,

This is slightly confusing to be honest.

I don't want to criticize this poll too much, but both my first impression and after reading what other people have said, the words/expressions used in the poll seems to either not quite be what people think they are, or they are not defined well enough.

...

Fair enough. It'd probably be quite hard to create a "perfect" set of options for this question. For "headless" I was thinking of space on a server in a datacenter. But that could well be a "virtual machine"... And a laptop generally has a single board... And if you're running in a VM would you say the hardware was laptop/desktop/server...? And some people call a laptop a notebook.

I'm disappointed that more people don't have their own mainframe. And that no-one misses Minicomputer (e.g. VAX) :-)

So, maybe it should have been

Laptop
Desktop
Server (ie. remote access)
SBC (e.g. Raspberry Pi)
VM (virtual machine, on your local hardware)

?

To be honest, I just wanted to see how many people use laptops (presumably with WLAN).
 
Old 05-30-2021, 02:00 PM   #29
hitest
Guru
 
Registered: Mar 2004
Location: Prince Rupert, B.C., Canada
Posts: 6,671

Rep: Reputation: 2920Reputation: 2920Reputation: 2920Reputation: 2920Reputation: 2920Reputation: 2920Reputation: 2920Reputation: 2920Reputation: 2920Reputation: 2920Reputation: 2920
Installed Slackware64-current on my trusty old T410 Thinkpad.
 
Old 05-30-2021, 03:06 PM   #30
KeithE
Member
 
Registered: Jan 2003
Location: Mesa, AZ
Distribution: Mint, Slackware
Posts: 131

Rep: Reputation: 26
Quote:
Originally Posted by bassmadrigal View Post
It is much, much easier to just boot off a -current installation media (you could even use the usbboot.img) and then simply point the installer to a 14.2 package archive (I had it saved to a folder on my computer and just ensured it was mounted prior to starting the install so I didn't need to deal with two different thumbdrives, one with 14.2 and one with -current). Once the install finishes, before you reboot, upgrade your kernel packages to the ones from -current and update your bootloader.

You'll now be running 14.2 with the kernels from -current.

Actually, if you keep the 14.2 archive on your computer's drive and mount it before the install, you could simply replace the kernel packages of 14.2 with the ones from -current before you start the install and then you won't need to worry about upgrading them later nor dealing with your bootloader.
Thanks for all the good advice guys, but doing all that is far more trouble than it's worth. I downloaded the latest -current ISO last night, and will try it out. 14.2 is just too old to be of practical use to me anymore. Not just because of the 4.4 kernel that won't boot on some machines, but the ancient glibc 2.23 that is also giving me a few fits, notably with some Firefox add-ons.
 
  


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
Poll: (Without the poll) - How is Linux used in your workplace? SlowCoder General 13 09-11-2007 11:03 PM
C programming style (sort of a poll) elmafiacs Programming 9 08-31-2004 05:03 AM
Weekly Hardware Poll, January 12th: How fast do you push data? finegan Linux - Hardware 4 02-05-2004 08:16 PM
Weekly Hardware Poll, January 5th: What Chip are you buying next. finegan Linux - Hardware 5 01-12-2004 07:08 AM

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

All times are GMT -5. The time now is 12:43 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
Open Source Consulting | Domain Registration