- WLUG - wlug.mailman3.com

Re: [Wlug] ls character range wildcard oddity?

by Theodore Ruegsegger

It looks like a locale issue. In the old "C" locale, sorting a list put all cap letters before all lowercase letters. In the "en_US.UTF-8" locale, apparently the Ubuntu default, they're sorted as in a regular dictionary, regardless of caps. For example: ls apple berry Berry charlie Hope that's more helpful than my first response! Ted On Fri, Jun 19, 2015 at 9:46 AM, Theodore Ruegsegger <gruntly(a)gmail.com> wrote: > Disregard last transmission. I shoulda read your post more carefully. > > Ted > > On Fri, Jun 19, 2015 at 9:44 AM, Theodore Ruegsegger <gruntly(a)gmail.com> wrote: >> b != B >> >> HTH, >> Ted >> >> On Fri, Jun 19, 2015 at 9:29 AM, Brett Russ <bruss(a)alum.wpi.edu> wrote: >>> Can someone explain this to my evidently inadequately caffeinated brain? I >>> was trying to use a lower case character range wildcard to list all files >>> not starting with an uppercase letter and I noticed it wasn't working as I'd >>> expect. So I created this simple example and still don't understand what's >>> happening. >>> >>> Dir with two files: >>> >>> brett@spider /tmp/test $ \ls >>> apple Berry >>> >>> This is what I'd expect to see: >>> >>> brett@spider /tmp/test $ \ls [a-b]* >>> apple >>> >>> This makes no sense. Is this a bug?: >>> >>> brett@spider /tmp/test $ \ls [a-c]* >>> apple Berry >>> >>> From here on are just a few extra examples confirming the oddity of the >>> above. >>> >>> brett@spider /tmp/test $ \ls [a]* >>> apple >>> >>> brett@spider /tmp/test $ \ls [b]* >>> ls: cannot access [b]*: No such file or directory >>> >>> brett@spider /tmp/test $ \ls [c]* >>> ls: cannot access [c]*: No such file or directory >>> >>> brett@spider /tmp/test $ \ls a* >>> apple >>> >>> brett@spider /tmp/test $ \ls b* >>> ls: cannot access b*: No such file or directory >>> >>> brett@spider /tmp/test $ \ls c* >>> ls: cannot access c*: No such file or directory >>> >>> brett@spider /tmp/test $ dpkg -S `which ls` >>> coreutils: /bin/ls >>> >>> brett@spider /tmp/test $ dpkg -s coreutils >>> Package: coreutils >>> Essential: yes >>> Status: install ok installed >>> Priority: required >>> Section: utils >>> Installed-Size: 6020 >>> Maintainer: Ubuntu Developers <ubuntu-devel-discuss(a)lists.ubuntu.com> >>> Architecture: amd64 >>> Multi-Arch: foreign >>> Version: 8.21-1ubuntu5.1 >>> [SNIP] >>> >>> >>> Thanks, >>> Brett >>> >>> _______________________________________________ >>> Wlug mailing list >>> Wlug(a)mail.wlug.org >>> http://mail.wlug.org/mailman/listinfo/wlug >>>

June 19, 2015

Re: [Wlug] ls character range wildcard oddity?

by Theodore Ruegsegger

Disregard last transmission. I shoulda read your post more carefully. Ted On Fri, Jun 19, 2015 at 9:44 AM, Theodore Ruegsegger <gruntly(a)gmail.com> wrote: > b != B > > HTH, > Ted > > On Fri, Jun 19, 2015 at 9:29 AM, Brett Russ <bruss(a)alum.wpi.edu> wrote: >> Can someone explain this to my evidently inadequately caffeinated brain? I >> was trying to use a lower case character range wildcard to list all files >> not starting with an uppercase letter and I noticed it wasn't working as I'd >> expect. So I created this simple example and still don't understand what's >> happening. >> >> Dir with two files: >> >> brett@spider /tmp/test $ \ls >> apple Berry >> >> This is what I'd expect to see: >> >> brett@spider /tmp/test $ \ls [a-b]* >> apple >> >> This makes no sense. Is this a bug?: >> >> brett@spider /tmp/test $ \ls [a-c]* >> apple Berry >> >> From here on are just a few extra examples confirming the oddity of the >> above. >> >> brett@spider /tmp/test $ \ls [a]* >> apple >> >> brett@spider /tmp/test $ \ls [b]* >> ls: cannot access [b]*: No such file or directory >> >> brett@spider /tmp/test $ \ls [c]* >> ls: cannot access [c]*: No such file or directory >> >> brett@spider /tmp/test $ \ls a* >> apple >> >> brett@spider /tmp/test $ \ls b* >> ls: cannot access b*: No such file or directory >> >> brett@spider /tmp/test $ \ls c* >> ls: cannot access c*: No such file or directory >> >> brett@spider /tmp/test $ dpkg -S `which ls` >> coreutils: /bin/ls >> >> brett@spider /tmp/test $ dpkg -s coreutils >> Package: coreutils >> Essential: yes >> Status: install ok installed >> Priority: required >> Section: utils >> Installed-Size: 6020 >> Maintainer: Ubuntu Developers <ubuntu-devel-discuss(a)lists.ubuntu.com> >> Architecture: amd64 >> Multi-Arch: foreign >> Version: 8.21-1ubuntu5.1 >> [SNIP] >> >> >> Thanks, >> Brett >> >> _______________________________________________ >> Wlug mailing list >> Wlug(a)mail.wlug.org >> http://mail.wlug.org/mailman/listinfo/wlug >>

