bash does not run startup files

Configuration Information [Automatically generated, do not change]: Machine: i686 OS: linux-gnu - Red Hat Enterprise Linux Client release 5.3 (Tikanga) Compiler: gcc Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='i686' -DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='i686-pc-linux-gnu' -DCONF_V

Re: delete elements from an array...

On Tue, 10 Mar 2009, OnTheEdge wrote: I'm having a problem getting this to work. I'm currently doing this using a file instead of an array, but it is too slow. Here's what I'm trying to do: For each record in my main array (array1), I want to get a match out of array2 and append it to the arra

cannot get bash-4.0.10 to run initialization scripts

both the original 4.0.0 version from the source repository or a newly patched bash 4.0.10 with patches from this list *still* will not run /etc/profile, ~/.bashrc, or ~/.bash_profile as documented in the INVOCATION section of the man page, no matter how it is started: via login, via exec, or via x

Re: IFS valid characters

> What are the valid charactes for the IFS variable? In particular, is '\0' a > valid one? Technically, yes, but in practice it's not useful. There are too many things represented as C strings to make NUL work right. Chet -- ``The lyf so short, the craft so long to lerne.'' - Chaucer Chet R

delete elements from an array...

I'm having a problem getting this to work. I'm currently doing this using a file instead of an array, but it is too slow. Here's what I'm trying to do: For each record in my main array (array1), I want to get a match out of array2 and append it to the array1 record. After I get the match, I want

remove elements from an array...

-- View this message in context: http://www.nabble.com/remove-elements-from-an-array...-tp22440301p22440301.html Sent from the Gnu - Bash mailing list archive at Nabble.com.

Feature request

I would like to see read's -d option expanded to accept a string of characters, any one of which would terminate input. The character which terminates input should be stored in a variable, e.g., $REPLY_END. -- Chris F.A. Johnson, webmaster

IFS valid characters

Hi, What are the valid charactes for the IFS variable? In particular, is '\0' a valid one?

Re: file descriptors, redirection and other animals....

On Mar 9, 7:10 pm, Stephane CHAZELAS wrote: > 2009-03-9, 05:03(-07), simonm: > > Not sure what you're trying to achieve. Have you got some example? > > Note that comp.unix.shell would be a better place to ask kind of > question. OK. > -- > Stéphane Thanks for the response, Stephane. I'll answer

Bash-4.0 Official Patch 10

BASH PATCH REPORT = Bash-Release: 4.0 Patch-ID: bash40-010 Bug-Reported-by:Mike Frysinger Bug-Reference-ID: <200903030122.56206.vap...@gentoo.org> Bug-Reference-URL: http://lists.gnu.org/archive/html/bu

Bash-4.0 Official Patch 9

BASH PATCH REPORT = Bash-Release: 4.0 Patch-ID: bash40-009 Bug-Reported-by:"Chris F.A. Johnson" Bug-Reference-ID: <4d6b7$49a88cec$cef88ba3$16...@teksavvy.com> Bug-Reference-URL: http://lists.gnu.org/arc

Bash-4.0 Official Patch 8

BASH PATCH REPORT = Bash-Release: 4.0 Patch-ID: bash40-008 Bug-Reported-by:Mike Frysinger Bug-Reference-ID: <200902261030.54062.vap...@gentoo.org> Bug-Reference-URL: http://lists.gnu.org/archive/html/bu

Bash-4.0 Official Patch 7

BASH PATCH REPORT = Bash-Release: 4.0 Patch-ID: bash40-007 Bug-Reported-by:AnMaster Bug-Reference-ID: <49a41c18.80...@tele2.se> Bug-Reference-URL: http://lists.gnu.org/archive/html/bug-bash/2009-02/msg0

Bash-4.0 Official Patch 6

BASH PATCH REPORT = Bash-Release: 4.0 Patch-ID: bash40-006 Bug-Reported-by:Evgeniy Zhemchugov Bug-Reference-ID: Bug-Reference-URL: http://lists.gnu.org/archive/html/bug-bash/2009-02/msg00202.html Bug

