Bug#500123: [INTL:sv] Swedish strings for cdebconf-terminal debconf
package: cdebconf-terminal severity: wishlist tags: patch l10n -- brother http://frakalendern.se# translation of cdebconf-terminal.po to swedish # Copyright (C) YEAR THE PACKAGE'S COPYRIGHT HOLDER # This file is distributed under the same license as the PACKAGE package. # # Martin Bagge [EMAIL PROTECTED], 2008. msgid msgstr Project-Id-Version: cdebconf-terminal\n Report-Msgid-Bugs-To: [EMAIL PROTECTED] POT-Creation-Date: 2008-07-31 13:04+0200\n PO-Revision-Date: 2008-09-25 12:28+0100\n Last-Translator: Martin Bagge [EMAIL PROTECTED]\n Language-Team: swedish [EMAIL PROTECTED]\n MIME-Version: 1.0\n Content-Type: text/plain; charset=UTF-8\n Content-Transfer-Encoding: 8bit\n X-Generator: KBabel 1.11.4\n #. Type: text #. Description #: ../cdebconf-gtk-terminal.templates:1
Bug#500079: Bug#497110: Missing root option for other detected Linux OS on dmraid
Frans Pop ha scritto: improvement before it can be merged. Before it gets merged I'd like to see a dual boot with Windows tested as well. Unfortunately I haven't a dual boot with Windows for testing. As this whole section is Linux-specific, I don't really like it being outside the 'case' statement. If it remains outside, it should start with a test for host_os. Why is Linux-specific ? I think the missing root option is for other OS on dmraid in general, not only for Linux OS on dmraid Note that in other places we use 'dmraid -s -c'. Is there a real difference? Consistency is important! -sa displays only active raid sets, I think you should use -sa also in other place. Why not just set tmp_part instead of tmp_satadevn in the first hunk? Then this whole hunk would not be needed. Right, attached the new debdiff Giuseppe. diff -Nru grub-installer-1.34/debian/changelog grub-installer-1.35/debian/changelog --- grub-installer-1.34/debian/changelog2008-09-22 02:47:51.0 +0200 +++ grub-installer-1.35/debian/changelog2008-09-25 14:12:22.0 +0200 @@ -1,3 +1,11 @@ +grub-installer (1.35) unstable; urgency=low + + [Giuseppe Iuculano] + * Fix root detection in menu.lst for dmraid devices discovered by os-prober +(Closes: #500079) + + -- Giuseppe Iuculano [EMAIL PROTECTED] Thu, 25 Sep 2008 14:10:33 +0200 + grub-installer (1.34) unstable; urgency=low [ Frans Pop ] diff -Nru grub-installer-1.34/grub-installer grub-installer-1.35/grub-installer --- grub-installer-1.34/grub-installer 2008-09-21 22:25:25.0 +0200 +++ grub-installer-1.35/grub-installer 2008-09-25 14:35:09.0 +0200 @@ -135,6 +135,21 @@ tmp_drive=$(grep -v '^#' $device_map | grep $tmp_disk *$ | \ sed 's%.*\(([hf]d[0-9][a-g0-9,]*)\).*%\1%') + # If not found, check if it is a SATA RAID partition, and set tmp_drive and tmp_part + if type dmraid /dev/null 21 [ -z $tmp_drive ]; then + for frdisk in $(dmraid -sa -c | grep -v No RAID disks); do + if echo $(basename $tmp_disk) | grep -q $frdisk; then + for raiddisk in $(dmraid -r -c | grep -v No RAID disks); do + if [ $(dmraid -r -cr $raiddisk)=$frdisk ]; then + tmp_drive=$(grep -v '^#' $device_map | grep $raiddisk *$ | \ + sed 's%.*\(([hf]d[0-9][a-g0-9,]*)\).*%\1%') + tmp_part=$(basename $tmp_disk | sed s%$frdisk%%) + fi + done + fi + done + fi + # If not found, print an error message and exit if [ -z $tmp_drive ]; then echo $1 does not have any corresponding BIOS drive. 12 signature.asc Description: OpenPGP digital signature
let the Debian-Installer partitioner recognize LVM logical volumes on encrypted RAID 1 partition
Dear list, I hope this is the right place to ask. If not excuse me and please point me to the right one. I changed my mainboard with processor with 64 bit capability. I used the old hard disks where I installed a Debian 32bit Linux kernel on before, which works. My goal is to “reinstall” Debian with a 64bit Linux kernel. But unfortunately I am getting a problem on the way. Idea: Just reinstall Debian amd64 and tell the Debian-Installer to keep the old /home and /var partition. Problem: I am using a RAID 1 setup with an encrypted partition with LVM volumes on it and I do not get the Debian-Installer to recognize it. Now I will elaborate a bit. You can find a little more information at [1]. # Setup All the following steps were done with the Debian-Installer some time ago. • two hard disks (SATA) /dev/sda and /dev/sdb • Create two partitions sd[ab]0 and sd[ab]1 for boot and data. Each of them were put into a RAID 1 array. • Encrypt md1 with LUKS. • Setup up LVM with logical volumes for /home, /var, /usr, …. • Back then I had to use the work around in [2], but this seems unrelated. # Steps to reinstall Debian with amd64 Linux kernel 1. prepare and boot from USB stick with debian-testing-amd64-businesscard.iso 2. do steps until detect hard disks and than partition hard disk 3. raid devices and LVM volumes are not shown 4. open a shell and do some steps according to [3] # anna-install crypto-modules cryptsetup-udeb # depmod -a # modprobe dm-mod # modprobe aes I think after this step the Raid devices are shown in the partitioning menu of the Debian-Installer. # cryptsetup luksOpen /dev/md1 md1_crypt This succeeds. From here on I do not know what to do. I try # lvdisplay File descriptor 3 left open File descriptor 4 left open File descriptor 5 left open File descriptor 6 left open I did not find anything useful searching the Internet. On [4] it says to use lsof, but this is not available in the Debian-Installer. # mount rootfs on / type rootfs (rw) none on /proc type proc (rw) none on /sys type sysfs (rw) tmpfs on /dev type tmpfs (rw,mode=755) none on /dev/pts type devpts (rw,mode=600) /dev/sdb1 on /hd-media type vfat (ro,fmask=0022,dmask=0022,allow_utime=17,codepage=cp437,iocharset=utf8) Can you give me a hint and can I provide more information? Thanks a lot, Paul [1] https://www.debian-administration.org/users/PaulePanter/weblog/3 [2] http://wiki.debian.org/DebianInstaller/RAIDvsCrypto [3] http://wiki.debian.org/DebianInstaller/Rescue/Crypto [4] http://archives.devshed.com/forums/linux-97/lvm-file-descriptor-left-open-snapshot-problems-1201586.html signature.asc Description: Dies ist ein digital signierter Nachrichtenteil
Accessing Lenny Netboot Daily Images for PowerPC
Hi All, I'm doing some work with embedded systems and am currently trying to install Lenny via netboot with an NFS mounted root filesystem. While attempting to access the netboot daily images for PowerPC I see that a HTTP 404 is being returned for the following URL: http://people.debian.org/~wouter/d-i/powerpc/daily/ A bad link on the debain-installer page (http://www.debian.org/devel/debian-installer/) or a problem with the daily builds for PowerPC? I didn't see any similar looking issues in the wiki so I'm posting here. Regards, -jmh -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#500123: marked as done ([INTL:sv] Swedish strings for cdebconf-terminal debconf)
Your message dated Thu, 25 Sep 2008 18:04:07 +0200 with message-id [EMAIL PROTECTED] and subject line Re: Bug#500123: [INTL:sv] Swedish strings for cdebconf-terminal debconf has caused the Debian Bug report #500123, regarding [INTL:sv] Swedish strings for cdebconf-terminal debconf 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 [EMAIL PROTECTED] immediately.) -- 500123: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=500123 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- package: cdebconf-terminal severity: wishlist tags: patch l10n -- brother http://frakalendern.se# translation of cdebconf-terminal.po to swedish # Copyright (C) YEAR THE PACKAGE'S COPYRIGHT HOLDER # This file is distributed under the same license as the PACKAGE package. # # Martin Bagge [EMAIL PROTECTED], 2008. msgid msgstr Project-Id-Version: cdebconf-terminal\n Report-Msgid-Bugs-To: [EMAIL PROTECTED] POT-Creation-Date: 2008-07-31 13:04+0200\n PO-Revision-Date: 2008-09-25 12:28+0100\n Last-Translator: Martin Bagge [EMAIL PROTECTED]\n Language-Team: swedish [EMAIL PROTECTED]\n MIME-Version: 1.0\n Content-Type: text/plain; charset=UTF-8\n Content-Transfer-Encoding: 8bit\n X-Generator: KBabel 1.11.4\n #. Type: text #. Description #: ../cdebconf-gtk-terminal.templates:1---End Message--- ---BeginMessage--- Quoting Martin Bagge ([EMAIL PROTECTED]): package: cdebconf-terminal severity: wishlist tags: patch l10n This package is a D-I component and its localization is updated through Debian Installer processes. signature.asc Description: Digital signature ---End Message---
Interaction with user in preseed's early/late command
Hi, I'm trying to customize an ubuntu 8.04 installation using an alternate CD. I created an preseed file and I use early and late commands to customize the installation. Commands to install and remove packages work fine. I'm having trouble in executing scripts that interacts with the user. For example, if I try to run the following script, it doesn't work the way I want, because I can't activate the virtual terminal(vt) #3 via script. The 'echos' are redirected to vt #3 but not the 'read' command, so the installations stops because it can't pass the read command. - #!/bin/sh chvt 3 echo \n /dev/tty3 echo /dev/tty3 echo Enter your name: read name echo You entered $name --- When you change to other vt(command chvt 3), you get the message Please press enter to activate this console and have to press Enter to activate the virtual terminal.I tried to simulate that 'Enter' using the echo commands above, but they don't work, the vt remains deactivated. I don't know if I made myself clear. My english is not that good .. Any suggestions to solve my problem? any help will be appreciated. Thanks in advance. -- Att Gustavo Miranda. Linux User 410767
Re: Interaction with user in preseed's early/late command
On Thursday 25 September 2008, Gustavo Miranda wrote: I'm trying to customize an ubuntu 8.04 installation using an alternate ^^^ Next time please ask your question on a Ubuntu mailing list. CD. I created an preseed file and I use early and late commands to customize the installation. Commands to install and remove packages work fine. I'm having trouble in executing scripts that interacts with the user. For example, if I try to run the following script, it doesn't work the way I want, because I can't activate the virtual terminal(vt) #3 via script. The 'echos' are redirected to vt #3 but not the 'read' command, so the installations stops because it can't pass the read command. You CANNOT use stdin/stderr to interact with users during the installation. You should always use debconf questions. You can create a custom udeb to ask your questions, but it is also possible to create templates on the fly. Examples of the last can be found here: http://hands.com/d-i/. Cheers, FJP -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Accessing Lenny Netboot Daily Images for PowerPC
On Thursday 25 September 2008, Jason Hanna wrote: While attempting to access the netboot daily images for PowerPC I see that a HTTP 404 is being returned for the following URL: The images are not available because of a recent server move. Most arches have already made the switch needed for this move, but the persons doing the powerpc and sparc builds have not yet done so. Images will hopefully be available again soon. Cheers, FJP -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: let the Debian-Installer partitioner recognize LVM logical volumes on encrypted RAID 1 partition
On Thursday 25 September 2008, Paul Menzel wrote: Problem: I am using a RAID 1 setup with an encrypted partition with LVM volumes on it and I do not get the Debian-Installer to recognize it. If you use a daily built version of the installer, both pre-existing RAID and pre-existing LVM devices should be recognized automatically. Cheers, FJP -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#498358: installation-report: Successful installation
On Thu, Sep 11, 2008 at 11:58:39AM +0200, Jérémy Bobbio wrote: If you have the machine installed, could you try to update to 2.6.26-5 and your BIOS setting to its original value? [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=496603 I finally got to try it, it works now. Thanks. signature.asc Description: Digital signature
Re: Update of the installation-guide with RAID 6 and 10
On Monday 22 September 2008, Ryan Niebur wrote: So, I completely forgot about this. (sorry) Can this patch still be applied? Is there any reason why it hasn't yet? I had ignored the patch because I expected Jérémy to take care of it as he'd started the tread and had also done the merge of the code. I have now committed the patch after review and with a few minor changes. Jérémy: can you please commit the other two sets of changes for the manual that you sent to the list? Cheers, FJP signature.asc Description: This is a digitally signed message part.
Installing with D-I from d-ports.org
Someone asked on IRC a few weeks back how to do this. I asked to mail the question to the list, but that never happened (which IMO is silly). Anyway, I happened to be thinking about that yesterday and thought I'd just spontaneously share my thoughts with you. As always in D-I there are a few thousand possible solutions, ranging from ugly hacks to elegant written code. My suggestion would be to use an elegant hack, at least for the time being. The only problem is during installation. During build, assuming the build host points to d-ports, everything should work fine. During installation you basically want to avoid displaying the mirror list. But you also want to allow users to use a local mirror. Easiest solution for that is probably to use initrd preseeding [1]. This should do the above and avoid the need to modify any components. The preseed file should contain the following three lines (ignoring security mirrors for now as you only have unstable): d-i mirror/country string manual d-i mirror/http/hostname string debian-ports.org d-i mirror/http/hostname seen false The first line ensures that the country list is not displayed. The last two lines ensure that the hostname _is_ asked, but has the correct default. The preseed file can be included in the images by using a mechanism that was in place for the Etch installer, but which has been dropped in trunk. Check out installer/build from the etch branch, and see the unstable.cfg file and grep for PRESEED_SUITE. IMO it should be no problem to again add something like that for d-ports. The variable (DEBIAN_PORTS maybe?) could simply be set in config/m68k.cfg. Cheers, FJP [1]http://d-i.alioth.debian.org/manual/en.i386/apbs01.html#preseed-methods http://d-i.alioth.debian.org/manual/en.i386/apbs02.html#preseed-loading signature.asc Description: This is a digitally signed message part.
Bug#498358: marked as done (installation-report: Successful installation)
Your message dated Thu, 25 Sep 2008 23:26:02 +0200 with message-id [EMAIL PROTECTED] and subject line Re: Bug#498358: installation-report: Successful installation has caused the Debian Bug report #498358, regarding installation-report: Successful installation 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 [EMAIL PROTECTED] immediately.) -- 498358: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=498358 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Package: installation-reports Version: 2.35 Severity: normal -- Package-specific info: Boot method: CD Image version: Daily built netinst Date: Sep 08 Machine: Acer Veriton M261 Partitions: Device Boot Start End Blocks Id System /dev/hdc1 * 1 31 248976 83 Linux /dev/hdc2 32 1001180164350 8e Linux LVM 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: You have to change some mode for the SATA controller in the BIOS, or Linux won't detect the controller. -- Please make sure that the hardware-summary log file, and any other installation logs that you think would be useful are attached to this report. Please compress large files using gzip. Once you have filled out this report, mail it to [EMAIL PROTECTED] == Installer lsb-release: == DISTRIB_ID=Debian DISTRIB_DESCRIPTION=Debian GNU/Linux installer DISTRIB_RELEASE=5.0 (lenny) - installer build 20080907-22:58 X_INSTALLATION_MEDIUM=cdrom == Installer hardware-summary: == umame -a: Linux rompe 2.6.26-1-amd64 #1 SMP Thu Aug 28 11:13:42 UTC 2008 x86_64 unknown lspci -knn: 00:00.0 Host bridge [0600]: Silicon Integrated Systems [SiS] 671MX [1039:0671] lspci -knn: 00:01.0 PCI bridge [0604]: Silicon Integrated Systems [SiS] SiS AGP Port (virtual PCI-to-PCI bridge) [1039:0003] lspci -knn: 00:02.0 ISA bridge [0601]: Silicon Integrated Systems [SiS] SiS968 [MuTIOL Media IO] [1039:0968] (rev 01) lspci -knn: 00:02.5 IDE interface [0101]: Silicon Integrated Systems [SiS] 5513 [IDE] [1039:5513] (rev 01) lspci -knn: Kernel driver in use: SIS_IDE lspci -knn: Kernel modules: pata_sis, sis5513 lspci -knn: 00:03.0 USB Controller [0c03]: Silicon Integrated Systems [SiS] USB 1.1 Controller [1039:7001] (rev 0f) lspci -knn: Kernel driver in use: ohci_hcd lspci -knn: Kernel modules: ohci-hcd lspci -knn: 00:03.1 USB Controller [0c03]: Silicon Integrated Systems [SiS] USB 1.1 Controller [1039:7001] (rev 0f) lspci -knn: Kernel driver in use: ohci_hcd lspci -knn: Kernel modules: ohci-hcd lspci -knn: 00:03.3 USB Controller [0c03]: Silicon Integrated Systems [SiS] USB 2.0 Controller [1039:7002] lspci -knn: Kernel driver in use: ehci_hcd lspci -knn: Kernel modules: ehci-hcd lspci -knn: 00:04.0 Ethernet controller [0200]: Silicon Integrated Systems [SiS] 191 Gigabit Ethernet Adapter [1039:0191] (rev 02) lspci -knn: Kernel driver in use: sis190 lspci -knn: Kernel modules: sis190 lspci -knn: 00:06.0 PCI bridge [0604]: Silicon Integrated Systems [SiS] PCI-to-PCI bridge [1039:000a] lspci -knn: Kernel driver in use: pcieport-driver lspci -knn: 00:0f.0 Audio device [0403]: Silicon Integrated Systems [SiS] Azalia Audio Controller [1039:7502] lspci -knn: 00:1f.0 PCI bridge [0604]: Silicon Integrated Systems [SiS] PCI-to-PCI bridge [1039:0004] lspci -knn: Kernel driver in use: pcieport-driver lspci -knn: 01:00.0 VGA compatible controller [0300]: Silicon Integrated Systems [SiS] 771/671 PCIE VGA Display Adapter [1039:6351] (rev 10) lsmod: Module Size Used by lsmod: ufs67720 0 lsmod: qnx4 13576 0 lsmod: ntfs 188544 0 lsmod: battery16904 0 lsmod: dm_mod 58864 5 lsmod: md_mod 80164 0 lsmod: xfs 475432 0 lsmod: reiserfs 211072 0 lsmod: jfs 157904 0 lsmod: ext3 124688 1 lsmod: jbd51240 1 ext3 lsmod: vfat
Embedded Lenny Install on PowerPC
I'm working on an embedded project - currently trying to install Lenny on an AMCC PowerPC 405EX evaluation board (Kilauea). Sorry for the newbie question and let me know if I should be posting somewhere else. I've got a 2.6.26 kernel cross-compiled (running Lenny AMD64 and ELDK 4.2 on my workstation) and am using U-Boot (v1.3.2) on my evaluation board. At boot time I've configured U-Boot to download my custom kernel and FDT blob and NFS mount the root file system. The root file system is an expansion of the initrd.gz file (from the Lenny Beta 2 installer netboot folder) - including updated modules added by running 'make ... install-modules'. My embedded system boots and the install procedure begins. Everything is fine until I reach the 'Download Installer Components' page. I'm receiving an error message saying: 'No kernel modules were found. This is probably due to a mismatch between the kernel used by this version of the installer and the kernel version available in the archive' I presume this is due to the fact I've compiled my own kernel and the version strings don't exactly match? There is also a warning logged in /var/log/syslog from anna[3678] noting 'no packages for kernel in archive'. Is there a way to turn up the debugging during install to see what the actual mismatch is? Any other suggestions as to resolution or next steps are also welcome. Thanks, -jmh -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Embedded Lenny Install on PowerPC
On Friday 26 September 2008, Jason Hanna wrote: 'No kernel modules were found. This is probably due to a mismatch between the kernel used by this version of the installer and the kernel version available in the archive' This is really very simple. The 'uname -r' of the running D-I kernel must match the package name of module udebs, which is in general *-modules-$(uname -r)-di. And of course they must be ABI compatible. Note that the actual comparison is with a field in the control file of the udebs and not the package name. For example: $ dpkg -e sata-modules-2.6.26-1-amd64-di_1.46_amd64.udeb Package: sata-modules-2.6.26-1-amd64-di Source: linux-kernel-di-amd64-2.6 Version: 1.46 Kernel-Version: 2.6.26-1-amd64 Architecture: amd64 [...] But of course that field will match the package name. The disadvantage of using a netboot image is that normally it will need to download modules from a mirror. You may be better of just including all modules you need in the initrd or compiling them into the kernel (if size limits allow). If you do that you can just ignore the error. Cheers, FJP signature.asc Description: This is a digitally signed message part.
[D-I Manual] Build log for en (25 Sep 2008)
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/appendix/preseed.xml
Uen/using-d-i/modules/mdcfg.xml
Updated to revision 56132.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Embedded Lenny Install on PowerPC
Thanks Frans. Wanted to make sure I understood the exact formula. Downloaded the (older) kernel source and completed the EXTRAVERSION attribute in the makefile. Re-compiled and I *should* be all set now. Regards, -jmh On Thu, Sep 25, 2008 at 6:39 PM, Frans Pop [EMAIL PROTECTED] wrote: On Friday 26 September 2008, Jason Hanna wrote: 'No kernel modules were found. This is probably due to a mismatch between the kernel used by this version of the installer and the kernel version available in the archive' This is really very simple. The 'uname -r' of the running D-I kernel must match the package name of module udebs, which is in general *-modules-$(uname -r)-di. And of course they must be ABI compatible. Note that the actual comparison is with a field in the control file of the udebs and not the package name. For example: $ dpkg -e sata-modules-2.6.26-1-amd64-di_1.46_amd64.udeb Package: sata-modules-2.6.26-1-amd64-di Source: linux-kernel-di-amd64-2.6 Version: 1.46 Kernel-Version: 2.6.26-1-amd64 Architecture: amd64 [...] But of course that field will match the package name. The disadvantage of using a netboot image is that normally it will need to download modules from a mirror. You may be better of just including all modules you need in the initrd or compiling them into the kernel (if size limits allow). If you do that you can just ignore the error. Cheers, FJP -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
