Re: Unclear Firefox situation
Dnia 19-09-2007, Śr o godzinie 22:22 +0200, Rafał Cygnarowski napisał(a): quotation If an individual or organization is creating a Community Edition of Mozilla Firefox or Thunderbird, it must use the names Firefox Community Edition or Thunderbird Community Edition to identify this software. These names may be further qualified to identify the software (e.g. Firefox Community Edition, French, Thunderbird Community Edition, Joe's optimized AMD Opteron build, etc.). Localizers may also translate the words Community Edition. /quotation So... Mozilla Firefox should be called just Firefox... isn't it true? Ehm -- and not 'Fierefox Community Edition' ?? [EMAIL PROTECTED] ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
BR-s and R-s policy
Patrys asked me to up evolution spec to 1.12 (corresponding with GNOME 2.20) and I've spotted, that during the GNOME packages update all the BR-s and R-s of gnome packages were upped to 2.20 line. The question is -- Is this necessary? I mean I've looked into evolution's configure.in and it seems it doesn't need half the newest packages that are listed in BR-s and R-s in evolution.spec (like it needs GConf2 = 2.0.0, not newest, shiniest 2.19). So is this some kind of policy, to require newest packages possible at the time of upping spec? [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: BR-s and R-s policy
Dnia 20-09-2007, Cz o godzinie 08:57 +0200, Arkadiusz Miskiewicz napisał(a): On Thursday 20 of September 2007, Marcin Król wrote: So is this some kind of policy, to require newest packages possible at the time of upping spec? It seems so. Its stupid IMO to bump version to highest possible ignoring real requirements. It's used to ensure that there are latest packages on the builders. That's the only reason I know. Ehm -- but wouldn't that be achieved just by installing packages on build? Every package needs to be build anyway, so it would be just logical to install it then. [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: http://hardware4linux.info/
Dnia 19-07-2007, Cz o godzinie 16:21 +0200, Mariusz Mazur napisał(a): We don't have anything for storing and browsing through hardware profiles and the website in the subject looks all webish2.0 and colorfull and has round edges. If someone could get through the software, package it and maybe send it to both ac and th, that'd be neat (/me -enotime). Oh, you can mail the author afterwards -- he's responsive, from mandriva and actually knows what pld is and took the effort of bugging us on irc about his solution. If it takes off, both users and developers could probably benefit from it (e.g. I'd know beforehand what laptops are supported by pld out of the box or something). http://cvs.pld-linux.org/cgi-bin/cvsweb/SPECS/hwreport.spec [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: SPECS: vim.spec - with python, ruby and tcl by default - rel 3 for...
Dnia 17-06-2007, N o godzinie 22:02 +0200, Jakub Bogusz napisał(a): But the original question was: do particular language support overhead is worth its benefits? Are there already some packaged or custom vim addons which need all these languages? 1. I use vim to develop python code and the bindings are good. 2. I got some plugins from vim.org that assist. I've got so many of them I actually am afraid to try packaging them for PLD as I'm not sure I'll recognize now all the plugins in my ~/.vim dir. 3. PLD is doing the maximum functionality maximum deps packages. Think OO. For all the minimum requirements there's always vim-static and e3. [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: Yum repodata in PLD
Dnia 24-05-2007, czw o godzinie 17:43 +0300, Elan Ruusamäe napisał(a): i'm +1 +1 - especially as poldek can make use of Suggest macro. [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: Thank you geninitrd for screwing my evening
Dnia 15-05-2007, wto o godzinie 22:33 +0200, Patryk Zawadzki napisał(a):
Please stop changing geninitrd to your liking without performing
sanity checks FIRST.
A the initramfs was my idea in the first place I feel responsible to
respond. I'm sorry for You screwed up evening. Nevertheless there's
nothing I could do to prevent it.
http://www.mail-archive.com/pld-devel-en@lists.pld-linux.org/msg02492.html
http://www.mail-archive.com/pld-devel-en@lists.pld-linux.org/msg02508.html
As You see I've asked for some checkups of the scripts and the checkups
and rewrites have been done.
- geninitrd generates initromfs images by default (why isbeyond my
imagination, I can only think about bootsplash bling bling here)
As it supposed to do in TH (the development version - totally not meant
for server usage). AC defaults to romfs. Bootsplash doesn't need
initramfs - fbsplash needs. And initramfs is the way to do booting up in
upstream. Look it up on i.e. kernel lists if You please.
- initromfs uses the following magic to determine the device
(copy-pasted for your entertainment):
BEGIN {
num_pattern_short = [0-9][0-9][0-9];
num_pattern = [0-9] num_pattern_short;
dev_pattern = [hms][a-z][a-z]([0-9])+;
partition = no_partition_found;
min = -1; maj = -1;
gsub(/.*root=/,NIL,c);
gsub(/ .*/,NIL,c);
sub(^0x, , c);
if (c ~ ^ num_pattern_short $) sub(^, 0, c);
if (c ~ ^ num_pattern $) {
maj = sprintf(%d,substr(c,1,2));
min = sprintf(%d,substr(c,3));
}
if (c ~ ^\/dev\/ dev_pattern $) sub(^/dev/,, c);
if (c ~ ^ dev_pattern $) partition = c;
}
- /dev/vgsys/* does not seem to match any of these clever rules, but
lo and behold as we have an alternative way...
- root=fe00 does not match any of these either, what a clever
coincidence as THE FUCKING LVM2 DEVICE HAPPENS TO BE (major, minor)
exactly 254, 0
Well, since You obviously have the equipment to test it, as I didn't and
don't have now as well, I suggest, for You as a PLD developer, to add
some other 'magic' rules that would match Your equipment.
P.S.
I'd guess that UUID recognizing would be great here, as It'd solve the
numbers and devices magic.
Once more sorry for Your last time.
[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: Thank you geninitrd for screwing my evening
Dnia 16-05-2007, śro o godzinie 08:45 +0200, Arkadiusz Miskiewicz napisał(a): DON'T use ,,th is development'' as excuse for such things please. Yea, maybe You're right. Nevertheless I couldn't have tested it in the first place, that's why I've asked the RFC. http://svn.pld-linux.org/cgi-bin/viewsvn/geninitrd/trunk/geninitrd?r1=8409r2=8560p1=geninitrd/trunk/geninitrdp2=geninitrd/trunk/geninitrd I hope it helps. As for the devices paths way (like /dev/something/even_futher) I can't imagine all the variations of the path to actually make it work, but I'll think bout it. [EMAIL PROTECTED] ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Console service for non-breakable fbsplash
Hi. I've been toying around fbsplash for some time now. I've been searching of a way to make the fbsplash's splash non-stop visible during boot. The problem I've found is console service from kbd. Is it really needed to switch to every console in every /sbin/open and even do manual /sbin/switchto from time to time?? I'm attaching a patch witch throws out all the console switching stuff to make the silent splash stay on top as long as possible. After applying it gets much better. There's just the: run_cmd Loading keyboard table loadkeys $KEYTABLE /dev/tty0 /dev/tty0 stuff left, which changes to a verbose console. I'm not sure what the run_cmd foo bar /dev/tty0 /dev/tty0 is supposed to do? Why inputting from tty? Why forcing output to tty? After removing the stuff the splash stays almost perfectly on top all the time. Only for a blink of an eye it turns to some console (not sure what other command in /etc/init.d/console does that, but it's definitely this service). Oh - and with initng running mingetty changes to the just runned console, not sure bout normal init boot, because I can't find mingetty in rc-scripts. Please comment on the patch. I'd like to commit it in some time. [EMAIL PROTECTED] Index: kbd.init === RCS file: /cvsroot/SOURCES/kbd.init,v retrieving revision 1.29 diff -u -r1.29 kbd.init --- kbd.init 7 Dec 2006 21:11:55 - 1.29 +++ kbd.init 14 May 2007 07:24:01 - @@ -68,19 +68,16 @@ fi for cons in $SET_FONT_TERMINALS; do -/usr/bin/open -c $cons -s -w -- /sbin/setsysfont +/usr/bin/open -c $cons -w -- /sbin/setsysfont if [ $NUM_LOCK ]; then if [ $NUM_LOCK = on ]; then - /usr/bin/open -c $cons -s -w -- /usr/bin/setleds -D +num + /usr/bin/open -c $cons -w -- /usr/bin/setleds -D +num else - /usr/bin/open -c $cons -s -w -- /usr/bin/setleds -D -num + /usr/bin/open -c $cons -w -- /usr/bin/setleds -D -num fi fi done - if [[ $tty = [0-9]* ]]; then -/usr/bin/switchto $tty - fi else /sbin/setsysfont fi @@ -120,11 +117,8 @@ setterm_option=$setterm_option -store for cons in $SET_FONT_TERMINALS; do - /usr/bin/open -c $cons -s -w -- /usr/bin/setterm $setterm_option + /usr/bin/open -c $cons -w -- /usr/bin/setterm $setterm_option done - if [[ $tty = [0-9]* ]]; then - /usr/bin/switchto $tty - fi touch /var/lock/subsys/console } ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: Console service for non-breakable fbsplash
Dnia 14-05-2007, pon o godzinie 09:49 +0200, Jacek Konieczny napisał(a): And fonts and keyboard input are set right on all the text consoles? I doubt. Hm - I haven't spotted any problems. What to look for?? I've got utf-8 polish terminals and all get set properly - I can read and write polish signs. I've only removed the switches, all console magic is still there. Terminal configuration commands operate on the controlling terminal or the standard input. I guess the redirections are to set the terminal right even if script is run from e.g. ssh. Ok - I get the idea. Still, there's only one command issued that way and the service has many console manipulation commands. Thx [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: Console service for non-breakable fbsplash
Dnia 14-05-2007, pon o godzinie 13:06 +0200, Jacek Konieczny napisał(a): If the switches were not needed, then it is good they were removed. Maybe they were required some time ago, but now the problem is fixed somewhere else (newer kernel). Well - after answering You I've found some more magic regarding bootsplash (former implementation of splashes) in rc-scripts. It's in 99% made to be able to show percentage of work in the silent output. I'm trying to make it usable with fbsplash as well. Have you tried removing the redirections? Yes. It boots. The Loading... line isn't shown on the default tty (I haven't checked if it is on the redirected one, as I deliberately use an empty tty for silent splash and I output all the stuff to tty12 via the kernel option console=tty12, because otherwise it'd screw up the splash with debug messages). Have you tried the script when booting with serial port as default console? I don't have any machine with serial console - sorry. Can't test that out. On the other hand I could try to make my laptop a serial terminal for my desktop, or the other way around, but I haven't used serial terminal. Thx 4 the discussion [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: geninitrd 8142
Dnia 29-01-2007, pon o godzinie 08:34 +0100, Przemyslaw Iskra napisał(a): Does it matter ? There is only one correct solution - make udev work properly, or copy the device at initramfs creation time (like initrd does). Yes. Udev *does* work correctly. The problem is, that in initramfs we have to mount and switch root manually!! This means we need to know, which partition *is* the root one, as udev will make dev nodes for *all* detectable hardware. [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: geninitrd 8142
Dnia 28-01-2007, nie o godzinie 22:18 +0100, Artur Frysiak napisał(a): root=/dev/vg1/root with initrdfs=rom works but with initramfs not. True. I'll look into that in 3-4 days (I'm finishing my engineers degree) I wander, how many more such possibilities exist. [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: geninitrd 8142
Dnia 27-01-2007, sob o godzinie 14:58 +0100, Rafał Cygnarowski napisał(a): I've updated geninitrd to use /sbin/udevd (as new udev doesn't have /sbin/udev anymore). Sent to builder and should work. Root is on /dev/sda6 - SATA2 disk. I mean what is passed at boot time to kernel as parameters. For example I pass: root=0302 init=/sbin/initng acpi_sleep=s3_bios video=vesafb:1024x768-32 splash=verbose,theme:ppcrcd,tty:12 console=tty1 The root parameters gives initrd an idea how to mount disks, so it's crucial it is set propelry (formats are /dev/something, 0302, 0x0302 (numbers change depending on Your disk and partition)) BTW: th kernel-2.6.17.13 on ftp doesn't detect my disk on SATA controller - 2.6.16.35 from th-test does. Not udev/initrd matter IMHO [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: geninitrd 8142
Dnia 27-01-2007, sob o godzinie 17:28 +0100, Przemyslaw Iskra napisał(a): using four digits is the standart way: root=0806 or root=0x0806, but if root=806 works geninitrd should be fixed Yea, didn't see that 806 too, but I've made it possible for geninitrd to understand. Please build it from CVS (I don't want to release another version to ftp before testing) [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: geninitrd 8142
Dnia 27-01-2007, sob o godzinie 18:08 +0100, Jaroslaw Dziubek napisał(a): I have a problem with pivot_root - which is not included in any package. pivot_root is a part of busyboxes. [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: SVN: geninitrd/trunk/geninitrd
Dnia 27-01-2007, sob o godzinie 18:35 +0100, Przemyslaw Iskra
napisał(a):
semicolon is missing
hm - true - no idea how it worked for me.
anyway, this is wrong, theck this one:
echo root=0303 | awk 'BEGIN { prefix=root=; num_pattern_short =
[0-9][0-9][0-9]; num_pattern = num_pattern_short [0-9]; } $0 ~
prefix num_pattern_short { sub(prefix, prefix 0); } { print }'
returns:
root=00303
there should be '$' or something
fck - got to rethink that ;/
[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: SVN: geninitrd/trunk/geninitrd
Dnia 27-01-2007, sob o godzinie 19:31 +0100, Przemyslaw Iskra napisał(a): consider the attached script, simplified, and should work Feel free to use that and commit to SVN. I've added a patch to make the ona already being used work (I think). [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] SMP for all!
Dnia 21-01-2007, nie o godzinie 21:58 +0100, Arkadiusz Miskiewicz napisał(a): +1 I use SMP kernels while having a single one-core CPU. It's just damn easier to share packages among laptops. +1 +1 here, too. An unsure +1, if an SMP kernel really works everywhere and doesn't post problems. I.E. Amarok and probably some other apps do some magic on their own to ensure smooth ridding on SMP machines and wouldn't this post problems?? About the mistake of installing UP on SMP machine - the spec could look up /proc/cpu or whatever to ensure proper kernel is being installed. [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: Qt
Dnia 06-01-2007, sob o godzinie 19:26 +0100, Łukasz Jernaś napisał(a):
While building KDE4 some issues came up. First of all our Qt4 qmake is named
different than in every other distro.
Nah - 90% of work is done. Just set QTDIR to %{_libdir}/qt4 and PATH too
$QTDI/bin:$PATH and everything works. Just some minor links:
[EMAIL PROTECTED] qt4]$ ls -l
razem 4
drwxr-xr-x 2 root root 4096 2007-01-03 00:35 bin
lrwxrwxrwx 1 root root 22 2007-01-03 00:17 doc
- /usr/share/doc/qt4-doc
drwxr-xr-x 2 root root 15 2006-11-22 13:34 include
lrwxrwxrwx 1 root root 22 2007-01-03 00:35 mkspecs
- /usr/share/qt4/mkspecs
drwxr-xr-x 11 root root 151 2007-01-02 13:32 plugins
[EMAIL PROTECTED]
___
pld-devel-en mailing list
pld-devel-en@lists.pld-linux.org
http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Poldek robi BUM
Przy install -F * powitał mnie taki kwiatek: kdelibs-devel-3.5.5-4.x86_64 zaznaczył kdelibs-libs-3.5.5-4.x86_64 (wł. kdelibs-libs 9:3.5.5-2) Something wrong, something not quite right. Assertion 'pkg_is_marked(ictx-ts-pms, pkg) == 0' failed, mark.c:101 Please report this bug to [EMAIL PROTECTED]. Przerwane Całość loga załączniku. [EMAIL PROTECTED] ~]$ rpm -qa | grep poldek poldek-0.20.1-0.20060823.21.6.x86_64 poldek-libs-0.20.1-0.20060823.21.6.x86_64 Zdrawiam [EMAIL PROTECTED] Installing set #32 Przetwarzanie zale¿no¶ci... kdelibs-3.5.5-2.x86_64 zostanie zast±piony przez kdelibs-3.5.5-4.x86_64 kdelibs-devel-3.5.5-2.x86_64 zostanie zast±piony przez kdelibs-devel-3.5.5-4.x86_64 kdelibs-devel-3.5.5-4.x86_64 zaznaczy³ xorg-lib-libICE-devel-1.0.3-1.x86_64 (w³. libtool(/usr/lib64/libICE.la)) xorg-lib-libICE-devel-1.0.2-1.x86_64 zostanie zast±piony przez xorg-lib-libICE-devel-1.0.3-1.x86_64 xorg-lib-libICE-devel-1.0.3-1.x86_64 zaznaczy³ xorg-lib-libICE-1.0.3-1.x86_64 (w³. xorg-lib-libICE = 1.0.3-1) xorg-lib-libICE-1.0.2-1.x86_64 zostanie zast±piony przez xorg-lib-libICE-1.0.3-1.x86_64 xorg-lib-libICE-1.0.2-3.athlon zostanie zast±piony przez xorg-lib-libICE-1.0.3-1.x86_64 b³±d: libICE.so.6 jest wymagany przez wine-0.9.16-1.athlon b³±d: libICE.so.6 jest wymagany przez wine-dll-d3d-0.9.16-1.athlon b³±d: libICE.so.6 jest wymagany przez wine-dll-gl-0.9.16-1.athlon b³±d: libICE.so.6 jest wymagany przez opera-9.02-2.athlon kdelibs-devel-3.5.5-4.x86_64 zaznaczy³ xorg-lib-libSM-devel-1.0.2-4.x86_64 (w³. libtool(/usr/lib64/libSM.la)) xorg-lib-libSM-devel-1.0.2-1.x86_64 zostanie zast±piony przez xorg-lib-libSM-devel-1.0.2-4.x86_64 xorg-lib-libSM-devel-1.0.2-4.x86_64 zaznaczy³ xorg-lib-libSM-1.0.2-4.x86_64 (w³. xorg-lib-libSM = 1.0.2-4) xorg-lib-libSM-1.0.2-1.x86_64 zostanie zast±piony przez xorg-lib-libSM-1.0.2-4.x86_64 xorg-lib-libSM-1.0.2-3.athlon zostanie zast±piony przez xorg-lib-libSM-1.0.2-4.x86_64 b³±d: xorg-lib-libSM-1.0.2-3.athlon (w³. libSM.so.6) jest wymagany przez opera-9.02-2.athlon b³±d: xorg-lib-libSM-1.0.2-3.athlon (w³. libSM.so.6) jest wymagany przez wine-0.9.16-1.athlon b³±d: xorg-lib-libSM-1.0.2-3.athlon (w³. libSM.so.6) jest wymagany przez wine-dll-d3d-0.9.16-1.athlon b³±d: xorg-lib-libSM-1.0.2-3.athlon (w³. libSM.so.6) jest wymagany przez wine-dll-gl-0.9.16-1.athlon kdelibs-devel-3.5.5-4.x86_64 zaznaczy³ xorg-lib-libX11-devel-1.1.1-1.x86_64 (w³. libtool(/usr/lib64/libX11.la)) xorg-lib-libX11-devel-1.0.99.1-1.x86_64 zostanie zast±piony przez xorg-lib-libX11-devel-1.1.1-1.x86_64 xorg-lib-libX11-devel-1.1.1-1.x86_64 zaznaczy³ xorg-lib-libXau-devel-1.0.3-1.x86_64 (w³. libtool(/usr/lib64/libXau.la)) xorg-lib-libXau-devel-1.0.2-1.x86_64 zostanie zast±piony przez xorg-lib-libXau-devel-1.0.3-1.x86_64 xorg-lib-libXau-devel-1.0.3-1.x86_64 zaznaczy³ xorg-lib-libXau-1.0.3-1.x86_64 (w³. xorg-lib-libXau = 1.0.3-1) xorg-lib-libXau-1.0.2-1.x86_64 zostanie zast±piony przez xorg-lib-libXau-1.0.3-1.x86_64 xorg-lib-libXau-1.0.2-3.athlon zostanie zast±piony przez xorg-lib-libXau-1.0.3-1.x86_64 xorg-lib-libX11-devel-1.1.1-1.x86_64 zaznaczy³ xorg-lib-libXdmcp-devel-1.0.2-4.x86_64 (w³. libtool(/usr/lib64/libXdmcp.la)) xorg-lib-libXdmcp-devel-1.0.2-1.x86_64 zostanie zast±piony przez xorg-lib-libXdmcp-devel-1.0.2-4.x86_64 xorg-lib-libXdmcp-devel-1.0.2-4.x86_64 zaznaczy³ xorg-lib-libXdmcp-1.0.2-4.x86_64 (w³. xorg-lib-libXdmcp = 1.0.2-4) xorg-lib-libXdmcp-1.0.2-1.x86_64 zostanie zast±piony przez xorg-lib-libXdmcp-1.0.2-4.x86_64 xorg-lib-libXdmcp-1.0.2-3.athlon zostanie zast±piony przez xorg-lib-libXdmcp-1.0.2-4.x86_64 xorg-lib-libX11-devel-1.1.1-1.x86_64 zaznaczy³ libxcb-devel-1.0-4.x86_64 (w³. libtool(/usr/lib64/libxcb-xlib.la)) libxcb-devel-1.0-4.x86_64 zaznaczy³ libpthread-stubs-0.1-1.x86_64 (w³. libpthread-stubs) libxcb-devel-1.0-4.x86_64 zaznaczy³ libxcb-1.0-4.x86_64 (w³. libxcb = 1.0-4) xorg-lib-libX11-devel-1.1.1-1.x86_64 zaznaczy³ xorg-lib-libX11-1.1.1-1.x86_64 (w³. xorg-lib-libX11 = 1.1.1-1) xorg-lib-libX11-1.0.99.1-1.x86_64 zostanie zast±piony przez xorg-lib-libX11-1.1.1-1.x86_64 xorg-lib-libX11-1.0.99.2-3.athlon zostanie zast±piony przez xorg-lib-libX11-1.1.1-1.x86_64 b³±d: xorg-lib-libX11-1.0.99.2-3.athlon (w³. libX11.so.6) jest wymagany przez opera-9.02-2.athlon b³±d: xorg-lib-libX11-1.0.99.2-3.athlon (w³. libX11.so.6) jest wymagany przez wine-0.9.16-1.athlon b³±d: xorg-lib-libX11-1.0.99.2-3.athlon (w³. libX11.so.6) jest wymagany przez wine-dll-d3d-0.9.16-1.athlon b³±d: xorg-lib-libX11-1.0.99.2-3.athlon (w³. libX11.so.6) jest wymagany przez wine-dll-gl-0.9.16-1.athlon zach³anna aktualizacja Mesa-libGL-6.5-1.20060911.1.athlon do 6.5.2-2 (niespe³nione libX11.so.6) b³±d: Mesa-libGL-6.5.2-2.x86_64: equal version installed, give up b³±d: libX11.so.6 jest wymagany przez Mesa-libGL-6.5-1.20060911.1.athlon kdelibs-devel-3.5.5-4.x86_64 zaznaczy³ xorg-lib-libXcursor-devel-1.1.8-3.x86_64 (w³. libtool(/usr/lib64/libXcursor.la))
Re: Poldek robi BUM
Dnia 02-01-2007, wto o godzinie 10:21 +0100, Cezary Krzyzanowski napisał(a): Przy install -F * powitał mnie taki kwiatek: Ekhmsorry - Evo gave me en before pl and I didn't see that. Nevertheless the problem stays. [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 24-12-2006, nie o godzinie 21:04 +0100, Łukasz Jernaś napisał(a): One more flaw - initramfs seems to ignore the initlevel parameter passed to the kernel from grub (setting it in /etc/inittab fixes the problem though) Hm - I haven't noticed that running normal init requires any parameter. shouldn't it be added before compressing the initrd? No - bootsplash is added the same way - appended to the image. This part works fine. i'm using kernel-desktop as a testbed. [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 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 initrdtab cpio -i initrdtab If this works, You have initramfs, if not - You've got initrd. If initrd, please mount it: mkdir fuck modprobe loop mount -oloop -tromfs initrdtab 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 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 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: vlc-gcc-hack.patch
Dnia 13-12-2006, śro o godzinie 09:17 +0100, Paweł Sikora napisał(a): glen, if you want such typedefs use /dev/brain, include mmintrin.h and pass -mmmx to cflags. We aren't a group of folk screaming at each other in the middle of a field. Please use /dev/courtsy next time. [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: Initramfs in geninitrd - ready RFC
Dnia 10-12-2006, nie o godzinie 00:41 +0100, Cezary Krzyzanowski
napisał(a):
Ok these changes *should* make possible proper initramfs start with both
udev on and off (I'm using udev, but I've also tested without and it
seems to work)
Ok - so finished - works.
I've replaced a mix of awk and sh to clean awk parsing and then I do
what I must in sh (like making a device node). The device will be
created if there is no device in /dev passed by root (regardless of
udev). So if there is no udev or udev fails to make a device and s/b
passed it as a parameter - it will be made as long it exists
in /proc/partitions
Full support for fbsplash incorporated as well. Some sanity checks (as
not both bootsplash and fbslash, or no fbsplash other then in
initramfs). Should work nicely.
I've also modified the sysconfig geninitrd file and splashutils
sysconfig fbsplash file to show options needed to be set for fbplash to
work correctly.
The only remaining problem is udev. Gonna toy with it later.
For now please wrie any comments. On resolving all comments I'm
commiting back to trunk and sending to buildres.
[EMAIL PROTECTED]
Index: geninitrd
===
--- geninitrd (.../trunk/geninitrd) (wersja 8099)
+++ geninitrd (.../branches/devel/geninitrd) (wersja 8099)
@@ -41,6 +41,8 @@
rootdev_nr=0
# default bootsplash is off, if it have to be on, install bootsplash package
BOOT_SPLASH=no
+# default same as bootsplash, if on install splashutils and some splashutils theme
+FB_SPLASH=no
# is /dev on tmpfs. internal variable
tmpfs_dev=
@@ -59,7 +61,8 @@
echo[--with=module] [--image-version] [--fstab=fstab] [--nocompress]
echo[--initrdfs=rom|ext2|cram] [--modules-conf=modules.conf]
echo[--with-raidstart] [--without-raidstart] [--with-insmod-static]
- echo[--without-bootsplash] [--lvmtoolsversion=1|2] [--with-udev] [--without-udev]
+ echo[--without-bootsplash] [--without-fbsplash]
+ echo[--lvmtoolsversion=1|2] [--with-udev] [--without-udev]
echo[--without-suspend] [--without-suspend2] [--without-dmraid]
echoinitrd-image kernel-version
echo(ex: `basename $0` /boot/initrd-2.2.5-15.img 2.2.5-15)
@@ -781,6 +784,10 @@
. /etc/sysconfig/bootsplash
fi
+if [ -r /etc/sysconfig/fbsplash ] ; then
+ . /etc/sysconfig/fbsplash
+fi
+
if [ ! -x /bin/initrd-busybox ] ; then
echo /bin/initrd-busybox is missing !
exit 1
@@ -817,6 +824,9 @@
--without-bootsplash)
BOOT_SPLASH=no
;;
+ --without-fbsplash)
+ FB_SPLASH=no
+ ;;
--without-suspend)
USE_SUSPEND=no;
;;
@@ -915,8 +925,7 @@
if [ x = x$INITRDFS ] ; then
if [ x = x$FS ] ; then
# default value
- # XXX: initramfs blocked for now
- if [ 1 = 0 -a $pack_version -ge 002005 ] ; then
+ if [ $pack_version -ge 002005 ] ; then
INITRDFS=initramfs
else
INITRDFS=rom
@@ -1005,6 +1014,16 @@
fi
fi
+if is_yes $FB_SPLASH; then
+ if is_yes $BOOT_SPLASH; then
+ echo 2 You can't use both bootsplash and fbsplash! Please choose one.
+ exit 1
+ elif [ $INITRDFS != initramfs ]; then
+ echo 2 FB_SPLASH works only if INITRDFS is initramfs!.
+ exit 1
+ fi
+fi
+
if [ ! -f /proc/mounts ]; then
echo 2 WARNING: /proc filesystem not mounted, may cause wrong results or failure.
fi
@@ -1047,6 +1066,9 @@
findmodule -lzf
fi
+if is_yes $FB_SPLASH; then
+ findmodule -evdev
+fi
if [ -n $ifneeded -a -z $MODULES ]; then
debug No modules are needed -- not building initrd image.
exit 0
@@ -1464,8 +1486,58 @@
if [ $INITRDFS = initramfs ]; then
mkdir -p $MNTIMAGE/newroot
cp -HR $org_rootdev $MNTIMAGE/dev
- echo mount -t $rootFs $org_rootdev /newroot $s
- echo switch_root /newroot /sbin/init $s
+ # Parsing root parameter
+ # We support passing root as hda3 /dev/hda3 0303 0x0303
+ cat 'EOF' $s
+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
+EOF
+ cat EOF $s
+mount -t
Re: Initramfs in geninitrd
Dnia 11-12-2006, pon o godzinie 15:37 +0100, Jacek Konieczny napisał(a): Do you have /sys mounted in the initramfs before starting udev? Yea - both mounted (/proc and /sys) - double checked that with sh while boot. BTW - I should have everything configured by geninitrd to make udev run - right? I don't see any difference in running udev in initramfs and initrd. [EMAIL PROTECTED] ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Initramfs in geninitrd
Today I've smoked my first 'serious' sh script, making another script
(linuxrc). Now I feel what webdevelopers must feel like.
Ok these changes *should* make possible proper initramfs start with both
udev on and off (I'm using udev, but I've also tested without and it
seems to work)
The generated init script can make use of root paramter, both in
form /dev/something /my/dir/super/device or 0203 and init parameter.
I've also done some early setups for splashutils. I've got silent and
verbose splash working on my laptop and I'll write some splash adding to
geninitrd.
One thing that makes me trouble is udev. Now static linked udev doesn't
do totally anything in init/linuxrc. It doesn't make a single device!
As I've sniffed arround, we're renaming udev in our udev.spec to
initrd-udev, but FC ppl rename udevd and start a static udevd in init.
I've been able to make this happen, but that implies having a static
udevtrigger and udevsettle in initramfs, as a little tweaked start_udev
script there. That could be wrong. Any ideas then how to make udev
happen in early boot instaed of whole udev daemon??
[EMAIL PROTECTED]
Index: trunk/geninitrd
===
--- trunk/geninitrd (wersja 8089)
+++ trunk/geninitrd (kopia robocza)
@@ -41,6 +41,8 @@
rootdev_nr=0
# default bootsplash is off, if it have to be on, install bootsplash package
BOOT_SPLASH=no
+# default same as bootsplash, if on install splashutils and some splashutils theme
+FB_SPLASH=no
# is /dev on tmpfs. internal variable
tmpfs_dev=
@@ -59,7 +61,8 @@
echo[--with=module] [--image-version] [--fstab=fstab] [--nocompress]
echo[--initrdfs=rom|ext2|cram] [--modules-conf=modules.conf]
echo[--with-raidstart] [--without-raidstart] [--with-insmod-static]
- echo[--without-bootsplash] [--lvmtoolsversion=1|2] [--with-udev] [--without-udev]
+ echo[--without-bootsplash] [--without-fbsplash]
+ echo[--lvmtoolsversion=1|2] [--with-udev] [--without-udev]
echo[--without-suspend] [--without-suspend2] [--without-dmraid]
echoinitrd-image kernel-version
echo(ex: `basename $0` /boot/initrd-2.2.5-15.img 2.2.5-15)
@@ -781,6 +784,10 @@
. /etc/sysconfig/bootsplash
fi
+if [ -r /etc/sysconfig/fbsplash ] ; then
+ . /etc/sysconfig/fbsplash
+fi
+
if [ ! -x /bin/initrd-busybox ] ; then
echo /bin/initrd-busybox is missing !
exit 1
@@ -817,6 +824,9 @@
--without-bootsplash)
BOOT_SPLASH=no
;;
+ --without-fbsplash)
+ FB_SPLASH=no
+ ;;
--without-suspend)
USE_SUSPEND=no;
;;
@@ -915,8 +925,7 @@
if [ x = x$INITRDFS ] ; then
if [ x = x$FS ] ; then
# default value
- # XXX: initramfs blocked for now
- if [ 1 = 0 -a $pack_version -ge 002005 ] ; then
+ if [ $pack_version -ge 002005 ] ; then
INITRDFS=initramfs
else
INITRDFS=rom
@@ -1047,6 +1056,9 @@
findmodule -lzf
fi
+if is_yes $FB_SPLASH; then
+ findmodule -evdev
+fi
if [ -n $ifneeded -a -z $MODULES ]; then
debug No modules are needed -- not building initrd image.
exit 0
@@ -1464,8 +1476,34 @@
if [ $INITRDFS = initramfs ]; then
mkdir -p $MNTIMAGE/newroot
cp -HR $org_rootdev $MNTIMAGE/dev
- echo mount -t $rootFs $org_rootdev /newroot $s
- echo switch_root /newroot /sbin/init $s
+ echo mount -t proc none /proc $s
+ # the worst part if we don't have udev
+ if [ $USE_UDEV != yes ]; then
+ # We either have root passed into kernel as /dev/something or as a maj-min number
+ # we parse acordingly
+ cat 'EOF' $s
+root=$(busybox awk ' /root=/ { gsub(/.*root=/,NIL,$0); gsub(/ .*/,NIL,$0); print $0; } ' /proc/cmdline )
+if [[ $root == +(/+([A-z0-9])) ]]; then
+ rootnr=$(busybox awk -v root=$root ' { if ($4 == root) { print $1 $2; } } ' /proc/partitions)
+else
+ rootnr=${root#??} ${root%??}
+ root=$(busybox awk \
+ BEGIN { maj=${root#??}; min=${root%??}; } \
+ { if ( (\$1 == maj) (\$2 == min) ) { print \$4; } } \
+ /proc/partitions )
+fi
+mknod $root b $rootnr
+EOF
+ fi
+ cat EOF $s
+mount -t $rootFs \$root /newroot
+init=\$(busybox awk ' /init=\// { gsub(/.*init=/,NIL,\$0); gsub(/ .*/,NIL,\$0); print \$0; } ' /proc/cmdline )
+if [ -z \$init -o ! -n /newroot\$init ]; then
+ init=/sbin/init
+fi
+umount /proc
+exec switch_root /newroot \$init
+EOF
# we need real file, not symlink
rm -f $MNTIMAGE/init
cp -a $MNTIMAGE/linuxrc $MNTIMAGE/init
___
pld-devel-en mailing list
pld-devel-en@lists.pld-linux.org
http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: Fwd: SPECS: mozilla-firefox.spec - updated to version 2.0, - release 0....
Dnia 25-10-2006, śro o godzinie 14:50 +0200, Arkadiusz Miskiewicz napisał(a): On Wednesday 25 October 2006 14:41, Elan Ruusamäe wrote: what was wrong merging first from DEVEL? work duplication really sucks! + this way is wrong according to mozilla people and we ALREADY had problems wit this. I'm totally unaware, why did You (cieciwa) tried to make FF once more, when DEVEL branch had it almost all!? + We can't distribute MOZILLA_OFFICIAL and despite DEVEL branch mentioned this, You insisted on building version, we are not allowed to build!! mozilla-firefox will distribute binary version of FF. Work on FF has been moved to iceweasel and that is the place You could work on, instead destroying what was done here. [EMAIL PROTECTED] -- Fear leads to anger, anger leads to hate, hate leads to suffering - Yoda ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: SPECS: swiftfox.spec - update License
Dnia 20-09-2006, śro o godzinie 12:43 +0200, Tomasz Mateja napisał(a): According to license we can name it f.ex. pldswitfox or switfox-PLD and make it distributable :) Yes - if we make it build from their sources, which isn't as easy as it seems. I've failed to build it from spec, by hand or even from config flags shown on their webpage. Maby just easier? mozilla-firefox-swift ? [EMAIL PROTECTED] -- Fear leads to anger, anger leads to hate, hate leads to suffering - Yoda ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
