Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!

Bug 489460

Summary: The fstab example of the stages is still ext3
Product: Gentoo Release Media Reporter: Agostino Sarubbo <ago>
Component: StagesAssignee: Gentoo's Team for Core System packages <base-system>
Status: RESOLVED DUPLICATE    
Severity: minor CC: releng, zerochaos
Priority: Normal    
Version: unspecified   
Hardware: All   
OS: Linux   
Whiteboard:
Package list:
Runtime testing required: ---

Description Agostino Sarubbo gentoo-dev 2013-10-26 12:38:23 UTC
While we suggest in the handbook to have the rootfs as ext4, the stage's fstab still contains it as ext3, I'd suggest to change it.
Comment 1 Jorge Manuel B. S. Vicetto (RETIRED) Gentoo Infrastructure gentoo-dev 2013-10-28 13:32:32 UTC
I believe we don't touch fstab when building stages. Instead, the file comes from sys-apps/baselayout. I just checked the contents of baselayout-2.2.tar.bz2 and share.Linux/fstab includes the following entries:

/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

So to address this report, the file should be updated to use ext4.
Comment 2 Rick Farina (Zero_Chaos) gentoo-dev 2013-10-28 14:05:27 UTC
imho, it's an example file. why update to ext4? why not xfs? why not reiser4?  Point it, it's an example, not even usable, if we wanted to "update" it to make it more usable then "auto" seems more sane than a specific filesystem.
Comment 3 Jorge Manuel B. S. Vicetto (RETIRED) Gentoo Infrastructure gentoo-dev 2013-10-28 14:08:43 UTC
It's an example file, but I believe traditionally we've kept it in sync with the handbook. Anyway, I'll defer to base-system on this one - it's even their package.
Comment 4 SpanKY gentoo-dev 2013-11-28 20:19:39 UTC
i fixed this a while ago.  there just hasn't been a new release yet.

http://sources.gentoo.org/baselayout?view=revision&revision=3206

*** This bug has been marked as a duplicate of bug 451596 ***