Re: Spam cleaning for August 2004
Quoting Don Wright (wdi...@wricomp.net): Today I see this storm is still present. Does it need additional follow up with listmasters or should it be marked manually like the rest? I'd say mark it manually. Apparently, that will be more efficient..:-) The best for doing this efficiently is by downloading the list archive as a mailbox, then use an efficiant MUA to tag all mails and bouonce them to the report spam mail address. signature.asc Description: Digital signature
Please allow NBD in testing
Hi, The NBD packages are currently blocked because the package produces a udeb. Since the version in testing has a bug that prevents the initscript from working with the module-init-tools that are also in testing, it would be nice if you could allow NBD to migrate. This will have zero impact on the installer, since the NBD udeb is not (yet) used by it. Thanks, -- The biometric identification system at the gates of the CIA headquarters works because there's a guard with a large gun making sure no one is trying to fool the system. http://www.schneier.com/blog/archives/2009/01/biometrics.html signature.asc Description: Digital signature
Processing of partman-base_134_amd64.changes
partman-base_134_amd64.changes uploaded successfully to localhost along with the files: partman-base_134.dsc partman-base_134.tar.gz partman-base_134_amd64.udeb partman-utils_134_amd64.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
partman-base_134_amd64.changes ACCEPTED
Accepted: partman-base_134.dsc to pool/main/p/partman-base/partman-base_134.dsc partman-base_134.tar.gz to pool/main/p/partman-base/partman-base_134.tar.gz partman-base_134_amd64.udeb to pool/main/p/partman-base/partman-base_134_amd64.udeb partman-utils_134_amd64.udeb to pool/main/p/partman-base/partman-utils_134_amd64.udeb Override entries for your package: partman-base_134.dsc - source debian-installer partman-base_134_amd64.udeb - standard debian-installer partman-utils_134_amd64.udeb - extra debian-installer 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
kernel-wedge 2.61 MIGRATED to testing
FYI: The status of the kernel-wedge source package in Debian's testing distribution has changed. Previous version: 2.58 Current version: 2.61 -- 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
mklibs 0.1.29 MIGRATED to testing
FYI: The status of the mklibs source package in Debian's testing distribution has changed. Previous version: 0.1.27 Current version: 0.1.29 -- 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
Bug#539521: marked as done (mke2fs hangs formatting RAID6)
Your message dated Thu, 6 Aug 2009 19:02:17 +0200 with message-id 20090806170217.ga11...@quark.vpn.nusquama.org and subject line Re: Bug#539521: mke2fs hangs formatting RAID6 has caused the Debian Bug report #539521, regarding mke2fs hangs formatting RAID6 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 539521: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=539521 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: installation-reports Boot method: netinst ISO image Image version: http://cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/amd64/iso-cd/debian-testing-amd64-netinst.iso Date: Aug. 1, 2009 Machine: Core i7 920, ASUS WS P6T7 Supercomputer Processor: Core i7 920 Memory: 6 GB Partitions: N/A Output of lspci -knn (or lspci -nn): N/A 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: [E] Install base system:[ ] Clock/timezone setup: [ ] User/password setup:[ ] Install tasks: [ ] Install boot loader:[ ] Overall install:[ ] Comments/Problems: I created a RAID1 to hold the /boot partition and formatted as ext3 just fine. When trying to format a RAID6 LVM group for /, mke2fs (creating an ext3 fs) sits there and does nothing. This has been happening for a week at least. RAID1: 5 partitions, 0 spares RAID6: 5 partitions, 0 spares, one LVM logical group for the root fs Booted with nopat to get around a console hang problem but the issue also happens in the graphical install (nopat not needed). ---End Message--- ---BeginMessage--- On Sat, Aug 01, 2009 at 12:22:22PM -0500, David Greene wrote: Oh, it finally did kick off and apparently formatted the partition. The progress meter went to 33% immediately and then just sat there. I saw this behavior last week and then it really did sit there for hours. So it appears whatever problem existed a week ago is gone Thank you for following up. I'm closing the bug. but that the UI could use some work. Indeed. As I understand, it is not possible to get more fine- grained progress output from mkfs.ext3, so we are currently stuck with the very coarse two(?)-step progress bar. Max ---End Message---
udpkg: add a --os option
Hi, In the kfreebsd branch of the debian-installer we are using at some places uname to detect if we are running on GNU/Linux on GNU/kFreeBSD, when the script doesn't differ a lot. This is not something really clean, and I think that adding a --os option to udpkg (similar to the --arch option) could help. What do you think? Aurelien -- Aurelien Jarno GPG: 1024D/F1BCDB73 aurel...@aurel32.net http://www.aurel32.net -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#249041: marked as done (Please support disk labels (LABEL=))
Your message dated Thu, 6 Aug 2009 19:40:33 +0200 with message-id 20090806174033.ga13...@quark.vpn.nusquama.org and subject line Re: Bug#249041: Please support disk labels (LABEL=) has caused the Debian Bug report #249041, regarding Please support disk labels (LABEL=) to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 249041: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=249041 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: partman Severity: wishlist Please add an option to specify a disk label (max 16 characters), and use that in fstab if it's available. - Forwarded message from Andrew Pollock apoll...@debian.org - From: Andrew Pollock apoll...@debian.org Subject: Re: Bug#248902: installation-report debian-installer beta4, arch i386 Date: Fri, 14 May 2004 11:39:06 +1000 To: Martin Michlmayr t...@cyrius.com Cc: debian-boot@lists.debian.org User-Agent: Mutt/1.5.4i On Thu, May 13, 2004 at 11:13:01PM +0100, Martin Michlmayr wrote: * tbm t...@cyrius.com [2004-05-13 21:02]: * Nico Dietrich nicodietr...@web.de [2004-05-13 20:22]: LABEL=/ / ext3defaults1 1 LABEL=/home /home ext3defaults1 2 How did you get those LABELs? Did you do that by hand after d-i? Someone suggested a while ago to use LABEL= in d-i. Can someone who uses this feature explain exactly how it works? If I put LABEL=/home in a /etc/fstab, how does Linux know which partition is associated with this label? Basically, at filesystem creation time (or afterwards) labels are added to the filesystems. AFAIK, this is an ext2/3 and xfs feature, I'm not aware of other filesystems that have it, someone may correct me. This can be done with the mke2fs/tune2fs/mkfs.xfs -L option, or the e2label/xfs_admin programs. From fstab(5): Instead of giving the device explicitly, one may indicate the (ext2 or xfs) filesystem that is to be mounted by its UUID or volume label (cf. e2label(8) or xfs_admin(8)), writing LABEL=label or UUID=uuid, e.g., `LABEL=Boot' or `UUID=3e6be9de-8139-11d1-9106-a43f08d823a6'. This will make the system more robust: adding or removing a SCSI disk changes the disk device name but not the filesystem volume label. So, it would actually be probably more desirable to mount using the UUID than the label (however the label is more memorable), as most filesystems have a UUID, whereas only a few support a label. I would suggest that in the case of ext2/3 and XFS, when a filesystem is created, it automatically gets labelled with a name relevant to what the filesystem mount point should be, but perhaps in all cases the /etc/fstab entry uses the filesystem's UUID. The administrator can, if need be in a recovery situation, mount /usr by going mount LABEL=/usr /usr, but the system would normally mount /usr by it's UUID. Hope this helps. Andrew - End forwarded message - - Forwarded message from Colin Watson cjwat...@debian.org - From: Colin Watson cjwat...@debian.org Subject: Re: Bug#248902: installation-report debian-installer beta4, arch i386 Date: Fri, 14 May 2004 03:24:47 +0100 To: debian-boot@lists.debian.org Cc: Martin Michlmayr t...@cyrius.com User-Agent: Mutt/1.3.28i On Fri, May 14, 2004 at 11:39:06AM +1000, Andrew Pollock wrote: On Thu, May 13, 2004 at 11:13:01PM +0100, Martin Michlmayr wrote: Someone suggested a while ago to use LABEL= in d-i. Can someone who uses this feature explain exactly how it works? If I put LABEL=/home in a /etc/fstab, how does Linux know which partition is associated with this label? Basically, at filesystem creation time (or afterwards) labels are added to the filesystems. AFAIK, this is an ext2/3 and xfs feature, I'm not aware of other filesystems that have it, someone may correct me. JFS does, according to mkfs.jfs(8); although mount(8) doesn't mention it so maybe it wouldn't work for this purpose, I'm not sure. -- Colin Watson [cjwat...@flatline.org.uk] -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org - End forwarded message - - Forwarded message from Martin Michlmayr t...@cyrius.com - From: Martin Michlmayr t...@cyrius.com Subject: Re: Bug#248902: installation-report debian-installer beta4, arch i386 Date: Fri, 14 May 2004 16:51:23 +0100 To: debian-boot@lists.debian.org User-Agent: Mutt/1.5.6i * Colin Watson cjwat...@debian.org [2004-05-14 03:24]: JFS does, according
Re: Spam cleaning for August 2004
On Thursday 06 August 2009, Christian Perrier wrote: Quoting Don Wright (wdi...@wricomp.net): Today I see this storm is still present. Does it need additional follow up with listmasters or should it be marked manually like the rest? I'd say mark it manually. Apparently, that will be more efficient..:-) The best for doing this efficiently is by downloading the list archive as a mailbox, then use an efficiant MUA to tag all mails and bouonce them to the report spam mail address. But I for one have absolutely ZERO intention of *reviewing* so many identical stupid messages. That's simply a waste of time (and extremely stupid work too). If they make it into the review system, you'll have to count me out until they are gone again. Please try contacting the listmasters again. Cheers, FJP -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Please allow NBD in testing
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 06-08-2009 05:13, Wouter Verhelst wrote: Hi, The NBD packages are currently blocked because the package produces a udeb. Since the version in testing has a bug that prevents the initscript from working with the module-init-tools that are also in testing, it would be nice if you could allow NBD to migrate. This will have zero impact on the installer, since the NBD udeb is not (yet) used by it. Unblocked. unblock nbd/1:2.9.13-2 Kind regards, - -- Felipe Augusto van de Wiel (faw) Debian. Freedom to code. Code to freedom! -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEAREIAAYFAkp7QWkACgkQCjAO0JDlyka2+QCeJw6dCDcoZYV/ARechwUtxlrS a3wAoMMj+nYRoyKEtI2UPYPLRTGAC+sk =Raoj -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
[d-i on kfreebsd] quick status report
Hi. The kfreebsd debian-installer port did a lot of progress. Among basic features it only misses grub-installer. To let you test current status (svn r60004), I prepared * monolithic image [1] * netboot image [2] * debs needed in the build environment [3] * udebs needed in localeudebs + kernel related [4] + others [5] (each linked ls file is the list of files in the same directory) (In the future I'll remove these files) To test the images in QEMU $ qemu-img create vhd.img 1G $ qemu -boot d -cdrom mini.iso vhd.img Cheers, Luca Favatella [1] http://slackydeb.altervista.org/files/debian_gnu_kfreebsd/tmp/20090806/2230_r60004/monolithic/ls [2] http://slackydeb.altervista.org/files/debian_gnu_kfreebsd/tmp/20090806/2230_r60004/netboot/ls [3] http://slackydeb.altervista.org/files/debian_gnu_kfreebsd/tmp/20090806/2230_r60004/debs/ls [4] http://slackydeb.altervista.org/files/debian_gnu_kfreebsd/tmp/20090806/2230_r60004/udebs/kfreebsd-kernel-di-i386/ls [5] http://slackydeb.altervista.org/files/debian_gnu_kfreebsd/tmp/20090806/2230_r60004/udebs/ls -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: reopening 529977, reassign 529977 to tasksel
Processing commands for cont...@bugs.debian.org:
reopen 529977
Bug #529977 {Done: James Vega james...@debian.org} [vim-tiny] vim.tiny
doesn't provide /usr/bin/vim command (vim alternative is missing)
# Manually reassigning to taskel since Frank forgot to Cc control@
reassign 529977 tasksel
Bug #529977 [vim-tiny] vim.tiny doesn't provide /usr/bin/vim command (vim
alternative is missing)
Bug reassigned from package 'vim-tiny' to 'tasksel'.
Bug #529977 [tasksel] vim.tiny doesn't provide /usr/bin/vim command (vim
alternative is missing)
Bug No longer marked as found in versions vim/2:7.2.148-2.
Bug #529977 [tasksel] vim.tiny doesn't provide /usr/bin/vim command (vim
alternative is missing)
Ignoring request to alter fixed versions of bug #529977 to the same values
previously set
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
[PATCH] use grub to boot d-i CD
This patch uses grub to boot kfreebsd-i386 d-i CD.
Thanks to Robert Millan.
I tested this on kfreebsd-i386.
It should not affect GNU/Linux builds.
Please note that in the meantime I
* added hw.ata.ata_dma=0
* added/improved comments for hw.ata.ata_dma=0 and hw.ata.atapi_dma=0
I'm not writing these things in a changelog entry.
I think it is not needed, because this first version on d-i with
kfreebsd support is unreleased yet.
Cheers,
Luca Favatella
Index: build/boot/kfreebsd/grub.cfg
===
--- build/boot/kfreebsd/grub.cfg (revision 0)
+++ build/boot/kfreebsd/grub.cfg (revision 0)
@@ -0,0 +1,18 @@
+
+set cd=$root
+
+menuentry Install Debian GNU/kFreeBSD {
+ echo Loading ...
+ set root=$cd
+ freebsd /boot/kernel/kernel.gz
+ freebsd_module_elf /boot/kernel/acpi.ko
+ freebsd_module /boot/mfsroot.gz type=mfs_root
+ set FreeBSD.vfs.root.mountfrom=ufs:/dev/md0
+ set FreeBSD.hw.ata.ata_dma=0 # needed for qemu hard disk # TODO: delete
+ set FreeBSD.hw.ata.atapi_dma=0 # needed for qemu cd # TODO: 1
+}
+
+menuentry Boot from first hard disk {
+ set root=hd0
+ chainloader +1
+}
Index: build/config/kfreebsd-i386.cfg
===
--- build/config/kfreebsd-i386.cfg (revision 60021)
+++ build/config/kfreebsd-i386.cfg (working copy)
@@ -12,28 +12,36 @@
INITRD_FS = ufs1
+grub_moddir=/usr/lib/grub/i386-pc
+
arch_boot_screens:
arch_tree:
-# Miniature CD image using kfreebsd-loader, with only an initrd, no udebs or debs.
+# Miniature CD image using GRUB, with only an initrd, no udebs or debs.
.PHONY: arch_miniiso
arch_miniiso: $(TEMP_INITRD) $(TEMP_KERNEL) $(TREE)
-rm -f $(TEMP_CD_TREE)/*
- mkdir -p $(TEMP_CD_TREE)/boot/{kernel,defaults}
+ mkdir -p $(TEMP_CD_TREE)/boot/{kernel,grub}
cp $(TEMP_KERNEL) $(TEMP_CD_TREE)/boot/kernel/kernel.gz
cp $(TEMP_INITRD) $(TEMP_CD_TREE)/boot/mfsroot.gz
cp $(TREE)/lib/modules/*/acpi.ko $(TEMP_CD_TREE)/boot/kernel/
- cp /boot/{cdboot,loader*,*.4th} $(TEMP_CD_TREE)/boot/
- cp /boot/defaults/loader.conf $(TEMP_CD_TREE)/boot/defaults/
- echo hw.ata.atapi_dma=0 $(TEMP_CD_TREE)/boot/loader.conf # TODO: 1
- echo mfsroot_load=\YES\ $(TEMP_CD_TREE)/boot/loader.conf
- echo mfsroot_type=\mfs_root\ $(TEMP_CD_TREE)/boot/loader.conf
- echo mfsroot_name=\/boot/mfsroot\ $(TEMP_CD_TREE)/boot/loader.conf
+ cp boot/kfreebsd/grub.cfg $(TEMP_CD_TREE)/boot/grub/
- genisoimage -r -J -b boot/cdboot -c boot.cat -no-emul-boot \
+ grub-mkimage -o $(TEMP_CD_TREE)/boot/grub/core.img \
+ biosdisk \
+ minicmd normal sh echo \
+ iso9660 \
+ bsd chain \
+ $(NULL)
+ cat $(grub_moddir)/cdboot.img $(TEMP_CD_TREE)/boot/grub/core.img \
+ $(TEMP_CD_TREE)/boot/grub/grub_eltorito
+ rm $(TEMP_CD_TREE)/boot/grub/core.img
+
+ genisoimage -r -J -b boot/grub/grub_eltorito -c boot.cat -no-emul-boot \
+ -boot-load-size 4 -boot-info-table \
-o $(TEMP_MINIISO) $(TEMP_CD_TREE)
Index: debian/changelog
===
--- debian/changelog (revision 60021)
+++ debian/changelog (working copy)
@@ -107,6 +107,7 @@
[ Luca Favatella ]
* Use arch indipendent code for LSB_DISTRIB_DESCRIPTION.
+ * Use grub to boot kfreebsd-i386 d-i CD. Thanks to Robert Millan.
-- Frans Pop f...@debian.org Tue, 04 Aug 2009 17:40:32 +0200
Little preseed problems
Hi I'm trying a preseeded Lenny 5.0.1 installation and some options are skipped and the defaults are selected. Please can you help me with any? The options skipped are: 1 ) cdrom-checker doesn't start with d-i cdrom-checker/start boolean true 2 ) OEM installation doesn't works with d-i oem-config/enable boolean true. 3 ) Xorg configuration are the default, and this preseeds are skipped: 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 for any questions.I don't know if any of this preseeds are not supported, sintax are correct or any additional preseed are needed. Sorry for my English and thanks a lot in advance wrong_preseed.cfg Description: Binary data
