I needed a little faster solution. I would like to upgrade to a newer release
of Linux, but that will take a while longer.
I have modified chandev.conf using sed and can not access our current LPAR.
Thanks for the suggestion,
Craig
-Original Message-
From: Linux on 390 Port
All,
Thanks for the many replies. My problem is resolved, and it seems to
due to running mkinitrd and zipl AFTER I've done the various YaST work.
Thanks again for the suggestions to get me back on track.
Tim
-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On
Hi All
I am in the process of setting up the install tree as per Mike's shell
(thanks Mike) but had a small snag in that the SP3 ISO's where not been
picked up , the script needs to be updated with the done in line 70
moved to line 82.
Regards
Gerard
On the whole of it, I would tend to agree, Mark. So I double checked things and
they looked OK.
Just to be clear on where I stood I started over on the z/OS side with the key
stuff.
I cleaned up /u/{userid}/.ssh - empty.
I cleaned up /etc/ssh except for the config files.
I cleaned up and
I somehow changed the shell directory in /etc/passwd file for root and =
now I cannot get in as root.
root:x:0:0:root:/root:q
I have no other user with administrative permissions to change anything. =
Does anyone know how to login to root on the z890 with this situation? =
I have seen some
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Ryan Stewart wrote:
| I somehow changed the shell directory in /etc/passwd file for root
| and = now I cannot get in as root.
|
| root:x:0:0:root:/root:q
|
| I have no other user with administrative permissions to change
| anything. = Does
Thanks for the responce Grega.
I tried what you suggested, but it does the same thing it does when I try to su
with no options. I don't know for sure, but from what I have seen when I try
to su, Linux does not let you alter the shell of the root user when logging in.
This is what I keep
If you have any other Linux guests you could link to the hosed pack in VM
and then mount it on the other image and repair /etc/passwd.
Only other thought is to try punching the initrd, kernel image, and parm
file again and once in the installer see if there's a shell or rescue option
available.
And if things ever get to the point where you don't have a valid shell
laying around, IPL the system from (in your case) the tape you used to
do the install. Insmod the DASD drivers, mount the root file system,
and use the installation system to fix /etc/passwd, or whatever.
Mark Post
Is there such a thing as Stand Alone Edit for Linux?
[EMAIL PROTECTED] 2/13/2006 3:42:08 PM
If you have any other Linux guests you could link to the hosed pack in VM
and then mount it on the other image and repair /etc/passwd.
Only other thought is to try punching the initrd, kernel image, and
On Feb 13, 2006, at 2:42 PM, Kyle Smith wrote:
If you have any other Linux guests you could link to the hosed pack
in VM
and then mount it on the other image and repair /etc/passwd.
Or you could get e2sh and repair your disk that way:
http://sinenomine.net/vm/ext2free
Adam
Grega Bremec wrote:
su -c /bin/bash --login
I'm not sure this command is going to work. I think the --login: option
is going to force the system to try and load the shell defined in the
passwd file *before* executing the command specified by -c. su will
fail because the passwd file entry for
Thanks all I'll give those a shot.
Ryan
-Original Message-
From: Linux on 390 Port on behalf of Post, Mark K
Sent: Mon 02/13/2006 3:43 PM
To: LINUX-390@VM.MARIST.EDU
Cc:
Subject: Re: Hosed root shell setting in /etc/passwd
Can you pass init=1 to the kernel when you IPL it?
This would drop you to single user mode, where you could make repairs.
On Mon, 13 Feb 2006, Adam Thornton wrote:
On Feb 13, 2006, at 2:42 PM, Kyle Smith wrote:
If you have any other Linux guests you could link to the hosed pack
in VM
I somehow changed the shell directory in /etc/passwd file for root and now I
cannot get in as root.
root:x:0:0:root:/root:q
I have no other user with administrative permissions to change anything. Does
anyone know how to login to root on the z890 with this situation? I have seen
some
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Eric Chevalier wrote:
| Grega Bremec wrote:
|
| su -c /bin/bash --login
|
| I'm not sure this command is going to work. I think the --login:
| option is going to force the system to try and load the shell defined
| in the passwd file *before*
Here's a study just out:
http://osdl.org/newsroom/press_releases/2006_Jan_02.beaverton.html/20006
_02_13_beaverton.html/newsitem_view
Marcy Cortes
(415) 243-6343
This message may contain confidential and/or privileged information.
If you are not the addressee or authorized to receive this for
See: http://www.vm.ibm.com/events/hillgang.pdf
23 Feb
8:30 for 9:00 until 14:00
CA Office
Herndon VA
RSVP to the Hillgang list
--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED]
* maximilian attems ([EMAIL PROTECTED]) wrote:
the s390 gys massaged the patch, please take belows.
thanks, updated to the version in Linus' tree
(commit 0defa3c19e7792001df09d6fa5ab461d3599ff6d)
-chris
--
For LINUX-390
19 matches
Mail list logo