Re: high characters in file names change in new potato vs. current slink

2000-08-11 Thread Nate Bargmann
On Fri, Aug 11, 2000 at 11:51:53AM -0400, Michael Stone wrote: > > Actually, that's not the best choice. You should be able to see the > characters if you have a locale set. (E.g., LANG=en_US or LANG=de_DE) Say, it pays to lurk around here! I've been driven nuts by Mutt not showing special chara

Re: high characters in file names change in new potato vs. current slink

2000-08-11 Thread Michael Stone
On Fri, Aug 11, 2000 at 01:04:06PM +1000, Herbert Xu wrote: > Daniel Barclay <[EMAIL PROTECTED]> wrote: > > Can someone tell me what I need to do to fix the following problem? > > ls --show-control-chars Actually, that's not the best choice. You should be able to see the characters if you have a

Re: high characters in file names change in new potato vs. current slink

2000-08-10 Thread Herbert Xu
Daniel Barclay <[EMAIL PROTECTED]> wrote: > Can someone tell me what I need to do to fix the following problem? ls --show-control-chars -- Debian GNU/Linux 2.1 is out! ( http://www.debian.org/ ) Email: Herbert Xu ~{PmV>HI~} <[EMAIL PROTECTED]> Home Page: http://gondor.apana.org.au/~herbert/ PGP

high characters in file names change in new potato vs. current slink

2000-08-10 Thread Daniel Barclay
Can someone tell me what I need to do to fix the following problem? I have a file in a Windows partition (VFAT) whose name includes a high (beyond-ASCII) character. That character shows up differently in my new potato system than it does in my slink system. In slink, the file name appears as "

Re: current slink

1999-01-19 Thread Bob Nielsen
I realize this is not conclusive, but I recently upgraded one of my systems to slink with the latest libc6 2.0.7.19981211 without incident (and subsequently to potato with only a minor problem (a missing dependency in netbase) which was easily resolved.) Bob On Tue, 19 Jan 1999, Noah L. Meyerhans

current slink

1999-01-19 Thread Noah L. Meyerhans
-BEGIN PGP SIGNED MESSAGE- I am thinking about upgrading my system (at least libc, apt, and things like that) to slink from hamm. But I don't want to do it if slink is known to be broken at this point. Was the glibc version problem of last week ever fixed? Does the currently available l