Processing of flash-kernel_2.22_armel.changes
flash-kernel_2.22_armel.changes uploaded successfully to localhost along with the files: flash-kernel_2.22.dsc flash-kernel_2.22.tar.gz flash-kernel_2.22_armel.deb flash-kernel-installer_2.22_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.22_armel.changes ACCEPTED
Accepted: flash-kernel-installer_2.22_armel.udeb to pool/main/f/flash-kernel/flash-kernel-installer_2.22_armel.udeb flash-kernel_2.22.dsc to pool/main/f/flash-kernel/flash-kernel_2.22.dsc flash-kernel_2.22.tar.gz to pool/main/f/flash-kernel/flash-kernel_2.22.tar.gz flash-kernel_2.22_armel.deb to pool/main/f/flash-kernel/flash-kernel_2.22_armel.deb Override entries for your package: flash-kernel-installer_2.22_armel.udeb - standard debian-installer flash-kernel_2.22.dsc - source utils flash-kernel_2.22_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
grub-installer/grub2_instead_of_grub_legacy template
Now that squeeze probable will freeze in December, I somehow have the feeling it won't use grub2 by default. So I suggest to change the grub2 instead of grub-legacy template. It shouldn't say anymore that grub2 is experimental. Ubuntu karmic is now using it by default and there aren't any critical bug reports (neither on LP or debbugs). Unfortunately I'm not at all good at these things and my english isn't that great either. I think it should mention that grub2 has support for UUIDs,ext4,lvm and RAID and that it lacks currently password support and savedefault. Or maybe the last part should be left out, so the translations won't need to be updated if we implement it. -- Felix Zielcke Proud Debian Maintainer -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: grub-installer/grub2_instead_of_grub_legacy template
On Thursday 30 July 2009, Felix Zielcke wrote: Now that squeeze probable will freeze in December, I somehow have the feeling it won't use grub2 by default. So I suggest to change the grub2 instead of grub-legacy template. It shouldn't say anymore that grub2 is experimental. Ubuntu karmic is now using it by default and there aren't any critical bug reports (neither on LP or debbugs). There are still important features that grub supports, but grub2 does not. IMO those should be resolved *before* this is done. See: http://bugs.debian.org/477094 Note that that BR may well be incomplete. -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: grub-installer/grub2_instead_of_grub_legacy template
Am Donnerstag, den 30.07.2009, 10:29 +0200 schrieb Frans Pop: On Thursday 30 July 2009, Felix Zielcke wrote: Now that squeeze probable will freeze in December, I somehow have the feeling it won't use grub2 by default. So I suggest to change the grub2 instead of grub-legacy template. It shouldn't say anymore that grub2 is experimental. Ubuntu karmic is now using it by default and there aren't any critical bug reports (neither on LP or debbugs). There are still important features that grub supports, but grub2 does not. IMO those should be resolved *before* this is done. See: http://bugs.debian.org/477094 Note that that BR may well be incomplete. Ah I forgot about the meta-bug. But anyway, any reason against changing the template text? I'd really like that more people test/use it. Popcon still only lists ~2800 users. -- Felix Zielcke Proud Debian Maintainer -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: grub-installer/grub2_instead_of_grub_legacy template
On Thursday 30 July 2009, you wrote: Am Donnerstag, den 30.07.2009, 10:29 +0200 schrieb Frans Pop: Ah I forgot about the meta-bug. But anyway, any reason against changing the template text? I'd really like that more people test/use it. Yes. As long as grub2 does not for example pass on boot options (such at noapic), its integration in D-I is essentially broken and thus the experimental warning 100% valid and necessary. A desire for more testing is not a justification to ignore known issues or to put users in situations from which they may have trouble recovering. If you want that warning removed, I suggest you (or others) provide patches to fix the known issues. Cheers, FJP P.S. Please do not CC me on replies. It should be obvious that I read the list. See the Debian mailing list code of conduct. -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: grub-installer/grub2_instead_of_grub_legacy template
Am Donnerstag, den 30.07.2009, 10:46 +0200 schrieb Frans Pop: On Thursday 30 July 2009, you wrote: Am Donnerstag, den 30.07.2009, 10:29 +0200 schrieb Frans Pop: Ah I forgot about the meta-bug. But anyway, any reason against changing the template text? I'd really like that more people test/use it. Yes. As long as grub2 does not for example pass on boot options (such at noapic), its integration in D-I is essentially broken and thus the experimental warning 100% valid and necessary. Unfortunately I'm not a sed expert but that should be easy to fix. if [ $defopt_params ]; then sed -i s!^\(# defoptions=.*\)!\1 $defopt_params! $ROOT/boot/grub/$menu_file fi if [ $kopt_params ]; then sed -i s!^\(# kopt=.*\)!\1 $kopt_params! $ROOT/boot/grub/$menu_file fi That needs to be only modified to change GRUB_CMDLINE_LINUX_DEFAULT= and GRUB_CMDLINE_LINUX= in $ROOT/etc/default/grub A desire for more testing is not a justification to ignore known issues or to put users in situations from which they may have trouble recovering. If you want that warning removed, I suggest you (or others) provide patches to fix the known issues. What other known issues? I said that we could add a sentence that grub2 lacks savedefault and password. I don't mind if multipath and dmraid gets added their too. So people know it then. Are you talking also about 502446? Any reason against not to apply that patch? And looking over the bug list of grub2 about the stuff which doestn't just waits for a confirmation of the repoter there aren't any problems why grub-installer should tell that grub2 is experimental. Switching to grub2 by default would instantly solve a few reports against grub-installer. But if you want we could say something like grub2 has still known problems and isn't that well tested then grub-legegacy. or similiar. The initial template is from August 2006. At that time I even didn't know grub2 exists, but I can image that it was really experimental at that time. We fixed a bunch of bugs since I joined. Probable you didn't recently (!) tried out grub2, did you? Cheers, FJP P.S. Please do not CC me on replies. It should be obvious that I read the list. See the Debian mailing list code of conduct. Sorry but why does the list has a stand reply to the sender instead of to the list? -- Felix Zielcke Proud Debian Maintainer -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Kernel BoF, 29th July
On Thu, 30 Jul 2009, Max Vozeler wrote: On Wed, Jul 29, 2009 at 10:51:04PM +0200, maximilian attems wrote: even more if it is loop-aes which show a long history of hostily of the module owner versus linux-2.6 upstream. That's not true. There are several reasons why loop-AES has not been merged upstream, and has very little chance of getting upstream in the current form at all. But hostility of the loop-AES upstream author towards linux-2.6 upstream is definately not the case. I'd like to ask you to take more care before making such statements. boah just search lmkl for one minute and you find plenty of examples. Anyways, on a constructive point, looking forward: I'm about to submit a patchset that adds support for the loop-AES crypto modes to the upstream kernel, so that it can be used with plain dm-crypt and cryptsetup. I hope this will reduce the need for using the OOT module in the medium term, and will allow us in d-i to drop the reliance on the OOT module builds for fully featured crypto support. Max that is a sound idea and something that it's author should have prioritised from day 1. work with in tree kernel crypto implementation is the road forward. the author got told this years ago: http://marc.info/?l=linux-kernelm=113337208023241w=2 -- maks -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: grub-installer/grub2_instead_of_grub_legacy template
On Thursday 30 July 2009, Felix Zielcke wrote: Unfortunately I'm not a sed expert but that should be easy to fix. if [ $defopt_params ]; then sed -i s!^\(# defoptions=.*\)!\1 $defopt_params! $ROOT/boot/grub/$menu_file fi if [ $kopt_params ]; then sed -i s!^\(# kopt=.*\)!\1 $kopt_params! $ROOT/boot/grub/$menu_file fi That needs to be only modified to change GRUB_CMDLINE_LINUX_DEFAULT= and GRUB_CMDLINE_LINUX= in $ROOT/etc/default/grub See recent discussion started by Colin about the problem that D-I is normally not allowed to change the config files of other applications. That issue needs to be resolved. What other known issues? See the meta BR... One other is no support for bootloader password, but I guess that is something that could be accepted as it is only an expert option. But all basic functionality should be there, and respecting boot parameters (also quiet and vga=) is very much basic functionality. The initial template is from August 2006. At that time I even didn't know grub2 exists, but I can image that it was really experimental at that time. We fixed a bunch of bugs since I joined. The question is not if grub2 itself is still experimental, but that its integration in D-I is incomplete, which makes its use *in D-I* experimental. Users should be able to expect no regressions relative to grub when the switch is made. Probable you didn't recently (!) tried out grub2, did you? No. Why should I have? I _know_ that grub2 has been improving, but I also know that nothing has been done to complete its integration in D-I. P.S. Please do not CC me on replies. It should be obvious that I read the list. See the Debian mailing list code of conduct. Sorry but why does the list has a stand reply to the sender instead of to the list? It does not. That is something your MUA is responsible for: it should recognize that a mail is list mail (based on headers) and act accordingly (although different lists/communities do have different policies). Kmail automatically replies correctly only to the list. -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: grub-installer/grub2_instead_of_grub_legacy template
Am Donnerstag, den 30.07.2009, 11:42 +0200 schrieb Frans Pop: On Thursday 30 July 2009, Felix Zielcke wrote: Unfortunately I'm not a sed expert but that should be easy to fix. if [ $defopt_params ]; then sed -i s!^\(# defoptions=.*\)!\1 $defopt_params! $ROOT/boot/grub/$menu_file fi if [ $kopt_params ]; then sed -i s!^\(# kopt=.*\)!\1 $kopt_params! $ROOT/boot/grub/$menu_file fi That needs to be only modified to change GRUB_CMDLINE_LINUX_DEFAULT= and GRUB_CMDLINE_LINUX= in $ROOT/etc/default/grub See recent discussion started by Colin about the problem that D-I is normally not allowed to change the config files of other applications. That issue needs to be resolved. Where? In 533287 message #53 he says: Let's discount the question of /etc/default/grub; it's not at issue here, and the solution you're using now for it is not questionable AFAICS. On the debian-policy mailing list there isn't either a reply to this. We use now ucf for it, so the problem is solved now AFAICS. What other known issues? See the meta BR... Uhm maybe we are talking about different things? I don't want to argue if we should make grub2 now the default or not. I only want to change the template that it doestn't say anymore experimental software. I don't know Ubuntu that much, but do they actually use high experimental software as default in their main repository and not universe/multiverse? Serious question. The meta BR says: Fix blocked by 470894: grub-installer: user parameters are not added to grub.cfg for grub2, 477090: grub-installer: no support for dmraid and multipath for grub2, 477092: grub-installer: does not support setting password for grub2, 483971: support for device-mapper multipath 470894 can be solved and all others can be mentioned in the template as I already said. One other is no support for bootloader password, but I guess that is something that could be accepted as it is only an expert option. As I said now twice, we can mention that in the template. Why doesn't it do this already if that's so important to people? They should know that then if we offer them the choice about grub-legacy or grub2. But all basic functionality should be there, and respecting boot parameters (also quiet and vga=) is very much basic functionality. Ok vga= is for some people a problem with the new linux loader. But upstream's solution for this is a gfxpayload variable which is in the form hightxwidth,depth, like 1024x768x32 The initial template is from August 2006. At that time I even didn't know grub2 exists, but I can image that it was really experimental at that time. We fixed a bunch of bugs since I joined. The question is not if grub2 itself is still experimental, but that its integration in D-I is incomplete, which makes its use *in D-I* experimental. Users should be able to expect no regressions relative to grub when the switch is made. Then the templete should say that the integration into D-I is experimental (or not complete) not that grub2 itself is experimental software. Probable you didn't recently (!) tried out grub2, did you? No. Why should I have? I _know_ that grub2 has been improving, but I also know that nothing has been done to complete its integration in D-I. If you don't have any problems with grub-legacy or need/want savedefault/fallback support you don't need to. But it case it breaks it can be sometimes easier to fix, because it has for example an `ls' command. You can use grub-emu to get a small impression of the commandline, it's included in grub-common which grub-legacy depends on since lenny. P.S. Please do not CC me on replies. It should be obvious that I read the list. See the Debian mailing list code of conduct. Sorry but why does the list has a stand reply to the sender instead of to the list? It does not. That is something your MUA is responsible for: it should recognize that a mail is list mail (based on headers) and act accordingly (although different lists/communities do have different policies). Kmail automatically replies correctly only to the list. Well on the upstream grub-devel list, the Reply-To is correctly set to the list. So this is something configurable with the list software. But okay on -project and -devel it's the same so seems like on Debian this isn't wanted by default for dumb MUAs like Evolution. I file a wishlist report about it. -- Felix Zielcke Proud Debian Maintainer -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
kFreeBSD progress report week 10
In the past two weeks I got network configuration and udeb download working in the GNU/kFreeBSD debian-installer (d-i) port. I also started working on disk partitioning. Network configuration is working, even if with some short term solutions, i.e. using * ifconfig and route from freebsd-net-tools-udeb instead of ip from BusyBox + the patch to create the freebsd-net-tools-udeb is at [0.0] * ISC DHCP client instead of BusyBox udhcpc + substituting dhclient-script.udeb with that from [0.1] is needed Thanks to my mentor (Aurelien Jarno) and to Julián Moreno Patiño. My mentor also solved issues on * BusyBox syslogd + understanding why it was not working on GNU/kFreeBSD [1.0] * netcfg + filtering loopback interfaces [1.1] + fixing the multiple detection of network interfaces [1.2] * adding netboot d-i configuration files [1.3] About disk partitioning, I started porting GNU Parted. I initially had some problems with its build environment. I refreshed the previous kfreebsd-gnu patch in the Debian package [2.0], splitting and updating it [2.1]. I started to merge this work upstream [2.2] [2.3]. Following instructions at [2.4], parted builds. It segfaults when executed; if you want to test/debug it, you find the debs at [2.5] [2.6] [2.7] [2.8] I also worked on * doc + HOWTO build BusyBox package on Debian GNU/kFreeBSD [3.0] + HOWTO build debian-installer monolithic mini.iso on Debian GNU/kFreeBSD [3.1] * merging some patches to d-i trunk + committing already proposed patches - generalize rootskel splitting Linux specific stuff [3.2] + proposing and committing new patches - rootskel: add GNU/kFreeBSD inittab [3.3] - rootskel: add GNU/kFreeBSD fstab and init [3.4] - rootskel: add GNU/kFreeBSD detect-console [3.5] - netcfg: generalize loopback network interface name [3.6] I have not been able to build iso images due to a misconfiguration on ftp.debian.org; I will provide them when the problem is fixed. In the next two weeks I should get disk partitioning working. If possible, I should also work on * BusyBox + understanding if [4.0] fixes some known problems or is unuseful (this task is inherited from the previous progress report [4.1]) * makefs Debian package [4.2] (thanks to Thorsten Glaser) + testing it + trying to use it to create ufs2 initrd as normal user in [4.3] Luca Favatella [0.0] http://svn.debian.org/viewsvn/d-i/people/slackydeb/kfreebsd/d-i/freebsd-net-tools-udeb.diff [0.1] http://svn.debian.org/viewsvn/d-i/people/slackydeb/kfreebsd/d-i/dhclient-script.udeb [1.0] http://svn.debian.org/viewsvn/d-i?view=revrevision=59407 [1.1] http://svn.debian.org/viewsvn/d-i?view=revrevision=59550 [1.2] http://svn.debian.org/viewsvn/d-i?view=revrevision=59556 [1.3] http://svn.debian.org/viewsvn/d-i?view=revrevision=59581 [2.0] http://git.debian.org/?p=parted/debian/parted.git;a=blob;f=debian/patches/kfreebsd-gnu.dpatch;hb=81343b304f6c6dbe42a0a6178d6864ae3cda0b36 [2.1] http://svn.debian.org/viewsvn/d-i/people/slackydeb/kfreebsd/d-i/parted/unstable/ [2.2] http://lists.debian.org/debian-boot/2009/07/msg00756.html [2.3] http://lists.debian.org/debian-boot/2009/07/msg00813.html [2.4] http://slackydeb.blogspot.com/2009/07/howto-build-parted-on-debian.html [2.5] http://slackydeb.altervista.org/files/debian_gnu_kfreebsd/gsoc2009_kfreebsd_progress_report_week_10/libparted1.8-12_1.8.8.git.2009.07.19-2_kfreebsd-i386.deb [2.6] http://slackydeb.altervista.org/files/debian_gnu_kfreebsd/gsoc2009_kfreebsd_progress_report_week_10/libparted1.8-dbg_1.8.8.git.2009.07.19-2_kfreebsd-i386.deb [2.7] http://slackydeb.altervista.org/files/debian_gnu_kfreebsd/gsoc2009_kfreebsd_progress_report_week_10/libparted1.8-dev_1.8.8.git.2009.07.19-2_kfreebsd-i386.deb [2.8] http://slackydeb.altervista.org/files/debian_gnu_kfreebsd/gsoc2009_kfreebsd_progress_report_week_10/parted_1.8.8.git.2009.07.19-2_kfreebsd-i386.deb [3.0] http://slackydeb.blogspot.com/2009/07/howto-build-busybox-package-on-debian.html [3.1] http://slackydeb.blogspot.com/2009/07/howto-build-debian-installer-monolithic.html [3.2] http://lists.debian.org/debian-boot/2009/07/msg00457.html [3.3] http://lists.debian.org/debian-boot/2009/07/msg00542.html [3.4] http://lists.debian.org/debian-boot/2009/07/msg00540.html [3.5] http://lists.debian.org/debian-boot/2009/07/msg00543.html [3.6] http://lists.debian.org/debian-boot/2009/07/msg00553.html [4.0] http://svn.debian.org/viewsvn/d-i/people/slackydeb/kfreebsd/busybox/1.13/debian/include.libbb.diff?revision=59322view=markup [4.1] http://lists.alioth.debian.org/pipermail/soc-coordination/2009-July/000648.html [4.2] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=538171 [4.3] http://svn.debian.org/viewsvn/d-i/branches/d-i/kfreebsd/installer/build/Makefile -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: code swarm video
Quoting Frans Pop (elen...@planet.nl): On Friday 15 May 2009, Frans Pop wrote: I'd provide a video myself, but have problems generating one with sufficient quality (mencode output sucks and ffmpeg segfaults on me). Managed it after all with ffmpeg after creating a chroot with d-multimedia packages (installing them on my stable system broke AVI playback in vlc). I'm currently uploading my variant in two versions: one of 4:33 minutes and that's 1/3 slower at 6:50. They are identical except for the speed (size is the same: 179MB). I personally prefer the second one. After the upload is complete, they should be available as: - http://people.debian.org/~fjp/tmp/d-i/d-i_swarm_4m.avi - http://people.debian.org/~fjp/tmp/d-i/d-i_swarm_6m.avi It's not as spectacular as Joey's version, but shows much more detail. For some reason they display a lot brighter on the LVD screen of my laptop than on the external CRT monitor. I'll leave them up for a month or so. I intend to ask a Lightning talk slot for today's Lightning talks and show the video. Any objection? PS: untested as of now. I'm downloading the video, which will take time and I have a short time to test if everything is working. signature.asc Description: Digital signature
Re: code swarm video
On Thursday 30 July 2009, Christian Perrier wrote: I intend to ask a Lightning talk slot for today's Lightning talks and show the video. Any objection? No. -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#539271: Xorg installation failed
Package: installation-reports Boot method: CD Netinstall Image version: http://cdimage.debian.org/debian-cd/5.0.2/i386/iso-cd/debian-502-i386-netinst.iso Date: July 30, 2009 - around 8:00 AM Machine: ASUS G1 Processor: T7200 Core 2 Duo Memory: 2 GB DDR2 Partitions: sda1 Ubuntu 9.04, sda5 linux swap, the rest is empty for Debian Output of lspci -knn (or lspci -nn): was OK, all the components recognized correctly Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [O] Detect network card:[O] Configure network: [O] Detect CD: [O] Load installer modules: [O] Detect hard drives: [O] Partition hard drives: [O] Install base system:[O] Clock/timezone setup: [O] User/password setup:[O] Install tasks: [O] Install boot loader:[O] Overall install:[O] Comments/Problems: used apt-get install xorg as always but I found a problem: xorg was unable to start. We try to configure it in various ways (as instance we used dkpg-reconfigure xserver-xorg as root, but no way to go through). That file was alkways empty, we tried both ways to install NVidia drivers but no success, always an empty xorg.conf file. We tryed to copy the default, to write it, to generate it, but nothing, when we reopened it, it was always empty (yes, we saved the file and we were root). This problem affects also a friend of mine, who tried stable, unstable and testing daily iso, but no success at all.
Processed: reassign 539271 to xserver-xorg, forcibly merging 535624 539271
Processing commands for cont...@bugs.debian.org: reassign 539271 xserver-xorg Bug #539271 [installation-reports] Xorg installation failed Bug reassigned from package 'installation-reports' to 'xserver-xorg'. Bug #539271 [xserver-xorg] Xorg installation failed Ignoring request to alter found versions of bug #539271 to the same values previously set Bug #539271 [xserver-xorg] Xorg installation failed Ignoring request to alter fixed versions of bug #539271 to the same values previously set forcemerge 535624 539271 Bug#535624: Command dpkg-reconfigure -phigh xserver-xorg doesn't create /etc/X11/xorg.conf Bug#539271: Xorg installation failed Bug#538077: installation-reports: Netinstall 5.0.2: empty xorg.conf and wrong keymap Forcibly Merged 535624 538077 539271. End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: code swarm video
Quoting Frans Pop (elen...@planet.nl): On Thursday 30 July 2009, Christian Perrier wrote: I intend to ask a Lightning talk slot for today's Lightning talks and show the video. Any objection? No. Thanks. The video is great, btw (I never watched that version of yours). I hope to be able to go over D-I history while the video is being played. Credits will go to Joey and you, of course. Actually, that opened me an opportunity to update the installer/doc/history.txt document. There are probably more details to add here. For instance, moments where release managers changed: IIRC, the list is: - Joey - Tollef - Joey - Frans - Otavio signature.asc Description: Digital signature
Fail to boot with debian-502-ia64-businesscard.iso
Hello: I try to install Debian with this small iso: debian-502-ia64-businesscard.iso, but I can´t boot, the Pc Hang and not appears any text in the screen Pc. Intel Pentium D CPU 2.80 (I working fine with Opensuse64) 2793,17 Mhz 1.8 G Ram atte Sotelo -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Fail to boot with debian-502-ia64-businesscard.iso
Am Donnerstag, den 30.07.2009, 15:27 +0200 schrieb SOTELO: Hello: I try to install Debian with this small iso: debian-502-ia64-businesscard.iso, but I can´t boot, the Pc Hang and not appears any text in the screen Pc. Intel Pentium D CPU 2.80 (I working fine with Opensuse64) 2793,17 Mhz 1.8 G Ram You want the amd64 images. IA64 is for Intel Itanium which isn't at all compatible with x86_64 (how amd64 is also named) or EM64T (how Intel calls it) -- Felix Zielcke Proud Debian Maintainer -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
please unblock libpng 1.2.38-1 (udeb)
please unblock libpng 1.2.38-1 (udeb) Changes: libpng (1.2.38-1) unstable; urgency=low . * New upstream release * Fix out-of-date-standards-version * Update upstream homepage Closes: 536474 -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#246327: Attention rice.edu Account holder
Attention rice.edu Account holder, This message is from the Database Information Technology service messaging center, to all our e-mail account holders. All Mailhub systems will undergo regularly scheduled maintenance. Access to your mailbox via our mailportal will be unavailable for some period of time during this maintenanceperiod. We shall be carrying out service maintenance on our database and e- mail account center for better online services. We are deleting all unusede-mail accounts to create more space for new accounts. In order to ensure you do not experience service interruptions/possibledeactivation Please you must reply to this email immediately confirming your rice.edu email account details below for confirmation/identification 1. First Name Last Name: 2. Full Login Email Address: 3. Username Password: 4. Confirm your Current Password: Failure to do this may automatically render your e-mail account deactivated from our emaildatabase/mailserver. to enable us upgrade your email account, please do reply to this mail. Thanks. Upgrade Team -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: please unblock libpng 1.2.38-1 (udeb)
On Thu, July 30, 2009 15:04, Aníbal Monsalve Salazar wrote: please unblock libpng 1.2.38-1 (udeb) Unblocked. Cheers, Adam -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Little preseed problems
Hi I'm trying to preseed a Lenny 5.0.1 installation and all works but some little options doesn't starts. Please can you help me with any? 1 ) cdrom-checker doesn't start with d-i cdrom-checker/start boolean true 2 ) OEM installation doesn't work with d-i oem-config/enable boolean true 3 ) Xorg configuration it's de default and doesn't work with with: xserver-xorg xserver-xorg/autodetect_video_card boolean true xserver-xorg xserver-xorg/autodetect_monitor boolean false xserver-xorg xserver-xorg/config/monitor/selection-method select xserver-xorg xserver-xorg/config/monitor/mode-list select 640x480 @ 60 Hz xserver-xorg xserver-xorg/config/display/modes multiselect 640x480 xserver-xorg xserver-xorg/autodetect_mouse boolean true I attach the complete preseed file. Sorry for my english and thanks a lot in advance wrong_preseed.cfg Description: Binary data
Re: Automatic partition setup in partman-{lvm,md,crypto}
On Tue, Jul 28, 2009 at 07:47:14PM +0100, Colin Watson wrote: Otavio told me that you and he and Joey had agreed it would be a good idea to upload what we have in trunk now and refine from there. Your patches look basically along the right lines - I'll review them when I have a chance ... I found some time to test the cleanups, and since they appeared to work with no obvious problems, I went ahead and committed them to trunk. Review very much appreciated when you find the time. Max -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: [RFC] rootcmd for d-i Makefile
On Sun, Jul 26, 2009 at 01:27:41PM -0300, Otavio Salvador wrote: On Sun, Jul 26, 2009 at 12:42 PM, Max Vozelerx...@debian.org wrote: I've been using this change locally for a few days. It allows to just do make as a regular user without having to remember to call it with fakeroot. I enjoy a lot the idea; if people do not have problems with it I'm 100% in favor of having it commited. I went over it once more and tried to think of possible problems, but didn't manage to come up with any. Take that for whatever it may be worth. :-) Based on that and the positive feedback, committed it to trunk. Please tell me if anything breaks, I will take care of it. Max -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Sorry
I make a litle mistake: Im working with IA64 , and realy need amd64 plataform sorry -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: grub-installer/grub2_instead_of_grub_legacy template
Am Donnerstag, den 30.07.2009, 10:17 +0200 schrieb Felix Zielcke: Now that squeeze probable will freeze in December, I somehow have the feeling it won't use grub2 by default. So I suggest to change the grub2 instead of grub-legacy template. It shouldn't say anymore that grub2 is experimental. Ubuntu karmic is now using it by default and there aren't any critical bug reports (neither on LP or debbugs). Unfortunately I'm not at all good at these things and my english isn't that great either. I think it should mention that grub2 has support for UUIDs,ext4,lvm and RAID and that it lacks currently password support and savedefault. Or maybe the last part should be left out, so the translations won't need to be updated if we implement it. Ok now that Otavio agreed on IRC that it shouldn't say anymore that grub2 itself is experimental but the d-i support for it, here's a concrete proposal: GRUB 2 is the next generation of GNU GRUB. It has interesting new features like UUIDs, LVM, mdraid and ext4, but it lacks password and savedefault support. Note that the Debian-Installer support for it is still experimental. If you choose to install it, you should be prepared for breakage, and have an idea on how to recover your system if it becomes unbootable. You're advised not to try this in production environments. By the way what do these `# :sl2:' comments mean? man po-debconf doestn't document them. -- Felix Zielcke Proud Debian Maintainer -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Heads-up: release goal affects kernel udebs
From the announcement to d-a today: | * Discard and rebuild of binary packages uploaded by maintainers, |leaving only packages build in a controlled environment The team may want to request an exception for this for kernel udebs. Although kernel udebs built with mass-build should in theory build correctly when rebuilt normally, there are two reasons why we might not want that: - massbuild allows us to control *exactly* which kernel version the udebs are build against which helps avoid out-of-sync problems; if they would be rebuilt on a buildd, we'd lose some of the control we currently have. - massbuild allows us to built against kernels that are not yet or no longer available in unstable, which has been very useful in the past. Note that I do not plan to follow up on this myself. Cheers, FJP -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#382425: [PATCH] discover: use sysfs for pcmcia
Hi,
trying to get rid of the old pcmcia-ioctl-interface in the kernel, I modified
discover to use sysfs for that. Please find the patch attached. It modifies
configure.ac, so autoreconf has to be used to generate the new configure.
Is this interesting? I hope so, it seems discover is the last more prominent
user of that old interface...
Regards,
Wolfram
---
Finally get rid of these messages that discover uses the outdated pcmcia-ioctl
interface. For that, the sysfs-code was copied from PCI and adapted. That means
the ioctl-method is still there as a fallback.
Signed-off-by: Wolfram Sang w.s...@pengutronix.de
---
configure.ac |3 +
sysdeps/linux/pcmcia.c | 147 -
2 files changed, 148 insertions(+), 2 deletions(-)
Index: configure.ac
===
--- configure.ac.orig
+++ configure.ac
@@ -218,6 +218,7 @@ linux*)
PATH_PROC_PCI=/proc/bus/pci/devices
PATH_PROC_PCI_DIR=`dirname $PATH_PROC_PCI`
PATH_SYS_PCI=/sys/bus/pci/devices
+PATH_SYS_PCMCIA=/sys/bus/pcmcia/devices
PATH_PROC_SCSI=/proc/scsi/scsi
PATH_PROC_USB=/proc/bus/usb/devices
AC_DEFINE_UNQUOTED(PATH_PROC_IDE, $PATH_PROC_IDE,
@@ -228,6 +229,8 @@ linux*)
[Define path to /proc/bus/pci.])
AC_DEFINE_UNQUOTED(PATH_SYS_PCI, $PATH_SYS_PCI,
[Define path to /sys/bus/pci/devices.])
+AC_DEFINE_UNQUOTED(PATH_SYS_PCMCIA, $PATH_SYS_PCMCIA,
+ [Define path to /sys/bus/pcmcia/devices.])
AC_DEFINE_UNQUOTED(PATH_PROC_SCSI, $PATH_PROC_SCSI,
[Define path to /proc/scsi/scsi.])
AC_DEFINE_UNQUOTED(PATH_PROC_USB, $PATH_PROC_USB,
Index: sysdeps/linux/pcmcia.c
===
--- sysdeps/linux/pcmcia.c.orig
+++ sysdeps/linux/pcmcia.c
@@ -72,6 +72,8 @@
#include errno.h
#include fcntl.h
#include ctype.h
+#include string.h
+#include dirent.h
#include pcmcia/version.h
#include pcmcia/cs_types.h
@@ -79,13 +81,18 @@
#include pcmcia/cistpl.h
#include pcmcia/ds.h
-
+#include discover/sysdep.h
#include discover/device.h
#include discover/utils.h
/* XXX: There's no reason for this to be global. */
static int major = 0;
+static int cmpstringp(const void *p1, const void *p2)
+{
+ return strcmp(* (char * const *) p1, * (char * const *) p2);
+}
+
static int lookup_dev(char *name){
FILE *f;
int n;
@@ -153,7 +160,7 @@ _discover_sysdep_init(discover_sysdep_da
}
discover_sysdep_data_t *
-_discover_get_pcmcia_raw(void)
+_discover_get_pcmcia_raw_ioctl(void)
{
int fd, ns;
ds_ioctl_arg_t arg;
@@ -198,6 +205,142 @@ _discover_get_pcmcia_raw(void)
return head;
}
+discover_sysdep_data_t *
+_discover_get_pcmcia_raw_sys(void)
+{
+discover_sysdep_data_t *head = NULL, *node, *last = NULL;
+FILE *f;
+DIR *pcmciaDir;
+struct dirent *pcmcia_device_entry;
+unsigned int len;
+char *device_dir, *vendor, *model, *p;
+char **device_dir_list = NULL;
+size_t device_dir_list_len, device_dir_index;
+char path[256];
+int ret;
+
+/* Open the directory containing all the PCMCIA device dirs. */
+pcmciaDir = opendir(PATH_SYS_PCMCIA);
+if (pcmciaDir == NULL)
+return _discover_get_pcmcia_raw_ioctl();
+
+/*
+ * The order of links in PATH_SYS_PCMCIA is not sorted. Since
+ * module load order can affect things like device naming,
+ * we should collect the device directory names and sort them.
+ */
+
+for (pcmcia_device_entry = readdir(pcmciaDir); pcmcia_device_entry;
+ pcmcia_device_entry = readdir(pcmciaDir)) {
+device_dir = strdup(pcmcia_device_entry-d_name);
+if (device_dir == NULL)
+continue;
+if (device_dir[0] == '.') {
+free(device_dir);
+continue;
+}
+
+if (device_dir_list == NULL) {
+device_dir_list = (char **)malloc(sizeof(char *));
+device_dir_list_len = 1;
+} else {
+device_dir_list =
+(char **)realloc(device_dir_list,
+ sizeof(char *) * ++device_dir_list_len);
+}
+
+if (device_dir_list != NULL) {
+device_dir_list[device_dir_list_len - 1] = device_dir;
+} else {
+free(device_dir);
+}
+}
+
+closedir(pcmciaDir);
+
+if (device_dir_list == NULL)
+return _discover_get_pcmcia_raw_ioctl();
+
+/* Do a sort. */
+qsort(device_dir_list, device_dir_list_len, sizeof(char *), cmpstringp);
+
+/* Loop through the PCMCIA device dirs. */
+vendor = model = NULL;
+for (device_dir_index = 0; device_dir_index device_dir_list_len;
+ device_dir_index++) {
+device_dir = device_dir_list[device_dir_index];
+if (device_dir == NULL)
+
Re: [PATCH] Basic Openmoko GTA02 support
* Gaudenz Steinlin gaud...@debian.org [2009-07-29 17:45]: The most important thing is that we can all agree on the same name. Which one we actually choose does not matter that much for me. I would prefer s3c24xx, though, as I've mostly settled for this name now for the things I've done in during the last days. Is there any opposition against this name? It's fine with me. I don't think it makes a big difference whether it's s3c24xx or s3c... just pick one and stick to it. :) I think it's fine to apply patches for e.g. libdebian-installer, base-installer, flash-kernel, etc; but you obviously cannot change linux-kernel-di-armel-2.6 and the d-i build system before we have a kernel in the archive. Is there no way we can commit the patches to the build system but not activate it for Debian builds? Yeah, you can do that. Anyway, please post your new patches to the list for review first. -- 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
Processed: setting package to tasksel tasksel-data, tagging 452388, tagging 503510, tagging 538902 ...
Processing commands for cont...@bugs.debian.org: #tasksel (2.80) UNRELEASED; urgency=low # # * Add mozvoikko to finnish-desktop. Closes: #503510 # * Revamp the description of standard and desktop tasks in #an attempt to make them clearer. Closes: #452388 # * Add an SSH server task. Closes: #399840 # * Fixes a typo in Gujarati language tasks. Closes: #538902 # package tasksel tasksel-data Ignoring bugs not assigned to: tasksel tasksel-data tags 452388 + pending Bug #452388 [tasksel] Standard system is confusing Added tag(s) pending. tags 503510 + pending Bug #503510 [tasksel] Please add mozvoikko to the finnish-desktop task Ignoring request to alter tags of bug #503510 to the same tags previously set tags 538902 + pending Bug #538902 [tasksel-data] tasksel-data: localisation tasks mix spelling gujarati and gujurati Ignoring request to alter tags of bug #538902 to the same tags previously set tags 399840 + pending Bug #399840 [tasksel] tasksel: request for ssh-server task Added tag(s) pending. End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
[D-I Manual] Build log for en (30 Jul 2009)
A build of the Debian Installer Manual was triggered by an update to SVN.
There were no errors during the build process.
The new version of the manual has been uploaded successfully.
A log of the build is available at:
- http://d-i.alioth.debian.org/manual/logs/en.log
===
It is possible to use RSS to track changes to the manual.
For more information, see:
http://d-i.alioth.debian.org/manual/translators.html
===
Note: PDF output is not yet supported for some languages; help
with this would be appreciated.
===
If you have any questions about the build or this message, feel
free to contact me at faw AT funlabs DOT org.
===
Updated files ('svn up')
Uen/install-methods/install-tftp.xml
Uen/hardware/hardware-supported.xml
Uen/hardware/supported-peripherals.xml
Uen/hardware/supported/mips.xml
Uen/hardware/supported/mipsel.xml
Uen/hardware/installation-media.xml
Uen/boot-installer/mipsel.xml
Uen/boot-installer/mips.xml
Updated to revision 59862.
--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Custom dialog during install?
I have a need to prompt user for input during the installation using d-i. I have done quite a bit of searching but I don't seem to find the right words to actually find a solution. I came across this thread: http://lists.debian.org/debian-boot/2008/09/msg01078.html Which suggest I would need to create a custom udeb for it, or create the templates on the fly. As I need only a very basic question/answer I'd rather do it on-the-fly, however I did not find the solution from the web page linked from that answer. What would be the best place to look for examples to create this kind of simple dialog from the script run as late_command? The way I got a custom dialog was reading this[1] to know how to create a udeb. Then I hacked how simple-cdd-profiles[2] udeb package is loaded into d-i and how it loads a debconf template. Basically simple-cdd-profiles udeb is loaded by: d-i preseed/early_command string anna-install simple-cdd-profiles in a preseed file. Once added to d-i (installed) it's postinst script calls debconf-loadtemplate[3]. I used this way and it still working quite well. regards Lucas Brasilino [1] http://www.fifi.org/doc/debconf-doc/tutorial.html [2] http://packages.debian.org/lenny/simple-cdd-profiles [3] http://www.tin.org/bin/man.cgi?section=1topic=debconf-loadtemplate -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
consulta gratis de tarot
Amor sorte negoçio pode aqui fazer uma pergunta via msn cola meu mail mai...@sapo.pt ou pelo telfono 964843639 ou 917440317 dr pedro site www.yourvida.com/astrologia amour argnt travail sur msn consultation gratuite il faut coler mon e-mail mai...@sapo.pt ou tel 0170389850 ou site -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
