Re: dpkg should support a --force-unsafe-io option or such

[Modestas Vainius]

Hello,

On sekmadienis 10 Spalis 2010 01:06:41 Otavio Salvador wrote:
> On Fri, Oct 8, 2010 at 8:55 PM, Modestas Vainius  wrote:
> ...
> 
> > It does not make much sense for dpkg to be in this uber-paranoid mode at
> > debian-installer time. If power fails, install process will probably have
> > to be started from scratch anyway. What's more, obviously I have no
> > choice to use libeatmydata or similar to fight this dpkg behaviour at
> > debian installer time.
> > 
> > In my opinion, dpkg should provide a way to turn off those offensive
> > *sync() calls and debian installer should make use of it.
> 
> I fully agree that d-i doesn't need and shouldn't use it by default.
> In fact some embedded systems shouldn't use it either in production
> mode if the media suffer of wearing.
> 
> As previously said in this thread, d-i needs to be restarted in case
> of power outage or something broken and fsync won't help on that
> except make it taking longer.

I feel rather strong about this issue because I keep running and running into 
it in different situations. I truly believe that it should be high priority 
for squeeze but I won't bump severity myself. To sum up:

1) current dpkg is bog slow on modern file systems (brtfs, ext4). What is 
more, due to frequent sync() calls, it is a very bad idea to run dpkg when 
other unrelated disk I/O (esp. on modern FSes) is in the background. It just 
slows everything down.

2) current dpkg is arguably not suitable for flash media (i.e. embedded 
devices). This hurts the "universal" part of Debian OS.

3) dpkg is pointlessly slow in such use cases as buildds where *sync() is not 
important at all.

4) while typical dpkg could be work arounded with libeatmydata, there is no 
cure for debian-installer.

And all this is to protect against power failure? Sure, the purpose is noble 
and maybe it's a good default but due to negative side effects I find it 
unacceptable that this behaviour is not configurable.

-- 
Modestas Vainius 


signature.asc
Description: This is a digitally signed message part.

Processing of partman-auto_93_i386.changes

[Archive Administrator]

partman-auto_93_i386.changes uploaded successfully to ftp-master.debian.org
along with the files:
  partman-auto_93.dsc
  partman-auto_93.tar.gz
  partman-auto_93_i386.udeb

Greetings,

Your Debian queue daemon (running on host ravel.debian.org)


-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/e1p4upk-00044p...@ravel.debian.org

Processing of partman-auto_93_i386.changes

[Archive Administrator]

partman-auto_93_i386.changes uploaded successfully to localhost
along with the files:
  partman-auto_93.dsc
  partman-auto_93.tar.gz
  partman-auto_93_i386.udeb

Greetings,

Your Debian queue daemon (running on host franck.debian.org)


-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/e1p4uqc-0006s6...@franck.debian.org

Bug#597087: marked as done (debian-installer: Swap space is too big when created by the guided partitioner)

[Debian Bug Tracking System]

Your message dated Sun, 10 Oct 2010 12:21:32 +
with message-id 
and subject line Bug#597087: fixed in partman-auto 93
has caused the Debian Bug report #597087,
regarding debian-installer: Swap space is too big when created by the guided 
partitioner
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.)


-- 
597087: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=597087
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: debian-installer
Severity: normal
Tags: d-i

Hi!

Sorry if it's already known or already reported, but trying to make a
install (with 20100916-10:40 daily-image of kfreebsd-amd64) on a disk
with 166 GB of free space, using the guided partitioner (selected the
option to split /home only), I had these partitions created:

7.0 GB /
5.9 GB swap
153.2 GB /home

The machine has 2 GB of RAM (just in case the RAM size is used to
calculate the swap space size).

Isn't 5.9 GB of swap too much? It's 3 times the size of the RAM and almost
the same size of /
Also, isn't 7.0 GB for / too little?

Thank you very much!

Best regards,
Nelson

-- System Information:
Debian Release: squeeze/sid
  APT prefers testing-proposed-updates
  APT policy: (500, 'testing-proposed-updates'), (500, 'testing'), (1, 
'experimental')
Architecture: i386 (i686)

Kernel: Linux 2.6.35-trunk-686 (SMP w/2 CPU cores)
Locale: LANG=pt_BR.utf8, LC_CTYPE=pt_BR.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash


--- End Message ---
--- Begin Message ---
Source: partman-auto
Source-Version: 93

We believe that the bug you reported is fixed in the latest version of
partman-auto, which is due to be installed in the Debian FTP archive:

