LinuxQuestions.org
Help answer threads with 0 replies.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 08-26-2018, 01:04 AM   #1936
gmgf
Senior Member
 
Registered: Jun 2012
Location: Bergerac, France
Distribution: Slackware
Posts: 1,700

Rep: Reputation: 665Reputation: 665Reputation: 665Reputation: 665Reputation: 665Reputation: 665

xfsprogs-4.18.0:

https://git.kernel.org/pub/scm/fs/xf...s-dev.git/log/
https://mirrors.edge.kernel.org/pub/...-4.18.0.tar.xz

media-player-info-24:

https://cgit.freedesktop.org/media-player-info/
https://www.freedesktop.org/software...info-24.tar.gz
 
Old 08-26-2018, 01:18 AM   #1937
gmgf
Senior Member
 
Registered: Jun 2012
Location: Bergerac, France
Distribution: Slackware
Posts: 1,700

Rep: Reputation: 665Reputation: 665Reputation: 665Reputation: 665Reputation: 665Reputation: 665
iso-codes (3.76 or 4.0)

https://salsa.debian.org/iso-codes-team/iso-codes
https://salsa.debian.org/iso-codes-t...es-3.79.tar.xz

https://salsa.debian.org/iso-codes-t...des-4.0.tar.xz
 
Old 08-26-2018, 03:24 AM   #1938
gmgf
Senior Member
 
Registered: Jun 2012
Location: Bergerac, France
Distribution: Slackware
Posts: 1,700

Rep: Reputation: 665Reputation: 665Reputation: 665Reputation: 665Reputation: 665Reputation: 665
librsvg-2.42.7:

http://ftp.gnome.org/pub/gnome/sourc...vg-2.42.7.news
http://ftp.gnome.org/pub/gnome/sourc...-2.42.7.tar.xz

openssh-7.8:

https://www.openssh.com/releasenotes.html
https://ftp.openbsd.org/pub/OpenBSD/...h-7.8p1.tar.gz
 
1 members found this post helpful.
Old 08-26-2018, 07:16 AM   #1939
Petri Kaukasoina
Member
 
Registered: Mar 2007
Posts: 392

Rep: Reputation: 247Reputation: 247Reputation: 247
cups-filters 1.21.1. (Needed to make printing work again here)
 
Old 08-26-2018, 11:58 AM   #1940
TurboBlaze
Member
 
Registered: Jan 2018
Location: Russian Federation, Lipetsk region, Dankov
Distribution: Porteus
Posts: 42

Rep: Reputation: Disabled
Current xauth-1.0.10-x86_64-2.txz have a bug with changing hostname - it breaks access to X
For fix this need to apply this patch to support adding such FamilyWild entries via xauth directly with an *:0 argument:
Code:
From bc78aa61cfbddaa27dee275f639ba40de6981b17 Mon Sep 17 00:00:00 2001
From: George V. Kouryachy (Fr. Br. George) <george@>
Date: Fri, 4 Aug 2017 18:37:33 +0300
Subject: [PATCH] parse_displayname: use FamilyWild for *:0

---
 xauth/gethost.c  |    4 ++++
 xauth/parsedpy.c |    4 ++++
 2 files changed, 8 insertions(+), 0 deletions(-)

