#5174 HIGH 8.2.0 (: Generated jffs2 filesystem should have built-in hardlinks.

[Zarro Boogs per Child]

#5174: Generated jffs2 filesystem should have built-in hardlinks.
---------------------------------+------------------------------------------
           Reporter:  kimquirk   |       Owner:  mstone              
               Type:  defect     |      Status:  new                 
           Priority:  high       |   Milestone:  8.2.0 (was Update.2)
          Component:  distro     |     Version:                      
         Resolution:             |    Keywords:                      
        Next_action:  never set  |    Verified:  0                   
Deployment_affected:             |   Blockedby:                      
           Blocking:             |  
---------------------------------+------------------------------------------

Comment(by sunrise1):

 Possiblity 2) (As mentioned above) - Have the factory do a partial boot
 after imaging the NAND FLASH, thus pre-creating the shallow copy. There
 might be an issue with having to do some sort of activation first, and
 there would certainly be an issue with adding a time-consuming step to
 [http://www.tagnice.com  nike air yeezy shoes]the manufacturing process.

 Possibility 3) In OLPC's release process, create the base .img file as
 usual, then load it onto a machine with "ak", boot it through the shallow-
 copy phase (but not to the point where a sugar nick is assigned), reboot
 back to OFW, save-nand, then sign the result and submit that to Quanta.
 This is procedurally cumbersome at the OLPC end, but requires no new
 tools. The pain is incurred once per release to manufacturing, instead of
 for every end user.

-- 
Ticket URL: <http://dev.laptop.org/ticket/5174#comment:16>
One Laptop Per Child <http://laptop.org/>
OLPC bug tracking system