| 1 |
Okay, I know it's very low on your priority list, but I figured out |
| 2 |
something new ;) |
| 3 |
|
| 4 |
How about scanning for the partition that shall be used for the initrd? |
| 5 |
It could be done with unionfs=scan and that wouldn't break compatibility |
| 6 |
for genkernel. I studied the UnionFS's scripts a bit longer and found |
| 7 |
that the file livecd.unionfs must exist on the partition that shall be |
| 8 |
used as rw-device for unionfs. Now it's easy to scan for it, just |
| 9 |
include the following function to |
| 10 |
/usr/share/genkernel/generic/initrd.scripts: |
| 11 |
|
| 12 |
find_unionfs(){ |
| 13 |
local FS |
| 14 |
goodmsg "Scanning for filesystem with file /livecd.unionfs" |
| 15 |
mkdir -p /union |
| 16 |
FS=`blkid -c /dev/null | cut -d: -f1` |
| 17 |
# find filesystem on blockdevice containing file livecd.unionfs |
| 18 |
for i in ${FS} |
| 19 |
do |
| 20 |
mount -t auto ${i} /union |
| 21 |
if [ -f /union/livecd.uinonfs ] |
| 22 |
then |
| 23 |
goodmsg "Found filesystem $i" |
| 24 |
UNIONFS=${i} |
| 25 |
umount /union |
| 26 |
break |
| 27 |
else |
| 28 |
umount /union |
| 29 |
fi |
| 30 |
done |
| 31 |
rmdir /union |
| 32 |
} |
| 33 |
|
| 34 |
then the function setup_unionfs() just needs a little patch at the |
| 35 |
beginning: |
| 36 |
|
| 37 |
setup_unionfs(){ |
| 38 |
if [ "${UNIONFS}" = "scan" ] |
| 39 |
then |
| 40 |
find_unionfs |
| 41 |
fi |
| 42 |
|
| 43 |
You say it's known to be broken, what else needs to be fixed besides bug |
| 44 |
99682 (and that is already resolved, as it seems)? I currently have the |
| 45 |
strange feeling, that unionctl is not copied to the initrd of the |
| 46 |
livecd, as it was not found when I booted from a CD made with 'genkernel |
| 47 |
--unionfs'. I tried to extract the file isolinux/gentoo.igz from the |
| 48 |
cdrom to check, but I didn't get all of it's contents, as it seems. |
| 49 |
'gunzip -c gentoo.igz | cpio -i' has only this content: |
| 50 |
|
| 51 |
./dev |
| 52 |
./dev/console |
| 53 |
./dev/null |
| 54 |
./dev/tty1 |
| 55 |
./bin |
| 56 |
./etc |
| 57 |
./etc/fstab |
| 58 |
./usr |
| 59 |
./usr/bin |
| 60 |
./usr/sbin |
| 61 |
./proc |
| 62 |
./temp |
| 63 |
./sys |
| 64 |
./var |
| 65 |
./var/lock |
| 66 |
./var/lock/dmraid |
| 67 |
./sbin |
| 68 |
|
| 69 |
But the file has extracted ~17 MB... Mounting it with -o loop didn't |
| 70 |
succeed either, but maybe I'm not having the right FS in my kernel. Can |
| 71 |
you help me on this? |
| 72 |
|
| 73 |
For me this feature is very important, and I would be willing to |
| 74 |
maintain the unionfs of the LiveCD, if it helps you having more time. |
| 75 |
|
| 76 |
Greetings, |
| 77 |
|
| 78 |
Georg |
| 79 |
|
| 80 |
Chris Gianelloni wrote: |
| 81 |
> On Thu, 2005-09-08 at 21:05 +0200, Georg Lippold wrote: |
| 82 |
> |
| 83 |
>>If in /usr/share/genkernel/generic/initrd.scripts the function parse_opt |
| 84 |
>>is changed with the corresponding | as delimiter, then one wouldn't have |
| 85 |
>>to change anything else. It would look like this: |
| 86 |
>> |
| 87 |
>>parse_opt() { |
| 88 |
>> case "$1" in |
| 89 |
>> *\|*) |
| 90 |
>> local key_name="`echo "$1" | cut -f1 -d\|`" |
| 91 |
>> local key_len=`strlen key_name` |
| 92 |
>> local value_start=$((key_len+2)) |
| 93 |
>> echo "$1" | cut -c ${value_start}- |
| 94 |
>> ;; |
| 95 |
>> esac |
| 96 |
>>} |
| 97 |
>> |
| 98 |
>> |
| 99 |
>>What is your opinion on this? |
| 100 |
> |
| 101 |
> |
| 102 |
> We don't support UnionFS in any way and don't have plans on doing so for |
| 103 |
> some time. We also do not want to break compatibility in genkernel |
| 104 |
> mid-release, as this caused us quite enough headaches between 2005.0 and |
| 105 |
> 2005.1's releases. |
| 106 |
> |
| 107 |
> To put it simply, the UnionFS support in genkernel is known to be broken |
| 108 |
> and not working well, which is why we have removed the --unionfs option |
| 109 |
> from genkernel. It is so low on our priority list, that we're |
| 110 |
> definitely saying that we'll get to it "when we have time" and I can |
| 111 |
> tell you that I, personally, won't have time for months. |
| 112 |
> |
| 113 |
> Remember that genkernel and catalyst *are* two separate projects, and |
| 114 |
> genkernel must maintain usability. We can't use a pipe to delimit |
| 115 |
> things, as that could be interpreted by the shell. |
| 116 |
> |
| 117 |
> Currently, all of our limited attention is focused on resolving bugs, |
| 118 |
> and working towards releasing catalyst 2.0 to the world. I'd almost |
| 119 |
> expect a feature freeze on genkernel for some time, as we work to |
| 120 |
> stabilize the codebase. |
| 121 |
> |
| 122 |
-- |
| 123 |
gentoo-catalyst@g.o mailing list |
Archives