public inbox for blinux-list@redhat.com
 help / color / mirror / Atom feed
From: "L. C. Robinson" <lcr@onewest.net>
To: BLinux List <blinux-list@redhat.com>
Subject: Re: Getting rid of Linux
Date: Fri, 4 Oct 2002 16:31:49 -0600 (MDT)	[thread overview]
Message-ID: <Pine.LNX.4.44.0210041447440.968-100000@rupin.localnet> (raw)
In-Reply-To: <OE70ylB1Ehu6WPvMDqs0000a109@hotmail.com>

On Thu, 3 Oct 2002, hotmail wrote:

> ... the computer boots, Grub gives me a list of
> RedHat or Windows. And if I do not choose then
> RedHat will load.

You could make windoze the default.

> Windows 98 is on drive C and Linux  uses the
> rest of the HD. I am told That I should
> uninstall Grub before deleteing the Linux
> partation. How do I uninstall Grub?

Why bother?  It will boot windoze in any event.  I
use lilo, not grub, so I don't know the details
(I'd have to look it up for you, in the
documentation, which I'm not inclined to do).
But you intend on deleting grub with the linux
partition, based on your comments later on.
Restore the mbr, using whatever windoze uses for
this.

> I am told that I can run FDISK to delete the
> Linux partition. How do I run FDISK?

Given the context here, you are asking for windoze
support from the wrong forum: off topic for this
list.  Interesting that you would want to junk
linux, instead of the other way around, which is
the usual eventuality for most users, if they have
made a reasonable effort with linux.  But we don't
really know what you plan on doing with your
computer, and in what context, or why.  Did you
see the recent posts on the superiority of linux
for blind users (the Red Hat 8.0 related thread)?

>  I assume Ineed sited assistance to use FDISK. i
>  am not familular With FDISK, (I Have only used
>  FDISK once), so instructions please?

Use the fdisk with windoze, or some other utility
from that sorry, insecure, toy OS.  A competent
user could use linux fdisk from a rescue disk, but
would still use the utilities of the OS that was
to use the space.

>  I wish to delete the Linux partition and extend
>  drive c to use the whole HD.

A mistake <grin>.  When Microsoft's broken
business model becomes painfully evident to
everyone in the near future, will you be forced to
reverse this process?  Their highest executives
have at long last been forced to publicly admit to
their problems (especially their gigantic and
probably unfixable security design fiasco), and
their inability to meet the linux threat.  It's
just a matter of time.  

Post your request in an M$ advocacy forum.
They'll love it, and you'll get plenty of eager
answers.  For even more fun, you could light a
fuse in comp.os.linux.advocacy -- uh, no,
never mind.  I should be ashamed of myself for
even thinking of it.

-- L. C. Robinson
reply to no_spam+munged_lcr@onewest.net.invalid

People buy MicroShaft for compatibility, but get
incompatibility and instability instead.  This is
award winning "innovation".  Find out how MS holds
your data hostage with "The *Lens*"; see
"CyberSnare" at
http://www.netaction.org/msoft/cybersnare.html




      reply	other threads:[~ UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 hotmail
 ` L. C. Robinson [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Pine.LNX.4.44.0210041447440.968-100000@rupin.localnet \
    --to=lcr@onewest.net \
    --cc=blinux-list@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).