public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "mirabilos" <eccesys@topmail.de>
To: <Wayne.Brown@altec.com>, "Thomas Dodd" <ted@cypress.com>,
	"John Madden" <weez@freelists.org>,
	"Petr Vandrovec" <VANDROVE@vc.cvut.cz>,
	"Jesper Juhl" <juhl@eisenstein.dk>,
	"Dax Kelson" <dax@gurulabs.com>,
	"Aaron Lunansky" <alunansky@rim.net>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: Current status of NTFS support
Date: Sat, 21 Apr 2001 12:19:23 -0000	[thread overview]
Message-ID: <021601c0ca5d$4e3c0720$de00a8c0@homeip.net> (raw)
In-Reply-To: <86256A34.00808239.00@smtpnotes.altec.com>

> Thanks to all who offered suggestions, both on the list and privately.
Rather
> than answer them all individually, I'm going to respond in this one
message.
>
> Unfortunately the upgrade is not going to be done by me, but by our PC
support
> team.  Our laptops originally were set up with two FAT32 partitions:
a small
> one for Win98 and applications, and a large one for data files.  I
used FIPS to
> carve off most of the large one for a swap partition and an ext2
partition.
> Now, because of the larger space requirements of Win2000, they're
going to wipe
> out everything on the drives and start from scratch.  They'll be doing
all our
> laptops in a short period of time, and want to do all of them the same
way.
>
> >From everything I've been told here, it sounds like my best bet is to
try and
> talk them into replacing the two FAT32 partitions (which are
contiguous) with
> one big one and leave my Linux partitions alone.  That way I won't
have to deal
> with NTFS at all.  Fortunately, one of the PC support guys ought to be
> sympathetic; he runs Linux at home and has asked me for advice in
getting it set
> up on his laptop, too.  I'll see if I can talk him into doing my
machine
> differently from the others.  I have to be careful, though; my Linux
use at work
> is tolerated, but not (yet) encouraged, and I don't want to rock the
boat too
> much.
>
> Thanks again to everyone.
>
> Wayne

I would, if it goes all wrong, just copy all the stuff from NTFS over
network
to your home PC (linux boot floppy, NTFS r/o mount), use a windoze boot
floppy
to create FAT32 partitions, get a FAT32 NT boot sector from somewhere
(or use
the Recovery Console which I find great) and copy it back over network.
This should run without any serious problems.

-mirabilos



  reply	other threads:[~2001-04-21 12:19 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-20 23:23 Current status of NTFS support Wayne.Brown
2001-04-21 12:19 ` mirabilos [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-04-20 22:08 Wayne.Brown
2001-04-20 22:31 ` Jesper Juhl
2001-04-20 22:33 ` Thomas Dodd
2001-04-20 23:48 ` Anton Altaparmakov
2001-04-20 23:52 ` Anton Altaparmakov
2001-04-20 23:55 ` Robert Szentmihalyi
2001-04-21  1:18   ` Lee Leahu
2001-04-21  1:34     ` J. Dow
2001-04-21  1:39     ` Doug McNaught
2001-04-21  2:07       ` Lee Leahu
2001-04-21  2:30         ` Tom Leete
2001-04-21  9:23       ` Anton Altaparmakov
2001-04-21  2:35 ` Ben Ford
2001-04-21  9:53 ` Dan Podeanu
2001-04-21 10:35 ` lk
2001-04-22 14:42 ` Pavel Machek

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='021601c0ca5d$4e3c0720$de00a8c0@homeip.net' \
    --to=eccesys@topmail.de \
    --cc=VANDROVE@vc.cvut.cz \
    --cc=Wayne.Brown@altec.com \
    --cc=alunansky@rim.net \
    --cc=dax@gurulabs.com \
    --cc=juhl@eisenstein.dk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ted@cypress.com \
    --cc=weez@freelists.org \
    /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