Re: Bug#563109: ITP: e17-modules-svn -- Misc plugins for the e17 window manager

[Albin Tonnerre]

On Wed, 30 Dec 2009 23:51 +0100, Mike Hommey wrote :
> On Wed, Dec 30, 2009 at 11:28:37PM +0100, Albin Tonnerre wrote:
> > Package: wnpp
> > Severity: wishlist
> > Owner: Albin Tonnerre 


> > * Package name: e17-modules-svn
> >   Version : 0.16.999.063
> >   Upstream Author : e17 development team 
> > 
> > * URL : http://www.enlightenment.org/
> > * License : various (GPL2, BSD, LGPL2.1)
> >   Programming Lang: C
> >   Description : Misc plugins for the e17 window manager

> > This package provides a collection of non-core modules for e17, from the
> > enlightenment.org SVN repository. They provide various functionnality, such 
> > as :
> >  - Tiling capability
> >  - Network status applet
> >  - cpu/mem/disks status applet
> >  - digital clock applet
> >  - experimental composite extension

> Could the package name *not* include -svn in its name, and use -extras
> or something similar if e17-modules only is not possible ?

Sure, I'll go for e17-modules-extras then.

Regards,
-- 
Albin Tonnerre


signature.asc
Description: Digital signature

Re: where is /etc/hosts supposed to come from?

[Vincent Bernat]

OoO En  cette nuit nuageuse du  jeudi 31 décembre 2009,  vers 01:16, Sam
Morris  disait :

>>> Adding meaningless configuration to work around programs that are
>>> broken by design does not seem like a good solution.
>> 
>> There are  a lot of  programs requiring some  kind of FQDN  (for example
>> because they implement a protocol requiring it). How should they get it?
>> I have never  seen a more universal that to get  node name with uname(),
>> then use gethostbyname(). Please, provide better way.

> The admin should supply it in the program's configuration, since only the 
> admin is able to know the correct value.

Sure, the admin would have to  configure a whole set of programs instead
of just configuring the canonical name in one unique place of the system
and let each program that needs it to autodiscover it?

This  does  not preclude  the  possibility  to  override what  has  been
discovered on a case by case basis.
-- 
panic ("No CPUs found.  System halted.\n");
2.4.3 linux/arch/parisc/kernel/setup.c


pgpsJCTUzoBfc.pgp
Description: PGP signature

Re: where is /etc/hosts supposed to come from?

[Philipp Kern]

On 2009-12-30, Henrique de Moraes Holschuh  wrote:
> On Wed, 30 Dec 2009, Philipp Kern wrote:
>> You don't switch to v6-only, you switch to dual stack IPv4+IPv6.  One point
>> being that with a v6-only host you're totally unable to reach IPv4 sites
>> without the help of application-level proxies.
> That's false.  You can use protocol-level gateways, which do NAT and PT
> (protocol translation).

Can you point me to one please?  I found that deprecated and entirely
unsupported.  But if there's a software for that available...

Kind regards,
Philipp Kern



-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: where is /etc/hosts supposed to come from?

[Henrique de Moraes Holschuh]

On Thu, 31 Dec 2009, Philipp Kern wrote:
> On 2009-12-30, Henrique de Moraes Holschuh  wrote:
> > On Wed, 30 Dec 2009, Philipp Kern wrote:
> >> You don't switch to v6-only, you switch to dual stack IPv4+IPv6.  One point
> >> being that with a v6-only host you're totally unable to reach IPv4 sites
> >> without the help of application-level proxies.
> > That's false.  You can use protocol-level gateways, which do NAT and PT
> > (protocol translation).
> 
> Can you point me to one please?  I found that deprecated and entirely
> unsupported.  But if there's a software for that available...

Cisco boxes...

-- 
  "One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie." -- The Silicon Valley Tarot
  Henrique Holschuh


-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: where is /etc/hosts supposed to come from?

[Vincent Lefevre]

On 2009-12-30 15:31:12 -0200, Henrique de Moraes Holschuh wrote:
> On Tue, 29 Dec 2009, Vincent Lefevre wrote:
> > On 2009-12-29 17:44:31 +0100, Milan P. Stanic wrote:
> > > Mutt in testing/unstable use /etc/mailname.
> > 
> > But not the official Mutt version.
> 
> Who lets you configure the correct domain you want it to use for email
> addresses in its config files, although I don't recall if you can tell it
> what to use for message-ids.

Yes, that's what I had to do after reporting Mutt bug 3298 (Mutt has
its own buggy way to determine the FQDN: it uses /etc/resolv.conf
while /etc/hosts may have the precedence).

> Debian mutt will autoconfigure better, but that's it.
> 
> That said, the canonical name is required by POSIX, but POSIX (looking at
> SuSv3) doesn't require it to be unique, doesn't give it any application
> usage notes, and in fact doesn't even require it to be a FQDN (which is, in
> fact a pratical requirement of the stuff that uses the canonical name).

POSIX says:

  If the AI_CANONNAME flag is specified and the nodename argument is
  not null, the function shall attempt to determine the canonical name
  corresponding to nodename (for example, if nodename is an alias or
  shorthand notation for a complete name).
  ^^

So, it isn't intended to be a short name. As this is mostly
implementation defined, it may be difficult to be very accurate.

Also, otherwise, what would be the point of having a "canonical name"
in addition to a node name if there isn't any requirement?

> If you want proper message-ids, do it right and have a GUUID in it.

Perhaps, hoping that Message-Ids wouldn't be too long (I've seen
broken messages due to Message-Ids generated by Pine, related to
word-wrapping IIRC).

> If mutt depends on the result of gethostname() to be unique in the
> whole world to generate proper message-ids, it is broken.

Actually, there's a low probability of duplicates (but practically
possible) if many people use a broken FQDN such as "localhost".

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / Arénaire project (LIP, ENS-Lyon)


-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: where is /etc/hosts supposed to come from?

[Mike Hommey]

On Thu, Dec 31, 2009 at 02:02:36PM +0100, Vincent Lefevre wrote:
> POSIX says:
> 
>   If the AI_CANONNAME flag is specified and the nodename argument is
>   not null, the function shall attempt to determine the canonical name
>   corresponding to nodename (for example, if nodename is an alias or
>   shorthand notation for a complete name).
>   ^^
> 
> So, it isn't intended to be a short name. As this is mostly
> implementation defined, it may be difficult to be very accurate.

Where does the above say it must be a FQDN ? It says that *for example*,
*if* nodename is blah blah. So, what if the nodename is *not* that ?
(which it is not on a lot of hosts)

Mike


-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: where is /etc/hosts supposed to come from?

[Vincent Lefevre]

On 2009-12-30 11:54:57 -0800, Russ Allbery wrote:
> Vincent Lefevre  writes:
> > "stanford.edu" is definitely wrong. First it's just a domain name, not a
> > FQDN (as required by the mailname(5) man page).
> 
> stanford.edu is an RFC 1035 FQDN.

RFC 1035 (from /usr/share/doc/RFC/links/rfc1035.txt.gz) doesn't define
what a FQDN is. It doesn't contain "FQDN", and the only occurrence of
"fully" and "qualified" is in "Gateways will also have host level
pointers at their fully qualified addresses.

FYI, here's what Wikipedia[*] (though not authoritative and sometimes
containing errors) says:

  For example, given a device with a local hostname myhost and a
  parent domain name example.com, the fully qualified domain name is
  written as myhost.example.com. This fully qualified domain name
  therefore uniquely identifies the host — while there may be many
  resources in the world called myhost, there is only one
  myhost.example.com.

[*] http://en.wikipedia.org/wiki/Fully_qualified_domain_name

> > This would meen that two different machines could generate the same
> > Message-Id; the right part of "@" in a Message-Id should contain the
> > hostname to avoid this kind of problems.
> 
> The term "message ID" appears nowhere in the description of /etc/mailname.
> Why do you think it's supposed to be used for generating message IDs?

Earlier in the discussion:

  "Anything mail related must use /etc/mailname if it needs something
   ^
  that can be translated to an IP address."

> It is specifically intended for generating e-mail addresses.

In such a case, "hostname -f" (or equivalent) is still useful to
generate message-ids. And the Debian mailname(5) man page doesn't
say e-mail addresses specifically.

> > Moreover, concerning the e-mail addresses, root is local to the machine,
> > so that generating a mail from r...@stanford.edu is incorrect.
> 
> You do not know either that root is local to my system or that
> r...@stanford.edu is incorrect for it.  Both of those are configuration
> *choices*, not requirements.

But r...@stanford.edu wouldn't be the same root. Perhaps the Debian
mailname(5) man page should make clear what is intended for local
users and use consistent terminology.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / Arénaire project (LIP, ENS-Lyon)


-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: where is /etc/hosts supposed to come from?

[Vincent Lefevre]

On 2009-12-30 15:33:05 -0200, Henrique de Moraes Holschuh wrote:
> Better correct myself here.  POSIX provides a way for apps to query the
> canonical host name, but DOES NOT REQUIRE IT TO BE A FQDN.
> 
> So, it provided the notion of a "special name", the canonical host name.
> 
> In practice, it has to be a FQDN, but that's due to bad usage by
> applications, not a POSIX (or SuSv3) requirement.

One problem is that it seems to be the only way to get the FQDN
of the host. FYI, I use the FQDN as a way to identify the hosts
(and a FQDN is more meaningful and probably more stable than an
arbitrary UUID).

But I don't know any software that tries to resolve the FQDN,
except broken MTAs that reject mail if they can't resolve the
FQDN, despite the fact that the client is on a private network.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / Arénaire project (LIP, ENS-Lyon)


