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.
The right date of Last Login is already available in Slackware.
When I gave the exact time in the BIOS, to the following reboot:
"fsck from util-linux
last login 24-03-2040
last login in the future"
And all the partitions were verified.
Yes, that page a couple of others seem to suggest that the 'fix' will be to switch from sysvinit to systemd
Time will tell whether or not Patrick decides to make that switch sometime in the future.
Time will also tell whether or not he decides to drop 32bit all-together and have only 64bit Slackware.
A quick and dirty, fully backwards compatible, solution would be to replace
Code:
#if __WORDSIZE == 64 && defined __WORDSIZE_COMPAT32
int32_t ut_session; /* Session ID (getsid(2)),
used for windowing */
struct {
int32_t tv_sec; /* Seconds */
int32_t tv_usec; /* Microseconds */
} ut_tv; /* Time entry was made */
#else
with
Code:
#if __WORDSIZE == 64 && defined __WORDSIZE_COMPAT32
int32_t ut_session; /* Session ID (getsid(2)),
used for windowing */
struct {
uint32_t tv_sec; /* Seconds */
uint32_t tv_usec; /* Microseconds */
} ut_tv; /* Time entry was made */
#else
I see no need to lookup login occasions before 1970 on any Linux system... Such a quick fix will give us another 60+ years before the problem reoccurs.
A quick and dirty, fully backwards compatible, solution would be to replace
Code:
#if __WORDSIZE == 64 && defined __WORDSIZE_COMPAT32
int32_t ut_session; /* Session ID (getsid(2)),
used for windowing */
struct {
int32_t tv_sec; /* Seconds */
int32_t tv_usec; /* Microseconds */
} ut_tv; /* Time entry was made */
#else
with
Code:
#if __WORDSIZE == 64 && defined __WORDSIZE_COMPAT32
int32_t ut_session; /* Session ID (getsid(2)),
used for windowing */
struct {
uint32_t tv_sec; /* Seconds */
uint32_t tv_usec; /* Microseconds */
} ut_tv; /* Time entry was made */
#else
I see no need to lookup login occasions before 1970 on any Linux system... Such a quick fix will give us another 60+ years before the problem reoccurs.
regards Henrik
Is there not a better fix than that which would only last till a bit past my 124th birthday ?
Version 3.09 of SysV init contains to key changes.
On Linux distributions which use the musl C library (instead of glibc) we can now build properly. Specifically, the hddown helper program now builds on musl C systems.
The reboot command is now able to pass messages to the underlying firmware on Linux systems during a reboot. This allows the admin to pass information to the underlying firmware to, for example, ask the system to boot from another partition. Should be helpful on Raspberry Pi systems.
The reboot command can pass a message to the firmware when using the "-m" command line flag.
This release also improves the Makefile's clean directive.
Can we have some marker in a Slackware script, clarifying when booting starts, and/or printing the date?
In particular, I would like to ask that the following line be added to /etc/rc.d/rc.S right before the "PATH=/usr/local/sbin:/usr/sbin:/sbin:/usr/local/bin:/usr/bin:/bin" line:
Code:
printf "%s:Welcome to Slackware userspace!\n" "$(/usr/bin/date --iso=seconds)"
And the following line
Code:
printf "%s:Welcome to Slackware initrd!\n" "$(/bin/date --iso=seconds)"
right before the "INITRD=$(cat /initrd-name)" line in /boot/initrd-tree/init (/usr/share/mkinitrd/initrd-tree.tar.gz)
At the moment I am filtering this lines from boot logs using the following pattern:
Code:
/mount: proc mounted on \/proc./
But having a distinct marker would have been better for everyone, I think.
Suggestions for build kde module 'applications' without 'kdepim',
if you build applications without kdepim, the compilation will fail at module 'kosmindoormap' because it need the module 'kopeninghours', kopeninghours is in module kdepim, i think it better to push it in applications just before kosmindoormap.
other problem 'zanshin' and 'merkuro', also not build in applications, this too modules need many kdepim modules (akonadi,akonadi-calendar,akonadi-contacts, etc....),i think it'better to push these in kdepim.
Suggestions for build kde module 'applications' without 'kdepim',
if you build applications without kdepim, the compilation will fail at module 'kosmindoormap' because it need the module 'kopeninghours', kopeninghours is in module kdepim, i think it better to push it in applications just before kosmindoormap.
other problem 'zanshin' and 'merkuro', also not build in applications, this too modules need many kdepim modules (akonadi,akonadi-calendar,akonadi-contacts, etc....),i think it'better to push these in kdepim.
Is there something wrong with kdepim which makes you want to build things without it ?
Suggestions for build kde module 'applications' without 'kdepim',
if you build applications without kdepim, the compilation will fail at module 'kosmindoormap' because it need the module 'kopeninghours', kopeninghours is in module kdepim, i think it better to push it in applications just before kosmindoormap.
other problem 'zanshin' and 'merkuro', also not build in applications, this too modules need many kdepim modules (akonadi,akonadi-calendar,akonadi-contacts, etc....),i think it'better to push these in kdepim.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
