RE: [expert] ram issue(continued)
Right On -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of b5dave Sent: Thursday, January 18, 2001 10:50 PM To: [EMAIL PROTECTED] Subject: RE: [expert] ram issue(continued) chronos, I'll tell you right off the bat that I'm in a real foul mood tonight, and I'm not at all certain why. But responding to your post might be theraputic (sp??). #1: The ability to edit files is essential in any Unix variant, be it Linux, Solaris, BSD, etc, etc. #2: The Operating systems mentioned or suggested in #1 are only suitable for those people who have the willingness and ability to learn how to edit files (at the very least!) #3: Most of the people in the world do not have either the willingness nor the ability to learn how to edit a file. #4: Your posts suggest that you are like most of the people in the world. #5: Most of the people in the world would find Windows or the Macintosh more suitable. #6: As #5 will have many people on this list in fits, just let me say that for every computer literate type, there are two associated parents, four associated grandparents, innumerable sisters and brothers, cousins, nieces and nephews, etc. To suggest that tech savy, or even semi-competent computer users are in the minority should be both an obvious and trivial observation. #7: Given #1 - #6, and if they obtain in your case, I think it's reasonable to ask why *you* are choosing the Linux route? I know my mother is far from being expert "pointer-and-clicker", yet even the expert "pointers-and-clickers" from the Windows world, as certified and highly paid as they sometimes are, are completely lost when computer use means brain use. #8: In Linux, computer use means brain use. In Windows, that is not necessarily the case. If you want your computer to be nice & easy, then , by all means, stick with Windows. That is what Windows was meant for. The same goes for the Mac. Just because Linux users need to be be at least semi-smart is no reason why you should be denied a satisfying PC experience. Microsoft and Apple design computers for most of the people in the world, people just like you. Peace b5dave. On 19-Jan-2001 chronos . wrote: > To Chris- > No I have absolutly no experience editing files. So go flame away. I am > a newbie and I dont understand sue me. > You started somewhere too. Kick me off the list for all I care. Excuse > me for not being a genius. > On Thu, 18 Jan 2001 15:00:05 -0500 "D. Stark - eSN" > <[EMAIL PROTECTED]> wrote: >>Except I think the fella is using grub. >> >>Chronos: >> >>First off, run this from a command line: >> >>[dstart@fweeble ~]$ cat /etc/lilo.conf >> >>Just the cat part, mind you. If you DON'T have a file called >>/etc/lilo.conf, >>you installed grub as your boot loader. All of the great advice >>everybody >>has offered up to this point is for naught. Were I you, at this point, >>I'd >>say screw it all and reinstall, this time choosing LILO as your boot >>loader >>(why did Mandrake include grub? freedom of choice?). Were I you. Who >>knows, >>it may solve the ram issue. If it doesn't then Chris' great advice >>below >>will work. >> >>You're a newbie, I betcha. Don't worry, we all start somewhere. I was >>lucky >>enough to room with a net.god in college. I know sending people to >>LinuxDoc.org is my answer to most tech questions, but you might want to >>spend some time reading up here: >> >>http://linuxdoc.org/LDP/gs/ >> >>also: >> >>http://63.209.80.231/en/doc/72/en/ref.html/index.html (mandrake users >>manual) >> >>Seriously, a good place to go to keep from killing yourself. If you >>would >>like a good deadtree guide, check out O'Rielly's >>_Learning_the_UNIX_Operating_System_. It's a very good book to get you >>up to >>speed on the basics. From there the specifics become a lot easier to >>handle. >>Make sure to learn to use 'grep' and 'less' as well. They're your >>friends. >> >>Derek Stark >>IT / Linux Admin >>eSupportNow >>xt 8952 >> >>-Original Message- >>From: [EMAIL PROTECTED] >>[mailto:[EMAIL PROTECTED]]On Behalf Of Chris Spencer >>Sent: Thursday, January 18, 2001 2:29 PM >>To: [EMAIL PROTECTED] >>Subject: Re: [expert] ram issue(continued) >> >> >>On 18 Jan 2001, chronos . wrote: >> >>> Hi all, >>> I`m running mandrake 7.1 and I have 128 for ram but it only sees 64 >>> of my >>128. I went to mandrakeuser.org and found the following- edit tittle >>linux >>kernel (hd0,0)/boot/vml
RE: [expert] ram issue(continued)
chronos, I'll tell you right off the bat that I'm in a real foul mood tonight, and I'm not at all certain why. But responding to your post might be theraputic (sp??). #1: The ability to edit files is essential in any Unix variant, be it Linux, Solaris, BSD, etc, etc. #2: The Operating systems mentioned or suggested in #1 are only suitable for those people who have the willingness and ability to learn how to edit files (at the very least!) #3: Most of the people in the world do not have either the willingness nor the ability to learn how to edit a file. #4: Your posts suggest that you are like most of the people in the world. #5: Most of the people in the world would find Windows or the Macintosh more suitable. #6: As #5 will have many people on this list in fits, just let me say that for every computer literate type, there are two associated parents, four associated grandparents, innumerable sisters and brothers, cousins, nieces and nephews, etc. To suggest that tech savy, or even semi-competent computer users are in the minority should be both an obvious and trivial observation. #7: Given #1 - #6, and if they obtain in your case, I think it's reasonable to ask why *you* are choosing the Linux route? I know my mother is far from being expert "pointer-and-clicker", yet even the expert "pointers-and-clickers" from the Windows world, as certified and highly paid as they sometimes are, are completely lost when computer use means brain use. #8: In Linux, computer use means brain use. In Windows, that is not necessarily the case. If you want your computer to be nice & easy, then , by all means, stick with Windows. That is what Windows was meant for. The same goes for the Mac. Just because Linux users need to be be at least semi-smart is no reason why you should be denied a satisfying PC experience. Microsoft and Apple design computers for most of the people in the world, people just like you. Peace b5dave. On 19-Jan-2001 chronos . wrote: > To Chris- > No I have absolutly no experience editing files. So go flame away. I am > a newbie and I dont understand sue me. > You started somewhere too. Kick me off the list for all I care. Excuse > me for not being a genius. > On Thu, 18 Jan 2001 15:00:05 -0500 "D. Stark - eSN" > <[EMAIL PROTECTED]> wrote: >>Except I think the fella is using grub. >> >>Chronos: >> >>First off, run this from a command line: >> >>[dstart@fweeble ~]$ cat /etc/lilo.conf >> >>Just the cat part, mind you. If you DON'T have a file called >>/etc/lilo.conf, >>you installed grub as your boot loader. All of the great advice >>everybody >>has offered up to this point is for naught. Were I you, at this point, >>I'd >>say screw it all and reinstall, this time choosing LILO as your boot >>loader >>(why did Mandrake include grub? freedom of choice?). Were I you. Who >>knows, >>it may solve the ram issue. If it doesn't then Chris' great advice >>below >>will work. >> >>You're a newbie, I betcha. Don't worry, we all start somewhere. I was >>lucky >>enough to room with a net.god in college. I know sending people to >>LinuxDoc.org is my answer to most tech questions, but you might want to >>spend some time reading up here: >> >>http://linuxdoc.org/LDP/gs/ >> >>also: >> >>http://63.209.80.231/en/doc/72/en/ref.html/index.html (mandrake users >>manual) >> >>Seriously, a good place to go to keep from killing yourself. If you >>would >>like a good deadtree guide, check out O'Rielly's >>_Learning_the_UNIX_Operating_System_. It's a very good book to get you >>up to >>speed on the basics. From there the specifics become a lot easier to >>handle. >>Make sure to learn to use 'grep' and 'less' as well. They're your >>friends. >> >>Derek Stark >>IT / Linux Admin >>eSupportNow >>xt 8952 >> >>-Original Message- >>From: [EMAIL PROTECTED] >>[mailto:[EMAIL PROTECTED]]On Behalf Of Chris Spencer >>Sent: Thursday, January 18, 2001 2:29 PM >>To: [EMAIL PROTECTED] >>Subject: Re: [expert] ram issue(continued) >> >> >>On 18 Jan 2001, chronos . wrote: >> >>> Hi all, >>> I`m running mandrake 7.1 and I have 128 for ram but it only sees 64 >>> of my >>128. I went to mandrakeuser.org and found the following- edit tittle >>linux >>kernel (hd0,0)/boot/vmlinuz root=dev/hda1 then append mem=128M to the >>end of >>it. The problem is I type pico then tittle linux and it gives me a new >>file >>then I type kernel etc. and all it does is places a file
RE: [expert] ram issue(continued)
Honestly, the information Chris provided has to be the best and most thorough answer I've ever seen. He is also right, I kept seeing the same message and the same replies over and over again. Look, I don't think you have any right to get angry with him. And I also think you do need to spend some time reading the documentation. Or at least reviewing things during install. During install, you were asked to verify what Mandrake detected for your RAM. If the actual amount was different, you were supposed to type it in there. Thanks > To Chris- > No I have absolutly no experience editing files. So go flame away. I am a newbie and >I dont understand sue me. > You started somewhere too. Kick me off the list for all I care. Excuse me for not >being a genius. > On Thu, 18 Jan 2001 15:00:05 -0500 "D. Stark - eSN" <[EMAIL PROTECTED]> wrote: > >Except I think the fella is using grub. > > > >Chronos: > > > >First off, run this from a command line: > > > >[dstart@fweeble ~]$ cat /etc/lilo.conf > > > >Just the cat part, mind you. If you DON'T have a file called /etc/lilo.conf, > >you installed grub as your boot loader. All of the great advice everybody > >has offered up to this point is for naught. Were I you, at this point, I'd > >say screw it all and reinstall, this time choosing LILO as your boot loader > >(why did Mandrake include grub? freedom of choice?). Were I you. Who knows, > >it may solve the ram issue. If it doesn't then Chris' great advice below > >will work. > > > >You're a newbie, I betcha. Don't worry, we all start somewhere. I was lucky > >enough to room with a net.god in college. I know sending people to > >LinuxDoc.org is my answer to most tech questions, but you might want to > >spend some time reading up here: > > > >http://linuxdoc.org/LDP/gs/ > > > >also: > > > >http://63.209.80.231/en/doc/72/en/ref.html/index.html (mandrake users > >manual) > > > >Seriously, a good place to go to keep from killing yourself. If you would > >like a good deadtree guide, check out O'Rielly's > >_Learning_the_UNIX_Operating_System_. It's a very good book to get you up to > >speed on the basics. From there the specifics become a lot easier to handle. > >Make sure to learn to use 'grep' and 'less' as well. They're your friends. > > > >Derek Stark > >IT / Linux Admin > >eSupportNow > >xt 8952 > > > >-Original Message- > >From: [EMAIL PROTECTED] > >[mailto:[EMAIL PROTECTED]]On Behalf Of Chris Spencer > >Sent: Thursday, January 18, 2001 2:29 PM > >To: [EMAIL PROTECTED] > >Subject: Re: [expert] ram issue(continued) > > > > > >On 18 Jan 2001, chronos . wrote: > > > >> Hi all, > >> I`m running mandrake 7.1 and I have 128 for ram but it only sees 64 of my > >128. I went to mandrakeuser.org and found the following- edit tittle linux > >kernel (hd0,0)/boot/vmlinuz root=dev/hda1 then append mem=128M to the end of > >it. The problem is I type pico then tittle linux and it gives me a new file > >then I type kernel etc. and all it does is places a file in my home > >directory under root. Ctrl W does not work. When I type pico kernel etc. by > >itself it says unexpected token (h and exits. How do I edit this file ? > >There has to be a way to edit this. Keep in mind I`m no genius here so I > >need pretty much exact instructions on what to do. Ie type pico then > >whatever I need to edit the file. > > > >Chronos, > > > >I have seen you post this question numerous times and I've seen people > >answer you with some very good answers. With all due respect, there comes > >a time when you need to think for yourself and work with the instructions > >that have been given to you. You want to edit a file? How would you do it > >in DOS? Typing in 'edit' isn't going to magically open up the file you > >want to modify. Typing in edit will. These are basic concepts > >of computer usuage that, no matter what operating system you are using, do > >the job. > > > >That said I am going to settle this once and for all. If you have problems > >following these instructions then I cannot help you any further. > > > >If you are using KDE or Gnome, login as root; Go to Programs->Editors->and > >pick whatever editor you want. Go to File->Open; Change the directory to > >/etc (ie: if the default is /root, go up a dir level to /, then click on > >/etc). Double-click on the file lilo.conf. About 10 lines down you will > >
Re: [expert] ram issue(continued)
> No I have absolutly no experience editing files. So go flame away. I am a newbie and >I dont understand sue me. You started somewhere too. Kick me off the list for all I >care. Excuse me for not being a genius. Whether you're a genius or not is irrelevant. Having an attitude like the one you're demonstrating is sure, however, to cause all the help available in this conference to just pass you by. Cheers --- Larry
Re: [expert] ram issue(continued)
I tried grub for a VERY brief time. I then simply replaced it by running lilo. I didn't have to do anything fancy-schamancy, just ran lilo - it eliminated grub and next time I rebooted, there was lilo. On Thursday 18 January 2001 06:01 pm, you wrote: > To Chris- > No I have absolutly no experience editing files. So go flame away. I am a > newbie and I dont understand sue me. You started somewhere too. Kick me off > the list for all I care. Excuse me for not being a genius. > > On Thu, 18 Jan 2001 15:00:05 -0500 "D. Stark - eSN" <[EMAIL PROTECTED]> wrote: > >Except I think the fella is using grub. > > > >Chronos: > > > >First off, run this from a command line: > > > >[dstart@fweeble ~]$ cat /etc/lilo.conf > > > >Just the cat part, mind you. If you DON'T have a file called > > /etc/lilo.conf, you installed grub as your boot loader. All of the great [...]
RE: [expert] ram issue(continued)
To Chris- No I have absolutly no experience editing files. So go flame away. I am a newbie and I dont understand sue me. You started somewhere too. Kick me off the list for all I care. Excuse me for not being a genius. On Thu, 18 Jan 2001 15:00:05 -0500 "D. Stark - eSN" <[EMAIL PROTECTED]> wrote: >Except I think the fella is using grub. > >Chronos: > >First off, run this from a command line: > >[dstart@fweeble ~]$ cat /etc/lilo.conf > >Just the cat part, mind you. If you DON'T have a file called /etc/lilo.conf, >you installed grub as your boot loader. All of the great advice everybody >has offered up to this point is for naught. Were I you, at this point, I'd >say screw it all and reinstall, this time choosing LILO as your boot loader >(why did Mandrake include grub? freedom of choice?). Were I you. Who knows, >it may solve the ram issue. If it doesn't then Chris' great advice below >will work. > >You're a newbie, I betcha. Don't worry, we all start somewhere. I was lucky >enough to room with a net.god in college. I know sending people to >LinuxDoc.org is my answer to most tech questions, but you might want to >spend some time reading up here: > >http://linuxdoc.org/LDP/gs/ > >also: > >http://63.209.80.231/en/doc/72/en/ref.html/index.html (mandrake users >manual) > >Seriously, a good place to go to keep from killing yourself. If you would >like a good deadtree guide, check out O'Rielly's >_Learning_the_UNIX_Operating_System_. It's a very good book to get you up to >speed on the basics. From there the specifics become a lot easier to handle. >Make sure to learn to use 'grep' and 'less' as well. They're your friends. > >Derek Stark >IT / Linux Admin >eSupportNow >xt 8952 > >-Original Message- >From: [EMAIL PROTECTED] >[mailto:[EMAIL PROTECTED]]On Behalf Of Chris Spencer >Sent: Thursday, January 18, 2001 2:29 PM >To: [EMAIL PROTECTED] >Subject: Re: [expert] ram issue(continued) > > >On 18 Jan 2001, chronos . wrote: > >> Hi all, >> I`m running mandrake 7.1 and I have 128 for ram but it only sees 64 of my >128. I went to mandrakeuser.org and found the following- edit tittle linux >kernel (hd0,0)/boot/vmlinuz root=dev/hda1 then append mem=128M to the end of >it. The problem is I type pico then tittle linux and it gives me a new file >then I type kernel etc. and all it does is places a file in my home >directory under root. Ctrl W does not work. When I type pico kernel etc. by >itself it says unexpected token (h and exits. How do I edit this file ? >There has to be a way to edit this. Keep in mind I`m no genius here so I >need pretty much exact instructions on what to do. Ie type pico then >whatever I need to edit the file. > >Chronos, > >I have seen you post this question numerous times and I've seen people >answer you with some very good answers. With all due respect, there comes >a time when you need to think for yourself and work with the instructions >that have been given to you. You want to edit a file? How would you do it >in DOS? Typing in 'edit' isn't going to magically open up the file you >want to modify. Typing in edit will. These are basic concepts >of computer usuage that, no matter what operating system you are using, do >the job. > >That said I am going to settle this once and for all. If you have problems >following these instructions then I cannot help you any further. > >If you are using KDE or Gnome, login as root; Go to Programs->Editors->and >pick whatever editor you want. Go to File->Open; Change the directory to >/etc (ie: if the default is /root, go up a dir level to /, then click on >/etc). Double-click on the file lilo.conf. About 10 lines down you will >see something that looks like this: > >image=/boot/vmlinuz > label=linux > root=/dev/hdx > initrd="/boot/initrd-2.2.17-mdk.img > append " hdg=ide-scsi ide3=autotune ide2=autotune" > >See the append line? No, its not going to look exactly the same as whats >in this email but thats the line you're looking for. Inside the quotation >marks INSERT the mem=128M statement. So that now it will look something >like this: > > append "mem=128M hdg=ide-scsi ide3=autotune ide2=autotune" > >Do not change anything else. Save the changes and exit the editor. Now >open a terminal window and type in: lilo and hit your enter key. If you >get errors you made a typo. Follow the instructions about and fix your >error. Re-run lilo when done. Once you get no errors, reboot your >machine. > >If you are not running KDE or Gnome, then login as root. Type in the >command cd
Re: [expert] ram issue(continued)
On Thursday 18 January 2001 10:44 am, you wrote: > Hi all, > I`m running mandrake 7.1 and I have 128 for ram but it only sees 64 of my > 128. I went to mandrakeuser.org and found the following- edit tittle linux > kernel (hd0,0)/boot/vmlinuz root=dev/hda1 then append mem=128M to the end > of it. The problem is I type pico then tittle linux and it gives me a new > file then I type kernel etc. and all it does is places a file in my home > directory under root. Ctrl W does not work. When I type pico kernel etc. by > itself it says unexpected token (h and exits. How do I edit thi file ? > There has to be a way to edit this. Keep in mind I`m no genius here so I > need pretty much exact instructions on what to do. Ie type pico then > whatever I need to edit the file. Thank you, > Chronos Probably the easiest way to edit the file is to use "kedit" from within KDE. The file is found at /boot/grub/menu.lst. Yuo can navigate to the file using your file manager (Konquerer) and right click on it and choose "open With" then type in kedit. PATH to FILE= /boot/grub FILE= menu.lst Hope this helps, -- Ken Thompson Electrocom Computer Services Payette, Idaho Ph. (208) 642-7101 - 1- (888) 642-7101 Web: http://www.nwaa.com Email: [EMAIL PROTECTED]
RE: [expert] ram issue(continued)
Except I think the fella is using grub. Chronos: First off, run this from a command line: [dstart@fweeble ~]$ cat /etc/lilo.conf Just the cat part, mind you. If you DON'T have a file called /etc/lilo.conf, you installed grub as your boot loader. All of the great advice everybody has offered up to this point is for naught. Were I you, at this point, I'd say screw it all and reinstall, this time choosing LILO as your boot loader (why did Mandrake include grub? freedom of choice?). Were I you. Who knows, it may solve the ram issue. If it doesn't then Chris' great advice below will work. You're a newbie, I betcha. Don't worry, we all start somewhere. I was lucky enough to room with a net.god in college. I know sending people to LinuxDoc.org is my answer to most tech questions, but you might want to spend some time reading up here: http://linuxdoc.org/LDP/gs/ also: http://63.209.80.231/en/doc/72/en/ref.html/index.html (mandrake users manual) Seriously, a good place to go to keep from killing yourself. If you would like a good deadtree guide, check out O'Rielly's _Learning_the_UNIX_Operating_System_. It's a very good book to get you up to speed on the basics. From there the specifics become a lot easier to handle. Make sure to learn to use 'grep' and 'less' as well. They're your friends. Derek Stark IT / Linux Admin eSupportNow xt 8952 -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Chris Spencer Sent: Thursday, January 18, 2001 2:29 PM To: [EMAIL PROTECTED] Subject: Re: [expert] ram issue(continued) On 18 Jan 2001, chronos . wrote: > Hi all, > I`m running mandrake 7.1 and I have 128 for ram but it only sees 64 of my 128. I went to mandrakeuser.org and found the following- edit tittle linux kernel (hd0,0)/boot/vmlinuz root=dev/hda1 then append mem=128M to the end of it. The problem is I type pico then tittle linux and it gives me a new file then I type kernel etc. and all it does is places a file in my home directory under root. Ctrl W does not work. When I type pico kernel etc. by itself it says unexpected token (h and exits. How do I edit this file ? There has to be a way to edit this. Keep in mind I`m no genius here so I need pretty much exact instructions on what to do. Ie type pico then whatever I need to edit the file. Chronos, I have seen you post this question numerous times and I've seen people answer you with some very good answers. With all due respect, there comes a time when you need to think for yourself and work with the instructions that have been given to you. You want to edit a file? How would you do it in DOS? Typing in 'edit' isn't going to magically open up the file you want to modify. Typing in edit will. These are basic concepts of computer usuage that, no matter what operating system you are using, do the job. That said I am going to settle this once and for all. If you have problems following these instructions then I cannot help you any further. If you are using KDE or Gnome, login as root; Go to Programs->Editors->and pick whatever editor you want. Go to File->Open; Change the directory to /etc (ie: if the default is /root, go up a dir level to /, then click on /etc). Double-click on the file lilo.conf. About 10 lines down you will see something that looks like this: image=/boot/vmlinuz label=linux root=/dev/hdx initrd="/boot/initrd-2.2.17-mdk.img append " hdg=ide-scsi ide3=autotune ide2=autotune" See the append line? No, its not going to look exactly the same as whats in this email but thats the line you're looking for. Inside the quotation marks INSERT the mem=128M statement. So that now it will look something like this: append "mem=128M hdg=ide-scsi ide3=autotune ide2=autotune" Do not change anything else. Save the changes and exit the editor. Now open a terminal window and type in: lilo and hit your enter key. If you get errors you made a typo. Follow the instructions about and fix your error. Re-run lilo when done. Once you get no errors, reboot your machine. If you are not running KDE or Gnome, then login as root. Type in the command cd /etc. Then type in the command pico lilo.conf. Make the same change as described above. Make sure you run lilo after editing the file. Linux isn't much different than Windows or DOS. Most things work exactly the same way. Have you ever editted a file in Windows? Doing it under Linux uses the same principles. -Chris
Re: [expert] ram issue(continued)
On 18 Jan 2001, chronos . wrote: > Hi all, > I`m running mandrake 7.1 and I have 128 for ram but it only sees 64 of my 128. I >went to mandrakeuser.org and found the following- edit tittle linux kernel >(hd0,0)/boot/vmlinuz root=dev/hda1 then append mem=128M to the end of it. The problem >is I type pico then tittle linux and it gives me a new file then I type kernel etc. >and all it does is places a file in my home directory under root. Ctrl W does not >work. When I type pico kernel etc. by itself it says unexpected token (h and exits. >How do I edit this file ? There has to be a way to edit this. Keep in mind I`m no >genius here so I need pretty much exact instructions on what to do. Ie type pico then >whatever I need to edit the file. Chronos, I have seen you post this question numerous times and I've seen people answer you with some very good answers. With all due respect, there comes a time when you need to think for yourself and work with the instructions that have been given to you. You want to edit a file? How would you do it in DOS? Typing in 'edit' isn't going to magically open up the file you want to modify. Typing in edit will. These are basic concepts of computer usuage that, no matter what operating system you are using, do the job. That said I am going to settle this once and for all. If you have problems following these instructions then I cannot help you any further. If you are using KDE or Gnome, login as root; Go to Programs->Editors->and pick whatever editor you want. Go to File->Open; Change the directory to /etc (ie: if the default is /root, go up a dir level to /, then click on /etc). Double-click on the file lilo.conf. About 10 lines down you will see something that looks like this: image=/boot/vmlinuz label=linux root=/dev/hdx initrd="/boot/initrd-2.2.17-mdk.img append " hdg=ide-scsi ide3=autotune ide2=autotune" See the append line? No, its not going to look exactly the same as whats in this email but thats the line you're looking for. Inside the quotation marks INSERT the mem=128M statement. So that now it will look something like this: append "mem=128M hdg=ide-scsi ide3=autotune ide2=autotune" Do not change anything else. Save the changes and exit the editor. Now open a terminal window and type in: lilo and hit your enter key. If you get errors you made a typo. Follow the instructions about and fix your error. Re-run lilo when done. Once you get no errors, reboot your machine. If you are not running KDE or Gnome, then login as root. Type in the command cd /etc. Then type in the command pico lilo.conf. Make the same change as described above. Make sure you run lilo after editing the file. Linux isn't much different than Windows or DOS. Most things work exactly the same way. Have you ever editted a file in Windows? Doing it under Linux uses the same principles. -Chris
Re: [expert] ram issue (continued)
The first letter of the extension of the file is the letter "l", not the number one. You might want to try # pico /boot/grub/menu.[TAB] then you will see what files there are, and you are sure to get one that exists. Buchan "chronos ." wrote: > > Hi all, > I`m using mandrake 7.1 and it only sees 64 of my 128 of ram. I went to >mandrakeuser.org and found the following - edit /boot/grub/menu.1st as root then >"find" kernel (hd0,5)/vmlinuz root=/dev/hda6. I`m supposed to append mem=128 to the >end of that line.I`m using pico to edit the file. Now then ctrl-W does not work. It >asks what file so I tell it the above and it says not found. So what am I looking for >? Typing pico /boot/grub/menu.1st helps me make a file entittled boot. Nothing >more.And then promptly places it in my home root directory. So how do I get to the >actual file linux uses to boot and append to it ? I need very explicit instructions. >Obviously I`m missing something here. > Thank you, Chronos. > > _ > Email your boss can't read - sign up for free disinfo.net email > at http://www.disinfo.com, your gateway to the underground -- |Registered Linux User #182071-| Buchan MilneMechanical Engineer, Network Manager Cellphone * Work +27 82 472 2231 * +27 21 808 2497 Stellenbosch Automotive Engineering http://www.cae.co.za