June 19, 2015

Re: [Wlug] ls character range wildcard oddity?

by Theodore Ruegsegger

b != B HTH, Ted On Fri, Jun 19, 2015 at 9:29 AM, Brett Russ <bruss(a)alum.wpi.edu> wrote: > Can someone explain this to my evidently inadequately caffeinated brain? I > was trying to use a lower case character range wildcard to list all files > not starting with an uppercase letter and I noticed it wasn't working as I'd > expect. So I created this simple example and still don't understand what's > happening. > > Dir with two files: > > brett@spider /tmp/test $ \ls > apple Berry > > This is what I'd expect to see: > > brett@spider /tmp/test $ \ls [a-b]* > apple > > This makes no sense. Is this a bug?: > > brett@spider /tmp/test $ \ls [a-c]* > apple Berry > > From here on are just a few extra examples confirming the oddity of the > above. > > brett@spider /tmp/test $ \ls [a]* > apple > > brett@spider /tmp/test $ \ls [b]* > ls: cannot access [b]*: No such file or directory > > brett@spider /tmp/test $ \ls [c]* > ls: cannot access [c]*: No such file or directory > > brett@spider /tmp/test $ \ls a* > apple > > brett@spider /tmp/test $ \ls b* > ls: cannot access b*: No such file or directory > > brett@spider /tmp/test $ \ls c* > ls: cannot access c*: No such file or directory > > brett@spider /tmp/test $ dpkg -S `which ls` > coreutils: /bin/ls > > brett@spider /tmp/test $ dpkg -s coreutils > Package: coreutils > Essential: yes > Status: install ok installed > Priority: required > Section: utils > Installed-Size: 6020 > Maintainer: Ubuntu Developers <ubuntu-devel-discuss(a)lists.ubuntu.com> > Architecture: amd64 > Multi-Arch: foreign > Version: 8.21-1ubuntu5.1 > [SNIP] > > > Thanks, > Brett > > _______________________________________________ > Wlug mailing list > Wlug(a)mail.wlug.org > http://mail.wlug.org/mailman/listinfo/wlug >

June 19, 2015

ls character range wildcard oddity?

by Brett Russ

Can someone explain this to my evidently inadequately caffeinated brain? I was trying to use a lower case character range wildcard to list all files not starting with an uppercase letter and I noticed it wasn't working as I'd expect. So I created this simple example and still don't understand what's happening. Dir with two files: brett@spider /tmp/test $ \ls apple Berry This is what I'd expect to see: brett@spider /tmp/test $ \ls [a-b]* apple This makes no sense. Is this a bug?: *brett@spider /tmp/test $ \ls [a-c]*apple Berry* >From here on are just a few extra examples confirming the oddity of the above. brett@spider /tmp/test $ \ls [a]* apple brett@spider /tmp/test $ \ls [b]* ls: cannot access [b]*: No such file or directory brett@spider /tmp/test $ \ls [c]* ls: cannot access [c]*: No such file or directory brett@spider /tmp/test $ \ls a* apple brett@spider /tmp/test $ \ls b* ls: cannot access b*: No such file or directory brett@spider /tmp/test $ \ls c* ls: cannot access c*: No such file or directory brett@spider /tmp/test $ dpkg -S `which ls` coreutils: /bin/ls brett@spider /tmp/test $ dpkg -s coreutils Package: coreutils Essential: yes Status: install ok installed Priority: required Section: utils Installed-Size: 6020 Maintainer: Ubuntu Developers <ubuntu-devel-discuss(a)lists.ubuntu.com> Architecture: amd64 Multi-Arch: foreign Version: 8.21-1ubuntu5.1 [SNIP] Thanks, Brett

June 19, 2015

Re: [Wlug] WLUG Meeting tomorrow! Jun 11th, 2015! Native ZFS on linux!

