Re: Raising minimum CPU requirement for i386 kernel
Hi, Bastian Blank schrieb: > This means that Debian will get uninstallable on the following CPUs: > - Intel i486, > - Intel Pentium (MMX), > - AMD K5, > - AMD K6(-2, -3), Many schools are using LTSP on Debian (Edu) and have this hardware as their thinclients. Would be a shame if all those schools using free software cannot use the next release (and following) because their hardware is no longer supported. And I'm talking of really large numbers here worldwide. Regards, -- .''`. Philipp Hübner : :' : pgp fp: BA61 0B0A 2626 D49C BFC6 1C18 1619 74E4 C259 E0E8 `. `'` HP: http://debalance.funpic.de, Skype: philipp-huebner `- ICQ: 235-524-440, Jabber: der_scha...@jabber.org signature.asc Description: OpenPGP digital signature
Re: Raising minimum CPU requirement for i386 kernel
On Sun, May 24, 2009 at 9:07 PM, Bastian Blank wrote: > - VIA C3 before Nehemiah and > - National Semiconductor Geode (GXm, GXLV, GX1 and GX2). That affects XO-1 hardware being manufactured now, and C3s are among the viable CPUs for low cost, low dissipation "school server" style hardware. On the school server, I do my best to keep Debian a valid alternative (though the builds are Fedora based) and with a bit of packaging help most (all?) the XS specific packages could be in Debian. On the XO side, Jonas is packaging sugar and there's a mini-CDD called DebXO that seems to be quite active. I understand supporting additional hw does mean sizable work. Thanks for the fantastic work done so far. Please do consider not dropping support. cheers, m -- martin.langh...@gmail.com mar...@laptop.org -- School Server Architect - ask interesting questions - don't get distracted with shiny stuff - working code first - http://wiki.laptop.org/go/User:Martinlanghoff -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#530392: fixed
We believe that the bug you reported is now fixed; the following package(s) have been removed from unstable: linux-kernel-di-m68k-2.6 | 0.94 | source Note that the package(s) have simply been removed from the tag database and may (or may not) still be in the pool; this is not a bug. The package(s) will be physically removed automatically when no suite references them (and in the case of source, when no binary references it). Please also remember that the changes have been done on the master archive (ftp-master.debian.org) and will not propagate to any mirrors (ftp.debian.org included) until the next cron.daily run at the earliest. Packages are never removed from testing by hand. Testing tracks unstable and will automatically remove packages which were removed from unstable when removing them from testing causes no dependency problems. Bugs which have been reported against this package are not automatically removed from the Bug Tracking System. Please check all open bugs and close them or re-assign them to another package if the removed package was superseded by another one. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 530...@bugs.debian.org. The full log for this bug can be viewed at http://bugs.debian.org/530392 This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org. Debian distribution maintenance software pp. Frank Lichtenheld (the ftpmaster behind the curtain) -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#530391: fixed
We believe that the bug you reported is now fixed; the following package(s) have been removed from unstable: ata-modules-2.6.26-2-ixp4xx-di | 1.37lenny2 | arm cdrom-core-modules-2.6.26-2-footbridge-di | 1.37lenny2 | arm cdrom-core-modules-2.6.26-2-iop32x-di | 1.37lenny2 | arm core-modules-2.6.26-2-footbridge-di | 1.37lenny2 | arm core-modules-2.6.26-2-iop32x-di | 1.37lenny2 | arm core-modules-2.6.26-2-ixp4xx-di | 1.37lenny2 | arm core-modules-2.6.26-2-orion5x-di | 1.37lenny2 | arm crc-modules-2.6.26-2-footbridge-di | 1.37lenny2 | arm crc-modules-2.6.26-2-iop32x-di | 1.37lenny2 | arm crc-modules-2.6.26-2-ixp4xx-di | 1.37lenny2 | arm crc-modules-2.6.26-2-orion5x-di | 1.37lenny2 | arm crypto-core-modules-2.6.26-2-footbridge-di | 1.37lenny2 | arm crypto-core-modules-2.6.26-2-iop32x-di | 1.37lenny2 | arm crypto-core-modules-2.6.26-2-ixp4xx-di | 1.37lenny2 | arm crypto-core-modules-2.6.26-2-orion5x-di | 1.37lenny2 | arm crypto-dm-modules-2.6.26-2-footbridge-di | 1.37lenny2 | arm crypto-dm-modules-2.6.26-2-iop32x-di | 1.37lenny2 | arm crypto-dm-modules-2.6.26-2-ixp4xx-di | 1.37lenny2 | arm crypto-dm-modules-2.6.26-2-orion5x-di | 1.37lenny2 | arm crypto-modules-2.6.26-2-footbridge-di | 1.37lenny2 | arm crypto-modules-2.6.26-2-iop32x-di | 1.37lenny2 | arm crypto-modules-2.6.26-2-ixp4xx-di | 1.37lenny2 | arm crypto-modules-2.6.26-2-orion5x-di | 1.37lenny2 | arm ext2-modules-2.6.26-2-iop32x-di | 1.37lenny2 | arm ext2-modules-2.6.26-2-ixp4xx-di | 1.37lenny2 | arm ext2-modules-2.6.26-2-orion5x-di | 1.37lenny2 | arm ext3-modules-2.6.26-2-iop32x-di | 1.37lenny2 | arm ext3-modules-2.6.26-2-ixp4xx-di | 1.37lenny2 | arm ext3-modules-2.6.26-2-orion5x-di | 1.37lenny2 | arm fat-modules-2.6.26-2-footbridge-di | 1.37lenny2 | arm fat-modules-2.6.26-2-iop32x-di | 1.37lenny2 | arm fat-modules-2.6.26-2-ixp4xx-di | 1.37lenny2 | arm fat-modules-2.6.26-2-orion5x-di | 1.37lenny2 | arm ide-core-modules-2.6.26-2-iop32x-di | 1.37lenny2 | arm ide-modules-2.6.26-2-footbridge-di | 1.37lenny2 | arm ide-modules-2.6.26-2-iop32x-di | 1.37lenny2 | arm input-modules-2.6.26-2-iop32x-di | 1.37lenny2 | arm input-modules-2.6.26-2-ixp4xx-di | 1.37lenny2 | arm input-modules-2.6.26-2-orion5x-di | 1.37lenny2 | arm isofs-modules-2.6.26-2-footbridge-di | 1.37lenny2 | arm isofs-modules-2.6.26-2-iop32x-di | 1.37lenny2 | arm jffs2-modules-2.6.26-2-orion5x-di | 1.37lenny2 | arm kernel-image-2.6.26-2-footbridge-di | 1.37lenny2 | arm kernel-image-2.6.26-2-iop32x-di | 1.37lenny2 | arm kernel-image-2.6.26-2-ixp4xx-di | 1.37lenny2 | arm kernel-image-2.6.26-2-orion5x-di | 1.37lenny2 | arm linux-kernel-di-arm-2.6 | 1.37lenny2 | source loop-modules-2.6.26-2-footbridge-di | 1.37lenny2 | arm loop-modules-2.6.26-2-iop32x-di | 1.37lenny2 | arm loop-modules-2.6.26-2-ixp4xx-di | 1.37lenny2 | arm loop-modules-2.6.26-2-orion5x-di | 1.37lenny2 | arm md-modules-2.6.26-2-footbridge-di | 1.37lenny2 | arm md-modules-2.6.26-2-iop32x-di | 1.37lenny2 | arm md-modules-2.6.26-2-ixp4xx-di | 1.37lenny2 | arm md-modules-2.6.26-2-orion5x-di | 1.37lenny2 | arm minix-modules-2.6.26-2-orion5x-di | 1.37lenny2 | arm multipath-modules-2.6.26-2-footbridge-di | 1.37lenny2 | arm multipath-modules-2.6.26-2-iop32x-di | 1.37lenny2 | arm multipath-modules-2.6.26-2-ixp4xx-di | 1.37lenny2 | arm multipath-modules-2.6.26-2-orion5x-di | 1.37lenny2 | arm nic-modules-2.6.26-2-footbridge-di | 1.37lenny2 | arm nic-modules-2.6.26-2-iop32x-di | 1.37lenny2 | arm nic-modules-2.6.26-2-ixp4xx-di | 1.37lenny2 | arm nic-modules-2.6.26-2-orion5x-di | 1.37lenny2 | arm nic-shared-modules-2.6.26-2-footbridge-di | 1.37lenny2 | arm nic-shared-modules-2.6.26-2-orion5x-di | 1.37lenny2 | arm nic-usb-modules-2.6.26-2-iop32x-di | 1.37lenny2 | arm nic-usb-modules-2.6.26-2-ixp4xx-di | 1.37lenny2 | arm nic-usb-modules-2.6.26-2-orion5x-di | 1.37lenny2 | arm nls-core-modules-2.6.26-2-footbridge-di | 1.37lenny2 | arm nls-core-modules-2.6.26-2-iop32x-di | 1.37lenny2 | arm reiserfs-modules-2.6.26-2-footbridge-di | 1.37lenny2 | arm reiserfs-modules-2.6.26-2-iop32x-di | 1.37lenny2 | arm reiserfs-modules-2.6.26-2-ixp4xx-di | 1.37lenny2 | arm reiserfs-modules-2.6.26-2-orion5x-di | 1.37lenny2 | arm sata-modules-2.6.26-2-iop32x-di | 1.37lenny2 | arm sata-modules-2.6.26-2-ixp4xx-di | 1.37lenny2 | arm sata-modules-2.6.26-2-orion5x-di | 1.37lenny2 | arm scsi-core-modules-2.6.26-2-footbridge-di | 1.37lenny2 | arm scsi-core-modules-2.6.26-2-iop32x-di | 1.37lenny2 | arm scsi-core-modules-2.6.26-2-ixp4xx-di | 1.37lenny2 | arm scsi-core-modules-2.6.26-2-orion5x-di | 1.37lenny2 | arm usb-modules-2.6.26-2-footbridge-di | 1.37lenny2 | arm usb-modules-2.6.26-2-iop32x-di | 1.37lenny2 | arm usb-modules-2.6.26-2-ixp4xx-di | 1.37lenny2 | arm usb-modules-2.6.26-2-orion5x-di | 1.37lenny2 | arm usb-storage-modules-2.6.26-2-footbridge-di | 1.37lenny2 | arm usb-storage-modules-2.6.26-2-iop32x-di | 1.37lenny2 | arm usb-storage-modules-2.6.26-2-ixp4xx-di | 1.37lenny2 | arm usb-storage-modules-2.6.26-2-orion5x-di | 1.37lenny2 | arm Note that the package(s) have simpl
Re: Raising minimum CPU requirement for i386 kernel
On Sun, 24 May 2009, Bastian Blank wrote: > Hi folks > > I would like to raise the minimum CPU requirement for the shipped Linux > kernels in the i386 port to i686 (with cmov). [..] Popcon gives us some rough numbers to think about: linux-image-2.6-68649518 linux-image-2.6-486 6191 Given that the installer's automatic kernel choice tends to be accurate, we've got quite some non-cmov users. Actually, i386 has got many more non-cmov users than any non-i386/amd64 architecture has _in total_: linux-image-2.6-ixp4xx 772 (=arm/armel) linux-image-2.6-powerpc 551 linux-image-2.6-sparc64 192 linux-image-2.6-orion5x 106 (=arm/armel) (rest <100) #include So, the good work you're doing to keep supporting arm/powerpc/sparc/etc. will actually benefit much less users than the number you'll be annoying when you drop i386 non-cmov ... Best regards, Anne Bezemer -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Man slays killer leopard with spzear
<>
Donkey Kong Classjic!
<>
Miss America Won't Testiify In sex Sting Case
<>
Dutch unvveil robot to fill car gas tank
<>
Re: Raising minimum CPU requirement for i386 kernel
"J.A. Bezemer" writes: > On Sun, 24 May 2009, Bastian Blank wrote: > >> Hi folks >> >> I would like to raise the minimum CPU requirement for the shipped Linux >> kernels in the i386 port to i686 (with cmov). > [..] > > Popcon gives us some rough numbers to think about: > > linux-image-2.6-68649518 > linux-image-2.6-486 6191 > > Given that the installer's automatic kernel choice tends to be accurate, > we've got quite some non-cmov users. Actually, i386 has got many more > non-cmov users than any non-i386/amd64 architecture has _in total_: > > linux-image-2.6-ixp4xx 772 (=arm/armel) > linux-image-2.6-powerpc 551 > linux-image-2.6-sparc64 192 > linux-image-2.6-orion5x 106 (=arm/armel) > (rest <100) > > #include > > So, the good work you're doing to keep supporting arm/powerpc/sparc/etc. > will actually benefit much less users than the number you'll be annoying > when you drop i386 non-cmov ... > > > Best regards, > > Anne Bezemer And how many people with such low power systems do run popcon? How many use a custom kernel? MfG Goswin -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Problems with graphical installer "gtk"
Hi First, sorry for my bad English from Barcelona. I'm trying a preseed installation and "hd-media" images and It's OK. I tried the "DEBIAN_FRONTEND" parameter with "newt" and "text" frontend and it's OK. When I try with "DEBIAN_FRONTEND=gtk", the following error apears: /home/cjwatson/src/debian/debian-installer/branch/lenny/packages/cdebconf/src/frontend.c:275 (frontend_new): Cannot load frontend module /usr/lib/cdebconf/frontend/gtk.so: /usr/lib/cdebconf/frontend/gtk.so: cannot open shared object: No such file or directory Process (1081): INFO: kbd-module: setting console module to unicode. I have downloaded image from here: http://ftp.debian.org/debian/dists/lenny/main/installer-i386/current/images/hd-media/gtk/ I check with md5sum "hd-media" and iso image and it's OK. I preseed the image with the parameters : kernel /boot/vmlinuz preseed/file=/preseed.cfg debian-installer/locale=en_UK console-setup/layout=es It's compatible "preseed.cfg" file with "gtk installation"? What does the *"bogl"* and "corba" parameters? Thanks for all in advance Oriol Matavacas
linux-kernel-di-arm-2.6 REMOVED from testing
FYI: The status of the linux-kernel-di-arm-2.6 source package in Debian's testing distribution has changed. Previous version: 1.37lenny2 Current version: (not in testing) Hint: Package not in unstable The script that generates this mail tries to extract removal reasons from comments in the britney hint files. Those comments were not originally meant to be machine readable, so if the reason for removing your package seems to be nonsense, it is probably the reporting script that got confused. Please check the actual hints file before you complain about meaningless removals. -- This email is automatically generated once a day. As the installation of new packages into testing happens multiple times a day you will receive later changes on the next day. See http://release.debian.org/testing-watch/ for more information. -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: Illustrated Guide to Installing Debian GNU/Linux
Hi Eric, On Sonntag, 22. Februar 2009, Eric Doviak wrote: > At Holger's suggestion, I placed the "Illustrated Guide to Installing > Debian" on the Debian Wiki[1]. > [1] http://wiki.debian.org/LennyIllustratedInstall Cool! > I'm not sure what the next step is here, so please let me know what > else I can do/should do to help. I'll blog about it, to make it a bit more known :-) regards, Holger signature.asc Description: This is a digitally signed message part.
Re: Raising minimum CPU requirement for i386 kernel
On Mon May 25 2009 06:03:40 Goswin von Brederlow wrote: > And how many people with such low power systems do run popcon? How > many use a custom kernel? OTOH, none of the non-cmov i386 systems here run popcon either. --Mike Bird -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
preseed the dm-crypt passphrase failed
Hello, i tried to install about 20 laptops full preseeded with crypted root and swap (and a normal /boot). The installation work but without accepting my preseeded partman-crypto/passphrase (and partman-crypto/passphrase-again). I use 'd-i preseeded partman-crypto/passphrase password ' and the same with 'partman-crypto/passphrase-again'. I see the Values in the 'passwords.dat' when the system is processing the preseed file but it seems that the 'blockdev-keygen' script didn't get it. Is it not possible to preseed this value? Or how is it possible debug partman-crypto precessing? I did not find any information about a solution for problem. I search the last two weeks for an answer in the internet :-( Many thanks for any help Gabriel -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
preseed the dm-crypt passphrase failed
Hello, i tried to install about 20 laptops full preseeded with crypted root and swap (and a normal /boot). The installation work but without accepting my preseeded partman-crypto/passphrase (and partman-crypto/passphrase-again). I use 'd-i preseeded partman-crypto/passphrase password ' and the same with 'partman-crypto/passphrase-again'. I see the Values in the 'passwords.dat' when the system is processing the preseed file but it seems that the 'blockdev-keygen' script didn't get it. Is it not possible to preseed this value? Or how is it possible debug partman-crypto precessing? I did not find any information about a solution for problem. I search the last two weeks for an answer in the internet :-( Many thanks for any help Gabriel -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processing of flash-kernel_2.19_armel.changes
flash-kernel_2.19_armel.changes uploaded successfully to localhost along with the files: flash-kernel_2.19.dsc flash-kernel_2.19.tar.gz flash-kernel_2.19_armel.deb flash-kernel-installer_2.19_armel.udeb Greetings, Your Debian queue daemon -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
flash-kernel_2.19_armel.changes ACCEPTED
Accepted: flash-kernel-installer_2.19_armel.udeb to pool/main/f/flash-kernel/flash-kernel-installer_2.19_armel.udeb flash-kernel_2.19.dsc to pool/main/f/flash-kernel/flash-kernel_2.19.dsc flash-kernel_2.19.tar.gz to pool/main/f/flash-kernel/flash-kernel_2.19.tar.gz flash-kernel_2.19_armel.deb to pool/main/f/flash-kernel/flash-kernel_2.19_armel.deb Override entries for your package: flash-kernel-installer_2.19_armel.udeb - standard debian-installer flash-kernel_2.19.dsc - source utils flash-kernel_2.19_armel.deb - optional utils Announcing to debian-devel-chan...@lists.debian.org Thank you for your contribution to Debian. -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: preseed the dm-crypt passphrase failed
On Monday 25 May 2009, Gabriel wrote: > I did not find any information about a solution for problem. Please file a bug report against partman-crypto for this issue, so we can better track the discussion. Provide at least the following information: - the exact image you are using (full URL of the image you downloaded) - does it work correctly if you do _not_ preseed partman? - the contents of your preseed file for partman (with a fictional passphrase) - a debug log for partman-crypto: - run the installation with 'priority=medium' and *only* the partman questions preseeded (again with fictional passphrase) - just before you start partman, add a line 'set -x' in the script blockdev-keygen script AND in the file /lib/partman/lib/crypto-base.sh - save /var/log/syslog after the point where you see the error and send it to us - the hardware-summary for that installation (in /var/log after you run the "Save debug logs" option from the main menu) Please gzip the syslog before sending it, otherwise your mail may not reach the mailing list. Cheers, FJP -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
mmc-modules should be loaded by default on ARM Kirkwood
The mmc-modules udeb should be downloaded automatically because installations to an SD card will be quite popular on one device. This is not done at the moment because the module is priority "extra". I assume the correct way to proceed is to change the priority of this udeb to "standard" in linux-kernel-di-armel-2.6/package-list and ask the FTP masters to change the override file. Is this correct? -- Martin Michlmayr http://www.cyrius.com/ -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: mmc-modules should be loaded by default on ARM Kirkwood
* Otavio Salvador [2009-05-25 17:20]: > I'd say that you could make a module depends on it; so it will be > uploaded from network or from the media (as done for other modules > already). Well, I don't really see which other module should depend on it. What did you have in mind exactly? -- Martin Michlmayr http://www.cyrius.com/ -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: mmc-modules should be loaded by default on ARM Kirkwood
On Monday 25 May 2009, Martin Michlmayr wrote: > The mmc-modules udeb should be downloaded automatically because > installations to an SD card will be quite popular on one device. > This is not done at the moment because the module is priority "extra". > > I assume the correct way to proceed is to change the priority of this > udeb to "standard" in linux-kernel-di-armel-2.6/package-list and ask > the FTP masters to change the override file. Do they accept different priority for the same udeb for different arches? Even if they do, I doubt we really want that (too hard to keep track of such subtle differences). IMO the better solution is to load it using anna-install, either during hw-detect or early in partman, based on a (sub)architecture test. hw-detect is probably the most logical choice. -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: mmc-modules should be loaded by default on ARM Kirkwood
Hello Martin, On Mon, May 25, 2009 at 5:09 PM, Martin Michlmayr wrote: > The mmc-modules udeb should be downloaded automatically because > installations to an SD card will be quite popular on one device. > This is not done at the moment because the module is priority "extra". > > I assume the correct way to proceed is to change the priority of this > udeb to "standard" in linux-kernel-di-armel-2.6/package-list and ask > the FTP masters to change the override file. > > Is this correct? I'd say that you could make a module depends on it; so it will be uploaded from network or from the media (as done for other modules already). -- Otavio Salvador O.S. Systems E-mail: ota...@ossystems.com.br http://www.ossystems.com.br Mobile: +55 53 9981-7854 http://projetos.ossystems.com.br -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: mmc-modules should be loaded by default on ARM Kirkwood
* Frans Pop [2009-05-25 22:30]: > Do they accept different priority for the same udeb for different arches? The udeb name contains the name of the subarch, so it would be unique. > IMO the better solution is to load it using anna-install, either > during hw-detect or early in partman, based on a (sub)architecture > test. hw-detect is probably the most logical choice. Hmm, that seems overengineered too. How about I simply include the udeb in the netboot initrd for that particular subarch? -- Martin Michlmayr http://www.cyrius.com/ -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: mmc-modules should be loaded by default on ARM Kirkwood
Hello, On Mon, May 25, 2009 at 5:38 PM, Martin Michlmayr wrote: > * Frans Pop [2009-05-25 22:30]: >> Do they accept different priority for the same udeb for different arches? > > The udeb name contains the name of the subarch, so it would be unique. > >> IMO the better solution is to load it using anna-install, either >> during hw-detect or early in partman, based on a (sub)architecture >> test. hw-detect is probably the most logical choice. > > Hmm, that seems overengineered too. How about I simply include the > udeb in the netboot initrd for that particular subarch? This works but I'd prefer to not bloat the initrd with non-required modules. I'd more for hw-detect or partman as suggested by Frans. Between both I think that hw-detect is the most logical place for it. -- Otavio Salvador O.S. Systems E-mail: ota...@ossystems.com.br http://www.ossystems.com.br Mobile: +55 53 9981-7854 http://projetos.ossystems.com.br -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: mmc-modules should be loaded by default on ARM Kirkwood
On Monday 25 May 2009, Martin Michlmayr wrote: > * Frans Pop [2009-05-25 22:30]: > > Do they accept different priority for the same udeb for different > > arches? > > The udeb name contains the name of the subarch, so it would be unique. Right. I still don't like it much. > > IMO the better solution is to load it using anna-install, either > > during hw-detect or early in partman, based on a (sub)architecture > > test. hw-detect is probably the most logical choice. > > Hmm, that seems overengineered too. I disagree. The function of hw-detect, and in this case more particular disk-detect, is to ensure any hardware needed for partitioning gets made available. IMO this fits that definition perfectly. > How about I simply include the udeb in the netboot initrd for that > particular subarch? Against that is that it's not needed at that stage, so it's initrd bloat. And that _is_ an issue on arm. -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: Make d-i capable to cross compile armel|* firmware images
Hi, This was one of the release main goals and if nobody has something in favour of it, this goal should be dropped avoiding complexity grow in code and maintainability. Cheers -- Héctor Orón -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#515990: Short Notice!!!
Your email has been award the lump sum in the Irish Online,send us your info to get the £1,350,000 Names., Address..., Sex..., Tel... -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#515990: Short Notice!!!
Your email has been award the lump sum in the Irish Online,send us your info to get the £1,350,000 Names., Address..., Sex..., Tel... -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#515990: Short Notice!!!
Your email has been award the lump sum in the Irish Online,send us your info to get the £1,350,000 Names., Address..., Sex..., Tel... -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#529307: Loan service
This is to inform you that e-LOAN Inc.is currently offering loan to both firms and individuals at low interest rate(2%)Contact us today at: loanservic...@aol.com -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#524233: console-setup should conflict with console-data
On Sat, 23 May 2009, Anton Zinoviev wrote: > On Wed, Apr 15, 2009 at 07:14:34PM +0200, Kurt Roeckx wrote: > > Package: console-setup, console-data > > Severity: serious > > > > Hi, > > > > console-setup and console-data both allow you to setup the > > keyboard layout but they do not take each other settings into > > account. > > > > I think there is yet an other package that does the same thing, > > but I'm not sure about it's name. > > I didn't close this bug because I was considering to add a Debconf > question asking which package should configure the console (similar to > that the user gets with more than one display manager - xdm, wdm, kdm, > gdm). But after a second thought I doubt this is worth the effort - > console-tools is almost unmaintained and there are still some things > that console-setup doesn't do, such as the default state of NumLock, > setterm. Moreover the scripts in console-tools and console-data are in > bad shape and it will be difficult for their maintainers to do the > required changes. > > So unless there are objections I'd like to close #524233 and #524239. Such choice ought to be documented in a README.Debian and maybe even in the description. The user should have a way to know what is more or less obsolete and what should be kept on his system to have proper console configuration support. Cheers, -- Raphaël Hertzog Contribuez à Debian et gagnez un cahier de l'admin Debian Lenny : http://www.ouaza.com/wp/2009/03/02/contribuer-a-debian-gagner-un-livre/ -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
