SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Re the "cruft" and "zombie" packages, I had more in mind really old stuff that is just laying around but not being used any more (yes, I know it's subjective, but definitely not commonly used things like emacs, KDE, etc). Was intended as more of a spring cleaning type idea for Pat to consider.
that is what I as going to say, day month year is US Military,
News to me. Date Time Group is traditionally formatted as DDHHMM(Z)MONYY
DD day (including leading 0)
HH hour (0-23)
MM minute (0-59)
(Z) Z for GMT (Z time zone, use other letters to show other time zones)
MON 3 letter abbreviation of the month
YY last two digits of year (you'd think we'd have learned from Y2K...)
Haha, well I don't personally use KDE, but lots of people do. Emacs on the other hand, that goes in the category of a life essential Obviously it needs to be kept there for the philistines too (they may come around one day).
Re the "cruft" and "zombie" packages, I had more in mind really old stuff that is just laying around but not being used any more (yes, I know it's subjective, but definitely not commonly used things like emacs, KDE, etc). Was intended as more of a spring cleaning type idea for Pat to consider.
Hey, I say this as someone who was upset when "fvwm95" was removed but here goes.... Is it finally time to ditch "xv"? There are so many alternatives that weren't abandoned in like 1994 or whatever, and that are free as opposed to proprietary software.
Hey, I say this as someone who was upset when "fvwm95" was removed but here goes.... Is it finally time to ditch "xv"? There are so many alternatives that weren't abandoned in like 1994 or whatever, and that are free as opposed to proprietary software.
Are there some patches around that extend the period of 'development' by several years? I see that some of these are added by PV...
News to me. Date Time Group is traditionally formatted as DDHHMM(Z)MONYY
DD day (including leading 0)
HH hour (0-23)
MM minute (0-59)
(Z) Z for GMT (Z time zone, use other letters to show other time zones)
MON 3 letter abbreviation of the month
YY last two digits of year (you'd think we'd have learned from Y2K...)
I won't comment on the rest of your comment.
that's good because I do not even remember what it was.
and yes I remember going into zulu , tango, delta, and such for time zones, but never paid much attention to that because it wasn't something I really needed to worry about as long as I wasn't late for watch, I was in the clear.
but I remember writing out a check, back when they had such things, and put the date, day, month, year and the sales person said I filled it out wrong, because it wasn't month, day, year. and i just blew her off, said that is how the military writes it. bye bye.
that was after I got out still being programmed to do things the military way.
I don't know if it is the right place to ask: would it be possible to add the bépo keyboard layout for the console in the future Slackware release? So one could type:
Code:
$ loadkeys fr-bepo-latin9
I have taken the keymap from Arch Linux since Slackware doesn't provide it.
Thanks!
Last edited by removed033; 02-04-2019 at 11:33 PM.
Reason: typo
root[/data/slackware64-current/slackware64]# upgradepkg a/glibc-solibs-2.29-x86_64-2.txz
+==============================================================================
| Remplacement du paquet glibc-solibs-2.23-x86_64-4_slack14.2 par a/glibc-solibs-2.29-x86_64-2.txz.
+==============================================================================
Pre-installing package glibc-solibs-2.29-x86_64-2...
Removing package /var/log/packages/glibc-solibs-2.23-x86_64-4_slack14.2-upgraded-2019-02-05,07:42:39...
/sbin/installpkg: line 64: warning: setlocale: LC_TIME: cannot change locale (fr_FR.utf8)
Verifying package glibc-solibs-2.29-x86_64-2.txz.
Installing package glibc-solibs-2.29-x86_64-2.txz:
PACKAGE DESCRIPTION:
# glibc-solibs (shared GNU C libraries)
#
# This package contains the shared libraries, binaries, and support
# files required to run most Linux applications linked with glibc.
#
Executing install script for glibc-solibs-2.29-x86_64-2.txz.
Package glibc-solibs-2.29-x86_64-2.txz installed.
Package glibc-solibs-2.23-x86_64-4_slack14.2 upgraded with new package a/glibc-solibs-2.29-x86_64-2.txz.
root[/data/slackware64-current/slackware64]# man installpkg
man: can't set the locale; make sure $LC_* and $LANG are correct
root[/data/slackware64-current/slackware64]# echo $LANG
fr_FR.utf8
root[/data/slackware64-current/slackware64]# upgradepkg ../../slackware64-14.2/patches/packages/glibc-solibs-2.23-x86_64-4_slack14.2.txz
+==============================================================================
| Upgrading glibc-solibs-2.29-x86_64-2 package using ../../slackware64-14.2/patches/packages/glibc-solibs-2.23-x86_64-4_slack14.2.txz
+==============================================================================
Pre-installing package glibc-solibs-2.23-x86_64-4_slack14.2...
/sbin/installpkg: line 64: warning: setlocale: LC_TIME: cannot change locale (fr_FR.utf8)
Removing package /var/log/packages/glibc-solibs-2.29-x86_64-2-upgraded-2019-02-05,07:55:42...
--> Deleting /usr/lib64/gconv/IBM858.so
Verifying package glibc-solibs-2.23-x86_64-4_slack14.2.txz.
Installing package glibc-solibs-2.23-x86_64-4_slack14.2.txz:
PACKAGE DESCRIPTION:
# glibc-solibs (shared GNU C libraries)
#
# This package contains the shared libraries, binaries, and support
# files required to run most Linux applications linked with glibc.
#
Executing install script for glibc-solibs-2.23-x86_64-4_slack14.2.txz.
Package glibc-solibs-2.23-x86_64-4_slack14.2.txz installed.
Paquet glibc-solibs-2.29-x86_64-2 remplacé par le nouveau paquet ../../slackware64-14.2/patches/packages/glibc-solibs-2.23-x86_64-4_slack14.2.txz.
root[/data/slackware64-current/slackware64]#
Mind the difference:
after upgradepkg to 2.29:
Code:
Package glibc-solibs-2.23-x86_64-4_slack14.2 upgraded with new package a/glibc-solibs-2.29-x86_64-2.txz.
But after upgradepkg to 2.23:
Code:
Paquet glibc-solibs-2.29-x86_64-2 remplacé par le nouveau paquet ../../slackware64-14.2/patches/packages/glibc-solibs-2.23-x86_64-4_slack14.2.txz
This is on Slint, will try on Slackware64-current later today if I can.
PS. On second thought, that's probaly a bid idea to upgrade only glibc-solib, not glibc and glibc-i18n together. Anyway I solved the issue that leaded me to test that not having to upgrade glibc for now, cf. the post #2826
Last edited by Didier Spaier; 02-05-2019 at 12:54 PM.
Reason: PS added.
Hey, I say this as someone who was upset when "fvwm95" was removed but here goes.... Is it finally time to ditch "xv"? There are so many alternatives that weren't abandoned in like 1994 or whatever, and that are free as opposed to proprietary software.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.