bug in hostname

2003-10-07 Thread Martin MOKREJŠ
Hi, hostname(1) does not accept -s option to print short hostname, ie. not foo.bar.baz but only foo. It is required on Tru64Unix 5.1A during system startup. When hostname from coreutils is found, the system hostname is set improperly(to "-s"). Please provide full compatibility: hostname(1)

Re: bug in hostname

2003-10-07 Thread Bob Proulx
Martin MOKREJ? wrote: > Hi, > hostname(1) does not accept -s option to print short hostname, > ie. not foo.bar.baz but only foo. It is required on Tru64Unix 5.1A > during system startup. When hostname from coreutils is found, > the system hostname is set improperly(to "-s"). Many software distr

Re: bug in hostname

2003-10-07 Thread Martin MOKREJŠ
On Tue, 7 Oct 2003, Steven Augart wrote: I have the same suggestion: remove hostname from coreutils. Who needs such a crap? ;) I already deleted that fom our installation. I want to keep rest of coreutils. BTW: What is the problem with kill? Another binary to be deleted? > I could not agree more

Re: bug in hostname

2003-10-07 Thread Steven Augart
I could not agree more.    I am not terribly pleased that there is now a simple-minded "hostname" command in "coreutils"; after I installed 5.0.92 (cvs head) in my Linux machine's /usr/local/bin, suddenly the machine renamed itself to "--fqdn".  Why?  Because at least one program that "root"

Re: bug in hostname

2003-10-07 Thread Jim Meyering
Steven Augart <[EMAIL PROTECTED]> wrote: > I could not agree more.I am not terribly pleased that there is now a `now'? It's been in the sh-utils/coreutils for over 8 years. I agree in principle that these days coreutils `hostname' program is often not useful. But bear in mind that the vast

Re: bug in hostname

2003-10-07 Thread Steven Augart
I took your approach too.  Luckily, I did not install the GNU versions on top of the ones that shipped from my Linux distributor, so I didn't wipe out the existing /bin/hostname.  So it was easy to run "rm /usr/local/bin/hostname". The problem with "kill" probably won't affect you and your

Re: bug in hostname

2003-10-07 Thread Paul Jarc
Jim Meyering <[EMAIL PROTECTED]> wrote: > But bear in mind that the vast majority of users don't have a > problem because they use these tools via a distribution mechanism > (.rpm, .deb) that arranges not to install programs like hostname > that can cause trouble. Still, it would be nice to make l

Re: bug in hostname

2003-10-07 Thread Steven Augart
Jim Meyering <[EMAIL PROTECTED]> 10/07/2003 01:56 PM To: Steven Augart/Watson/Contr/[EMAIL PROTECTED] cc: Martin MOKREJŠ <[EMAIL PROTECTED]>, [EMAIL PROTECTED] Subject:Re: bug in hostname Steven Augart <[EMAIL PROTECTED]> wrote: > I could not agree more.

Re: bug in hostname

2003-10-07 Thread Jim Meyering
Steven Augart <[EMAIL PROTECTED]> wrote: > Paul Jarc's point that the GNU/Hurd system will need a hostname program is > well put. Perhaps we could provide a simple way for more casual users not > to install the hostname program. But really, if we add simple support for > --fqdn and --short (as we

Re: bug in hostname

2003-10-07 Thread Martin MOKREJŠ
On Tue, 7 Oct 2003, Paul Jarc wrote: > Jim Meyering <[EMAIL PROTECTED]> wrote: > > But bear in mind that the vast majority of users don't have a > > problem because they use these tools via a distribution mechanism > > (.rpm, .deb) that arranges not to install programs like hostname > > that can c

md5sum: Output format error on files with backslash in their names

2003-10-07 Thread W. L.
Dear Team, using md5sum on files with a backslash in their filenames gives an error in the output file format: A waste backslash is output at the beginning of the line. Also the backslashes themselves are quoted: Bug or feature? Please check following example: > md5sum ../div/Üble\ Filenamen/*

Re: bug in hostname

2003-10-07 Thread Steven Augart
I looked through the Open Group documents that the letters you sent me pointed to. I'm not clear on whether it's required to reject unknown arguments starting with a - but not after a --. That would significantly influence my implementation -- I would prefer to have hostname work like this: