Bug #243
weird behavior in the shell
| Status: | New | Start date: | ||
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | - | % Done: | 0% |
|
| Category: | - | |||
| Target version: | - |
Description
Hi,
I'm not sure if this is a 'real' bug but I'm curious if anyone knows the
cause. Check this:
zoot# echo $PATH
/sbin:/bin:/usr/sbin:/usr/bin:/usr/games:/usr/local/sbin:/usr/local/bin:/usr/pkg/bin:/usr/pkg/sbin:/usr/pkg/xorg/bin:/home/s/bin
zoot# pwd
/usr/src/sys/dev/disk/md
zoot# .
/usr/sbin/.: Permission denied.
zoot# cd /
zoot# .
/usr/sbin/.: Permission denied.
In other words: The strange thing is that whereever I type . on the csh
prompt, I get the /usr/sbin/.: message regardless of what my current
directory is.
On a Solaris system I get ".: Permission denied." which is what I'd
expect rather.
So, can anyone enlighten me why DragonFly behaves like that?
Sascha
Related todos
History
Updated by qhwt+dfly almost 7 years ago
On Sat, Jul 15, 2006 at 09:40:52AM +0200, Sascha Wildner wrote:
> I'm not sure if this is a 'real' bug but I'm curious if anyone knows the
> cause. Check this:
>
> zoot# echo $PATH
> /sbin:/bin:/usr/sbin:/usr/bin:/usr/games:/usr/local/sbin:/usr/local/bin:/usr/pkg/bin:/usr/pkg/sbin:/usr/pkg/xorg/bin:/home/s/bin
> zoot# pwd
> /usr/src/sys/dev/disk/md
> zoot# .
> /usr/sbin/.: Permission denied.
> zoot# cd /
> zoot# .
> /usr/sbin/.: Permission denied.
>
> In other words: The strange thing is that whereever I type . on the csh
> prompt, I get the /usr/sbin/.: message regardless of what my current
> directory is.
>
> On a Solaris system I get ".: Permission denied." which is what I'd
> expect rather.
>
> So, can anyone enlighten me why DragonFly behaves like that?
I observed that the same thing happens on tcsh-6.12-2 on RedHat Linux 8.0;
the consistency is that it's always the third component in $PATH that is
prefixed to `.' in the error message.
Cheers.
Updated by corecode over 6 years ago
can we close this?
Updated by swildner over 6 years ago
Nope.
Sascha
Updated by corecode almost 6 years ago
can we close this?
Updated by corecode over 4 years ago
can we close this?
Updated by corecode over 4 years ago
can we close this?
Updated by swildner over 4 years ago
Nope.
Sascha
Updated by tuxillo about 2 years ago
Hi,
I think tcsh tries to execve() to path "."
execve(2) manpage says:
[EACCES] The new process file is not an ordinary file.
Cheers,
Antonio Huete