Your message dated Fri, 19 Nov 2010 20:18:30 +0100
with message-id <[email protected]>
and subject line Re: Bug#603920: shadow: securetty misses support for ttyO[0-3]
devices
has caused the Debian Bug report #603920,
regarding shadow: securetty misses support for ttyO[0-3] devices
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.)
--
603920: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=603920
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: shadow
Severity: wishlist
as described in https://bugs.launchpad.net/bugs/512845 securetty.linux
misses support for serial ports on TI OMAP boards if the DMA-offloaded
driver instead of the default 8250 one is used for serial ports.
a fix can be found at
http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/maverick/shadow/maverick/revision/36
-- System Information:
Debian Release: squeeze/sid
APT prefers maverick-updates
APT policy: (500, 'maverick-updates'), (500, 'maverick-security'),
(500, 'maverick')
Architecture: armel (armv7l)
Kernel: Linux 2.6.29-arm2-ac100 (SMP w/2 CPU cores; PREEMPT)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
signature.asc
Description: This is a digitally signed message part
--- End Message ---
--- Begin Message ---
Hello,
On Thu, Nov 18, 2010 at 03:37:52PM +0100, [email protected] wrote:
>
> as described in https://bugs.launchpad.net/bugs/512845 securetty.linux
> misses support for serial ports on TI OMAP boards if the DMA-offloaded
> driver instead of the default 8250 one is used for serial ports.
>
> a fix can be found at
> http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/maverick/shadow/maverick/revision/36
It looks like it was already fixed in 1:4.1.4.2+svn3283-1
--
Nekral
--- End Message ---