Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.user > #229177

Re: Fixing a Grub Foul-up, Not There Yet.

From "Martin McCormick" <martin.m@suddenlink.net>
Newsgroups linux.debian.user
Subject Re: Fixing a Grub Foul-up, Not There Yet.
Date 2020-11-30 18:00 +0100
Message-ID <BgUGS-2pF-1@gated-at.bofh.it> (permalink)
References <BbRTj-6Mo-1@gated-at.bofh.it> <BbVDA-yZ-3@gated-at.bofh.it> <BdGh3-7nD-3@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


I am going to respond to one of my earlier posts as it doesn't
help things at all to spread misinformation which I am guilty of,
here.
"Martin McCormick" <martin.m@suddenlink.net> writes:
>         I appear to be using grub, not grub2.  

	No.  It's grub2.  Old Grub is now grub-legacy and is
probably a dead fly on somebody's wall by now.

>         There's an extra little wrinkle in that, as a computer
> warier who happens to be blind, grub isn't really accessible in
> that you can not get direct access to it via a serial port and
> terminal, say, from another computer that is actually working.

I was simply wrong there.  Of course, one has to have the lines now
in /etc/default/grub that used to be in menu.lst but the idea is
the same.  If one has a serial port which is available at boot
time, grub should work headlessly.

	The issue with the instance of grub that seems to have a
run-time error due to a problem with modules, may be unusual
because it may actually be a goner before it runs since it
doesn't get to load it's modules.

Martin

Back to linux.debian.user | Previous | Next — Previous in thread | Find similar | Unroll thread


Thread

Fixing a Grub Foul-up "Martin McCormick" <martin.m@suddenlink.net> - 2020-11-16 20:00 +0100
  Re: Fixing a Grub Foul-up Dan Ritter <dsr@randomstring.org> - 2020-11-16 20:40 +0100
    Re: Fixing a Grub Foul-up "Martin McCormick" <martin.m@suddenlink.net> - 2020-11-17 04:00 +0100
    Re: Fixing a Grub Foul-up "Martin McCormick" <martin.m@suddenlink.net> - 2020-11-30 05:00 +0100
      Re: Fixing a Grub Foul-up David <bouncingcats@gmail.com> - 2020-12-01 15:40 +0100
        Re: Fixing a Grub Foul-up Solved! "Martin McCormick" <martin.m@suddenlink.net> - 2020-12-01 21:10 +0100
  Re: Fixing a Grub Foul-up John Boxall <jboxall47@gmail.com> - 2020-11-16 20:40 +0100
    Re: Fixing a Grub Foul-up Kenneth Parker <sea7kenp@gmail.com> - 2020-11-17 03:00 +0100
  Re: Fixing a Grub Foul-up David <bouncingcats@gmail.com> - 2020-11-17 00:00 +0100
    Fixing a Grub Foul-up, Not There Yet. "Martin McCormick" <martin.m@suddenlink.net> - 2020-11-21 20:00 +0100
      Re: Fixing a Grub Foul-up, Not There Yet. Felix Miata <mrmazda@earthlink.net> - 2020-11-21 20:40 +0100
        Re: Fixing a Grub Foul-up, Not There Yet. "Martin McCormick" <martin.m@suddenlink.net> - 2020-11-22 00:10 +0100
          Re: Fixing a Grub Foul-up, Not There Yet. Felix Miata <mrmazda@earthlink.net> - 2020-11-22 01:20 +0100
          Re: Fixing a Grub Foul-up, Not There Yet. Kushal Kumaran <kushal@locationd.net> - 2020-11-22 02:10 +0100
      Re: Fixing a Grub Foul-up, Not There Yet. Dan Ritter <dsr@randomstring.org> - 2020-11-22 01:10 +0100
        Re: Fixing a Grub Foul-up, Not There Yet. "Martin McCormick" <martin.m@suddenlink.net> - 2020-11-22 04:50 +0100
      Re: Fixing a Grub Foul-up, Not There Yet. "Martin McCormick" <martin.m@suddenlink.net> - 2020-11-30 18:00 +0100

csiph-web