Instead of cat use the ed command
1,$n
which will print the file with line #s
you can print a range with
1,20n
21,40n
and so forth
to print the line you just changed for verification
just do n<enter>
Don't forget w to write the updated file
then q to quit
I think ed is much better than sed because I like to
see what is happening. After all, I have already
screwed it up once!
|--------+---------------------------->
| | Tom Duerbusch |
| | <[EMAIL PROTECTED]|
| | scity.com> |
| | Sent by: Linux on |
| | 390 Port |
| | <[EMAIL PROTECTED]|
| | ST.EDU> |
| | |
| | |
| | 05/23/2005 09:41 |
| | AM |
| | Please respond to |
| | Linux on 390 Port |
| | |
|--------+---------------------------->
>---------------------------------------------------------------------------------------------------------------------------|
|
|
| To: [email protected]
|
| cc:
|
| Subject: Re: SLES 9 boot failing on dasd issue...
|
>---------------------------------------------------------------------------------------------------------------------------|
My first guess is that you need to "activate" the dasd. I haven't got to
that part in my docs yet.
But as far as a line editor, there is "ed".
Sample commands, in case you hosed your only Linux image:
4 n (lists line 4)
4 s/linux22/linux25/ (change command for line 4)
4 d (deletes line 4)
I usually do a 'cat' before hand to see what statements on on what lines.
Tom Duerbusch
THD Consulting
>>> [EMAIL PROTECTED] 05/23/05 7:41 AM >>>
I added new dasd to an image, used it with no problems, but ended up
booting the image for some reason and now it's stuck on the following
messages. I am not all that adept yet at this Linux stuff so I'm hoping
this isn't something where I have to re-install it as that's what I'm
thinking.
�/sbin/fsck.ext3 (1) -- /Concur fsck.ext3 -a /dev/dasdc1
fsck.ext3: No such device or address while trying to open /dev/dasdc1
Possibly non-existent or swap device?
fsck.ext3 /dev/dasdc1 failed (status 0x8). Run manually!
So, I only have access thru the z/VM image at boot time and I can logon to
root, but then there seems to be no way to edit anything. VI is quite ugly
at that point I ass/u/me under 3270 emulation. SO, I'm hoping there are
commands that I can either remove this dasd and try to add it again, or
something else that fixes why it can't be found. I did look before a boot
of it and it's in my z/VM directory for that image. I did a google search
but nothing really jumped out so I try here now. THANX in advance...
Brian W. France
Systems Administrator (Mainframe)
Pennsylvania State University
Administrative Information Services - Infrastructure/Sysarc
Rm 25 Shields Bldg., University Park, Pa. 16802
814-863-4739
[EMAIL PROTECTED]
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or
visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or
visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
