1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
|
# Copyright (C) 2009 One Laptop Per Child
# Licensed under the terms of the GNU GPL v2 or later; see COPYING for details.
. $OOB__shlib
versioned_fs=$(read_config base versioned_fs)
prepopulate_run=$(read_config base prepopulate_run)
python_optimize=$(read_config base python_optimize)
buildnr=$(read_buildnr)
isopath=$outputdir/$(image_name).iso
if [[ "$python_optimize" != "0" ]]; then
export PYTHONOPTIMIZE=$python_optimize
fi
# due to popular demand
# FIXME: ship in olpc-utils?
cat >$fsmount/boot/README <<EOF
The following documentation is for developers only.
=== PARTITIONED LAYOUT ===
On systems where 2 partitions are used (root and boot), OLPC OS builds
duplicate the boot contents in 2 places:
1. On the root filesystem, at /versions/pristine/hash/boot
which in turn is hardlinked to /versions/run/hash/boot
A booted system chroots into the /versions/run/hash root, so these files are
then accessible at /boot.
These files are not used during boot.
2. On the boot filesystem, which is mounted on a running system at /bootpart
This is a versioned filesystem layout.
OpenFirmware looks at the "boot" directory (a symlink in this case) on this
partition during early boot in order to find the kernel and supporting
files.
In other words, if you want to use a different kernel or initramfs then you
want to put the files in /bootpart/boot.
Installing a kernel RPM will put the new kernel and initramfs in /boot, so
this will not take effect on reboot. You need to synchronize those new files
into the real boot partition, e.g.:
# rsync --delete-before -av /boot/ /bootpart/boot/
This duplication is a consequence of the olpc-update design, where updates
can currently only be presented as a single filesystem tree described by a
single contents manifest. That filesystem tree must remain in pristine
condition in order for future updates to happen efficiently.
=== UNPARTITIONED LAYOUT ===
On systems where only a single partition is used, there is no duplication
of files (although there are multiple links). However, on a booted system,
/boot is not (exactly) the location that OFW boots from.
On a booted system, you are typically not seeing the actual disk layout,
instead you are seeing a chroot (with various bind mounts to distort it
further) setup by the initramfs.
OFW boots from the real /boot, which is an indirect symlink to the real
/versions/pristine/x/boot. On a booted system, /boot corresponds to the
real /versions/run/x/boot. Therefore any files you put in /boot will not
be available to OFW at boot-time, and if you break the hard links of existing
files then your changes will also not take effect.
Installing a kernel RPM will put the new kernel and initramfs in /boot, so
this will not take effect on reboot. You need to synchronize those new files
into the real boot area, e.g.:
# cp -a /boot/* /versions/boot/current/boot/
EOF
# image-creator seems to conditionally create and populate this directory
# based on the setup of the host computer. let's make it consistent,
# we aren't using selinux...
rm -rf $fsmount/selinux
# strip all trailing slashes from the targets of symlinks.
# this is needed for creation of a USB update image (iso file) where the
# iso format cannot encode a symlink with a trailing slash.
# this would then cause content manifest verification failure when being
# installed.
find $fsmount -type l -lname '*/' -exec bash -c "shopt -s extglob; i=\$(readlink {}); i=\${i%%*(/)}; ln -snf \$i {}" \;
# normalize modification times of all files for faster updates (#4259)
# note that python needs special consideration here: the mtime is encoded
# into the pyc file. so we must regenerate all pyc files.
OLPC_EPOCH="2007-11-02 12:00:00Z"
# kill all *.pyo and *.pyc
find $fsmount/etc -xdev -name "*.py[oc]" -delete
find $fsmount/usr/lib -xdev -name "*.py[oc]" -delete
find $fsmount/usr/share -xdev -name "*.py[oc]" -delete
# note: we ignore errors from "find" below, because touch will try and
# update mtimes on symlinks to (e.g.) /proc/self/fd/0 which will not succeed
# for obvious reasons
# normalize mtimes of all files
echo "Normalize file times..."
find $fsmount -xdev -print0 | xargs -0 touch -h -c -d "$OLPC_EPOCH" || :
# fails to compile due to "..."
rm -f $fsmount/usr/lib/python2.7/lib2to3/tests/data/py3_test_grammar.py*
# now regenerate the .pyc files
# (add -OO to generate .pyo files instead when we tackle dlo trac #8431)
echo "Compiling python bytecode..."
chroot $fsmount python -m compileall /usr/lib /usr/share > /dev/null
# now we have to normalize the mtimes of the new pyc/pyo files, but we'll do
# that after we've finished making other fs changes below
if [ "$versioned_fs" = "1" ]; then
# Make upgradable
mkdir -p $fsmount/versions/pristine/$buildnr
mkdir -p $fsmount/versions/{updates,contents,sticky,run}
for f in $(ls -a $fsmount/ |egrep -v '^(\.|\.\.|versions|home|security|lost\+found)$' ); do
mv $fsmount/$f $fsmount/versions/pristine/$buildnr/
done
mkdir -p $fsmount/versions/pristine/$buildnr/{versions,home,security}
mkdir -p $fsmount/{sys,proc,dev}
echo "Generating contents manifest..."
chroot $fsmount/versions/pristine/$buildnr /usr/sbin/olpc-contents-create -f /.xo-files -p /etc/passwd -g /etc/group /
mv $fsmount/versions/pristine/$buildnr/.xo-files $fsmount/versions/contents/$buildnr
cp $fsmount/versions/contents/$buildnr $outputdir/$(image_name).toc
if [ "$prepopulate_run" = "1" ]; then
echo "Pre-populating /versions/run tree..."
cp -arl $fsmount/versions/pristine/$buildnr \
$fsmount/versions/run/$buildnr
fi
fi
# now normalize mtimes again
echo "Normalize file times..."
find $fsmount -xdev -print0 | xargs -0 touch -h -c -d "$OLPC_EPOCH" || :
# now that we've generated the .contents file, its important that nobody
# makes any more changes to the files. let's try and be sure of that
mount -o remount,ro $fsmount
|