by E Johnson

Shouldn't the tagline say Please excuse my levity? But roflol, you guys. Liz J On 11 June 2015 at 17:06, Frank Sweetser <fs(a)wpi.edu> wrote: > And I was hoping to see a file system that only stored data formatted in > iambic pentameter... > ---- > Sent from my Android device with K-9 Mail. Please excuse my brevity. > > > > > See you in the future, if you're going that way. > > > > -- Keith >

June 11, 2015

Re: [Wlug] WLUG Meeting tomorrow! Jun 11th, 2015! Native ZFS on linux!

by Frank Sweetser

And I was hoping to see a file system that only stored data formatted in iambic pentameter... ---- Sent from my Android device with K-9 Mail. Please excuse my brevity. On June 11, 2015 2:42:02 PM EDT, Keith Wright <kwright(a)keithdiane.us> wrote: >Tim Keller <turbofx(a)gmail.com> writes: >> >> Sick of your limited file systems? Worried it won't scale when >pentabyte >> disks hit the market? > >There have been five byte storage devices since 1945. >Expensive, but available. They were called mercury >delay lines. > >On the other hand a petabyte (+1e+15 bytes) would be a lot. > >> I'll be doing a talk/demo of the ZFS (Zettabyte File >> System) naively running on Linux. > >This time I really am puzzled. >Do you mean "natively"? That would be a cliche. >What you said passes spell check would be good for >us simple French folk. > >> This is going to be held in the campus center Rm. 129 a.k.a >"Chairman's >> Room" at 7pm. > >The web page still says TBD. No matter, I intend to be there, >but if I were lost with only an Apple Eye BrowServer for guidance... > >> Refreshments will be provided. > >Good. I am less cranky when my mouth is full. > >See you in the future, if you're going that way. > > -- Keith >_______________________________________________ >Wlug mailing list >Wlug(a)mail.wlug.org >http://mail.wlug.org/mailman/listinfo/wlug

June 11, 2015

Re: [Wlug] WLUG Meeting tomorrow! Jun 11th, 2015! Native ZFS on linux!

by Keith Wright

Tim Keller <turbofx(a)gmail.com> writes: > > Sick of your limited file systems? Worried it won't scale when pentabyte > disks hit the market? There have been five byte storage devices since 1945. Expensive, but available. They were called mercury delay lines. On the other hand a petabyte (+1e+15 bytes) would be a lot. > I'll be doing a talk/demo of the ZFS (Zettabyte File > System) naively running on Linux. This time I really am puzzled. Do you mean "natively"? That would be a cliche. What you said passes spell check would be good for us simple French folk. > This is going to be held in the campus center Rm. 129 a.k.a "Chairman's > Room" at 7pm. The web page still says TBD. No matter, I intend to be there, but if I were lost with only an Apple Eye BrowServer for guidance... > Refreshments will be provided. Good. I am less cranky when my mouth is full. See you in the future, if you're going that way. -- Keith

June 11, 2015

WLUG Meeting tomorrow! Jun 11th, 2015! Native ZFS on linux!

by Tim Keller

Hey Everybody, Sick of your limited file systems? Worried it won't scale when pentabyte disks hit the market? Good news, I've got a file system for you! I'll be doing a talk/demo of the ZFS (Zettabyte File System) naively running on Linux. This is going to be held in the campus center Rm. 129 a.k.a "Chairman's Room" at 7pm. Refreshments will be provided. Thanks, Tim. -- I am leery of the allegiances of any politician who refers to their constituents as "consumers".

June 10, 2015

Re: [Wlug] WLUG meeting this week

by Tim Keller

Definitely! I'll make sure that Chuck gets the slides, etc. On Wed, Jun 10, 2015 at 11:10 AM, Joel <joelgroup(a)gmail.com> wrote: > > I am bummed out that home / requirements / life will keep me away from the > WLUG meeting this week. > > Very interested in learning about ZFS details, tips and configuration for > the home NAS I am currently building. > > Any chance post meeting you could share your ZFS slides and info either on > WLUG site or via email? > > Thank you, > > Joel > > > _______________________________________________ > Wlug mailing list > Wlug(a)mail.wlug.org > http://mail.wlug.org/mailman/listinfo/wlug > -- I am leery of the allegiances of any politician who refers to their constituents as "consumers".

June 10, 2015

WLUG meeting this week

by Joel

I am bummed out that home / requirements / life will keep me away from the WLUG meeting this week. Very interested in learning about ZFS details, tips and configuration for the home NAS I am currently building. Any chance post meeting you could share your ZFS slides and info either on WLUG site or via email? Thank you, Joel

June 10, 2015