From zbiggy at o2.pl Sat Nov 8 00:05:57 2008 From: zbiggy at o2.pl (Zbigniew Luszpinski) Date: Sat, 8 Nov 2008 00:05:57 +0100 Subject: lunar-1.6.4-beta1-i686.iso some feedback Message-ID: <200811080005.57537.zbiggy@o2.pl> Hello, I think speedtch DSL modem support should be removed from boot kernel of lunar-1.6.4-beta1 ISO. I use this modem and when it is connected to computer during iso boot the kernel segfaults during speedtch module init and freezes. CONFIG_USB_SPEEDTOUCH=n Another reason for removing it from bootkernel is that the speedtouch USB modem will not work without binary firmware uploaded to modem during every boot. Lunar iso has no such firmware files so modem will not work even if speedtch module will be working. Another issue is with time zones installer menu. For lunar-1.6.4-beta1-i686 this is complete mess. This is weird as earlier isos have working time zones menu. The last issue candidate is creation of swap file. After creating swap partition in previous step, the next step for creating swap file should not appear because swap was already created. have a nice day, zbiggy From dennisveatch at bellsouth.net Sat Nov 8 04:09:39 2008 From: dennisveatch at bellsouth.net (Dennis Veatch) Date: Fri, 7 Nov 2008 22:09:39 -0500 Subject: [Lunar-commits] ImageMagick: Yes, I have read the NOTE in the DETAILS. However, the current In-Reply-To: <20081108030426.ACE819B1B0@doppio.foo-projects.org> References: <20081108030426.ACE819B1B0@doppio.foo-projects.org> Message-ID: <200811072209.39262.dennisveatch@bellsouth.net> On Friday 07 November 2008 22:03:16 Dennis 'stumbles' Veatch wrote: > commit 32776be38fea37d352522a120e7cd41b7cdd90c5 > Author: Dennis 'stumbles' Veatch > Date: Fri Nov 7 22:03:16 2008 -0500 > > ImageMagick: Yes, I have read the NOTE in the DETAILS. However, the > current version borks on the make, this one does not. Revert it if you > like. --- > graphics/ImageMagick/DETAILS | 32 ++++++++++++++++---------------- > 1 files changed, 16 insertions(+), 16 deletions(-) > > diff --git a/graphics/ImageMagick/DETAILS b/graphics/ImageMagick/DETAILS > index 14928d7..fe9f489 100644 > --- a/graphics/ImageMagick/DETAILS > +++ b/graphics/ImageMagick/DETAILS > @@ -2,30 +2,30 @@ > # the x.y.z-0 releases. Instead, ONLY when x.y.z-0 is released, then we > # should version bump to x.y.(z-1)-(highest). That version is always > # kept on the ftp.imagemagick.org site and should be considered STABLE!!! > - MODULE=ImageMagick > - VERSION=6.4.4-10 > - BASEVERSION=$(echo $VERSION | cut -d- -f1) > - SOURCE=$MODULE-$VERSION.tar.bz2 > -SOURCE_DIRECTORY=$BUILD_DIRECTORY/$MODULE-$BASEVERSION > - SOURCE_URL[0]=ftp://ftp.imagemagick.org/pub/ImageMagick > - SOURCE_URL[1]=$SFORGE_URL/imagemagick > - SOURCE_URL[2]=ftp://mirror.aarnet.edu.au/pub/ImageMagick > - SOURCE_URL[3]=ftp://ftp.fu-berlin.de/unix/X11/graphics/ImageMagick > - SOURCE_URL[4]=ftp://ftp.eos.hokudai.ac.jp/pub/graphics/ImageMagick > - SOURCE_URL[5]=ftp://ftp.kddlabs.co.jp/graphics/ImageMagick > - > SOURCE_URL[6]=ftp://ftp.u-aizu.ac.jp/pub/graphics/image/ImageMagick/imagema >gick.org - > SOURCE_URL[7]=ftp://zoffy.asahi-net.or.jp/pub/graphics/ImageMagick - > SOURCE_URL[8]=ftp://ftp.nluug.nl/pub/ImageMagick > + MODULE=ImageMagick > + VERSION=6.4.5-4 > + BASEVERSION=$(echo $VERSION | cut -d- -f1) > + SOURCE=$MODULE-$VERSION.tar.bz2 > +SOURCE_DIRECTORY=$BUILD_DIRECTORY/$MODULE-$BASEVERSION > + SOURCE_URL[0]=ftp://ftp.imagemagick.org/pub/ImageMagick > + SOURCE_URL[1]=$SFORGE_URL/imagemagick > + SOURCE_URL[2]=ftp://mirror.aarnet.edu.au/pub/ImageMagick > + SOURCE_URL[3]=ftp://ftp.fu-berlin.de/unix/X11/graphics/ImageMagick > + SOURCE_URL[4]=ftp://ftp.eos.hokudai.ac.jp/pub/graphics/ImageMagick > + SOURCE_URL[5]=ftp://ftp.kddlabs.co.jp/graphics/ImageMagick > + > SOURCE_URL[6]=ftp://ftp.u-aizu.ac.jp/pub/graphics/image/ImageMagick/imagema >gick.org + > SOURCE_URL[7]=ftp://zoffy.asahi-net.or.jp/pub/graphics/ImageMagick + > SOURCE_URL[8]=ftp://ftp.nluug.nl/pub/ImageMagick > SOURCE_URL[9]=http://ftp.surfnet.nl/pub/ImageMagick > SOURCE_URL[10]=ftp://giswitch.sggw.waw.pl/pub/graphics/ImageMagick > SOURCE_URL[11]=ftp://ftp.sunet.se/pub/multimedia/graphics/ImageMagick > SOURCE_URL[12]=http://hpux.connect.org.uk/hppd/hpux/X11/Viewers > SOURCE_URL[13]=ftp://ftp.fifi.org/pub/ImageMagick > SOURCE_URL[14]=ftp://ftp.rge.com/pub/multimedia/imagemagick > - SOURCE_VFY=sha1:4ddd575c9ea520eed598b6871049e9a4d7bad2d2 > + SOURCE_VFY=sha1:c3c5cc2a5c6cb3244e47e61cb08ca4d29f6f3d89 > WEB_SITE=http://www.imagemagick.org > ENTERED=20010922 > - UPDATED=20081031 > + UPDATED=20081107 > PSAFE=no > SHORT="Automated and interactive manipulation of images" > > _______________________________________________ > Lunar-commits mailing list > Lunar-commits at lunar-linux.org > http://foo-projects.org/mailman/listinfo/lunar-commits Crapola. My bad. The prior version does lin fine, had a brain fart. I will revert this if it turns out to be an issue. -- You can tuna piano but you can't tune a fish. http://www.lunar-linux.org/ It's worth the spin. From dennisveatch at bellsouth.net Tue Nov 11 20:10:37 2008 From: dennisveatch at bellsouth.net (Dennis Veatch) Date: Tue, 11 Nov 2008 14:10:37 -0500 Subject: [Lunar-commits] microcode: updated to release 20080910 all Intel P6 and later CPUs supported In-Reply-To: <20081111185916.101399B1B5@doppio.foo-projects.org> References: <20081111185916.101399B1B5@doppio.foo-projects.org> Message-ID: <200811111410.37591.dennisveatch@bellsouth.net> On Tuesday 11 November 2008 13:57:37 Zbigniew Luszpinski wrote: > commit 0521037b0be9f65f6cad4bacfd48e299cf4088af > Author: Zbigniew Luszpinski > Date: Tue Nov 11 19:57:37 2008 +0100 > > microcode: updated to release 20080910 all Intel P6 and later CPUs > supported --- > utils/microcode/BUILD | 6 +++--- > utils/microcode/DETAILS | 26 +++++++++++++++++++------- > utils/microcode/PRE_BUILD | 5 ++++- > 3 files changed, 26 insertions(+), 11 deletions(-) > > diff --git a/utils/microcode/BUILD b/utils/microcode/BUILD > index fa3ece5..436c339 100644 > --- a/utils/microcode/BUILD > +++ b/utils/microcode/BUILD > @@ -1,8 +1,8 @@ > ( > > - bzcat $SOURCE_CACHE/$SOURCE > microcode.dat && > prepare_install && > - install -m644 microcode.dat /etc/ && > - rm microcode.dat > + mkdir -p /etc/firmware && > + install -m644 $MODULE-$VERSION.dat /etc/firmware && > + ln -sf /etc/firmware/$MODULE-$VERSION.dat /etc/microcode.dat > > ) > $C_FIFO 2>&1 > diff --git a/utils/microcode/DETAILS b/utils/microcode/DETAILS > index 1365129..b940b84 100644 > --- a/utils/microcode/DETAILS > +++ b/utils/microcode/DETAILS > @@ -1,13 +1,25 @@ > MODULE=microcode > - VERSION=20070907.dat > - SOURCE=${MODULE}-${VERSION}.bz2 > - SOURCE_URL=http://www.urbanmyth.org/microcode/ucode/ > + VERSION=20080910 > + SOURCE=$MODULE-$VERSION.tgz > + SOURCE_URL=http://downloadmirror.intel.com/14303/eng/ > SOURCE_DIRECTORY=$BUILD_DIRECTORY/$MODULE-$VERSION > - SOURCE_VFY=sha1:d51a6d76758bdf29145078377a60c4c23656310f > - WEB_SITE="http://www.urbanmyth.org/microcode/" > + SOURCE_VFY=sha1:4be35128816268521f93362095c3fa26f1ce9388 > + WEB_SITE=http://downloadcenter.intel.com/ > ENTERED=20070916 > - UPDATED=20070916 > + UPDATED=20081111 > SHORT="Intel microcode - data files" > cat < -Processor microcode files. > +The microcode data file contains the latest > +microcode definitions for all Intel processors. > +Intel releases microcode updates to correct > +processor behavior as documented > +in the respective processor specification updates. > +While the regular approach to getting > +this microcode update is via a BIOS upgrade, > +Intel realizes that this can be an administrative hassle. > +The Linux Operating System and VMware ESX products > +have a mechanism to update the microcode after booting. > +For example, this file will be used by > +the operating system mechanism if the file is placed > +in the /etc/firmware directory of the Linux system. > EOF > diff --git a/utils/microcode/PRE_BUILD b/utils/microcode/PRE_BUILD > index 27ba77d..149e8d0 100644 > --- a/utils/microcode/PRE_BUILD > +++ b/utils/microcode/PRE_BUILD > @@ -1 +1,4 @@ > -true > +mk_source_dir $SOURCE_DIRECTORY && > +cd $SOURCE_DIRECTORY && > +cp $SOURCE_CACHE/$SOURCE . && > +unpack $SOURCE > _______________________________________________ > Lunar-commits mailing list > Lunar-commits at lunar-linux.org > http://foo-projects.org/mailman/listinfo/lunar-commits ermm, I think that really should be /lib/firmware and not /etc/firmware for the dat file. -- You can tuna piano but you can't tune a fish. http://www.lunar-linux.org/ It's worth the spin. From zbiggy at o2.pl Tue Nov 11 21:33:11 2008 From: zbiggy at o2.pl (Zbigniew Luszpinski) Date: Tue, 11 Nov 2008 21:33:11 +0100 Subject: [Lunar-commits] microcode: updated to release 20080910 all Intel P6 and later CPUs supported In-Reply-To: <200811111410.37591.dennisveatch@bellsouth.net> References: <20081111185916.101399B1B5@doppio.foo-projects.org> <200811111410.37591.dennisveatch@bellsouth.net> Message-ID: <200811112133.12099.zbiggy@o2.pl> Tuesday 11 of November 2008 20:10:37 Dennis Veatch wrote: > > +For example, this file will be used by > > +the operating system mechanism if the file is placed > > +in the /etc/firmware directory of the Linux system. > > EOF > ermm, I think that really should be /lib/firmware and not /etc/firmware for > the dat file. This comment about /etc/firmware was taken from microcode download page at Intel website: http://downloadcenter.intel.com/detail_desc.aspx?agr=&ProductID=49&DwnldID=14303&strOss=&OSFullName=&lang=eng Just followed Intel suggestion. microcode_ctl command however uses /etc/microcode.dat so symlink is created at the end of install. Maybe Auke know or can ask microcode maintainer at Intel why /etc/firmware is recommended instead of /lib/firmware where usually firmware is placed or /etc/microcode.dat which is default microcode file location which microcode_ctl command uses. AFAIK only /etc/microcode.dat location is important because microcode_ctl command makes use of it by default (changeable by using -f pathToMicrocode parameter). have a nice day, Zbigniew 'zbiggy' Luszpinski From sofar at foo-projects.org Tue Nov 11 22:58:07 2008 From: sofar at foo-projects.org (Kok, Auke) Date: Tue, 11 Nov 2008 13:58:07 -0800 Subject: [Lunar-commits] microcode: updated to release 20080910 all Intel P6 and later CPUs supported In-Reply-To: <200811112133.12099.zbiggy@o2.pl> References: <20081111185916.101399B1B5@doppio.foo-projects.org> <200811111410.37591.dennisveatch@bellsouth.net> <200811112133.12099.zbiggy@o2.pl> Message-ID: <4919FFEF.40505@foo-projects.org> Zbigniew Luszpinski wrote: > Tuesday 11 of November 2008 20:10:37 Dennis Veatch wrote: >>> +For example, this file will be used by >>> +the operating system mechanism if the file is placed >>> +in the /etc/firmware directory of the Linux system. >>> EOF > >> ermm, I think that really should be /lib/firmware and not /etc/firmware for >> the dat file. > > This comment about /etc/firmware was taken from microcode download page at > Intel website: > http://downloadcenter.intel.com/detail_desc.aspx?agr=&ProductID=49&DwnldID=14303&strOss=&OSFullName=&lang=eng > Just followed Intel suggestion. microcode_ctl command however > uses /etc/microcode.dat so symlink is created at the end of install. > > Maybe Auke know or can ask microcode maintainer at Intel why /etc/firmware is > recommended instead of /lib/firmware where usually firmware is placed > or /etc/microcode.dat which is default microcode file location which > microcode_ctl command uses. > > AFAIK only /etc/microcode.dat location is important because microcode_ctl > command makes use of it by default (changeable by using -f pathToMicrocode > parameter). > > have a nice day, > Zbigniew 'zbiggy' Luszpinski > _______________________________________________ > Lunar-dev mailing list > Lunar-dev at lunar-linux.org > http://foo-projects.org/mailman/listinfo/lunar-dev I'll look into that. ty for noticing. Auke From sofar at foo-projects.org Fri Nov 14 19:47:00 2008 From: sofar at foo-projects.org (Kok, Auke) Date: Fri, 14 Nov 2008 10:47:00 -0800 Subject: e17 version numbering bug In-Reply-To: <20081114113538.920049B1B0@doppio.foo-projects.org> References: <20081114113538.920049B1B0@doppio.foo-projects.org> Message-ID: <491DC7A4.3070000@foo-projects.org> > New versions: (138) > e17-svn : svn-44 -> svn-45 > e_dbus-svn : svn-44 -> svn-45 > e_modules-svn : svn-44 -> svn-45 > e_utils-svn : svn-44 -> svn-45 > eclair-svn : svn-44 -> svn-45 > ecore-svn : svn-44 -> svn-45 > edb-svn : svn-44 -> svn-45 > edje-svn : svn-44 -> svn-45 > eet-svn : svn-44 -> svn-45 > efreet-svn : svn-44 -> svn-45 > eina-svn : svn-44 -> svn-45 > elicit-svn : svn-44 -> svn-45 > embryo-svn : svn-44 -> svn-45 > emotion-svn : svn-44 -> svn-45 > emprint-svn : svn-44 -> svn-45 > engrave-svn : svn-44 -> svn-45 > entice-svn : svn-44 -> svn-45 > epeg-svn : svn-44 -> svn-45 > epsilon-svn : svn-44 -> svn-45 > esmart-svn : svn-44 -> svn-45 > etk-svn : svn-44 -> svn-45 > evas-svn : svn-44 -> svn-45 > ewl-svn : svn-44 -> svn-45 > examine-svn : svn-44 -> svn-45 > exhibit-svn : svn-44 -> svn-45 > exml-svn : svn-44 -> svn-45 whoever wrote the code that generates these version numbers: what are you going to do in week 1 of next year???? Cheers, Auke