-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: where is /etc/hosts supposed to come from?

[Vincent Lefevre]

On 2009-12-31 14:10:46 +0100, Mike Hommey wrote:
> On Thu, Dec 31, 2009 at 02:02:36PM +0100, Vincent Lefevre wrote:
> > POSIX says:
> > 
> >   If the AI_CANONNAME flag is specified and the nodename argument is
> >   not null, the function shall attempt to determine the canonical name
> >   corresponding to nodename (for example, if nodename is an alias or
> >   shorthand notation for a complete name).
> >   ^^
> > 
> > So, it isn't intended to be a short name. As this is mostly
> > implementation defined, it may be difficult to be very accurate.
> 
> Where does the above say it must be a FQDN ? It says that *for example*,
> *if* nodename is blah blah. So, what if the nodename is *not* that ?
> (which it is not on a lot of hosts)

If it is not that, it is the complete name. But since it is
implementation-defined, which Debian's document defines the
canonical name?

Do you suggest that getnameinfo() be used to get the FQDN?

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / Arénaire project (LIP, ENS-Lyon)


-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: where is /etc/hosts supposed to come from?

[Jeremiah Foster]

On Dec 31, 2009, at 15:04, Vincent Lefevre wrote:

> On 2009-12-31 14:10:46 +0100, Mike Hommey wrote:
>> On Thu, Dec 31, 2009 at 02:02:36PM +0100, Vincent Lefevre wrote:
>>> POSIX says:

Have we resolved where the canonical hostname is going to reside or does 
reside? 

Debian's policy manual[0] states that `hostname --fqdn` is where this 
information should be gathered from. Is that the canonical method?

Jeremiah

0. http://www.debian.org/doc/debian-policy/ch-customized-programs.html

--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Help with Firmware issue

[chrisr]

> To whom it may concern
>
> I hope you can help us as we really desperate to solve a problem we
> currently facing with a product we imported from China that has a
> problem with the firmware
>
> The product is a 3.5 incn Hard disk media player that you can use to watch
> movies, download music , photo's and data
> based on the Silan sc 8636a chipset and based on a Linux O/S
>
>
> the problem is that when you start adding more folders, to the unit the
> units starts to slow down and eventually start hanging, and takes for
> ever to index and it searches forever
>
> also the problem we facing is that when you add more folders to the unit
> it come crashes and many of the folders cannot be seen when you are on TV
> mode
> but can be seen when connected to a PC via USB
>
>
> The problem is definitely with the firmware , but we cannot communicate
> with the supplier due to a language problem
> although they have been giving us updated firmwares we still dont;t seem
> to finding a correct solution to our problem
>
>
> It looks to me that there is logic problem with how the firmware
> functions
>
> we do not know who to ask for help and search
> the Internet and came across your website and hope you can help
>
> i am attaching a copy of the Firmware which is called Bank30.rom which
> is 2mb file which i have zipped to 1.4MB (WinZip 14.0)
>
>
> Thank you reading my email and hope you can help
>
> Regards
> Chris Rootman
>
> My mail bounced back as your server does not accept attachments

I can mail the file Bank30.rom to you

my email address is chr...@mighty.co.za

Have a great New year 2010


>


--
South Africa's premier free email service - www.webmail.co.za
--
For super low premiums, click here http://home.webmail.co.za/dd.pwm


-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: where is /etc/hosts supposed to come from?

[Iustin Pop]

On Thu, Dec 31, 2009 at 04:12:30PM +0100, Jeremiah Foster wrote:
> 
> On Dec 31, 2009, at 15:04, Vincent Lefevre wrote:
> 
> > On 2009-12-31 14:10:46 +0100, Mike Hommey wrote:
> >> On Thu, Dec 31, 2009 at 02:02:36PM +0100, Vincent Lefevre wrote:
> >>> POSIX says:
> 
> Have we resolved where the canonical hostname is going to reside or does 
> reside? 
> 
> Debian's policy manual[0] states that `hostname --fqdn` is where this 
> information should be gathered from. Is that the canonical method?

