Re: Section: The Bash Shell Startup Files - PATH=/your/head/asplode

2007-03-16 Thread Dan Nicholson
On 3/16/07, Dan Nicholson <[EMAIL PROTECTED]> wrote: > On 3/16/07, Jonathan Oksman <[EMAIL PROTECTED]> wrote: > > > The same semantics caused a simular bug with umask. My user > > (jonathan, group jonathan) got the default umask of 002 because of his > > uid being equal to gid. After compiling gp

Re: Section: The Bash Shell Startup Files - PATH=/your/head/asplode

2007-03-16 Thread Dan Nicholson
On 3/16/07, Jonathan Oksman <[EMAIL PROTECTED]> wrote: > > When I'm installing packages, I tend to use su constantly so that I > can switch in and out of root access to the filesystem. I'm sure lots > of you do this. Others among you, notably the jhalfs developers, > might make more use of sudo.

Re: Dash.

2007-03-16 Thread Dan Nicholson
On 3/16/07, Dan Nicholson <[EMAIL PROTECTED]> wrote: > On 3/16/07, Randy McMurchy <[EMAIL PROTECTED]> wrote: > > Dan Nicholson wrote these words on 03/16/07 09:27 CST: > > > > > It just needs some LFS boilerplate at the top. That's everything > > > upstream + LC_ALL=C in the mkbuiltins script that

Re: dhcp-3.0.2 dhclient-script fails to update resolv.conf with null domain-name

2007-03-16 Thread Dan Nicholson
On 3/16/07, Jonathan Oksman <[EMAIL PROTECTED]> wrote: > > I just did a quick reference between BLFS 6.1 and 6.2, and I gather > that would be the dhcp-3.0.5-client_dns-1.patch that you added? Yeah. That's a patch from the upstream alpha release, so it should work well. It's been working on my sys

Section: The Bash Shell Startup Files - PATH=/your/head/asplode

2007-03-16 Thread Jonathan Oksman
Hello BLFS Development! It's been a while since my first post here, so I figured I would add some of my observations since 6.2 has been released. I'll only be discussing the section "The Bash Shell Startup Files" today, since it is still fresh in my mind from my most recent build. First, a quick

Re: Dash.

2007-03-16 Thread Dan Nicholson
On 3/16/07, Randy McMurchy <[EMAIL PROTECTED]> wrote: > Dan Nicholson wrote these words on 03/16/07 09:27 CST: > > > It just needs some LFS boilerplate at the top. That's everything > > upstream + LC_ALL=C in the mkbuiltins script that I sent him and he > > said he would apply. > > How many patches

Re: Problem with bash-3.2 patch

2007-03-16 Thread Richard Gill
Hi Creating the regular expression in a variable, and then using this variable without quoting it in the conditional construct works, so we modified our bash'based package manager to act like this. I agree it's not cool to have a change in bash scripts parsing. Maybe an option or a specific BASH_

Re: Problem with bash-3.2 patch

2007-03-16 Thread Jens Stroebel
On Thu, Mar 15, 2007 at 01:12:11PM -0700, Dan Nicholson wrote: [..snip...] > > Following up my own post, sorry, but I thought the above incomplete after > > a bit more testing: > > > > It seems like it's OK to "" the left side of the comparison, > > but not the regex which should