changing grub

[Ray Parrish]

Leonard Chatagnier wrote:
> --- On Sat, 4/4/09, Ray Parrish <crp at cmc.net> wrote:
>
>   
>> From: Ray Parrish <crp at cmc.net>
>> Subject: Re: changing grub
>> To: "Ubuntu user technical support, not for general discussions" <ubuntu-users at lists.ubuntu.com>
>> Date: Saturday, April 4, 2009, 7:30 AM
>> Derek Broughton wrote:
>>     
>>> Knute Johnson wrote:
>>>
>>>   
>>>       
>>>> Vincent Trouilliez wrote:
>>>>     
>>>>         
>>>>> On Sat, 28 Mar 2009 10:50:10 -0600
>>>>> Gary Kirkpatrick <pegngary at gmail.com>
>>>>>           
>> wrote:
>>     
>>>>>       
>>>>>           
>>>>>> My wife wants windows to be the first
>>>>>>             
>> loading choice when grub comes up
>>     
>>>>>> (shame on her!).  Is there a way to do
>>>>>>             
>> that?
>>     
>>>>>>         
>>>>>>             
>>>>> Yep, just edit this file:
>>>>>
>>>>> /boot/grub/menu.lst
>>>>>
>>>>>       
>>>>>           
>>>> The option is the;
>>>>
>>>> default             0
>>>>
>>>> change it to the number of your windows entry.  If
>>>>         
>> you update and add a
>>     
>>>> kernel, you will have to do this again.
>>>>     
>>>>         
>>> Actually, not.  As menu.lst says:
>>>
>>> # Put static boot stanzas before and/or after
>>>       
>> AUTOMAGIC KERNEL LIST
>>     
>>> ### BEGIN AUTOMAGIC KERNELS LIST
>>> ## lines between the AUTOMAGIC KERNELS LIST markers
>>>       
>> will be modified
>>     
>>> ## by the debian update-grub script except for the
>>>       
>> default options below
>>     
>>> So, what you do if you _must_ have Windows first (and
>>>       
>> can't get a
>>     
>>> divorce...) is move the Windows stanza _before_ the
>>>       
>> AUTOMAGIC KERNELS, and
>>     
>>> then it will always be the first option.
>>>   
>>>       
>> Hello,
>>
>> Just wanted to address a small fine point here. When
>> starting a GUI 
>> application with root privileges, such as gedit you need to
>> use the gksu 
>> command on the start of the line, not the sudo command,
>> which is used 
>> for command line programs. so the earlier given command to
>> edit menu.lst 
>> should be -
>>
>> gksu gedit /boot/grub/menu.lst &
>>
>> I have also added an "&" on the end of the
>> command line, which will 
>> cause gedit to fork away from the Terminal session, so that
>> shutting 
>> down the Terminal window will not also shut down your gedit
>> session, 
>> which is will do, without the & on the end of the line.
>> If however, you 
>> want any error messages generated by gedit to be printed to
>> the terminal 
>> window, leave off the &, and leave the Terminal window
>> open until you 
>> are done with gedit.
>>
>> The reason for my clarification of this point is that in my
>> experience, 
>> attempting to start a GUI program with sudo usually will
>> not start the 
>> program. You issue the command, get prompted for your
>> password in 
>> terminal, then nothing happens after that.
>>
>> Later, Ray Parrish
>>
>>     
> Very strange, to me anyway, that you said and experienced what you did above.  Although, I've read on the list about using gksu ipo sudo for gui applications, I've never had an issue using sudo nano to edit any type of file using Kubuntu desktop anyway. I rarely use gnome as I like the kubuntu eye candy better but of course in an Ubuntu install. I don't understand the need for the &, why would anyone stop a terminal session while editing from it? Even if stopped by error, it's simle to restart it and continue. Gnome, or the Ubuntu Desktop, may react differently than the Kubuntu Desktop, I really don't know. Nano is the default editor for Kubuntu and works well for me in an Ubuntu install. I am using Kensole or a tty terminal in reference to what I've said.  Just another persons viewpoint.
> Leonard Chatagnier
> lenc5570 at sbcglobal.net
>   
Hello,

You're mixing apples and oranges there. nano is a command line editor 
which only works within terminal, not a true GUI editor like gedit, so 
of course it starts just fine with sudo. Maybe in Kubuntu they have 
expanded nano into an application that can run in it's own GUI window, 
but on Ubuntu, it's just an application which runs only within a 
Terminal window.

As to using the "&" with gedit, I sometimes want to use gedit for quite 
a while on more than one file in root mode, but have no need to keep the 
Terminal window open past the initial use of it to get gedit started in 
root mode. I'm not editing from the terminal window, I'm using a GUI 
application to do the editing. So, if I don't use the "&" and then close 
Terminal, it will close gedit before I'm ready for it to.

I much prefer the full use of the mouse and other GUI niceties when I'm 
editing files, so I always use gedit, instead of any of the command line 
editors like pine, nano, etc... with all of their unusual key combos 
needed to control them. 8-)

Later, Ray Parrish

-- 
Human reviewed index of links about the computer
http://www.rayslinks.com
Poetry from the mind of a Schizophrenic
http://www.writingsoftheschizophrenic.com/