| All Forums |
Register |
Login |
Search |
Subscriptions |
My Profile |
Inbox |
| Tool Warehouse |
FAQs |
Resources |
Help |
Member List |
Address Book |
Logout |
|
|
weird bash behaviour
|
Logged in as: Guest |
| Users viewing this topic: none |
|
Login  |
|
|
 weird bash behaviour - Mar. 10, '06, 12:46:29 PM
|
|
|
DeathWolf
Posts: 12
Joined: Mar. 7, '06,
Status: offline
|
I've been experiencing weird behaviour with bash:
1.copy/paste cuts very early, i dont know if it's bash related, or term related, but after a certain quantity of characters it cuts. It did that both in rxvt, puttycyg, and the default windows-based shell
2.running a script has odd behaviours like i had a script with this in it:
pkg_add autoconf-current-bin.tgz
pkg_add automake-current-bin.tgz
Running it
quote:
gzip: stdin: unexpected end of file
tar: End of archive volume 1 reached
tar: Sorry, unable to determine archive format.
.tgz' has unknown filename part!tems.com/pkgs/3.5/autoconf-current-bin.tgz
.tgz' by URLe to fetch `ftp://ftp.interopsystems.com/pkgs/3.5/autoconf-current-bin.tgz
gzip: stdin: unexpected end of file
tar: End of archive volume 1 reached
tar: Sorry, unable to determine archive format.
.tgz' has unknown filename part!tems.com/pkgs/3.5/automake-current-bin.tgz
.tgz' by URLe to fetch `ftp://ftp.interopsystems.com/pkgs/3.5/automake-current-bin.tgz
But if i do run the commands one by one separatly it does work perfectly
That's it for now, if anyone can confirm the problems/or any solution, i'd like to hear about it.
Thanks,
Paul-Kenji Cahier
< Message edited by DeathWolf -- Mar. 10, '06, 4:45:54 PM >
|
|
|
|
|
RE: weird bash behaviour - Mar. 10, '06, 9:17:52 PM
|
|
|
DeathWolf
Posts: 12
Joined: Mar. 7, '06,
Status: offline
|
and in the same family:
find . -name '*exta' => works
find . -name '*extb' => works
find . -name '*exta|*extb' => doesnt work
find . -name '*exta\|*extb' => doesnt work
If someone has an idea....
|
|
|
|
|
RE: weird bash behaviour - Mar. 10, '06, 11:05:21 PM
|
|
|
Rodney
Posts: 3728
Joined: Jul. 9, '02,
From: /Tools lab
Status: online
|
Check that on your machine DEP is off. Refer to the FAQ entry 2.07 (if I recall the number correctly).
|
|
|
|
|
RE: weird bash behaviour - Mar. 11, '06, 1:20:50 AM
|
|
|
DeathWolf
Posts: 12
Joined: Mar. 7, '06,
Status: offline
|
these arent core dumps
DEP is turned off(i double and triple checked, and it has been off since day0 of SP2 install)
All latest aptches installed
|
|
|
|
|
RE: weird bash behaviour - Mar. 11, '06, 9:38:06 PM
|
|
|
markfunk
Posts: 673
Joined: Mar. 31, '03,
Status: offline
|
quote:
find . -name '*exta|*extb' => doesnt work
find . -name '*exta\|*extb' => doesnt work
This is correct.
You can only use basic regex - extended regex isn't supported.
|
|
|
|
|
RE: weird bash behaviour - Mar. 12, '06, 1:15:38 AM
|
|
|
DeathWolf
Posts: 12
Joined: Mar. 7, '06,
Status: offline
|
any way of extending that?
it's really restricting
|
|
|
|
|
RE: weird bash behaviour - Mar. 12, '06, 10:55:40 PM
|
|
|
markfunk
Posts: 673
Joined: Mar. 31, '03,
Status: offline
|
You can use:
find . -name '*exta' -o -name '*extb'
The UNIX std spec says that the pattern matching is based on fnmatch(3) function
and this does not support extended reg. expressions.
|
|
|
|
 New Messages |
 No New Messages |
 Hot Topic w/ New Messages |
 Hot Topic w/o New Messages |
|
 Locked w/ New Messages |
 Locked w/o New Messages |
|
 Post New Thread
Reply to Message
Post New Poll
Submit Vote
Delete My Own Post
Delete My Own Thread
Rate Posts |
|
|
|
Printable Version