partman-auto_93.dsc
  to main/p/partman-auto/partman-auto_93.dsc
partman-auto_93.tar.gz
  to main/p/partman-auto/partman-auto_93.tar.gz
partman-auto_93_i386.udeb
  to main/p/partman-auto/partman-auto_93_i386.udeb



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 597...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Christian Perrier  (supplier of updated partman-auto 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Sun, 10 Oct 2010 10:01:02 +0200
Source: partman-auto
Binary: partman-auto
Architecture: source i386
Version: 93
Distribution: unstable
Urgency: low
Maintainer: Debian Install System Team 
Changed-By: Christian Perrier 
Description: 
 partman-auto - Automatically partition storage devices (partman) (udeb)
Closes: 597087
Changes: 
 partman-auto (93) unstable; urgency=low
 .
   * Team upload
 .
   [ Colin Watson ]
   * Use 'dh $@ --options' rather than 'dh --options $@', for
 forward-compatibility with debhelper v8.
 .
   [ Christian Perrier ]
   * Limit swap to 200% of physical memory. Closes: #597087
 .
   [ Updated translations ]
   * Asturian (ast.po) by maacub
   * Bulgarian (bg.po) by Damyan Ivanov
   * Bosnian (bs.po) by Armin Beširović
   * Danish (da.po) by Jacob Sparre Andersen
   * Persian (fa.po) by Ebrahim Byagowi
   * Portuguese (Brazil) (pt_BR.po) by Felipe Augusto van de Wiel (faw)
   * Telugu (te.po) by Arjuna Rao Chavala
Checksums-Sha1: 
 8d430db9e5b92b5ef0ca0f35c58177ef4edbd6ce 1491 partman-auto_93.dsc
 bcca84ee3956cd1b436210020f0206184c78ca48 114426 partman-auto_93.tar.gz
 f43601125030bd1909b0c76f4d92d4f9eb1f382a 76544 partman-auto_93_i386.udeb
Checksums-Sha256: 
 18a96b0b22e6a3ff26f8ad886b716e40f3df5184dca5acfe0cd02a1ed5340cba 1491 
partman-auto_93.dsc
 581b2068c7ca3493a08abac0d2df522c67facd9593ab56cd85dc59b1df718867 114426 
partman-auto_93.tar.gz
 f7c281245fdb05d7a762e33b8c39141e6e8b28467d1a62e518dca2aff5b37e06 76544 
partman-auto_93_i386.udeb
Files: 
 81befe7799cf2f8480cc576715228935 1491 debian-installer standard 
partman-auto_93.dsc
 2fba200809d360c03206764183b12088 114426 debian-installer standard 
partman-auto_93.tar.gz
 a043853648bc2bbb19b84ed8ce7bebd6 76544 debian-installer standard 
partman-auto_93_i386.udeb
Package-Type: udeb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)

iQIVAwUBTLGt9IcvcCxNbiWoAQLeYhAAhBzgmsHdO72ZnSy7kb99IlbqGqMC4UuS
YN3NJHJiMNdhKsubaI49vtF10W5+fMHZlCoLjtoIa+E6m+64QIHWpUKNTCHk1F0D
zBAS6jn/wmJpA/5gc9IHjvRu6EOR4VDW38DdMxYLPawPHe3ZBv1jizarKoRMKNBF
IORFep0/wi+X8X4zF+vVJFSSumqRW6

partman-auto_93_i386.changes ACCEPTED into unstable

[Debian FTP Masters]

Accepted:
partman-auto_93.dsc
  to main/p/partman-auto/partman-auto_93.dsc
partman-auto_93.tar.gz
  to main/p/partman-auto/partman-auto_93.tar.gz
partman-auto_93_i386.udeb
  to main/p/partman-auto/partman-auto_93_i386.udeb


Override entries for your package:
partman-auto_93.dsc - source debian-installer
partman-auto_93_i386.udeb - standard debian-installer

Announcing to debian-devel-chan...@lists.debian.org
Closing bugs: 597087 


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
Archive: http://lists.debian.org/e1p4uuc-00018z...@franck.debian.org

Re: Bug#584254: dpkg should support a --force-unsafe-io option or such

[Guillem Jover]

Hi!

On Sun, 2010-10-10 at 12:37:27 +0300, Modestas Vainius wrote:
> On sekmadienis 10 Spalis 2010 01:06:41 Otavio Salvador wrote:
> > On Fri, Oct 8, 2010 at 8:55 PM, Modestas Vainius  wrote:
> > > It does not make much sense for dpkg to be in this uber-paranoid mode at
> > > debian-installer time. If power fails, install process will probably have
> > > to be started from scratch anyway. What's more, obviously I have no
> > > choice to use libeatmydata or similar to fight this dpkg behaviour at
> > > debian installer time.
> > > 
> > > In my opinion, dpkg should provide a way to turn off those offensive
> > > *sync() calls and debian installer should make use of it.
> > 
> > I fully agree that d-i doesn't need and shouldn't use it by default.
> > In fact some embedded systems shouldn't use it either in production
> > mode if the media suffer of wearing.
> > 
> > As previously said in this thread, d-i needs to be restarted in case
> > of power outage or something broken and fsync won't help on that
> > except make it taking longer.
> 
> I feel rather strong about this issue because I keep running and running into 
> it in different situations. I truly believe that it should be high priority 
> for squeeze but I won't bump severity myself. To sum up:

I had planned to include changes for this for squeeze, but then the
sudden freeze happened, and after the initial reaction from the
release team on the first exception request I didn't feel like begging
for this and other changes.

> 1) current dpkg is bog slow on modern file systems (brtfs, ext4). What is 
> more, due to frequent sync() calls, it is a very bad idea to run dpkg when 
> other unrelated disk I/O (esp. on modern FSes) is in the background. It just 
> slows everything down.

Right, for some time now I've considered the switch from fsync() to
sync() (on Linux) to be a mistake, as it will affect unrelated file
systems, which might be disruptive in case there's background work being
done.

But this was done because those "modern file systems" didn't perform
adequately with fsync(), and they are the ones which require the syncs
or they will actually lose data.

> 3) dpkg is pointlessly slow in such use cases as buildds where *sync() is not 
> important at all.

Well, even if the buildd chroot supposedly should be able to be recreated
easily, if the zero-lenght file issues appear on it, then it might not
be obvious something is wrong, and might produce bogus packages.

> 2) current dpkg is arguably not suitable for flash media (i.e. embedded 
> devices). This hurts the "universal" part of Debian OS.

> 4) while typical dpkg could be work arounded with libeatmydata, there is no 
> cure for debian-installer.

Sure, I agree the user should be able to disable this, at their own
risk. Or on specific cases, like on d-i.

> And all this is to protect against power failure? Sure, the purpose is noble 
> and maybe it's a good default but due to negative side effects I find it 
> unacceptable that this behaviour is not configurable.

Not only power failures, any abrupt system crash, say the bus getting
locked up, or a user assisted reboot, can produce for example
zero-lenght files on at least ext4 file systems, I don't know about
btrfs. The worst though is that the performance issues affect the file
systems which really need those safety measures. Also take into account
these are not anecdotal cases, Ubuntu who has offered ext4 on installation
for some time now had *hundreds* of duped bug reports on broken systems
due to this.

Anyway, I actually had the changes around last July, and I'll run them
through the release team to see what they say. I've rebased them now,
and will polish them a bit, but they are essentially these:

  
  

regards,
guillem


-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20101010122146.ga31...@gaara.hadrons.org

GRUB2 doesn’t is installed on SATA HD

[Marcelo Laia]

I have a MB with 2 SATAI/II and 1 IDE 100 port.

I have installed 2 HDs, one IDE and one SATAII, and 1 SATA DVD rom.

MB BIOS detect IDE Master (channel 1) and SATA HD master on channel 2
and DVD rom slave on channel 2, too.

I do do a fresh instalation (Debian testing last week).

When I choose to install grub-pc on SATA HD and click "Continue",
installer tell me that I *don't" had choose any drive to install
grub-pc! I try to install it on the first partition of SATA HD and got
the same result. I choose install without grub-pc. The system is
installed ok.

However, when I reboot, bios tell me that there isn't a BOOT drive. No
boot here.

I boot with a livecd and do the steps to rescue grub. The process is
ok and no errors is reported.

I try to reboot from sata hd and bios tell me that no boot drive.

I boot with Super GRUB2 Disk and tell it to "Detect any GRUB2
installation (even if mbr is overwritten)". My GRUB is found on
(hd0,1) and I could load it and boot my system!

So, now, for boot my system, I need the SG2D all time.

I have installed the same system on IDE HD and all is fine! No
problem, so, no errors with my media dvd nor with the iso image.

What I could do to solve this issue?

Thank you very much!


-- 
Marcelo Luiz de Laia
www.ufvjm.edu.br/floresta
Diamantina - MG - Brasil (Brazil)
Linux user number 487797


-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/aanlktikmruymfo52z1nbef5odpxjjp3ol5q44nay2...@mail.gmail.com

Bug#599763: installation-reports: It works fine!

[David]

Package: installation-reports
Severity: wishlist



-- Package-specific info:

Boot method: CD
Image version: 10-Oct daily buit image
Date: 10-Oct

Machine: Compaq presario 2516EA
Partitions: 


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: fine




-- 

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 sub...@bugs.debian.org.

==
Installer lsb-release:
==
DISTRIB_ID=Debian
DISTRIB_DESCRIPTION="Debian GNU/Linux installer"
DISTRIB_RELEASE="6.0 (squeeze) - installer build 20101010-09:54"
X_INSTALLATION_MEDIUM=cdrom

==
Installer hardware-summary:
==
uname -a: Linux un 2.6.32-5-486 #1 Thu Aug 12 12:59:56 UTC 2010 i686 GNU/Linux
lspci -knn: 00:00.0 Host bridge [0600]: ATI Technologies Inc RS200/RS200M AGP 
Bridge [IGP 340M] [1002:cbb2] (rev 02)
lspci -knn: Kernel driver in use: agpgart-ati
lspci -knn: 00:01.0 PCI bridge [0604]: ATI Technologies Inc PCI Bridge [IGP 
340M] [1002:7010]
lspci -knn: 00:02.0 USB Controller [0c03]: ALi Corporation USB 1.1 Controller 
[10b9:5237] (rev 03)
lspci -knn: Subsystem: Hewlett-Packard Company Device [103c:0850]
lspci -knn: Kernel driver in use: ohci_hcd
lspci -knn: 00:06.0 Multimedia audio controller [0401]: ALi Corporation M5451 
PCI AC-Link Controller Audio Device [10b9:5451] (rev 02)
lspci -knn: Subsystem: Hewlett-Packard Company Device [103c:0850]
lspci -knn: 00:07.0 ISA bridge [0601]: ALi Corporation M1533/M1535/M1543 PCI to 
ISA Bridge [Aladdin IV/V/V+] [10b9:1533]
lspci -knn: Subsystem: ALi Corporation M1533/M1535/M1543 PCI to ISA Bridge 
[Aladdin IV/V/V+] [10b9:1533]
lspci -knn: 00:08.0 Modem [0703]: ALi Corporation M5457 AC'97 Modem Controller 
[10b9:5457]
lspci -knn: Subsystem: Hewlett-Packard Company Device [103c:0850]
lspci -knn: 00:0a.0 CardBus bridge [0607]: O2 Micro, Inc. OZ601/6912/711E0 
CardBus/SmartCardBus Controller [1217:6972]
lspci -knn: Subsystem: Hewlett-Packard Company Device [103c:0850]
lspci -knn: Kernel driver in use: yenta_cardbus
lspci -knn: 00:0c.0 FireWire (IEEE 1394) [0c00]: Texas Instruments TSB43AB21 
IEEE-1394a-2000 Controller (PHY/Link) [104c:8026]
lspci -knn: Subsystem: Hewlett-Packard Company Device [103c:0850]
lspci -knn: Kernel driver in use: firewire_ohci
lspci -knn: 00:0f.0 USB Controller [0c03]: ALi Corporation USB 1.1 Controller 
[10b9:5237] (rev 03)
lspci -knn: Subsystem: Hewlett-Packard Company Device [103c:0850]
lspci -knn: Kernel driver in use: ohci_hcd
lspci -knn: 00:10.0 IDE interface [0101]: ALi Corporation M5229 IDE [10b9:5229] 
(rev c4)
lspci -knn: Subsystem: Hewlett-Packard Company Device [103c:0850]
lspci -knn: Kernel driver in use: pata_ali
lspci -knn: 00:11.0 Bridge [0680]: ALi Corporation M7101 Power Management 
Controller [PMU] [10b9:7101]
lspci -knn: Subsystem: Hewlett-Packard Company Device [103c:0850]
lspci -knn: 00:12.0 Ethernet controller [0200]: National Semiconductor 
Corporation DP83815 (MacPhyter) Ethernet Controller [100b:0020]
lspci -knn: Subsystem: Hewlett-Packard Company Device [103c:0850]
lspci -knn: Kernel driver in use: natsemi
lspci -knn: 01:05.0 VGA compatible controller [0300]: ATI Technologies Inc 
Radeon IGP 330M/340M/350M [1002:4337]
lspci -knn: Subsystem: Hewlett-Packard Company Device [103c:0850]
usb-list: 
usb-list: Bus 01 Device 01: OHCI Host Controller [1d6b:0001]
usb-list:Level 00 Parent 00 Port 00  Class 09(hub  ) Subclass 00 Protocol 00
usb-list:Manufacturer: Linux 2.6.32-5-486 ohci_hcd
usb-list:Interface 00: Class 09(hub  ) Subclass 00 Protocol 00 Driver hub
usb-list: 
usb-list: Bus 02 Device 01: OHCI Host Controller [1d6b:0001]
usb-list:Level 00 Parent 00 Port 00  Class 09(hub  ) Subclass 00 Protocol 00
usb-list:Manufacturer: Linux 2.6.32-5-486 ohci_hcd
usb-list:Interface 00: Class 09(hub  ) Subclass 00 Protocol 00 Driver hub
lsmod: Module  Size  Used by
lsmod: ufs55534  0 
lsmod: qnx45078  0 
lsmod: ntfs  162603  0 
lsmod: reiserfs  173360  0 
lsmod: dm_mod 45925  0 
lsmod: md_mod 66027  0 
lsmod: xfs   404862  0 
lsmod: expor

Debugging yaboot issues (was: Re: Call for testers: new yaboot package release - experimental installer)

[Benjamin Cama]

Hi Zsombor,

First, my apologies for being so slow to answer. And thank you for the
custom installer you built.

I am very thankfull for your enthusiasm, but I would like to point out
some thing that you're doing wrong. I am saying that not to deter anyone
to do anything, but to try to be more organized, as it has already been
pointed out by other people from Debian : debian-powerpc is often a mess
any nobody else will want to help us if we don't try to do things in a
more organized way. We already had no help from the d-i team about this
new yaboot release, let's hope that by making things the "right way"
we'll get more help.

Le dimanche 10 octobre 2010 à 12:42 +0200, Zsombor a écrit :
> * official 64-bit kernel replaced by a custom kernel 
> [linux-image-2.6.32zsexp01]
>   with CONFIG_SCSI_PROC_FS=y   <- an idea to make it work on Mac

Don't do that. That /may/ work but it's not the right way to do that and
won't ever be accepted by the kernel team. This option has already been
deactivated years ago, and it's been years that yaboot should have
adapted to /sys. BTW, the error message is wrong in that it also
checks /sys for SCSI devices, but the /proc/scsi message has not been
updated regarding this change.

To help about this _specific_ issue, please report to #572869. Your SATA
controller should have been supported by yaboot, as I thought that
changes made to 1.3.16 fixed that, but it doesn't seem to be the case.
To help diagnose the problem, to anyone having this issue on a G5,
please also include the result of : ls /sys/bus/scsi/devices

> + added ehea nic module (for 64bit di-kernel only) <- to support Power6 
> netcard

A specific bug report should be opened to track that: Xavier, could you
do that ? The problem is that it happens on a custom image you made
Zsombor, and I'm not sure anyone will accept it as a valid BR.

That's where I am asking for help from the d-i team: how could we test
this new package from a d-i install disc ? Is there an easier and more
"officially-compliant" way, so that we can report bugs without doubts ?
Should we push the package to unstable directly ?

Regards,
benjamin


-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/1286749283.5299.45.ca...@nsk

Bug#599772: console-setup-udeb: console-setup during preseeded automatic installation ignore preseed values and stop

[George Shuklin]

Package: console-setup-udeb
Version: 1.56
Severity: important
Tags: d-i

Automated installation with preseed of Squeeze stops at dialogue 'Configure 
keyboard-keyboard layout'.

Even preseed file contain:

d-i console-setup/variant select us\
d-i console-setup/layout select us\

(I test it with us and USA values) log file still contains:

 Menu item 'console-setup-udeb' succeeded but requested to be left unconfigured.

I check it with following preseed strings and with kernel args values: 
layout=USA, layout=us, varian=us, variant=USA, but no success.

I think this same bug for Ubutu (confirmed):

https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/512592


-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.32-5-amd64 (SMP w/4 CPU cores)
Locale: LANG=ru_RU.utf8, LC_CTYPE=ru_RU.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash



-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/20101011005854.20356.83274.report...@desunote.ru