Bash-4.0 Official Patch 5

BASH PATCH REPORT = Bash-Release: 4.0 Patch-ID: bash40-005 Bug-Reported-by:Pierre Gaston Bug-Reference-ID: Bug-Reference-URL: http://lists.gnu.org/archive/html/bug-bash/2009-02/msg00206.html Bug-Desc

Bash-4.0 Official Patch 4

BASH PATCH REPORT = Bash-Release: 4.0 Patch-ID: bash40-004 Bug-Reported-by:Mike Frysinger Bug-Reference-ID: <200902231720.30519.vap...@gentoo.org> Bug-Reference-URL: http://lists.gnu.org/archive/html/bu

Bash-4.0 Official Patch 2

BASH PATCH REPORT = Bash-Release: 4.0 Patch-ID: bash40-002 Bug-Reported-by:p...@arcturus.universe Bug-Reference-ID: <20090221143709.13878.qm...@arcturus.universe> Bug-Reference-URL: http://lists.gnu.org/

Bash-4.0 Official Patch 3

BASH PATCH REPORT = Bash-Release: 4.0 Patch-ID: bash40-003 Bug-Reported-by:Bernd Eggink Bug-Reference-ID: <49a323f5.60...@sudrala.de> Bug-Reference-URL: http://lists.gnu.org/archive/html/bug-bash/2009-0

Bash-4.0 Official Patch 1

BASH PATCH REPORT = Bash-Release: 4.0 Patch-ID: bash40-001 Bug-Reported-by:Mike Frysinger Bug-Reference-ID: <200902211821.42188.vap...@gentoo.org> Bug-Reference-URL: http://lists.gnu.org/archive/html/bu

Re: Passing paths with spaces from one command to another

On Tue, Mar 10, 2009 at 02:31:06PM +0200, Angel Tsankov wrote: > What if the second command is a function defiend in a shell script, or a > bash built-in command? I assume this is related to Mike's earlier answer of: find . -print0 | xargs -0 ls You can use a while read loop: find . -prin

Re: file descriptors, redirection and other animals....

2009-03-10, 01:54(-07), simonm: [...] > cat very_large_text_file | a | long | and | complex | chain | of | > pipes | tee <(command_one) <(command_two) 1>/dev/null > > So, I want to apply command_one and command_two to the whole output of > the resulting text stream coming from "pipes". > > Is there

Re: Passing paths with spaces from one command to another

What if the second command is a function defiend in a shell script, or a bash built-in command?

Re: Bash question

On Sun, Mar 08, 2009 at 03:56:30PM -0700, jenea wrote: > This is my script: > = > #!/bin/bash > today_day=$(echo `date +"'%e %b %Y'"`) > echo `...` is usually redundant. In this case, it definitely is. You only need: today_day=$

Re: Passing paths with spaces from one command to another

On Tuesday 10 March 2009 07:42:29 Angel Tsankov wrote: > I want to pass the output from one command (e.g. find) to some other > command so that each path (output by the first command) gets into a > distinct positional parameter of the second command. How can I do this if > some paths contain space

Passing paths with spaces from one command to another

Hello, I want to pass the output from one command (e.g. find) to some other command so that each path (output by the first command) gets into a distinct positional parameter of the second command. How can I do this if some paths contain spaces?

file descriptors, redirection and other animals....

Hi all, Here's a quick one... The following works as expected: # exec 9<>test.file ; jot 50 >&9 ; tail -5 <&9 9>&- 46 47 48 49 50 The next one does not: # exec 9<>test.file ; jot 50 >&9 ; head -5 <&9 9>&- # The question is: Why? bash --version GNU bash, version 3.2.17(1)-release (i386-appl

Bash question

This is my script: = #!/bin/bash today_day=$(echo `date +"'%e %b %Y'"`) echo $today_day tar -cvz --newer $today_day -f /mnt/usb_backup/backup/diff/backupFull_`date +%Y%m%d`.tgz /mnt/mirror80gb/Shared_Folder/ This is the debug: ==