>> GRUB_DEFAULT=saved
> That's the one. Thanks for the reminder.
You're welcome.
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive:
http://lists.debian.org/6d4219cc1003171940u1b4d4b28qef440a1
On Tue, 16 Mar 2010 21:46:47 -0400 (EDT)
Stephen Powell wrote:
Hello Stephen,
> I'm glad to know that there is a way. Thanks.
YW.
--
Regards _
/ ) "The blindingly obvious is
/ _)radnever immediately apparent"
Now I found you out, I don't think you're so
On Tue, 16 Mar 2010 20:40:43 -0400
Tom H wrote:
Hello Tom,
> GRUB_DEFAULT=saved
That's the one. Thanks for the reminder.
--
Regards _
/ ) "The blindingly obvious is
/ _)radnever immediately apparent"
Life goes quick and it goes without warning
Bombsite B
>>> Again, is there no way to set a default in grub2? Is there no
>>> way, for example, to make the last-booted kernel the default kernel?
>> Modify /etc/default/grub to point to the relevant stanza, then run
>> grub-update. Changes made directly to /boot/grub/grub.cfg will get
>> overwritten nex
On Tue, 16 Mar 2010 14:48:39 -0400 (EDT), Brad Rogers wrote:
> On Tue, 16 Mar 2010 10:29:16 -0400 (EDT), Stephen Powell wrote:
>> Again, is there no way to set a default in grub2? Is there no
>> way, for example, to make the last-booted kernel the default kernel?
>
> Modify /etc/default/grub to p
>> Again, is there no way to set a default in grub2? Is there no
>> way, for example, to make the last-booted kernel the default kernel?
> Modify /etc/default/grub to point to the relevant stanza, then run
> grub-update. Changes made directly to /boot/grub/grub.cfg will get
> overwritten next upd
On Tue, 16 Mar 2010 10:29:16 -0400 (EDT)
Stephen Powell wrote:
Hello Stephen,
> Again, is there no way to set a default in grub2? Is there no
> way, for example, to make the last-booted kernel the default kernel?
Modify /etc/default/grub to point to the relevant stanza, then run
grub-update. C
On Tue, Mar 16, 2010 at 10:17 -0500, Mark Allums wrote:
> On 3/16/2010 8:28 AM, Wolodja Wentland wrote:
>
> >The easiest way would be to enforce a strict naming scheme (maybe with
> >lintian) so the aforementioned code can stay as simple as it is today.
> In the short run, an easy thing to do is
On 3/16/2010 8:28 AM, Wolodja Wentland wrote:
The easiest way would be to enforce a strict naming scheme (maybe with
lintian) so the aforementioned code can stay as simple as it is today.
In the short run, an easy thing to do is remove -trunk- image and all
corresponding packages, as it is a
On Tue, 16 Mar 2010 09:28:18 -0400 (EDT), Wolodja Wentland wrote:
> On Tue, Mar 16, 2010 at 09:03 -0400, Stephen Powell wrote:
>>
>> My guess is that grub2 simply makes a list of all files in /boot which begin
>> with linux-image, sorts them in descending order by the ASCII collating
>> sequence, a
On Tue, Mar 16, 2010 at 09:03 -0400, Stephen Powell wrote:
> On Tue, 16 Mar 2010 08:26:40 -0400 (EDT), Mitchell Laks wrote:
> >
> > I notice that others had problems with grub not updating the kernel
> > from linux-image-2.6.32-trunk-686 to linux-image-2.6.32-3-amd64
> > and I had this same probl
On Tue, Mar 16, 2010 at 07:53 -0500, Ron Johnson wrote:
> On 2010-03-16 07:26, Mitchell Laks wrote:
> Interesting thought. Does the system boot if you manually edit the
> grub config file?
The system boots fine if you select the new (-3-) kernel manually, so I
would think that it would also boot
On Tue, 16 Mar 2010 08:26:40 -0400 (EDT), Mitchell Laks wrote:
>
> I notice that others had problems with grub not updating the kernel
> from linux-image-2.6.32-trunk-686 to linux-image-2.6.32-3-amd64
> and I had this same problem.
>
> I suspect that this is because the heuristic that dpkg or ap
On 2010-03-16 07:26, Mitchell Laks wrote:
I notice that others had problems with grub not updating the kernel
from linux-image-2.6.32-trunk-686 to linux-image-2.6.32-3-amd64
and I had this same problem.
I suspect that this is because the heuristic that dpkg or apt or aptitude update
is using
f
I notice that others had problems with grub not updating the kernel
from linux-image-2.6.32-trunk-686 to linux-image-2.6.32-3-amd64
and I had this same problem.
I suspect that this is because the heuristic that dpkg or apt or aptitude update
is using
finds that linux-image-2.6.32-trunk-686 is gr
Hello,
On Thu, 2009-05-28 at 12:13 +1200, Simon wrote:
>
> We have a fresh install of lenny on a VM
Which VM?
> and tried to perform the initial apt-get update/upgrade but are having
> issues with dependency problems. Can someone point me in the correct
> direction here please?
> # apt-get u
On 16/01/2008, Rick Pasotto <[EMAIL PROTECTED]> wrote:
>
> I am currently running 2.6.22-3-k7 and update to testing daily. I
> seldome reboot but the last several times the grub menu has not
> displayed and the boot messages on the screen are pretty much illegible.
> I can sort of make out the word
I am currently running 2.6.22-3-k7 and update to testing daily. I
seldome reboot but the last several times the grub menu has not
displayed and the boot messages on the screen are pretty much illegible.
I can sort of make out the words but there seems to be some kind of
overlay on the letters makin
problem: on booting grub complains..
> > Error 15: File not found
but ofcourse, the kernel image file exists..
solution(?):
at the grub blue screen,
1. 'e'dit,
2. 'd'elete the "savedefault" line
3. 'b'oot
So I removed the line 'savedefault' from
/boot/grub/menu.lst file. But the next upgrade,
On Wed, Mar 17, 2004 at 10:17:10PM -0500, +* A Death *+ wrote:
> Well the new installer seems to work great ... except its doing
> nothing for me since the boot loader isnt working...
Please report problems with the new installer to debian-boot rather than
debian-user. Except:
> When the current
On Wed, Mar 17, 2004 at 10:17:10PM -0500, +* A Death *+ wrote:
>
> Well the new installer seems to work great ... except its doing
> nothing for me since the boot loader isnt working... no matter what i
> tell grub (take in mind everytime i give it i new install path I have
> to redo the whole ins
Incoming from +* A Death *+:
> Well the new installer seems to work great ... except its doing nothing for
> me since the boot loader isnt working... no matter what i tell grub (take in
> mind everytime i give it i new install path I have to redo the whole install
> (bug problem I assume)) it will
Well the new
installer seems to work great ... except its doing nothing for me since the boot
loader isnt working... no matter what i tell grub (take in mind everytime i give
it i new install path I have to redo the whole install (bug problem I assume))
it will not work I tried everythin
Anita Lewis wrote:
On Sun, 14 Dec 2003 12:27:04 -0600, Damon L. Chesser wrote:
Not at all! I will try something like that to be able to boot Debain.
As of now I have no way to boot the Debian install. since lilo did not
write to the drive. In fact, the installer, might not have correctly
On Sun, 14 Dec 2003 12:27:04 -0600, Damon L. Chesser wrote:
>>
> Not at all! I will try something like that to be able to boot Debain.
> As of now I have no way to boot the Debian install. since lilo did not
> write to the drive. In fact, the installer, might not have correctly
> written (and
Anita Lewis wrote:
On Sun, 14 Dec 2003 10:53:40 + (UTC), Anita Lewis wrote:
On Sat, 13 Dec 2003 21:58:25 -0600, Damon L. Chesser wrote:
I blew up my grub with the debian installer, and it (the installer) does
not rigth lilo to hda. How do I repair my grub? I know the drive
lay-outs
On Sun, 14 Dec 2003 10:53:40 + (UTC), Anita Lewis wrote:
> On Sat, 13 Dec 2003 21:58:25 -0600, Damon L. Chesser wrote:
>> I blew up my grub with the debian installer, and it (the installer) does
>> not rigth lilo to hda. How do I repair my grub? I know the drive
>> lay-outs, I can load knop
If I understand correctly, you've created a grub floppy? If not, you can
download a floppy image file
(http://www.gnu.org/software/grub/grub.html) and use the dd command to
create the floppy. With the floppy, you should be able to boot. You'll
have to manually type the commands (unless you can use
On Sat, 13 Dec 2003 21:58:25 -0600, Damon L. Chesser wrote:
> I blew up my grub with the debian installer, and it (the installer) does
> not rigth lilo to hda. How do I repair my grub? I know the drive
> lay-outs, I can load knoppix chroot and do a grub-floppy. But with the
> floppy then what
I blew up my grub with the debian installer, and it (the installer) does
not rigth lilo to hda. How do I repair my grub? I know the drive
lay-outs, I can load knoppix chroot and do a grub-floppy. But with the
floppy then what do I tell grub? the home of the grub config file is
hda6 (or hd0,
[EMAIL PROTECTED] wrote:
Second Post, don't know if the first made it out or not :)
I messed up the grub on my box with the Debian installer. I know the partioning scheam. I can make a grub-floppy, but can not run grub-install from knoppix. Debian did not write LILO, but did eat up the grub.
Second Post, don't know if the first made it out or not :)
I messed up the grub on my box with the Debian installer. I know the partioning
scheam. I can make a grub-floppy, but can not run grub-install from knoppix. Debian
did not write LILO, but did eat up the grub. I am sure I told it some
On 19 Jan 2000, Lars Weber wrote:
Hi Lars.
> David Teague <[EMAIL PROTECTED]> writes:
> > A GRUB floppy won't boot my old system which has a 486/66, 16 MB
> [...]
>
> I've heard that older versions of GRUB are having problems with ext2
> file-systems created by recent versions of the e2fsprogs.
Hi!
David Teague <[EMAIL PROTECTED]> writes:
> A GRUB floppy won't boot my old system which has a 486/66, 16 MB
> RAM, VL bus mother board, adaptec 2840 with (now) one 1GB scsi drive
> (Bios is enabled on the controller for that drive) and a scsi CD
> ROM. Linux 2.0 is on /dev/sda1, swap is on /
Hi
A GRUB floppy won't boot my old system which has a 486/66, 16 MB
RAM, VL bus mother board, adaptec 2840 with (now) one 1GB scsi drive
(Bios is enabled on the controller for that drive) and a scsi CD
ROM. Linux 2.0 is on /dev/sda1, swap is on /dev/sda2. 2.0.34
Kernel. The kernel is redev'ed
35 matches
Mail list logo
