Sponsored Content
Operating Systems Linux Slackware Anyone Using Slackware Anymore? Post 302877435 by drl on Sunday 1st of December 2013 08:07:19 AM
Old 12-01-2013
Hi.

No one here uses Slackware as a main OS, but it is among the options we have around for compare and contrast uses ... cheers, drl

Code:
# Uptimes for available machines 2013.12.01:
up   3 min      3 users: Antergos 3.11.4-1 (Arch) 
up  22 days     6 users: aptosid 2013.1 (Hesperides, Debian jessie/sid) 
up  25 days     5 users: CentOS 6.4 (Final) 
up   5 min      2 users: CRUX 3.0 
up  24 days     6 users: Debian (jessie) 
up  32 days     6 users: Debian 7.2 (wheezy, vm-server-ng) 
up  79 days     1 users: Debian 5.0 (lenny, vm-server) 
up  79 days     2 users: Debian 6.0 (squeeze, backups) 
up  95 days    42 users: Debian 5.0.8 (lenny, workstation) 
up  20 days    12 users: Fedora 19 KDE (Schrödinger's Cat) 
up  19 days     6 users: FreeBSD, 9.2-RELEASE-p9, amd64 
up  14 days     3 users: Mint 11 (Katya, LMDE, squeeze/sid) 
up   7 days     2 users: NetBSD 6.1.1/amd64 
up  15 days     3 users: OpenBSD, 5.3, amd64 
up  67 days     3 users: OpenIndiana Development oi_148 X86 
up  19 days     6 users: openSUSE 12.3 (Dartmouth) 
up 411 days     4 users: OSX 10.3.9 
up  12 days     6 users: Slackware 14.0

 

8 More Discussions You Might Find Interesting

1. Slackware

After installing linux cannot boot PC anymore?

After installing linux (slackware) my (experimental) computer can't boot anymore. When I start the pc it says: "There was an error during linux startup" (or something like that, it was written in my language and I'm a bad translator) And after that my computer doesn't do a thing anymore. I... (4 Replies)
Discussion started by: RellioN
4 Replies

2. UNIX for Dummies Questions & Answers

Can't login as SU anymore - SU: NO SHELL

the root shell has been changed in the file /etc/passwd, basically pointing to an incorrect directory. So now every time we login as 'su' I get the message 'su: no shell' so we can't login as superuser. Is there an easy way to rectify this? please use step by step instructions/commands - I... (4 Replies)
Discussion started by: homechoice
4 Replies

3. UNIX for Dummies Questions & Answers

connection doesn't work anymore

Hello, first of all, I want to make myself clear about my language. I'm brazilian, so I ask you all to understand if i commit any mistake with the grammar. Here is the problem. Some days ago I needed to use a "sh" command in the Terminal (I use a Mac OSX 10.5.6) followed by a file... (0 Replies)
Discussion started by: anubisbr
0 Replies

4. UNIX for Dummies Questions & Answers

Can't SSH as root anymore!

I've screwed something up in my sshd_config apparently, because I can't ssh with root anymore. I had disabled root login for security reasons, but then my ssh credentials with full administrative privelges stopped working. So then I reenabled root login (and reset ssh), but root now isn't... (3 Replies)
Discussion started by: cquarry
3 Replies

5. UNIX for Dummies Questions & Answers

Input of char 's' is not possible anymore

Hello, I have a big problem and no idea how to solve it. I was looking up commands in /bin with 'man' as I found 'sh'. In mistake I started the command. Now after that I can not input the character 's' in shell anymore! Even after restarting system the problem is still there. Mysterious... (7 Replies)
Discussion started by: daWonderer
7 Replies

6. Windows & DOS: Issues & Discussions

Can't login to Vista anymore

hello obviously something got messed up and I can't login to my Vista account anymore. the password was automatically disabled hence it was directly booting into vista. then I installed openSSH and created a password for the user. But vista login doesn't recognize this password and now I can't... (6 Replies)
Discussion started by: milhan
6 Replies

7. Solaris

Telnet access is not available anymore

Hi Folks, My telnet access to the server is not available anymore. I have found that when I execute >telnet IP, the login prompt for username/password entry is not displayed. Cursor blinks in a empty line and I dont see the prompt to enter my username. It hungs in this state and not possible... (1 Reply)
Discussion started by: ekorgur
1 Replies

8. What is on Your Mind?

They won't need so many sys admins anymore

Nice eye catching title huh ;) I got laid off along with 55000 others from HP worldwide have been expecting this for some time and now it's finally my turn. Most of the folks I know get laid off at around this age of 40+ so do take note. Ideas that ran thru my head this last few weeks:... (16 Replies)
Discussion started by: sparcguy
16 Replies
TIME.CONF(5)							 Linux-PAM Manual						      TIME.CONF(5)

NAME
time.conf - configuration file for the pam_time module DESCRIPTION
The pam_time PAM module does not authenticate the user, but instead it restricts access to a system and or specific applications at various times of the day and on specific days or over various terminal lines. This module can be configured to deny access to (individual) users based on their name, the time of day, the day of week, the service they are applying for and their terminal from which they are making their request. For this module to function correctly there must be a correctly formatted /etc/security/time.conf file present. White spaces are ignored and lines maybe extended with '' (escaped newlines). Text following a '#' is ignored to the end of the line. The syntax of the lines is as follows: services;ttys;users;times In words, each rule occupies a line, terminated with a newline or the beginning of a comment; a '#'. It contains four fields separated with semicolons, ';'. The first field, the services field, is a logic list of PAM service names that the rule applies to. The second field, the tty field, is a logic list of terminal names that this rule applies to. The third field, the users field, is a logic list of users or a netgroup of users to whom this rule applies. For these items the simple wildcard '*' may be used only once. With netgroups no wildcards or logic operators are allowed. The times field is used to indicate the times at which this rule applies. The format here is a logic list of day/time-range entries. The days are specified by a sequence of two character entries, MoTuSa for example is Monday Tuesday and Saturday. Note that repeated days are unset MoMo = no day, and MoWk = all weekdays bar Monday. The two character combinations accepted are Mo Tu We Th Fr Sa Su Wk Wd Al, the last two being week-end days and all 7 days of the week respectively. As a final example, AlFr means all days except Friday. Each day/time-range can be prefixed with a '!' to indicate "anything but". The time-range part is two 24-hour times HHMM, separated by a hyphen, indicating the start and finish time (if the finish time is smaller than the start time it is deemed to apply on the following day). For a rule to be active, ALL of service+ttys+users must be satisfied by the applying process. Note, currently there is no daemon enforcing the end of a session. This needs to be remedied. Poorly formatted rules are logged as errors using syslog(3). EXAMPLES
These are some example lines which might be specified in /etc/security/time.conf. All users except for root are denied access to console-login at all times: login ; tty* & !ttyp* ; !root ; !Al0000-2400 Games (configured to use PAM) are only to be accessed out of working hours. This rule does not apply to the user waster: games ; * ; !waster ; Wd0000-2400 | Wk1800-0800 SEE ALSO
pam_time(8), pam.d(5), pam(7) AUTHOR
pam_time was written by Andrew G. Morgan <morgan@kernel.org>. Linux-PAM Manual 06/04/2011 TIME.CONF(5)
All times are GMT -4. The time now is 07:20 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy