Referring to the link:

http://www.linuxquestions.org/questi...167/page2.html

I used Acronis utility and deleted the partition where solaris resides (sda3). After that I gapped Solaris DVD and install a fresh copy and chose the portion of hard disk as Solaris partition type.

When I finished the installation, I lost FC7 grub, (This is normal), I was able to see Solaris's grub and windows OS was listed within solaris's grub menu.

I reinstall FC7 grub to take control of the solaris's grub, and again the same problem happened /etc/fstab,,,,,,,,,,,still solaris partion if type swap not bf !!!!!!!!!!

Now solrais prtiton is sda4 not sda3 as you can see it here :
http://img337.imageshack.us/img337/7...eenshotzc1.png

Therefore in the menu.lst i have modified it from (hd0,2) to (hd0,3). and it worked.

Although this time I can boot into solaris OS, and


I have modified the solaris OS menu.lst and I accidentally I modified some lines which they should not have been modified,,,how can I access solaris menu.lst again ? only I can access Solrais failsafe mode, before editing I was able to access solaris normal mode.

So you reinstalled Solaris just to change the partition id ???
Looks quite overkill while a simple command is available to toggle between the old and new ID (Solaris fdisk).

When in failsafe mode, you are given the choice to mount the / partition at boot time. If it is mounted read-only, you can remount it without the r/o option to be able to fix the menu.lst file.

Not only that, but because i was not able to boot solaris
.

I have already mounted as read and write, but what editor should I use to open menu.lst for modification ?

Regards

I was understanding you were still able to boot Solaris from your previous replies.
So using Solaris partition as a Linux swap area, even without Linux swapping at all, was destructive as I was strongly suspecting.
This is a text file. I personally use either vi or one of its clones but any editor should work.

I was not able to boot solaris.

After answering 'yes' to the 'updated archives' question, your real disk-based root file system should be mounted on /a

I tried :

vi /boot/grub/menu.lst

but command not found

You could have made that clearer when I asked you about it:
http://www.linuxquestions.org/questi...05#post2975405
I doubt miniroot has no vi command. I'll check next time I reboot.

Anyway, I'm afraid you are editing your CD or DVD menu.lst, which obviously stay on a read-only filesystem, regardless of you beeing root or not.

As the message tells, use /a/boot/grub/menu.lst.

You are right. What I did I had created two threads on the same time, one of them under Linux and other under Solaris (the one that you was answering)

http://www.linuxquestions.org/questi...ess-ce-602130/

http://www.linuxquestions.org/questi...0/#post2978353

I did not like to ask many questions on one thread, and as you have noticed both links have different titles, but both threads went to other directions when there were chnaging in Solaris partition to Linux swap.


I did that with a, but I forgot to write " a " in my reply.

I am editing exactly this file : /a/boot/grub/menu.lst


I had used vi /a/boot/grub/menu.lst,,,,,but it does allow me to save , quit,,,,it not the same behaivor , when we use vi under Solaris or Linux when they are in a normal mode

Thanks

I already suggested that could be the issue but again, is "/a" mounted read/write or read/only ?

Have a look at the "mount" command output to check it.

I have answered above question in my previous reply.

Because I typed in : Y (for Yes) when I received the message in the quote below

I will check that again for confirmation

Then, what are the menu.lst permissions ?

-rw-r--r--

Post these commands output:

Before I post the output for :
mount | grep `df -k /a/boot|nawk '{print $1}' | tail +2`
truss touch /a/boot/grub/menu.lst

What I did I changed the permission for the : /a/boot/grub/menu.lst (I understood that implicitly from your advice, which was : " what are the menu.lst permissions " )

Then I used vi /a/boot/grub/menu.lst,,,,,and hardly (because vi in this mode not like vi in a normal mode,,,,I was able to modify the menu.lst, but i was not able to save that after modification!!!!!!) I was able to save the edited menu.lst.

Do I still need to post the output for the commands that you have mentioned above ?

So what were the permissions like before you changed them ?
Can you explain what you mean by "this mode" ?
Hmm, so were you able to save or not ?

I meant in the miniroot mode.
When I used vi in the miniroot mode (I called it: " this mode ", I meant failsafe mode), it is unlike when you use it in the normal operation for Solaris , when it boots.

It seems to me yes, thereforw I would have been able to boot solaris in normal mode (not failsafe mode)