| 1 |
I tested the latest snapshot build tbz2, using: |
| 2 |
|
| 3 |
19a768ea676e307c936787a0fbd5f11e build-ix86-20010629.tbz2 |
| 4 |
acc9a79bddde60c5c8aa7dc1d650e89b INSTALL-BUILD |
| 5 |
|
| 6 |
(If someone needs the version of INSTALL-BUILD I was using, drop me a |
| 7 |
line..) |
| 8 |
|
| 9 |
Summary: No major problems were encountered during the process, except for |
| 10 |
the linux kernel image being too big. |
| 11 |
|
| 12 |
----------------------------------------------------------------------- |
| 13 |
|
| 14 |
In step 1, we should make a note that some tars (older ?) use the "-I" |
| 15 |
option instead of "-j". |
| 16 |
|
| 17 |
----------------------------------------------------------------------- |
| 18 |
|
| 19 |
In step 2, we should instead of |
| 20 |
|
| 21 |
chroot /tmp/build /bin/bash |
| 22 |
|
| 23 |
have |
| 24 |
|
| 25 |
env -i TERM=$TERM `which chroot` /tmp/build /bin/bash |
| 26 |
|
| 27 |
This, to zero out the environment, copying only the TERM setting. I |
| 28 |
don't think we should make or have to make any assumptions about the |
| 29 |
environment when installing. Additionally, `which chroot` is needed |
| 30 |
because the PATH is empty by the time env runs the command. |
| 31 |
|
| 32 |
----------------------------------------------------------------------- |
| 33 |
|
| 34 |
Because of the change in step 2, the PATH is empty and thus in step 3 |
| 35 |
we need to change |
| 36 |
|
| 37 |
env-update |
| 38 |
|
| 39 |
to |
| 40 |
|
| 41 |
/usr/sbin/env-update |
| 42 |
|
| 43 |
----------------------------------------------------------------------- |
| 44 |
|
| 45 |
Step 5: |
| 46 |
|
| 47 |
Number of files transferred: 2974 |
| 48 |
|
| 49 |
----------------------------------------------------------------------- |
| 50 |
|
| 51 |
In step 7, I noticed this build included the /etc/make.profile symlink |
| 52 |
already, or was created by env-update, dunno... |
| 53 |
|
| 54 |
The "-march=pentiumpro" bug (imake compatibilty problems w/x11-4.1.0) |
| 55 |
hadn't been fixed in this release. I used the following settings: |
| 56 |
|
| 57 |
CHOST="i686-pc-linux-gnu" |
| 58 |
CFLAGS="-march=i686 -O3 -pipe" |
| 59 |
CXXFLAGS="-march=i686 -O3 -pipe" |
| 60 |
|
| 61 |
(non-MAINTAINER mode) |
| 62 |
|
| 63 |
----------------------------------------------------------------------- |
| 64 |
|
| 65 |
In step 8, I chose to use bootstrap-20010617.packages. |
| 66 |
|
| 67 |
Bootstrap failed, because: |
| 68 |
|
| 69 |
-rw-r--r-- 1 root root 154124 Jun 29 17:12 /usr/bin/wget |
| 70 |
|
| 71 |
After fixing it I checked the dir and established that all other files |
| 72 |
had their executable bits set. |
| 73 |
|
| 74 |
----------------------------------------------------------------------- |
| 75 |
|
| 76 |
In step 9, I chose not to modify the USE variables in make.conf to |
| 77 |
make sure the default install works. |
| 78 |
|
| 79 |
----------------------------------------------------------------------- |
| 80 |
|
| 81 |
In step 11, I chose to do: |
| 82 |
|
| 83 |
emerge /usr/portage/sys-kernel/linux/linux-2.4.4.9.ebuild |
| 84 |
|
| 85 |
----------------------------------------------------------------------- |
| 86 |
|
| 87 |
In step 12, as I already have grub installed, I chose not to do it |
| 88 |
again, instead I'll boot from the grub commandline. |
| 89 |
|
| 90 |
----------------------------------------------------------------------- |
| 91 |
|
| 92 |
Jumping on to http://gentoo.org/doc/install.html / 3. Configuration.. |
| 93 |
|
| 94 |
Add "fi-latin1" to the keymap list ;-) (yes, it's a dash, not a |
| 95 |
underscore). |
| 96 |
|
| 97 |
The example /etc/fstab had <dump/pass>, but I made it 1 1 instead |
| 98 |
(since I don't have a separate /boot partition, otherwise I would have |
| 99 |
made it 1 2, or maybe 0 2, hmm..). Also, in the web the root was |
| 100 |
mounted with "defaults" and in the example it was "notail,noatime". I |
| 101 |
chose "defaults". |
| 102 |
|
| 103 |
Hmm, why is the bzImage installed to /boot/boot/bzImage and not |
| 104 |
/boot/bzImage or something.. some fhs2.2 issue ? |
| 105 |
|
| 106 |
----------------------------------------------------------------------- |
| 107 |
|
| 108 |
Ok, booting of the 2.4.4.9 kernel failed in a message something like |
| 109 |
"Ran out of input data", and my guess that the kernel image would |
| 110 |
maybe be too big was confirmed: |
| 111 |
|
| 112 |
-rw-r--r-- 1 root 1217940 Jun 30 04:00 bzImage |
| 113 |
|
| 114 |
Don't know about you guys, but for me, the kernel stops booting when |
| 115 |
it gets somewhere over 1 meg.. Dunno where the exact limit goes, it's |
| 116 |
not 1048576 bytes but something a bit bigger.. Maybe it's 1 meg + the |
| 117 |
code to purge the compressed image? |
| 118 |
|
| 119 |
At this point, I didn't have time to do any more testing on this, so I |
| 120 |
had to leave it here for now. |
| 121 |
|
| 122 |
----------------------------------------------------------------------- |
| 123 |
|
| 124 |
- xkr47 |
Archives