LinuxQuestions.org
Welcome to the most active Linux Forum on the web.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Newbie
User Name
Password
Linux - Newbie This Linux forum is for members that are new to Linux.
Just starting out and have a question? If it is not in the man pages or the how-to's this is the place!

Notices


Reply
  Search this Thread
Old 05-16-2005, 01:21 PM   #1
rpd
LQ Newbie
 
Registered: Jan 2005
Location: Pretoria, South Africa
Distribution: Slackware (3.5) - Grey Cat Linux
Posts: 7

Rep: Reputation: 0
First login fails after installing Slackware 3.5


Hello world

After I have installed Slackware 3.5 using the install file system I downloaded from ftp sites, I have problem logging in.

I entered "root" to try and login. There was a long pause (approx 15 seconds) after which the login prompt just reappeared. There was no prompt for a password or error message saying "root" wasn't a good username. Just a delay and then a redisplay of the login prompt.

How I installed:
--------------------
It's a 486 with 24MB RAM. I have Windows 95 (FAT16) running fine on /dev/hda1. I used an UMSDOS distribution (Grey Cat Linux) with kernel 2.0.34 to load a rootdisk to install. This is the kernel I'm using. I formatted the /dev/hda2 partition as ext2 and /dev/hda3 as a "linux swap" partition.

The whole install process worked fine; no problems at all. When I booted for the first (and second, and third) time the kernel loaded beautifully from LILO and ran all my /etc/rc.d scripts and loaded all my daemons. When it came to the login screen (agetty, I think) there was this problem.
-------------------
What I've tried:
--------------------
I've checked my "passwd" and "group" files in /etc, and they both have "root" entries with user id 0 and nothing in the password field.
I didn't install "shadow", the password masking app.
---------------------

I'll naturally continue trying what comes to mind, but I'd appreciate your ideas and help, especially if you've encountered this problem before.

Thanks.
rpd
 
Old 05-16-2005, 03:30 PM   #2
Poetics
Senior Member
 
Registered: Jun 2003
Location: California
Distribution: Slackware
Posts: 1,181

Rep: Reputation: 49
Check out the Slackware forum -- it seems like a few other people were having that problem with specific setups, I'm sorry I don't know more off the top of my head.

Question though; why are you running Slack 3.5? ZipSlack is a very tiny version of Slackware that may be more suited to your needs (and it comes with a greatly-updated set of files compared to 3.5)
 
Old 05-16-2005, 04:14 PM   #3
masonm
Senior Member
 
Registered: Mar 2003
Location: Following the white rabbit
Distribution: Slackware64 14.2 Solus
Posts: 2,264

Rep: Reputation: 51
Get a newer version.

You will likely have fewer problems.
 
Old 05-19-2005, 02:02 PM   #4
rpd
LQ Newbie
 
Registered: Jan 2005
Location: Pretoria, South Africa
Distribution: Slackware (3.5) - Grey Cat Linux
Posts: 7

Original Poster
Rep: Reputation: 0
Thanks guys.
I was using Slackware 3.5 because it's a 486, but I'll definitely check out zipslack.

rpd
-----------
Slackware is for slackers.
 
Old 05-30-2005, 01:04 PM   #5
rpd
LQ Newbie
 
Registered: Jan 2005
Location: Pretoria, South Africa
Distribution: Slackware (3.5) - Grey Cat Linux
Posts: 7

Original Poster
Rep: Reputation: 0
Solution

I finally solved my problem!
When I installed everything I had a umask of 022 (the default).
This gave the installed files permissions not allowing execution by my new root (I think).
Anyway, I don't really know how umask works, but I set 'umask 000' before I installed again, and now everything works fine.

I hope this helps someone.
rpd
------------------
Slackware is for slackers
 
Old 05-30-2005, 02:57 PM   #6
btmiller
Senior Member
 
Registered: May 2004
Location: In the DC 'burbs
Distribution: Arch, Scientific Linux, Debian, Ubuntu
Posts: 4,284

Rep: Reputation: 371Reputation: 371Reputation: 371Reputation: 371
A umask of 022 will not prevent root from having executable permission (the owner has all permissions, 0 are masked, and for group and others write permissions (2) are masked. In no case is executable permission masked). So chances are that umask setting wqwasn't the real problem.

And use, please do get something newer -- goodness knows how many security and bug issues there are with a distro that old.
 
Old 05-30-2005, 04:13 PM   #7
DaWallace
Member
 
Registered: Feb 2004
Location: Southern Maine, United States
Distribution: Slackware Ubuntu Debian FreeBSD
Posts: 418

Rep: Reputation: 31
even the new stable versions support 486.
 
  


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
webmin fails login jordanthompson Linux - Software 2 06-17-2008 12:55 PM
Squirrel fails to login! mumux Linux - Networking 0 07-09-2005 02:44 AM
Localhost login fails Captain_Wally Linux - Newbie 0 12-03-2004 01:43 PM
Login fails - being taken back to login screen donhare Mandriva 3 11-11-2004 04:53 PM
graphical login fails in 9.1 chuck_notorious Slackware 2 10-31-2004 02:38 AM


All times are GMT -5. The time now is 03:56 PM.

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