This is a discussion on Slack building from source CD within the Slackware Linux Support forums, part of the Unix Operating Systems category; --> those who using slack, has anyone noticed this? I have this 2 extra slack source cds, one day I ...
| |||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| those who using slack, has anyone noticed this? I have this 2 extra slack source cds, one day I was listing files in the directories, hey~ how nice there's package building scripts for each source, so there I am, looked inside of each modified to optimize for my arch, running scripts... Holy crap! can't log back in, right after log- ging in logs out in auto mode. then I heard some hack put logout in ..bash profile, using rescue disc, mounted the partition, looked into it.. that wasn't exactly the cause oh well. any more story about this? |
| |||
| On Mon, 27 Sep 2004 02:07:01 +0000, Aiehce wrote: > any more story about this? How can we help you if you don't tell us what you did to break it in the first place, and the real problem is? Did you try to boot in single user mode (add "single" as a parameter to the kernel in LILO)? http://www.catb.org/~esr/faqs/smart-questions.html With kind regards, Daniel de Kok |
| |||
| On Mon, 27 Sep 2004 08:15:58 +0200, Daniel de Kok wrote: Yes, I passed single parm at lilo I did got access to the partition by mounting in rescue disk, but no clue what the script did to the system(supposed to build packages at /tmp) To make question more clear, Has anyone successfully compiled slack from the source using scripts provided? > On Mon, 27 Sep 2004 02:07:01 +0000, Aiehce wrote: > >> any more story about this? > > How can we help you if you don't tell us what you did to break it in the > first place, and the real problem is? Did you try to boot in single user > mode (add "single" as a parameter to the kernel in LILO)? > > http://www.catb.org/~esr/faqs/smart-questions.html > > With kind regards, > Daniel de Kok |
| |||
| On Mon, 27 Sep 2004 21:03:50 +0000, Aiehce wrote: after single mode, it still put me on login prompt. I'm checking inittab and according to it it runs rc.K for single I don't know dude, it just keeps kicking me back out automatically(loggin out) from the system > On Mon, 27 Sep 2004 08:15:58 +0200, Daniel de Kok wrote: > > Yes, I passed single parm at lilo > > I did got access to the partition by mounting in rescue disk, but no clue > what the script did to the system(supposed to build packages at /tmp) > > To make question more clear, > Has anyone successfully compiled slack from the source using scripts > provided? > >> On Mon, 27 Sep 2004 02:07:01 +0000, Aiehce wrote: >> >>> any more story about this? >> >> How can we help you if you don't tell us what you did to break it in the >> first place, and the real problem is? Did you try to boot in single user >> mode (add "single" as a parameter to the kernel in LILO)? >> >> http://www.catb.org/~esr/faqs/smart-questions.html >> >> With kind regards, >> Daniel de Kok |
| |||
| Aiehce wrote: > after single mode, it still put me on login prompt.**I'm*checking*inittab > and according to it it runs rc.K for single > I don't know dude, it just keeps kicking me back out automatically(loggin > out) from the system Could something have happened to the user's default shell? For example, a shell set to /bin/false will act just as you describe. Jeffrey |
| |||
| On Mon, 27 Sep 2004 16:30:52 -0700, Jeffrey Froman wrote: you mean in passwd right? well the for both root and as user it kicks me back out when tried to log in. I remember reading from someone else's post similar thing happended somewhere in usenet before. I'm using slack 10, someone execute this build shell scripts from source cds on test system. > Aiehce wrote: > >> after single mode, it still put me on login prompt.**I'm*checking*inittab >> and according to it it runs rc.K for single >> I don't know dude, it just keeps kicking me back out automatically(loggin >> out) from the system > > Could something have happened to the user's default shell? For example, a > shell set to /bin/false will act just as you describe. > > Jeffrey |
| ||||
| Aiehce wrote: <snip> Please trim your quotes, http://tinyurl.com/6438n and don't top post, http://tinyurl.com/5q355 -- Two Ravens "...hit the squirrel..." |