public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: James <wireless@tampabay.rr.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: Handbook(amd64)
Date: Thu, 14 Apr 2016 20:49:13 +0000 (UTC)	[thread overview]
Message-ID: <loom.20160414T224211-646@post.gmane.org> (raw)
In-Reply-To: 570FFA8B.8070001@charter.net

Corbin <corbinbird <at> charter.net> writes:



> > In the Kernel section of the amd64-handbook::
> >
> > "root #nano -w /etc/fstab
> > FILE /etc/fstabConfiguring the /boot mountpoint
> > /dev/sda2	/boot	ext2	defaults	0 2 "
> >
> > <then this note>

Ah, thx, I did find this which matches up with the default guidanced in the
setting up the disk secition::

/etc/fstabA full /etc/fstab example

/dev/sda2   /boot        ext2    defaults,noatime     0 2
/dev/sda3   none         swap    sw                   0 0
/dev/sda4   /            ext4    noatime              0 1
/dev/cdrom  /mnt/cdrom   auto    noauto,user          0 0


But, I guess I was not clear in proposing this as a bug. There should be a
clickable link to jump ahead to that section (just above that you
mentioned). But even more problematic the minimal_CD leaves the fresh
install with what I listed below::



> > Now finishing up the manual installation I have this default /etc/fstab::
> >
> > /dev/BOOT       /boot           ext2            noauto,noatime  1 2
> > /dev/ROOT       /               ext3            noatime         0 1
> > /dev/SWAP       none            swap            sw              0 0
> > /dev/cdrom     /mnt/cdrom      auto            noauto,ro       0 0
> > /dev/fd0       /mnt/floppy     auto            noauto          0 0
> >
> > which seems vintage. So a bug probable needs to be file on the 
> > handbook, but a bit of discussion might be wise, first.

I guess I was just expecting the minimal CD to match the handbook. So is
that a bug?  Is the missing link between the boot portion of the fstab
and the full fstab example a bug too? An enhancement

(yes, I did not see the full fstab in the subsequent section so thanks for
point that out.

Comments on if either if these are a bug?


James




      reply	other threads:[~2016-04-14 20:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-14 18:06 [gentoo-user] Handbook(amd64) James
2016-04-14 20:16 ` Corbin
2016-04-14 20:49   ` James [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=loom.20160414T224211-646@post.gmane.org \
    --to=wireless@tampabay.rr.com \
    --cc=gentoo-user@lists.gentoo.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