public inbox for gentoo-embedded@lists.gentoo.org
 help / color / mirror / Atom feed
From: wireless <wireless@tampabay.rr.com>
To: gentoo-embedded@lists.gentoo.org
Subject: Re: [gentoo-embedded] SOLVED planning a flash DOM x86 embedded system
Date: Thu, 24 Oct 2013 13:11:52 -0400	[thread overview]
Message-ID: <526954D8.9080008@tampabay.rr.com> (raw)
In-Reply-To: <CAHH9eM6jdZk=ROXiPwg+9mQmJ9XMDiM7PitbuKKvUbQfdfgstg@mail.gmail.com>

On 10/24/13 12:41, Francisco Ares wrote:

> It works now!
> It seems that blog shows an old style syntax.  Found others, though,
> like the following:
>
> http://www.viraj.org/b2evolution/blogs/index.php/2007/05/03/ubuntu_server_and_unionfs

>
> but for nowadays Gentoo systems (at least) the correct syntax is like
> the following (which works for me):
>
> /dev/sda3       /.var.rw <http://var.rw>        ext4
> noatime,defaults                                          0 2
> union           /var            unionfs
> default_permissions,allow_other,use_ino,nonempty,suid,cow,dirs=/.var.rw
> <http://var.rw>=rw:/.var.ro <http://var.ro>=ro  0 0
> tmpfs           /.etc.rw <http://etc.rw>        tmpfs
> defaults,mode=755                                         0 0
> union           /etc            unionfs
> default_permissions,allow_other,use_ino,nonempty,suid,cow,dirs=/.etc.rw
> <http://etc.rw>=rw:/.etc.ro <http://etc.ro>=ro  0 0
>
> Directories  /.var.ro <http://var.ro>   and    /.etc.ro <http://etc.ro>
> are already present on the root file system.
> It seems that this was the problem from the beginning, not been able to
> correctly mount those partitions at the proper and usual time.

This brings up a related issue, I filed a bug about [1].

Documenting how to use UUIDs in the installation handbook. I kept the 
bug generic, but I had Arm architectures in mine all along. With the 
porting of Grub2 to Arm (Linaro) is seems that soon there will be a 
myriad of file systems to run on the newer Arm systems [2] [3]. I 
struggle on how to write up the bug, so feel encourage to think about 
ways to simply or unify the installation handbooks, related to grub2, 
supporting a variety of new file systems, particularly related to arm. 
The existing arm handbook [4] is woefully out of date. Granted, the
gentoo-embedded handbook [5] is great, it does not address gentoo-distro
installation on the newer arm (64 bit)chips, akin to the x86 offerings.

So folks are resorting to all sorts of extraneous documentation [6]

Filing bugs (new or edit mine) to make the docs better, enhances 
Gentoo's appeal, imho.

James


[1]  https://bugs.gentoo.org/show_bug.cgi?id=483654

[2] 
http://www.arm.com/products/processors/instruction-set-architectures/armv8-r-architecture.php

[3] 
http://www.arm.com/products/processors/instruction-set-architectures/armv8-architecture.php

[4] http://www.gentoo.org/doc/en/handbook/handbook-arm.xml

[5] http://www.gentoo.org/proj/en/base/embedded/handbook/

[6] 
http://www.chromebook-linux.com/2011/11/gentoo-is-ready-for-chromebook.html


      reply	other threads:[~2013-10-24 17:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-24 16:41 [gentoo-embedded] SOLVED planning a flash DOM x86 embedded system Francisco Ares
2013-10-24 17:11 ` wireless [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=526954D8.9080008@tampabay.rr.com \
    --to=wireless@tampabay.rr.com \
    --cc=gentoo-embedded@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