Re: wiki edits
Dnia środa, 20 grudnia 2006 01:12, Elan Ruusamäe napisał:
> Thank you for your changes. Your attention to detail is appreciated.
> Status of sending notification mails:
> [en] cvsci, undefine: {u'undefine/at/pld-linux.org': (550, 'relay not
> permitted'), u'pld-cvs-commit/at/lists.pld-linux.org': (550, 'relay not
> permitted')}
Yeah, I know, will fix.
--
Judge others by their intentions and yourself by your results.
Guy Kawasaki
Education is an admirable thing, but it is well to remember from
time to time that nothing that is worth knowing can be taught.
Oscar Wilde
___
pld-devel-en mailing list
pld-devel-en@lists.pld-linux.org
http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
wiki edits
Thank you for your changes. Your attention to detail is appreciated.
Status of sending notification mails:
[en] cvsci, undefine: {u'undefine/at/pld-linux.org': (550, 'relay not
permitted'), u'pld-cvs-commit/at/lists.pld-linux.org': (550, 'relay not
permitted')}
--
glen
___
pld-devel-en mailing list
pld-devel-en@lists.pld-linux.org
http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: [Th] geninitrd borked?
Dnia 19-12-2006, wto o godzinie 23:24 +0100, Łukasz Jernaś napisał(a): > root=0303 (tried /dev/hda3 also) I'll check the rest tomorrow, I can barely > see the screen now :/ > I've generated initrd almost identical as Your. I've booted it successfully with 2.6.18.4_laptop-0.3 kernel. [EMAIL PROTECTED] ~]# geninitrd -v -f /boot/initrd-2.6.18.4_laptop-0.3.gz `uname -r` Finding IDE modules using ide_hostadapter Finding IDE modules using PCI ID database Using modules: kernel/drivers/ide/ide-core.ko.gz kernel/drivers/ide/pci/piix.ko.gz kernel/drivers/ide/ide-disk.ko.gz kernel/fs/xfs/xfs.ko.gz /bin/initrd-busybox -> /tmp/initrd.qlkO6P/bin/initrd-busybox Loading module [ide-core] without options. Loading module [piix] without options. Loading module [ide-disk] without options. Loading module [xfs] without options. Adding rootfs finding based on root= option support. 1969 bloków Output from geninitrd suggests we got the same initrd image. I've set udev off (as nothing from Your geninitrd suggests udev) no splashes (FB or BOOTSPLASH), just initramfs as the default initrdfs. Please edit the init script and let the whole file for set -x, to show where what gets fckd. [EMAIL PROTECTED] ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: [Th] geninitrd borked?
Dnia wtorek, 19 grudnia 2006 23:19, Cezary Krzyzanowski napisał: > Dnia 19-12-2006, wto o godzinie 23:12 +0100, Łukasz Jernaś napisał(a): > > Dnia wtorek, 19 grudnia 2006 22:18, Cezary Krzyzanowski napisał: > > > 1. Is the generated image initrd, or initramfs (should be the later). > > > > With latest geninitrd from th-test: > > Ok - so it seems to be initramfs. Good. Now the two other informations > please. One - does it crash on exec switch_root and I'd like to see Your > root= parameter on kernel boot. root=0303 (tried /dev/hda3 also) I'll check the rest tomorrow, I can barely see the screen now :/ -- Łukasz [DeeJay1] Jernaś ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: [Th] geninitrd borked?
Dnia 19-12-2006, wto o godzinie 23:12 +0100, Łukasz Jernaś napisał(a): > Dnia wtorek, 19 grudnia 2006 22:18, Cezary Krzyzanowski napisał: > > 1. Is the generated image initrd, or initramfs (should be the later). > > With latest geninitrd from th-test: Ok - so it seems to be initramfs. Good. Now the two other informations please. One - does it crash on exec switch_root and I'd like to see Your root= parameter on kernel boot. >From this script everything seems to be just fine, so the root parameter is crusial. Thx 4 the work [EMAIL PROTECTED] ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: [Th] geninitrd borked?
Dnia wtorek, 19 grudnia 2006 23:12, Łukasz Jernaś napisał: > Dnia wtorek, 19 grudnia 2006 22:18, Cezary Krzyzanowski napisał: > > 1. Is the generated image initrd, or initramfs (should be the later). Oh, it's an initramfs not initrd... -- Łukasz [DeeJay1] Jernaś ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: [Th] geninitrd borked?
Dnia wtorek, 19 grudnia 2006 22:18, Cezary Krzyzanowski napisał:
> 1. Is the generated image initrd, or initramfs (should be the later).
With latest geninitrd from th-test:
[EMAIL PROTECTED] ~]# geninitrd -v --without-bootsplash -f initrd.gz 2.6.16.36-1
Finding IDE modules using ide_hostadapter
Finding IDE modules using PCI ID database
Using modules: kernel/drivers/ide/ide-core.ko.gz
kernel/drivers/ide/pci/piix.ko.gz kernel/drivers/ide/ide-disk.ko.gz
kernel/fs/reiserfs/reiserfs.ko.gz
/bin/initrd-busybox -> /tmp/initrd.IodYzw/bin/initrd-busybox
Loading module [ide-core] without options.
Loading module [piix] without options.
Loading module [ide-disk] without options.
Loading module [reiserfs] without options.
Adding rootfs finding based on root= option support.
1276 bloków
init:
#! /bin/sh
set -x
insmod /lib/modules/2.6.16.36-1/kernel/drivers/ide/ide-core.ko
insmod /lib/modules/2.6.16.36-1/kernel/drivers/ide/pci/piix.ko
insmod /lib/modules/2.6.16.36-1/kernel/drivers/ide/ide-disk.ko
insmod /lib/modules/2.6.16.36-1/kernel/fs/reiserfs/reiserfs.ko
set +x
mount -t proc none /proc
root="$(busybox awk ' /root=\/dev\// { gsub(/.*root=\/dev\//,NIL,$0);
gsub(/ .*/,NIL,$0); print $0; } ' /proc/cmdline)"
if [ -n "$root" ]; then
rootnr="$(busybox awk -v root="$root" ' { if ($4 == root) { print
256*$1+$2; } } ' /proc/partitions)"
if [ -n "$rootnr" ]; then
echo "$rootnr" > /proc/sys/kernel/real-root-dev
fi
fi
umount /proc
set -x
set +x
mount -t proc none /proc
root="$(busybox awk -v prefix="root=" ' \
function separate_root ( txt ) \
{ \
gsub(/.*root=/,NIL,txt); \
gsub(/ .*/,NIL,txt); \
return txt \
} \
BEGIN { \
num_pattern = "[0-9][0-9][0-9][0-9]"; \
dev_pattern = "[hms][a-z][a-z]([0-9])+"; \
partition = "Metallica rocks!"; \
min = -1; maj = -1; \
} \
$0 ~ prefix "0x" num_pattern { sub(/root=0x/,"root="); } \
$0 ~ prefix num_pattern { \
gsub(/.*root=/,NIL,partition); \
gsub(/ .*/,NIL,partition); \
partition = separate_root( $0 ); \
maj = sprintf("%d",substr(partition,1,2)); \
min = sprintf("%d",substr(partition,3)); \
} \
$0 ~ prefix "\/dev\/" dev_pattern { sub(/root=\/dev\//,"root="); } \
$0 ~ prefix dev_pattern { \
partition = separate_root( $0 ); \
} \
$4 ~ partition { maj = $1; min = $2; } \
$1 ~ maj && $2 ~ min { partition = $4; } \
END { print sprintf("/dev/%s %d %d", partition, maj, min); }
' /proc/cmdline /proc/partitions)"
device=${root% * *}
maj=${root#* }
maj=${maj% *}
min=${root#* * }
set -x
if [ ! -b $device ]; then
mknod $device b $maj $min
fi
mount -t reiserfs $device /newroot
init="$(busybox awk ' /init=\// { gsub(/.*init=/,NIL,$0); gsub(/ .*/,NIL,$0);
print $0; } ' /proc/cmdline )"
if [ -z "$init" -o ! -x "/newroot$init" ]; then
init=/sbin/init
fi
umount /proc
exec switch_root /newroot $init
linuxrc:
#! /bin/sh
set -x
insmod /lib/modules/2.6.16.36-1/kernel/drivers/ide/ide-core.ko
insmod /lib/modules/2.6.16.36-1/kernel/drivers/ide/pci/piix.ko
insmod /lib/modules/2.6.16.36-1/kernel/drivers/ide/ide-disk.ko
insmod /lib/modules/2.6.16.36-1/kernel/fs/reiserfs/reiserfs.ko
set +x
mount -t proc none /proc
root="$(busybox awk ' /root=\/dev\// { gsub(/.*root=\/dev\//,NIL,$0);
gsub(/ .*/,NIL,$0); print $0; } ' /proc/cmdline)"
if [ -n "$root" ]; then
rootnr="$(busybox awk -v root="$root" ' { if ($4 == root) { print
256*$1+$2; } } ' /proc/partitions)"
if [ -n "$rootnr" ]; then
echo "$rootnr" > /proc/sys/kernel/real-root-dev
fi
fi
umount /proc
set -x
set +x
mount -t proc none /proc
root="$(busybox awk -v prefix="root=" ' \
function separate_root ( txt ) \
{ \
gsub(/.*root=/,NIL,txt); \
gsub(/ .*/,NIL,txt); \
return txt \
} \
BEGIN { \
num_pattern = "[0-9][0-9][0-9][0-9]"; \
dev_pattern = "[hms][a-z][a-z]([0-9])+"; \
partition = "Metallica rocks!"; \
min = -1; maj = -1; \
} \
$0 ~ prefix "0x" num_pattern { sub(/root=0x/,"root="); } \
$0 ~ prefix num_pattern { \
gsub(/.*root=/,NIL,partition); \
gsub(/ .*/,NIL,partition); \
partition = separate_root( $0 ); \
maj = sprintf("%d",substr(partition,1,2)); \
min = sprintf("%d",substr(partition,3)); \
} \
$0 ~ prefix "\/dev\/" dev_pattern { sub(/root=\/dev\//,"root="); } \
$0 ~ prefix dev_pattern { \
partition = separate_root( $0 ); \
} \
$4 ~ partition { maj = $1; min = $2; } \
$1 ~ maj && $2 ~ min { partition = $4; } \
END { print sprintf("/dev/%s %d %d", partition, maj, min); }
' /proc/cmdline /proc/partitions)"
device=${root% * *}
maj=${root#* }
maj=${maj% *}
min=${root#* * }
set -x
if [ ! -b $device ]; then
mknod $device b $maj $min
fi
mount -t reiserfs $device /newroot
init="$(busybox awk ' /init=\// { gsub(/.*init=/,NIL,$0); gsub(/ .*/,NIL,$0);
print $0; } ' /proc/cmdline )"
if [ -z "$init" -o ! -x "/newroot$init" ]; then
init=/sbin/init
fi
umount /proc
exec switch_root /newroot $init
--
Łukasz [DeeJay1] Jernaś
P.S. Sorry for co
Re: [Th] geninitrd borked?
Dnia 19-12-2006, wto o godzinie 22:03 +0100, Łukasz Jernaś napisał(a): > It would be a good idea, there's no need for an rw root while initrd is > running, it's set by rc-scripts after checking the partition. You miss the point - I didn't include mountintg rootfs rw as a feature, I've omitted the -r parameter because of lack of knowledge ;) Fixed and commited. I'll release another version later, when the second problem gets fixed. > No idea, I've just run geninitrd -v -f initrd-2.6.16.36-1.gz 2.6.16.36-1 and > it "included" bootsplash by default, although I have fbsplash installed too. Hm - I think that geninitrds sysconfig file by default has bootsplash and includes it whenever the bootsplash package is present. Let's divide two things. Both bootsplash and fbsplash need kernel patching in order to work and *also* need userspace programs. I'm not quite sure, if the newer PLD kernels include bootsplash patches at all and if the do, how does having both bootsplash and fbsplash *kernel* patches influence the system. > > > > cannot find rootfs - looks like initrd isn't even started in that case. > > > > Do You use initramfs as initrdfs, or old initrd ?? I must say as I have > > some idea what could be wrong with the rw/ro matter, but this just > > doesn't get to me. > > See above - I didn't touch anything in /e/s/geninitrd Darn - I don't have a bloody idea what could be wrong. Does that 'cannot find rootfs' occur in result of switch_root, or somewhere earlier?? Please check two things 4 me in order to fix that. 1. Is the generated image initrd, or initramfs (should be the later). mkdir /tmp/czarny_sucks cp /boot/initrd-2.6.something.gz /tmp/czarny_sucks cd /tmp/czarny_sucks gunzip initrd cpio -i < initrd If this works, You have initramfs, if not - You've got initrd. If initrd, please mount it: mkdir fuck modprobe loop mount -oloop -tromfs initrd shit and in both cases paste me the linuxrc/init script here. 2. What are You passing at kernel boot (through the bootloader) as the root parameter? My work in initramfs is to parse that parameter and mount the rootfs accordingly - I could've screwed that part, or didn't anticipate some parameter form. > N/P - 5 weeks is a long time though, it was enough to start and end my > engineering project ;) Yea, but /me wants to get world-famous. PPl don't get world-famous in 5 weeks of work ;p ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: [Th] geninitrd borked?
Dnia wtorek, 19 grudnia 2006 21:49, Cezary Krzyzanowski napisał: > Dnia 19-12-2006, wto o godzinie 20:21 +0100, Łukasz Jernaś napisał(a): > rc-scripts?? I didn't touch rc-scripts at all. I could have the root > mounted ro in initrd - that is a point. It would be a good idea, there's no need for an rw root while initrd is running, it's set by rc-scripts after checking the partition. > > Oh, and BTW when trying to use bootsplash > > Bootsplash? I didn't touch bootsplash. Do the new kernels in PLD support > bootsplash at all?? Don't they support fbsplash as default? No idea, I've just run geninitrd -v -f initrd-2.6.16.36-1.gz 2.6.16.36-1 and it "included" bootsplash by default, although I have fbsplash installed too. > > cannot find rootfs - looks like initrd isn't even started in that case. > > Do You use initramfs as initrdfs, or old initrd ?? I must say as I have > some idea what could be wrong with the rw/ro matter, but this just > doesn't get to me. See above - I didn't touch anything in /e/s/geninitrd > P.S. > Thx for the feedback. I don't have much time now (5 weeks to give my > engineers papers), but still this is my feature and I'll be assisting > such matters at hand. N/P - 5 weeks is a long time though, it was enough to start and end my engineering project ;) -- Łukasz [DeeJay1] Jernaś ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: [Th] geninitrd borked?
Dnia 19-12-2006, wto o godzinie 20:21 +0100, Łukasz Jernaś napisał(a): > Hello. > > I can't get my system to work with geninitrd-8103-1 > rc-scripts fail when trying to check my root filesystem, because it's mounted > read-write already. rc-scripts?? I didn't touch rc-scripts at all. I could have the root mounted ro in initrd - that is a point. > Oh, and BTW when trying to use bootsplash Bootsplash? I didn't touch bootsplash. Do the new kernels in PLD support bootsplash at all?? Don't they support fbsplash as default? > cannot find rootfs - looks like initrd isn't even started in that case. Do You use initramfs as initrdfs, or old initrd ?? I must say as I have some idea what could be wrong with the rw/ro matter, but this just doesn't get to me. > > Maybe it's because I'm more of an Iron Maiden fan than Metallica? ;) Yea - this is because of Your treacherous behavior ;) [EMAIL PROTECTED] P.S. Thx for the feedback. I don't have much time now (5 weeks to give my engineers papers), but still this is my feature and I'll be assisting such matters at hand. ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
mc:HEAD with utf8 still broken
With pl_PL (default iso8859-2) locale: - help (F1) is displayed in UTF-8 - view (F3) displays some junk instead of latin2 characters -- Jakub Boguszhttp://qboosh.pl/ ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
[Th] geninitrd borked?
Hello. I can't get my system to work with geninitrd-8103-1 rc-scripts fail when trying to check my root filesystem, because it's mounted read-write already. This doesn't happen with geninitrd-7899-0.1 at all. Oh, and BTW when trying to use bootsplash kernel crashes with a kernel panic - cannot find rootfs - looks like initrd isn't even started in that case. Maybe it's because I'm more of an Iron Maiden fan than Metallica? ;) -- Łukasz [DeeJay1] Jernaś pgp6EdAIivK6i.pgp Description: PGP signature ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: kernel24 2.4.33 for testing
On Wed, Aug 30, 2006 at 09:26:11AM +0200, Marcin Król wrote:
> > And I'm preparing next release now :/
> > CVE-2006-3745 fix (i.e. 2.4.33.2 patch) + squashfs update to 3.1.
> > I hope to commit it today.
>
> BTW, why 2.4.33.2 without EXTRAVERSION chunk?
I didn't want to introduce such new change then... and I was right.
I tried to add %{postver} to EXTRAVERSION at 2.4.33.4 time and it causes
system to stop just after running init. I don't know if it's kernel,
libc or modutils fault, but it happens on first fork(), execve() or
so... sh run as init stops when trying to execute any command.
The only thing that works then is SysRq.
I'll revert EXTRAVERSION change tomorrow, when finishing update to
2.4.33.6 (as new release with Version = 2.4.33).
--
Jakub Boguszhttp://qboosh.pl/
___
pld-devel-en mailing list
pld-devel-en@lists.pld-linux.org
http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: *gphoto2 in Ac
On Tuesday 19 December 2006 10:49, Jakub Bogusz wrote: > I see that *gphoto2 2.3.0 have been built for Ac, but they have been > misbuilt with(out) old libexif (i.e. libgphoto2 requires libexif 0.6.13, > but Ac has 0.6.12, so libgphoto2 built without libexif support, but > still requiring libexif 0.6.13 in .pc file - and that's the source of > libgphoto2 version detection problems in gphoto2 or other packages). > > Conclusion: if libgphoto2 2.3.0 stays in Ac, libexif must be updated to > 0.6.13 and libgphoto2 rebuilt afterwards. > > There was no soname change in libexif, but some apps require _build_ > time fixes (now headers must be included as instead of > just <*.h>); rebuilding is not needed. sent -- glen ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
*gphoto2 in Ac
I see that *gphoto2 2.3.0 have been built for Ac, but they have been misbuilt with(out) old libexif (i.e. libgphoto2 requires libexif 0.6.13, but Ac has 0.6.12, so libgphoto2 built without libexif support, but still requiring libexif 0.6.13 in .pc file - and that's the source of libgphoto2 version detection problems in gphoto2 or other packages). Conclusion: if libgphoto2 2.3.0 stays in Ac, libexif must be updated to 0.6.13 and libgphoto2 rebuilt afterwards. There was no soname change in libexif, but some apps require _build_ time fixes (now headers must be included as instead of just <*.h>); rebuilding is not needed. -- Jakub Boguszhttp://qboosh.pl/ ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