diff --git a/xauth/gethost.c b/xauth/gethost.c
index 8cb58c5..598ac48 100644
--- a/xauth/gethost.c
+++ b/xauth/gethost.c
@@ -180,6 +180,10 @@ struct addrlist *get_address_info (
      * information to be copied and set len to the number of bytes.
      */
     switch (family) {
+      case FamilyWild:			/* was :0 */
+	src = "\xff\xff";
+	len = strlen(src);
+	break;
       case FamilyLocal:			/* hostname/unix:0 */
 					/* handle unix:0 and :0 specially */
 	if (prefix == 0 && (strncmp (fulldpyname, "unix:", 5) == 0 ||
diff --git a/xauth/parsedpy.c b/xauth/parsedpy.c
index 97988d3..6c98339 100644
--- a/xauth/parsedpy.c
+++ b/xauth/parsedpy.c
@@ -141,6 +141,10 @@ parse_displayname (const char *displayname,
 	    family = FamilyInternet;
 	}
 #endif
+    } else if (len == 1 && *displayname == '*') {
+	/* ALT: wildcard cookie */
+	host = copystring("*", 1);
+	family = FamilyWild;
     } else if (!dnet && (*displayname == '[') && (*(ptr - 1) == ']')) {
 	/* Allow RFC2732-like [<IPv6NumericAddress>]:display syntax */
 	family = FamilyInternet6;
-- 
1.7.3.3
Link on the patch http://git.altlinux.org/people/georg...9ba40de6981b17

Last edited by TurboBlaze; 08-26-2018 at 12:01 PM.
 
Old 08-26-2018, 11:59 AM   #1941
jostber
Member
 
Registered: Jul 2001
Location: Skien, Norway
Distribution: Slackware 14.2 64-bit
Posts: 457

Rep: Reputation: 142Reputation: 142
Wonder if Cups 2.3 and the new planned driver format in this version will be incorporated in the Slackware 15.0?

https://www.cups.org/blog/2018-06-06...velopment.html
 
Old 08-26-2018, 12:01 PM   #1942
jostber
Member
 
Registered: Jul 2001
Location: Skien, Norway
Distribution: Slackware 14.2 64-bit
Posts: 457

Rep: Reputation: 142Reputation: 142
Add an extra secure kernel as a choice in Slackware and a slack version of the enforcemode like in SElinux:

https://en.wikipedia.org/wiki/Security-Enhanced_Linux
 
Old 08-26-2018, 12:12 PM   #1943
jostber
Member
 
Registered: Jul 2001
Location: Skien, Norway
Distribution: Slackware 14.2 64-bit
Posts: 457

Rep: Reputation: 142Reputation: 142
Add a backup tool for snapshots and restore as a standard in Slackware. Something like Mondorescue:

http://www.mondorescue.org/
 
Old 08-26-2018, 12:14 PM   #1944
jostber
Member
 
Registered: Jul 2001
Location: Skien, Norway
Distribution: Slackware 14.2 64-bit
Posts: 457

Rep: Reputation: 142Reputation: 142
Add a nice looking Slackware wallpaper with the logo and 15.0 a standard for the KDE users. Like this:

http://wallpapercave.com/wp/Wr8IqHz.jpg
 
1 members found this post helpful.
Old 08-26-2018, 12:25 PM   #1945
jostber
Member
 
Registered: Jul 2001
Location: Skien, Norway
Distribution: Slackware 14.2 64-bit
Posts: 457

Rep: Reputation: 142Reputation: 142
Have a half-yearly release cycle for Slackware versions. The incremental versions will mostly be security updates and bug fixes while the major releases will have the main new features. Current will then be for the major new releases. The major versions could come out about each 1.5 year.

Last edited by jostber; 08-26-2018 at 12:35 PM.
 
1 members found this post helpful.
Old 08-26-2018, 12:28 PM   #1946
chrisretusn
Member
 
Registered: Dec 2005
Location: Philippines
Distribution: Slackware64-current
Posts: 933

Rep: Reputation: 358Reputation: 358Reputation: 358Reputation: 358
Quote:
Originally Posted by montagdude View Post
I don't really see how it's any different. With my proposed changes, you would not get a .new file at all unless it was different from the previous default config file. This would be even more helpful for large complicated files where you've made lots of edits, because you wouldn't need to dig through it to find out whether there were important changes. No .new file = the only changes are the ones you made yourself. If there is a .new file, that means there are potentially important changes coming from the new package.
Okay maybe it's the use of default config file is what is blowing my mind. I consider the default config file the one included in the package being installed or upgraded (aka new config file). The currently installed config file would be the old one. If I make no changes then the old matches the new and the new config file will be deleted. With the current method if the old and new do not match the new is left for me to consider. In my case since I do all of my package updates using slackpkg, this will be handled at the end.

I think I see the light..., maybe not... You want to track the state of the default config file after it's first installed. If an update is made and the state of the default config file matches the state of the "first installed" config file, then no new config file is installed. The modified config file is basically ignored. So what happens if there are changes to the default config file that I may want to use, or may even need?
 
Old 08-26-2018, 12:54 PM   #1947
Didier Spaier
LQ Addict
 
Registered: Nov 2008
Location: Paris, France
Distribution: Slint64-14.2.1 on Lenovo Thinkpad W520
Posts: 8,753

Rep: Reputation: Disabled
Quote:
Originally Posted by jostber View Post
Have a half-yearly release cycle for Slackware versions. The incremental versions will mostly be security updates and bug fixes while the major releases will have the main new features. Current will then be for the major new releases. The major versions could come out about each 1.5 year.
I would prefer to stay with a release "when it's ready".

However it could help to provide from time to time (maybe half yearly or yearly) a new ISO, that would just be "the current state of the stable release", i.e. with all updates provided in /patches since the last release and possibly an update of the installer. Rationale:
  1. This could help people with recent hardware, not yet supported at time of the last release.
  2. This would alleviate the need for heavy upgrades just after installation for people installing a release a long time after it has been made available.
  3. It wouldn't add to the burden of maintenance for Pat beyond building the ISO itself as that wouldn't introduce a new version (in case the installer be updated, it could go in /patches, that's all.)
  4. There would be no need for current users of -stable to do anything when the new ISO becomes available.

Last edited by Didier Spaier; 08-26-2018 at 01:44 PM.
 
4 members found this post helpful.
Old 08-26-2018, 01:05 PM   #1948
montagdude
Senior Member
 
Registered: Apr 2016
Distribution: Slackware
Posts: 1,441

Rep: Reputation: 1069Reputation: 1069Reputation: 1069Reputation: 1069Reputation: 1069Reputation: 1069Reputation: 1069Reputation: 1069
Quote:
Originally Posted by chrisretusn View Post
I think I see the light..., maybe not... You want to track the state of the default config file after it's first installed. If an update is made and the state of the default config file matches the state of the "first installed" config file, then no new config file is installed. The modified config file is basically ignored. So what happens if there are changes to the default config file that I may want to use, or may even need?
In that case, you would get a .new file. I think ttk's summary a page or two is the clearest one. (I would link to it, but it's painful to do stuff like that on my phone. It's the one with 4 scenarios listed.)

Last edited by montagdude; 08-26-2018 at 01:07 PM.
 
Old 08-26-2018, 01:29 PM   #1949
Darth Vader
Senior Member
 
Registered: May 2008
Location: Romania
Distribution: DARKSTAR Linux 2008.1
Posts: 2,727

Rep: Reputation: 1235Reputation: 1235Reputation: 1235Reputation: 1235Reputation: 1235Reputation: 1235Reputation: 1235Reputation: 1235Reputation: 1235
Quote:
Originally Posted by Didier Spaier View Post
I would prefer to stay with a release "when it's ready".

However it could help to provide from time to time (maybe half yearly or yearly) a new ISO, that would just be "the current state of the stable release", i.e. with all updates provided in /patches since the last release and possibly an update of the installer. Rationale:
  1. This could help people with recent hardware, not yet supported at time of the last release.
  2. This would alleviate the need for heavy upgrades just after installation for people installing a release a long time after it has been made available.
  3. I wouldn't add to the burden of maintenance for Pat beyond building the ISO itself as that wouldn't introduce a new version (in case the installer be updated, it could go in /patches, that's all.)
  4. There would be no need for current users of -stable to do anything when the new ISO becomes available.
Regarding this idea, I thought already about an annual Service Pack.

This annual Service Pack can integrate the patches already issued through that year, and supplementary containing the switching to a newer LTS Kernel series and associated packages like the filesystems and tools, and an updated installer.

Additionally, the installer from a Service Pack can contain supplementary an "upgrade" option for installing packages, useful for applying the Service Pack on an existent installation. I think that's is possible because an Service Pack probably will not contains packages removals or renames.

This annual Service Pack could represent an incentive for those who pays subscriptions (then more sales for our BDFL) and in my opinion the Slackware 14.2 yells right now for it - see the endless issues with installation on EMMC and NVMe drives and support for many more modern hardware.

I know, I know, there will be raised the argument that the Slackware Gurus will build themselves new kernels and will do dark Slack-Fu art on installations, BUT not all users are Gurus, specially the rookies.

Last edited by Darth Vader; 08-26-2018 at 01:50 PM.
 
4 members found this post helpful.
Old 08-26-2018, 04:47 PM   #1950
sombragris
Member
 
Registered: Jul 2004
Location: Asuncion, Paraguay, South America
Distribution: Slackware
Posts: 425

Rep: Reputation: 183Reputation: 183
Quote:
Originally Posted by Didier Spaier View Post
However it could help to provide from time to time (maybe half yearly or yearly) a new ISO, that would just be "the current state of the stable release", i.e. with all updates provided in /patches since the last release and possibly an update of the installer. Rationale:
AlienBob provides this and it's updated practically with every new release of the ChangeLog:

https://slackware.nl/slackware/slackware64-current-iso/
 
2 members found this post helpful.
  


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
[SOLVED] Requests for -current (20151216) rworkman Slackware 3441 12-28-2017 03:50 PM

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

All times are GMT -5. The time now is 05:24 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
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration