public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Helge Hafting <helgehaf@aitel.hist.no>
To: Ketil Froyn <ketil-kernel@froyn.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: One disk, one filesystem, no partitions?
Date: Wed, 05 Jun 2002 09:56:24 +0200	[thread overview]
Message-ID: <3CFDC428.E9CB3E80@aitel.hist.no> (raw)
In-Reply-To: <Pine.LNX.4.40L0.0206041716270.1413-100000@ketil.np>

Ketil Froyn wrote:
> 
> Hi.
> 
> I have a question regarding something I came across a while ago. A
> filesystem (reiserfs) had been set up on a disk without making any
> partitions. The entry in /etc/fstab looked something like this:
> 
> /dev/hdc        /mount/point    reiserfs        defaults        0 0
> 
> When I saw this, I instinctively partitioned the drive so that /dev/hdc1
> was mounted instead. But was this really necessary? If I want to put only
> one filesystem on a disk, do I need to partition at all? It seemed to work
> fine before I changed it. I had just never heard of this before, and
> automatically assumed that the problems the box was having could be
> related to this.

fs'es are mounted from block devices, and /dev/hdc
is as much block device as /dev/hdc1.  Just like a
floppy - they don't have partition tables either.

Booting off such a thing will work too, if the bios
don't make assumptions about partitioning.  They
used not to, last time I looked the pc bios simply
executes the first sector of the disk and
the code there have do support partitions itself
if necessary.

I see no need to partition such a beast into
a single big partition - you just loose 
a sector to the partition table.  

Helge Hafting

      reply	other threads:[~2002-06-05  7:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-04 15:26 One disk, one filesystem, no partitions? Ketil Froyn
2002-06-05  7:56 ` Helge Hafting [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=3CFDC428.E9CB3E80@aitel.hist.no \
    --to=helgehaf@aitel.hist.no \
    --cc=ketil-kernel@froyn.net \
    --cc=linux-kernel@vger.kernel.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