This is a personal opinion, but having the canonical name rely on
“hostname --fqdn” is not a favorite of mine: hostname needs the resolver
to be working and functioning (e.g. it talks to your nameservers if
/etc/hosts doesn't contain your hostname/ip already).

IMHVO, this is a brittle setup and the FQDN should be available directly
on the host, without external dependencies. Which is why I personally
think the machine name (the one that the kernel knows) should hold the
canonical name.

Just my opinion, no need to flame - I know I lost this argument many
times already.

regards,
iustin


-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: where is /etc/hosts supposed to come from?

[Osamu Aoki]

Hi,

> On Wed, Dec 30, 2009 at 03:18:51PM -0200, Henrique de Moraes Holschuh wrote:
> > I prefer to allocate such host names in a real domain, and give them just 
> > TXT
> > records or 127.0.1.1 A records in some weird cases where I can't trust the
> > box to not do idiotic things like go to the DNS bypassing the libc resolver.

Yes.  This is certainly good thing to do.  But how many people outside
of DD world have a real domain controlled by them which is usable for
this purpose.
 
On Thu, Dec 31, 2009 at 11:11:00AM +1100, Brian May wrote:
> I wouldn't use ".local" as that seems to be treated as a special case by
> zeroconf enabled computers, and various OS seem to have zeroconf enabled by
> default (like it or not).

I do this now expecting no name crash since I do not think I connect to
any host with the same host name and such domain name in my lan.  (If
you are in zeroconf enabled lan and someone on the lan has the same host
name, isn't it a problem by itself?)

I know, according to rfc2606, "invalid" seems to be a choice for
the top level domain (TLD) to construct domain names that are sure to be
invalid from the Internet.  But result is the same as choosing "local".
(This was a choice which I used to use.)

I summarized this at:
  
http://www.debian.org/doc/manuals/debian-reference/ch05.en.html#_the_domain_name
and the following section.  If there is a better guideline for normal
people to follow, please give me pinter.

Osamu


-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: where is /etc/hosts supposed to come from?

[Philipp Kern]

On 2009-12-31, Osamu Aoki  wrote:
> I know, according to rfc2606, "invalid" seems to be a choice for
> the top level domain (TLD) to construct domain names that are sure to be
> invalid from the Internet.  But result is the same as choosing "local".
> (This was a choice which I used to use.)

Using .local in own environments sadly clashes with the (I think now
installed by default) mDNS namespace for locally-resolvable hostnames.
But it somehow makes sense for a laptop; it would even resolve.  ;-)

Kind regards,
Philipp Kern



-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Thank you for everything and a happy new year!

[Hans-J. Ullrich]

Dear debian-team, developers and community, 

now as the year 2009 is over, I want to thank you for all the help, the joy 
you gave me with debian and the time you spent for a better it-world for us 
all.

To all of you I say: May you have great year 2010, stay always sane, may all 
your dreams and wishes come true and have such much joy and fun as you ever 
want!

Just to say in short: Thank you very much for everything and the very,very, 
very best to you and your families!

Best regards

Hans-J. Ullrich
   


-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: where is /etc/hosts supposed to come from?

[Russ Allbery]

Vincent Lefevre  writes:
> On 2009-12-30 11:54:57 -0800, Russ Allbery wrote:
>> Vincent Lefevre  writes:

>>> "stanford.edu" is definitely wrong. First it's just a domain name, not a
>>> FQDN (as required by the mailname(5) man page).

>> stanford.edu is an RFC 1035 FQDN.

> RFC 1035 (from /usr/share/doc/RFC/links/rfc1035.txt.gz) doesn't define
> what a FQDN is. It doesn't contain "FQDN", and the only occurrence of
> "fully" and "qualified" is in "Gateways will also have host level
> pointers at their fully qualified addresses.

However, the other standards that do talk about FQDNs refer to RFC 1035
for the definition.  See, for instance, RFC 5322.

> FYI, here's what Wikipedia[*] (though not authoritative and sometimes
> containing errors) says:

>   For example, given a device with a local hostname myhost and a
>   parent domain name example.com, the fully qualified domain name is
>   written as myhost.example.com. This fully qualified domain name
>   therefore uniquely identifies the host — while there may be many
>   resources in the world called myhost, there is only one
>   myhost.example.com.

You're right, that's not authoritative and, in this case, is misleading.
Nothing about an FDQN implies uniqueness.  Wikipedia is trying to get at
the distinction between an unqualified name, which could duplicate many
other unqualified names in other domains, and a fully-qualified name which
has a single location in the DNS hierarchy.  However, an FQDN, despite
living in one place in the DNS hierarchy, may refer to multiple separate
systems (as it does for stanford.edu, time.stanford.edu, etc., all of
which are FQDNs).

-- 
Russ Allbery (r...@debian.org)   


--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: where is /etc/hosts supposed to come from?

[Vincent Lefevre]

