Requests for -current (14.2-->15.0)

Skaendo · 09-30-2019, 07:26 PM

Quote:

Originally Posted by igadoter

If I remember well smp are for processors with hyper-threading.

Turns out we are actually both right:

Quote:

Symmetric multiprocessing (SMP) involves a multiprocessor computer hardware and software architecture where two or more identical processors are connected to a single, shared main memory, have full access to all input and output devices, and are controlled by a single operating system instance that treats all processors equally, reserving none for special purposes. Most multiprocessor systems today use an SMP architecture. In the case of multi-core processors, the SMP architecture applies to the cores, treating them as separate processors.

https://en.wikipedia.org/wiki/Symmetric_multiprocessing

But it doesn't matter because like you said, "In -current 64 bit there is no diversity between smp and non-smp."

Jeebizz · 09-30-2019, 08:07 PM

Since the Linux kernel is now at a RC for 5.4, what are the chances that it goes LTS, and I wonder if Slackware wills stay on 4.19 or jump to the 5.x series?

Ser Olmy · 09-30-2019, 08:13 PM

Quote:

Originally Posted by Jeebizz

Since the Linux kernel is now at a RC for 5.4, what are the chances that it goes LTS,

Pretty good, as Greg Kroah-Hartman is on record saying he tends to let the last kernel release of the year become the next LTS.

cwizardone · 09-30-2019, 08:59 PM

Quote:

Originally Posted by Jeebizz

Since the Linux kernel is now at a RC for 5.4, what are the chances that it goes LTS, and I wonder if Slackware wills stay on 4.19 or jump to the 5.x series?

As a couple of board members have pointed out in the kernel thread,
https://www.kernel.org/category/releases.html

Jeebizz · 09-30-2019, 09:41 PM

Quote:

Originally Posted by cwizardone

Quote:

Originally Posted by Jeebizz

Since the Linux kernel is now at a RC for 5.4, what are the chances that it goes LTS, and I wonder if Slackware wills stay on 4.19 or jump to the 5.x series?

As a couple of board members have pointed out in the kernel thread,
https://www.kernel.org/category/releases.html

Well by that chart, perhaps Slackware should jump to 5.4 if we do not see a RC1 yet of current Slackware with 4.19, but thats just my crappy opinion

.

franzen · 10-01-2019, 09:18 AM

Quote:

Originally Posted by volkerdi

Wow, thanks very much for the hint on \+! I'd remembered find being a lot more snappy back in the 90s (oddly enough, since the equipment was slower). I've gone ahead and changed every find -exec in the build scripts that can handle a long list of args to use \+ instead.

While you are on it, what about changing

Code:

find . \
  \( -perm 777 -o -perm 775 -o -perm 750 -o -perm 711 -o -perm 555 -o -perm 511 \) \
  -exec chmod 755 {} \+ -o \
  \( -perm 666 -o -perm 664 -o -perm 640 -o -perm 600 -o -perm 444 -o -perm 440 -o -perm 400 \) \
  -exec chmod 644 {} \+

to

Code:

chmod -R u+w,go-w,a+rX-st .

There was a discussion back in 2016 on this topic:
https://lists.slackbuilds.org/piperm...ry/015553.html

olear · 10-01-2019, 09:40 AM

Quote:

Originally Posted by Jeebizz

Well by that chart, perhaps Slackware should jump to 5.4 if we do not see a RC1 yet of current Slackware with 4.19, but thats just my crappy opinion

.

Since Slackware stable is supported over several years the only sensible versions (right now) would be 4.14 or 4.9.

guanx · 10-01-2019, 10:39 AM

Quote:

Originally Posted by olear

Since Slackware stable is supported over several years the only sensible versions (right now) would be 4.14 or 4.9.

Then one will have to go to 2nd hand market to search for supported hardware.

Jeebizz · 10-01-2019, 10:54 AM

Quote:

Originally Posted by olear

Since Slackware stable is supported over several years the only sensible versions (right now) would be 4.14 or 4.9.

Current is on 4.19 though, and the only reason I bring it up is if there is not an eventual RC of Slackware soon - perhaps maybe -current should consider jumping to 5.4 when it is released.

Also back to the f2fs thing I noticed a problem, sure I can create the f2fs partition, but the installer won't install on it though:

Click image for larger version

Name: VirtualBox_Slackware_01_10_2019_10_50_58.png
Views: 46
Size: 12.0 KB
ID: 31433

Click image for larger version

Name: VirtualBox_Slackware_01_10_2019_10_51_35.png
Views: 43
Size: 4.5 KB
ID: 31434

f2fs is not listed as a fs, so if you try to install you get an error.

igadoter · 10-01-2019, 11:28 AM

What type partition with f2fs has? I am not quite sure but Linux partitions are detected by partition type not by filesystem.

Jeebizz · 10-01-2019, 11:43 AM

Quote:

Originally Posted by igadoter

What type partition with f2fs has? I am not quite sure but Linux partitions are detected by partition type not by filesystem.

Per cfdisk, sda2 just a standard Linux partition:

Click image for larger version

Name: VirtualBox_Slackware_01_10_2019_11_42_38.png
Views: 40
Size: 7.9 KB
ID: 31435

igadoter · 10-01-2019, 11:48 AM

On this picture /dev/sda2 is marked as jfs.

Jeebizz · 10-01-2019, 11:58 AM

Quote:

Originally Posted by igadoter

On this picture /dev/sda2 is marked as jfs.

Hrm you're right

, however I did tell the installer to format , guess it didn't.

Jeebizz · 10-01-2019, 12:13 PM

I don't know why the settings were not sticking, because I know I made sure to write to disk in cfdisk - I literally had to delete the VM and start a new, and this time I created the partitions - I can't explain why when I wiped the partition types and wrote to disk, it kept reverting back as being labeled as jfs. Look I know I ARE smart

but even I made sure to 'write to disk' in cfdisk

.

Click image for larger version

Name: VirtualBox_Slackware_01_10_2019_12_08_33.png
Views: 31
Size: 7.0 KB
ID: 31436

Anyways:

Click image for larger version

Name: VirtualBox_Slackware_01_10_2019_12_14_50.png
Views: 30
Size: 12.8 KB
ID: 31438

Click image for larger version

Name: VirtualBox_Slackware_01_10_2019_12_10_56.png
Views: 34
Size: 4.6 KB
ID: 31437

-edit

I hope I don't run into that on my production machine when I use cfdisk to wipe the partitions itself (writing to disk and the old fs still stays even after reboot)

olear · 10-01-2019, 12:31 PM

Quote:

Originally Posted by guanx

Then one will have to go to 2nd hand market to search for supported hardware.

Maybe, but releasing Slackware 15 with kernel 4.19 or 5.4 would be a bad decision in regards to security down the line.

I can get security updates to the kernel I run on Slackware 14.2 until 2022. Getting ~2 years on Slackware 15.0 is not good IMHO.

Looking back Slackware 15 should have been released (early) 2018 with kernel 4.14 (EOL 2024).