On 2009-12-31 16:35:58 +0100, Iustin Pop wrote:
> This is a personal opinion, but having the canonical name rely on
> “hostname --fqdn” is not a favorite of mine: hostname needs the resolver
> to be working and functioning (e.g. it talks to your nameservers if
> /etc/hosts doesn't contain your hostname/ip already).

Well, the practice, the FQDN is often available via /etc/hosts.

> IMHVO, this is a brittle setup and the FQDN should be available directly
> on the host, without external dependencies. Which is why I personally
> think the machine name (the one that the kernel knows) should hold the
> canonical name.

Either that, or having the FQDN in /etc/hosts. I don't see any problem
with that, excepts that iceweasel doesn't cope very well with this:

lrwxrwxrwx 1 vinc17 vinc17 15 2009-12-30 05:35:38 lock -> 127.0.1.1:+5537

I wonder why it doesn't use the FQDN. The IP addresse 127.0.1.1 is
incorrect when the directory is shared with other hosts.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / Arénaire project (LIP, ENS-Lyon)


-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: where is /etc/hosts supposed to come from?

[Vincent Lefevre]

On 2009-12-31 12:37:25 -0800, Russ Allbery wrote:
> Vincent Lefevre  writes:
> > On 2009-12-30 11:54:57 -0800, Russ Allbery wrote:
> >> Vincent Lefevre  writes:
> 
> >>> "stanford.edu" is definitely wrong. First it's just a domain name, not a
> >>> FQDN (as required by the mailname(5) man page).
> 
> >> stanford.edu is an RFC 1035 FQDN.
> 
> > RFC 1035 (from /usr/share/doc/RFC/links/rfc1035.txt.gz) doesn't define
> > what a FQDN is. It doesn't contain "FQDN", and the only occurrence of
> > "fully" and "qualified" is in "Gateways will also have host level
> > pointers at their fully qualified addresses.
> 
> However, the other standards that do talk about FQDNs refer to RFC 1035
> for the definition.  See, for instance, RFC 5322.

RFC 5322 doesn't mention "FQDN", "fully" or "qualified" either!
Perhaps you meant RFC 5321, which uses "FQDN" with a different
meaning, and uses "primary host name" for what is a FQDN here.
RFC 5321 also says "In the EHLO command, the host sending the
command identifies itself", implying that what you give after EHLO
must be unique (otherwise that's no longer an identification).

> > FYI, here's what Wikipedia[*] (though not authoritative and sometimes
> > containing errors) says:
> 
> >   For example, given a device with a local hostname myhost and a
> >   parent domain name example.com, the fully qualified domain name is
> >   written as myhost.example.com. This fully qualified domain name
> >   therefore uniquely identifies the host — while there may be many
> >   resources in the world called myhost, there is only one
> >   myhost.example.com.
> 
> You're right, that's not authoritative and, in this case, is misleading.
> Nothing about an FDQN implies uniqueness.  Wikipedia is trying to get at
> the distinction between an unqualified name, which could duplicate many
> other unqualified names in other domains, and a fully-qualified name which
> has a single location in the DNS hierarchy.  However, an FQDN, despite
> living in one place in the DNS hierarchy, may refer to multiple separate
> systems (as it does for stanford.edu, time.stanford.edu, etc., all of
> which are FQDNs).

No, they are not FQDNs of the corresponding hosts. For instance,
time.stanford.edu resolves to 3 IP addresses (3 hosts, I suppose):

time.stanford.edu has address 171.64.7.105
time.stanford.edu has address 171.64.7.67
time.stanford.edu has address 204.63.224.70

xvii% host 171.64.7.105
105.7.64.171.in-addr.arpa domain name pointer time-a.Stanford.EDU.
xvii% host 171.64.7.67
67.7.64.171.in-addr.arpa domain name pointer time-b.Stanford.EDU.
xvii% host 204.63.224.70
70.224.63.204.in-addr.arpa domain name pointer time-c.Stanford.EDU.

The respective FQDN's of these hosts seem to be time-a.Stanford.EDU,
time-b.Stanford.EDU and time-c.Stanford.EDU, and they are unique:
they all resolve to a *single* IP address.

xvii% host time-a.Stanford.EDU
time-a.Stanford.EDU has address 171.64.7.105
xvii% host time-b.Stanford.EDU
time-b.Stanford.EDU has address 171.64.7.67
xvii% host time-c.Stanford.EDU
time-c.Stanford.EDU has address 204.63.224.70

Note: this is a heuristic only; the only way to be sure that they
are the FQDN's of the host (as returned by "hostname -f") is to
test on the machines themselves.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / Arénaire project (LIP, ENS-Lyon)


-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: where is /etc/hosts supposed to come from?

[Russ Allbery]

Vincent Lefevre  writes:

> RFC 5322 doesn't mention "FQDN", "fully" or "qualified" either!  Perhaps
> you meant RFC 5321, which uses "FQDN" with a different meaning, and uses
> "primary host name" for what is a FQDN here.

Sorry, yes, that's the one I meant.  The mail format standard defines for
itself what, in essence, an FQDN is, but it doesn't use that terminology
and it does so only in the context of e-mail addresses.

> RFC 5321 also says "In the EHLO command, the host sending the command
> identifies itself", implying that what you give after EHLO must be
> unique (otherwise that's no longer an identification).

Uh, no.  That statement implies nothing of the sort; identification is not
necessarily unique.

> On 2009-12-31 12:37:25 -0800, Russ Allbery wrote:

>> You're right, that's not authoritative and, in this case, is
>> misleading.  Nothing about an FDQN implies uniqueness.  Wikipedia is
>> trying to get at the distinction between an unqualified name, which
>> could duplicate many other unqualified names in other domains, and a
>> fully-qualified name which has a single location in the DNS hierarchy.
>> However, an FQDN, despite living in one place in the DNS hierarchy, may
>> refer to multiple separate systems (as it does for stanford.edu,
>> time.stanford.edu, etc., all of which are FQDNs).

> No, they are not FQDNs of the corresponding hosts. For instance,
> time.stanford.edu resolves to 3 IP addresses (3 hosts, I suppose):

I've been participating in standardization of network protocols through
the IETF for more than a decade now, and I've never seen someone use this
definition of FQDN that you're using.  I'm quite confident that this is
not the intented interpretation of the standards to which you're
referring, in large part because I was participating in the mailing lists
on which they were written.

I'm going to bow out at this point, since I don't think either of us
are going to convince each other and so far as I can tell, no concrete
change is being proposed, so this is all sort of pointless.  If someone
proposes a concrete change, that's the point at which this all becomes
relevant to debate.

-- 
Russ Allbery (r...@debian.org)   


-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#563207: ITP: libmoosex-storage-perl -- serialization framework for Moose classes

[Jonathan Yu]

Package: wnpp
Owner: Jonathan Yu 
Severity: wishlist
X-Debbugs-CC: debian-devel@lists.debian.org,debian-p...@lists.debian.org

* Package name: libmoosex-storage-perl
  Version : 0.23
  Upstream Author : Chris Prather 
* URL : http://search.cpan.org/dist/MooseX-Storage/
* License : Artistic or GPL-1+
  Programming Lang: Perl
  Description : serialization framework for Moose classes

MooseX::Storage is a serialization framework for Moose classes. It provides a
flexible and highly pluggable way to serialize Moose classes to a number of
different formats and styles.



-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: where is /etc/hosts supposed to come from?

[Brian May]

On Thu, Dec 31, 2009 at 04:33:44PM +, Philipp Kern wrote:
> On 2009-12-31, Osamu Aoki  wrote:
> > I know, according to rfc2606, "invalid" seems to be a choice for
> > the top level domain (TLD) to construct domain names that are sure to be
> > invalid from the Internet.  But result is the same as choosing "local".
> > (This was a choice which I used to use.)
> 
> Using .local in own environments sadly clashes with the (I think now
> installed by default) mDNS namespace for locally-resolvable hostnames.
> But it somehow makes sense for a laptop; it would even resolve.  ;-)

Yes, that is what I was getting at too. It is also a problem for Mac OS X
boxes, at least without fiddling.

This can be a problem even if you don't intend to use zeroconf/mdns on your
network. Typically what happens is DNS queries time out without resolving
and packet traces show that there are no requests happening.

I don't know of any good choice for a TLD that is guaranteed not to be used on
the Internet, although currently I am using .pri (short for .private) here.

Even .local is only mentioned in a experimental RFC that had expired (at least
last I checked which was a while ago now).

In case any is confused of the relationship between mdns and zeroconf:

Package: libnss-mdns
Priority: optional
Section: admin
Installed-Size: 152
Maintainer: Ubuntu Core developers 
Original-Maintainer: Utopia Maintenance Team 

Architecture: amd64
Source: nss-mdns
Version: 0.10-3ubuntu3
Depends: libc6 (>= 2.4), base-files (>= 3.1.10), perl, avahi-daemon (>= 
0.6.16-1)
Suggests: avahi-autoipd | zeroconf
Filename: pool/main/n/nss-mdns/libnss-mdns_0.10-3ubuntu3_amd64.deb
Size: 25830
MD5sum: 622ed99ad2e7bc6b7f7ad95eb51e12fe
SHA1: a3bc1ead6d63e48d60f6c529778dfc9d9df00637
SHA256: 3206f5a6ceecc3838781b758a50443df7b54146677d94d790658cc9de1a60c56
Description: NSS module for Multicast DNS name resolution
 nss-mdns is a plugin for the GNU Name Service Switch (NSS) functionality
 of the GNU C Library (glibc) providing host name resolution via Multicast
 DNS (using Zeroconf, aka Apple Bonjour / Apple Rendezvous ), effectively
 allowing name resolution by common Unix/Linux programs in the ad-hoc mDNS
 domain .local.
Bugs: https://bugs.launchpad.net/ubuntu/+filebug
Origin: Ubuntu
Task: ubuntu-desktop, eucalyptus-node, eucalyptus-simple-cluster, print-server, 
kubuntu-desktop, kubuntu-netbook, edubuntu-desktop, xubuntu-desktop, 
mobile-mid, ubuntu-netbook-remix

-- 
Brian May 


-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#563208: ITP: libtest-json-perl -- Test JSON data

[Jonathan Yu]

Package: wnpp
Owner: Jonathan Yu 
Severity: wishlist
X-Debbugs-CC: debian-devel@lists.debian.org,debian-p...@lists.debian.org

* Package name: libtest-json-perl
  Version : 0.11
  Upstream Author : Curtis "Ovid" Poe 
* URL : http://search.cpan.org/dist/Test-JSON/
* License : Artistic or GPL-1+
  Programming Lang: Perl
  Description : Test JSON data

JavaScript Object Notation (JSON) is a lightweight data interchange format.
Test::JSON makes it easy to verify that you have built valid JSON and that it
matches your expected output.

See http://www.json.org/ for more information.



-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Work-needing packages report for Jan 1, 2010

[wnpp]

The following is a listing of packages for which help has been requested
through the WNPP (Work-Needing and Prospective Packages) system in the
last week.

Total number of orphaned packages: 646 (new: 1)
Total number of packages offered up for adoption: 131 (new: 2)
Total number of packages requested help for: 54 (new: 0)

Please refer to http://www.debian.org/devel/wnpp/ for more information.



The following packages have been orphaned:

   crossvc (#562509), orphaned 6 days ago (non-free)
 Description: graphical CVS frontend
 Installations reported by Popcon: 120

645 older packages have been omitted from this listing, see
http://www.debian.org/devel/wnpp/orphaned for a complete list.



The following packages have been given up for adoption:

   crossvc (#562509), offered 6 days ago (non-free)
 Description: graphical CVS frontend
 Installations reported by Popcon: 120

   dpatch (#562697), offered 4 days ago
 Description: Debian patch management system
 Reverse Depends: acx100-source drbd0.7-module-source drbd8-source
   kqemu-source lustre-source nvidia-kernel-legacy-173xx-source
   nvidia-kernel-legacy-71xx-source nvidia-kernel-legacy-96xx-source
   nvidia-kernel-source r-base-dev
 Installations reported by Popcon: 13411

129 older packages have been omitted from this listing, see
http://www.debian.org/devel/wnpp/rfa_bypackage for a complete list.



For the following packages help is requested:

   apt-cross (#540341), requested 146 days ago
 Description: retrieve, build and install libraries for
   cross-compiling
 Reverse Depends: apt-cross emdebian-buildsupport emdebian-qa
   emdebian-rootfs emdebian-tools libemdebian-tools-perl
 Installations reported by Popcon: 318

   ara (#450876), requested 781 days ago
 Description: utility for searching the Debian package database
 Installations reported by Popcon: 118

   asymptote (#517342), requested 307 days ago
 Description: script-based vector graphics language inspired by
   MetaPost
 Installations reported by Popcon: 1147

   athcool (#278442), requested 1892 days ago
 Description: Enable powersaving mode for Athlon/Duron processors
 Installations reported by Popcon: 167

   boinc (#511243), requested 357 days ago
 Description: BOINC distributed computing
 Reverse Depends: boinc-app-milkyway boinc-app-seti boinc-dbg
 Installations reported by Popcon: 1662

   cvs (#354176), requested 1407 days ago
 Description: Concurrent Versions System
 Reverse Depends: crossvc cvs-autoreleasedeb cvs-buildpackage cvs2cl
   cvs2html cvschangelogbuilder cvsconnect cvsd cvsps cvsservice (10
   more omitted)
 Installations reported by Popcon: 24941

   dctrl-tools (#448284), requested 796 days ago
 Description: Command-line tools to process Debian package
   information
 Reverse Depends: aptfs debian-goodies debtree dlocate
   haskell-devscripts libsbuild-perl linux-patch-debianlogo mlmmj
   simple-cdd ubuntu-dev-tools
 Installations reported by Popcon: 13303

   dietlibc (#544060), requested 125 days ago
 Description: diet libc - a libc optimized for small size
 Reverse Depends: libowfat-dev
 Installations reported by Popcon: 237

   dpkg (#282283), requested 1866 days ago
 Description: dselect: a user tool to manage Debian packages
 Reverse Depends: acct adacontrol advi advi-examples alien alqalam
   alsa-source am-utils-doc apt-build apt-cross (454 more omitted)
 Installations reported by Popcon: 88516

   elvis (#432298), requested 906 days ago
 Description: powerful clone of the vi/ex text editor (with X11
   support)
 Reverse Depends: elvis elvis-console elvis-tools
 Installations reported by Popcon: 413

   emdebian-tools (#540333), requested 146 days ago
 Description: emdebian crossbuilding tool set
 Reverse Depends: emdebian-buildsupport emdebian-qa emdebian-rootfs
   emdebian-tools
 Installations reported by Popcon: 174

   flightgear (#487388), requested 558 days ago
 Description: Flight Gear Flight Simulator
 Installations reported by Popcon: 668

   fluxbox (#552328), requested 67 days ago
 Description: Highly configurable and low resource X11 Window manager
 Reverse Depends: bbmail
 Installations reported by Popcon: 3057

   gentoo (#422498), requested 970 days ago
 Description: a fully GUI-configurable, two-pane X file manager
 Installations reported by Popcon: 217

   gnat-4.4 (#539562), requested 630 days ago
 Description: help needed to execute test cases
 Reverse Depends: adabrowse adacontrol asis-programs gnat gnat-4.4
   libasis2008 libasis2008-dev libaunit1-dev libaunit3 libaws-bin (38
   m

Bug#563213: ITP: libcolor-library-perl -- comprehensive named-colour library

[Jonathan Yu]

Package: wnpp
Owner: Jonathan Yu 
Severity: wishlist
X-Debbugs-CC: debian-devel@lists.debian.org,debian-p...@lists.debian.org

* Package name: libcolor-library-perl
  Version : 0.02
  Upstream Author : Robert Krimen 
* URL : http://search.cpan.org/dist/Color-Library/
* License : Artistic or GPL-1+
  Programming Lang: Perl
  Description : comprehensive named-colour library

Color::Library is a Perl module that provides a library of web (SVG, HTML
and CSS) colours, X11 colours, Windows system palette colours, and more. It
provides a simple way to specify colour names and retrieve the corresponding
RGB definition in return.

NOTE: this is needed for Chart::Clicker indirectly (there's a rather
large dependency chain there)



-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#563216: ITP: libmoosex-aliases-perl -- Moose extension for easy aliasing of methods and attributes

[Jonathan Yu]

Package: wnpp
Owner: Jonathan Yu 
Severity: wishlist
X-Debbugs-CC: debian-devel@lists.debian.org,debian-p...@lists.debian.org

* Package name: libmoosex-aliases-perl
  Version : 0.07
  Upstream Author : Jesse Luehrs , Chris Prather
,
Justin Hunter 
* URL : http://search.cpan.org/dist/MooseX-Aliases/
* License : Artistic or GPL-1+
  Programming Lang: Perl
  Description : Moose extension for easy aliasing of methods and attributes

MooseX::Aliases is an extension to Moose that facilitates simple aliasing of
methods and attributes. It provides an alias parameter for has() to generate
aliased accessors as well as the standard ones. Further, attributes can also
be initialized in the constructor via their aliased names.

Note: needed for Chart::Clicker



-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#563217: ITP: jxplorer -- A Java Ldap Browser

[Gabriele Giacone]

Package: wnpp
Severity: wishlist
Owner: Gabriele Giacone <1o5g4...@gmail.com>

* Package name: jxplorer
  Version : 3.2rc2
  Upstream Author : Chris Betts 
* URL : http://sourceforge.net/projects/jxplorer/
* License : Computer Associates Open Source Software License V.1.0
  Programming Lang: Java
  Description : A Java Ldap Browser

 JXplorer is an open source ldap browser originally developed by
 Computer Associates' eTrust Directory development lab. It is a
 standards compliant general purpose ldap browser that can be used
 to read and search any ldap directory, or any X500 directory with
 an ldap interface. 
 JXplorer is a fully functional piece of software with advanced
 security integration and support for the more difficult and
 obscure parts of the ldap protocol. It should run on any java
 supporting operating system. It's features include:
 .
  * Standard ldap operations: add/delete/copy/modify
  * Complex operations: tree copy and tree delete
  * Optional GUI based search filter construction
  * SSL and SASL authentication
  * pluggable editors/viewers
  * pluggable security providers
  * HTML templates/forms for data display
  * Full i18n support
  * LDIF file format support
  * highly user configurable
  * drag-n-drop browsing operation
  * DSML Support
  * handles complex ldap cases:
o multi valued rdns
o binary attributes
o Certificates and Passwords
o Unicode characters
o Special characters / UTF8 in distinguished names. 
  * Extensible architecture with object class based Java plugins
  * And much, much more...


Some doubts about "Computer Associates Open Source Software License"
avilable at http://jxplorer.org/licence.html



-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#563219: ITP: libforest-perl -- collection of N-ary tree related modules

[Jonathan Yu]

Package: wnpp
Owner: Jonathan Yu 
Severity: wishlist
X-Debbugs-CC: debian-devel@lists.debian.org,debian-p...@lists.debian.org

* Package name: libforest-perl
  Version : 0.07
  Upstream Author : Stevan Little 
* URL : http://search.cpan.org/dist/Forest/
* License : Artistic or GPL-1+
  Programming Lang: Perl
  Description : collection of N-ary tree related modules

Forest is a collection of Perl modules implementing a generalized N-ary tree
data structure. It also includes several modules useful for manipulating this
data, including loading data from file, indexing it in memory, and writing it
back out to files (in various formats).

NOTE: needed for Chart::Clicker



-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org