o chroot within it :
>
> root@marietto-Z87-HD3:/home/marietto/Scrivania/Chromebook/linux-distros#
> chroot ./jessie-armhf /bin/bash
>
> it gives the following error :
>
> chroot: can't execute command "/bin/bash": No such file or directory
Omit the interpreter:
#
On Sun, 18 Jun 2023, Mario Marietto wrote:
Hello.
with qemu works,but I thought that it was better to avoid the usage of
qemu.
I'm a bit puzzled what you're trying to do.
if you want to chroot on an amd64 machine then you have to use something
like qemu to emulate the armhf processor.
If yo
I try to chroot within it :
root@marietto-Z87-HD3:/home/marietto/Scrivania/Chromebook/linux-distros#
chroot ./jessie-armhf /bin/bash
it gives the following error :
chroot: can't execute command "/bin/bash": No such file or directory
but I see the file bash within the d
debian.org/debian <http://archive.debian.org/debian>
>> >
>> > and it worked ok,but when I try to chroot within it :
>> >
>> > root@marietto-Z87-HD3:/home/marietto/Scrivania/Chromebook/linux-distros#
>>
>> > chroot ./jessie-armhf /bin/bash
&
http://archive.debian.org/debian <http://archive.debian.org/debian>
> >
> > and it worked ok,but when I try to chroot within it :
> >
> > root@marietto-Z87-HD3:/home/marietto/Scrivania/Chromebook/linux-distros#
>
> > chroot ./jessie-armhf /bin/bash
&g
bian.org/debian>
and it worked ok,but when I try to chroot within it :
root@marietto-Z87-HD3:/home/marietto/Scrivania/Chromebook/linux-distros#
chroot ./jessie-armhf /bin/bash
it gives the following error :
chroot: can't execute command "/bin/bash": No such file or directory
bian.org/debian>
and it worked ok,but when I try to chroot within it :
root@marietto-Z87-HD3:/home/marietto/Scrivania/Chromebook/linux-distros#
chroot ./jessie-armhf /bin/bash
it gives the following error :
chroot: can't execute command "/bin/bash": No such file or directory
7-HD3:/home/marietto/Scrivania/Chromebook/linux-distros#
chroot ./jessie-armhf /bin/bash
it gives the following error :
chroot: can't execute command "/bin/bash": No such file or directory
but I see the file bash within the directory /bin of the debootstrapped
directory called
On Wed, 27 Feb 2008 15:34:27 -0500
"Michael Habashy" <[EMAIL PROTECTED]> wrote:
Hello Michael,
> Just curious...do you know any other way to reset the base components
> of debian??
As root, dpkg-reconfigure should help you do what you want.
If you fear your system has been compromised, reconfig
thanks for the reply.
Just curious...do you know any other way to reset the base components of
debian??
i.e. xdm,gdm,kde and etc...
thanks
mjh
On Tue, Feb 26, 2008 at 4:19 PM, Jamin Davis <[EMAIL PROTECTED]>
wrote:
> Michael Habashy wrote:
>
> > I do not want to kill this to death but..on a good
Michael Habashy wrote:
I do not want to kill this to death but..on a good system:
mach1:/bin# ls -l bash
-rwxr-xr-x 1 root root 769368 2006-12-11 17:28 bash
No one knows how to force a fresh copy of the base debian setup?? with
overly impacting my present system ??? to take care of the xwindow
please???
mjh
On Mon, Feb 25, 2008 at 10:57 PM, Rich Healey <[EMAIL PROTECTED]> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Michael Habashy wrote:
> > sorry..i lost you on that...you think that someone changed the
> permissions
> > on /bin/ba
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Michael Habashy wrote:
> sorry..i lost you on that...you think that someone changed the permissions
> on /bin/bash ???
> they are set to 766 to root.root
>
> can you try to phrase things differently ???
> thanks
> mjh
>
>
ECTED]>
> wrote:
> > I am logged in as root, and i try to su as a user : user1 ; I get the
> > following
> > error:
> >
> > rmachine:/home/user1/Maildir/cur# su user1
> >
> > Cannot execute /bin/bash: Permission denied
> >
> Hi,
> I'
sorry..i lost you on that...you think that someone changed the permissions
on /bin/bash ???
they are set to 766 to root.root
can you try to phrase things differently ???
thanks
mjh
On Mon, Feb 25, 2008 at 10:10 PM, Rich Healey <[EMAIL PROTECTED]> wrote:
> -BEGIN PGP SIGNE
dm package, i am left iwth kde ---when i login in with
> that...i get an xterm window pop up and it states the same thing : Cannot
> execute /bin/bash: Permission denied
>
> it is driving me up a wall.
>
> thanks..for any help...
> mjh
>
> On Mon, Feb 25, 2008 at 6:11
the same thing : Cannot
execute /bin/bash: Permission denied
it is driving me up a wall.
thanks..for any help...
mjh
On Mon, Feb 25, 2008 at 6:11 PM, Jeff D <[EMAIL PROTECTED]> wrote:
> Nuno Magalhães wrote:
> >> Cannot execute /bin/bash: Permission denied
> >
> >
Nuno Magalhães wrote:
Cannot execute /bin/bash: Permission denied
Er... have you by any chance tried checking out the permissions for
that file? It'll be executed by the user, not root. Try 766.
That should probably be 755 , not 766, you really dont want /bin/bash
writeable by anyon
> Cannot execute /bin/bash: Permission denied
Er... have you by any chance tried checking out the permissions for
that file? It'll be executed by the user, not root. Try 766.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
I am logged in as root, and i try to su as a user : user1 ; I get the
following
error:
rmachine:/home/user1/Maildir/cur# su user1
Cannot execute /bin/bash: Permission denied
On Mon, Aug 20, 2007 at 02:19:49PM -0800, Ken Irving wrote:
From: Ken Irving <[EMAIL PROTECTED]>
To: debian-user@lists.debian.org
Subject: Re: chroot: cannot run command `/bin/bash': No such file or
directory
Mail-Followup-To: debian-user@lists.debian.org
X-Spam-Chec
On Mon, Aug 20, 2007 at 10:33:20PM +0200, Gerard Robin wrote:
> On Mon, Aug 20, 2007 at 02:44:31PM -0400, Neil Watson wrote:
>> On Mon, Aug 20, 2007 at 08:40:09PM +0200, Gerard Robin wrote:
>>>> First post:
>>>>> ldd /bin/bash
>>>>&g
On Mon, Aug 20, 2007 at 02:44:31PM -0400, Neil Watson wrote:
From: Neil Watson <[EMAIL PROTECTED]>
To: debian-user@lists.debian.org
Subject: Re: chroot: cannot run command `/bin/bash': No such file or directory
X-Spam-Checker-Version: SpamAssassin 3.1.4 (2006-07-26) on murphy.debian
On Mon, Aug 20, 2007 at 08:40:09PM +0200, Gerard Robin wrote:
First post:
ldd /bin/bash
libncurses.so.5 => /lib/libncurses.so.5 (0x2b2d9014f000)
libdl.so.2 => /lib/libdl.so.2 (0x2b2d9039b000)
libc.so.6 => /lib/libc.so.6 (0x2b2d9059f000)
On Mon, Aug 20, 2007 at 02:24:18PM -0400, Neil Watson wrote:
From: Neil Watson <[EMAIL PROTECTED]>
To: debian-user@lists.debian.org
Subject: Re: chroot: cannot run command `/bin/bash': No such file or directory
X-Spam-Checker-Version: SpamAssassin 3.1.4 (2006-07-26) on murphy.debian
On Mon, Aug 20, 2007 at 08:12:24PM +0200, Gerard Robin wrote:
find /f:
/f
/f/bin
/f/bin/bash
/f/lib
/f/lib/libncurses.so.5
/f/lib/ld-2.6.1.so
/f/lib/libdl.so.2
/f/lib/libc.so.6
First post:
ldd /bin/bash
libncurses.so.5 => /lib/libncurses.so.5 (0x2b2d9014f000)
libdl
On Mon, Aug 20, 2007 at 02:01:07PM -0400, Neil Watson wrote:
From: Neil Watson <[EMAIL PROTECTED]>
To: debian-user@lists.debian.org
Subject: Re: chroot: cannot run command `/bin/bash': No such file or directory
X-Spam-Checker-Version: SpamAssassin 3.1.4 (2006-07-26) on murphy.debian
What does 'find /f' produce?
--
Neil Watson | Debian Linux
System Administrator| Uptime 2 days
http://watson-wilson.ca
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Hello,
I have a problem to use chroot:
I did:
sudo -s
mkdir /f
mkdir /f/bin /f/lib
cp /bin/bash /f/bin
ldd /bin/bash
libncurses.so.5 => /lib/libncurses.so.5 (0x2b2d9014f000)
libdl.so.2 => /lib/libdl.so.2 (0x2b2d9039b000)
libc.so.6 => /lib/
David Jarvie wrote:
> On Sunday 19 March 2006 18:47, Joey Hess wrote:
>> David Jarvie wrote:
>> > Permissions on root directories: all have as a minimum, 755. /tmp/
>> > and /var/tmp have 777.
>>
>> Have you checked the permissions of / ? Having it not world readable can
>> definitly cause this pr
David Jarvie wrote:
> Ah! So obvious when you think of it - yes, that was the cause. But why the
> permissions should have changed, I have no idea.
Often caused by untarring something in the wrong place.
--
see shy jo
signature.asc
Description: Digital signature
David Jarvie wrote:
>On Sunday 19 March 2006 18:47, Joey Hess wrote:
>
>
>>David Jarvie wrote:
>>
>>
>>>Permissions on root directories: all have as a minimum, 755. /tmp/
>>>and /var/tmp have 777.
>>>
>>>
>>Have you checked the permissions of / ? Having it not world readable can
>>defi
On Sunday 19 March 2006 18:47, Joey Hess wrote:
> David Jarvie wrote:
> > Permissions on root directories: all have as a minimum, 755. /tmp/
> > and /var/tmp have 777.
>
> Have you checked the permissions of / ? Having it not world readable can
> definitly cause this problem.
Ah! So obvious when y
Joey Hess wrote:
>David Jarvie wrote:
>
>
>>Permissions on root directories: all have as a minimum, 755. /tmp/
>>and /var/tmp have 777.
>>
>>
>
>Have you checked the permissions of / ? Having it not world readable can
>definitly cause this problem.
>
>
That certainly would be problematic
David Jarvie wrote:
> Permissions on root directories: all have as a minimum, 755. /tmp/
> and /var/tmp have 777.
Have you checked the permissions of / ? Having it not world readable can
definitly cause this problem.
--
see shy jo
signature.asc
Description: Digital signature
>
>Permissions on /home directories: all are owned by the respective user, and
>have 755 permissions.
>
>Disk space: plenty of space on all volumes.
>
>Permissions on libraries used by /bin/bash: I did a 'ldd /bin/bash':
>linux-gate.so.1 => (
user, and
have 755 permissions.
Disk space: plenty of space on all volumes.
Permissions on libraries used by /bin/bash: I did a 'ldd /bin/bash':
linux-gate.so.1 => (0xe000)
libncurses.so.5 => /lib/libncurses.so.5 (0xb7f43000)
libdl.so.2 =>
cript, but when I run something like:
> ---
> #!/bin/bash
>
> echo $(pwd)
>
> I always get $HOME, not the current working directory. I'd need to
> continue in the working directory from where the script was called to
> work on the files there. (I'd
Dear all,
Roland wrote:
/bin/sh exists for compatability with the legacy Bourne shell and does
not provide bash-specific features. In APP 1 I had a ~bash_cmd_rc file
with some output in the BASH_ENV, and it is ignored by /bin/sh, even
if /bin/sh is a softlink to /bin/bash on my machine
ince in the
> Linux machines (where I had that problem) /bin/sh is a link to
> /bin/bash, so I was expecting to see no difference with the change...
>
/bin/sh exists for compatability with the legacy Bourne shell and does
not provide bash-specific features. In APP 1 I had a ~ba
> --- Ursprüngliche Nachricht ---
> Von: Luis Finotti <[EMAIL PROTECTED]>
> You've got it:
>
> babbage[~/tmp]% echo $BASH_ENV
> /home/finotti/.bashrc
>
> This is set in the default ".bash_profile" here (at work). I've never
> changed it. So, that is not the usual case? What is the usua
Luis writes:
> /bin/sh is a link to /bin/bash, so I was expecting to see no difference
> with the change...
When called as sh bash attempts to be POSIX compliant.
--
John Hasler
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Luis writes:
> That does answer my question, but it did not work, likely because I have
> $BASH_ENV set to my .bashrc..
Why?
--
John Hasler
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Luis Finotti writes:
> I have
> ...
< ...
You have this in what file? Post all of whatever file it is in.
--
John Hasler
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
as, like that
line. So, I guess I'm trying to say "I have no idea". :-) I've
commented it out for now...
> Also, do you have the same problem if you use #!/bin/sh instead of
> #!/bin/bash? You mentioned wanting to be portable, so that's a good idea
> anyway
Dear Michael,
> You could change
>
> #! /bin/bash
>
> to
>
> #! /bin/bash --norc
That does answer my question, but it did not work, likely because I
have $BASH_ENV set to my .bashrc..
Thanks!
Luis
Hi Jan,
Thanks for the reply again!
> > open("/home/finotti/.bashrc", O_RDONLY|O_LARGEFILE) = 3
>
> There it is. From the bash manpage I gather that a non-interactive
> bash doesn't read _any_ startup files, except for any file that
> is mentioned in the environment variable $BASH_ENV. Does this
your problem.
What exactly are you trying to accomplish with this snippet? It certainly
doesn't look like a normal thing to do.
Also, do you have the same problem if you use #!/bin/sh instead of
#!/bin/bash? You mentioned wanting to be portable, so that's a good idea
anyway.
--
Wes
On 1/5/06, Luis Finotti <[EMAIL PROTECTED]> wrote:
> Maybe is the issue with my .bashrc, as it's been pointed out... But
> is there a way around it?
You could change
#! /bin/bash
to
#! /bin/bash --norc
--
Michael A. Marsh
http://www.umiacs.umd.edu/~mmarsh
http://mamarsh.blogspot.com
Dear Jan,
> Hm, this is a bit redundant - it's not necessary to wrap pwd into
> process substitution and echo the results... (...)
Thanks for the comment! It was just something to show the change...
> Besides, the snippet is procuding the desired result here ($pwd, not
> $HOME). AFAICT, bash d
Hi Luis!
> > strace -eopen bash -c "echo 'X'"
>
> Many repeated lines, but, after "uniq":
>
> open("/etc/ld.so.cache", O_RDONLY) = 3
> open("/lib/libtermcap.so.2", O_RDONLY) = 3
> open("/lib/libdl.so.2", O_RDONLY) = 3
> open("/lib/libc.so.6", O_RDONLY)= 3
> open("/dev/tty", O
Dear Wesley,
> The script you've shown works fine, just the way you want. Nothing in there
> is going to change the working directory.
>
> For example:
>
> $ pwd
> /home/wjl/tmp
> $ cat <test.sh
> #!/bin/bash
> echo $(pwd)
> EOF
> $ chmod a+x test.sh
&g
Dear David,
> Do you have some sort of "cd $HOME" type statement in your .bashrc or
> .bash_profile or .profile file (or similar)?
I have
---
AUTOHOME=$PWD
# Clean up stupid automounter directory
case $PWD in
$AUTOHOME*) cd $HOME${PWD#$AUTOHOME} ;;
e
Hi!
On Thu, Jan 05, 2006 at 02:25:10PM -0500, Luis Finotti wrote:
> Dear all,
>
> I realize that this should be "way off topic", so sorry about that...
>
> I've been working on a bash script, but when I run something like:
> ---
> #!/bin/bash
>
On Thursday 05 January 2006 12:25, Luis Finotti wrote:
> Dear all,
>
> I realize that this should be "way off topic", so sorry about that...
>
> I've been working on a bash script, but when I run something like:
> ---
> #!/bin/bash
>
> ech
On 1/5/06, Luis Finotti <[EMAIL PROTECTED]> wrote:
> Dear all,
>
> I realize that this should be "way off topic", so sorry about that...
>
> I've been working on a bash script, but when I run something like:
> ---
> #!/bin/bash
>
> ech
Dear all,
I realize that this should be "way off topic", so sorry about that...
I've been working on a bash script, but when I run something like:
-------
#!/bin/bash
echo $(pwd)
I always get $HOME, not the current working directory. I'd need to
con
[Please include my email address in replies]
Hi,
I am using Sarge.
Would it be expected for these 3 scripts to be still running 30mins after
my computer started?
root 3592 0.0 0.1 2744 1484 ?S19:05 0:00 /bin/bash
/etc/rc2.d/S20xprint start
root 3593 0.0 0.1 2744
On Fri, Aug 01, 2003 at 11:57:54AM -0700, Bill Moseley wrote:
[need to add a directory to the path for a cvs-over-ssh session]
| Now I assume that's becuase /home/foo/local/bin/cvs is not in the path.
| I tried setting path in .bash_profile (and .bashrc) on the remote
| machine but they don't seem
t;>which cvs
> /home/foo/local/bin/cvs
>
> $ cvs -d:ext:[EMAIL PROTECTED]:/home/foo/local/cvsroot co something
> /bin/bash: cvs: command not found
$ cat cvs-path
# source this into your shell like this:
# source cvs-path
#
# Hell, someone should forbid the university to
o/local/cvsroot co something
/bin/bash: cvs: command not found
Now I assume that's becuase /home/foo/local/bin/cvs is not in the path.
I tried setting path in .bash_profile (and .bashrc) on the remote
machine but they don't seem to be read on a ssh connection.
How do I get foo's PATH up
On Mon, 2003-06-23 at 21:33, Carel Fellinger wrote:
> Hai,
>
> when tonight I tried to boot into my system bypassing init I found to
> my surprise that "init=/bin/bash" doesn't work anymore. Atleast not
I know it works on a 2.5 kernel, I tried it (more than once :), t
Hai,
when tonight I tried to boot into my system bypassing init I found to
my surprise that "init=/bin/bash" doesn't work anymore. Atleast not
with kernel-image.2.4.20 and initrd. It still works with 2.2 kernels
without initrd. Googling and searching the deb archives didn
On Friday 13 June 2003 15:58 Elie De Brauwer wrote:
> On Friday 13 June 2003 20:17, Gabriel Meier wrote:
> > Hi,
> >
> > I solved the Problem some hours ago. I guess I checked every single lib,
> > but not the directory. It was set to 666. as a user, you seem to need 7.
> > I've no Idea, why it wo
Hi,
I solved the Problem some hours ago. I guess I checked every single lib, but
not the directory. It was set to 666. as a user, you seem to need 7. I've no
Idea, why it works for root without it.
Anyway, thanks for all the help.
Gabriel
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a
nything.
Hmm. All the stuff you showed me looks fine. The strace doesn't have any
answers obvious enough for my little brain to comprehend.
But you had mentioned before that your libraries were ok?
How about double checking by trying something like this :
:)
[EMAIL PROTECTED]:~]$ ls -
Dan Dofton <[EMAIL PROTECTED]> schrieb am 03.06.03 16:11:13:
>
> On Tue, 3 Jun 2003 12:32:46 +0200
> "gabriel meier" <[EMAIL PROTECTED]> wrote:
>
> > > >> So login is possible at the moment only for root.
> > > >> I c
On Tue, 3 Jun 2003 12:32:46 +0200
"gabriel meier" <[EMAIL PROTECTED]> wrote:
> > >> So login is possible at the moment only for root.
> > >> I checked all the user rights of / /bin /bin/bash and its dependend
A few ideas come to mind:
Did your non-roo
* gabriel meier <[EMAIL PROTECTED]> [2003-06-03 12:40]:
> >
> > what is the result of
> > cat /etc/shells
> > ?
>
> debian:~# cat /etc/shells
> # /etc/shells: valid login shells
> /bin/ash
> /bin/bash
> /bin/csh
> /bin/sh
&
t;
> >> Hi,
> >>
> >> I have some strange Problems with my user login here:
> >> Any time I log in with any user but root I get the following message:
> >>
> >>
> >> Cannot execute /bin/bash: Permission denied
> >
log in with any user but root I get the following message:
> >
> > Cannot execute /bin/bash: Permission denied
> >
> > So login is possible at the moment only for root.
> > I checked all the user rights of / /bin /bin/bash and its dependend libs
> >
I am subscribed to this list thanks schrieb am 02.06.03 14:54:46:
>
> * gabriel meier [2003-06-02 14:25]:
>
> > Cannot execute /bin/bash: Permission denied
> >
> > So login is possible at the moment only for root. I checked all
> > the user r
I am subscribed to this list thanks schrieb am 02.06.03 14:54:46:
>
> * gabriel meier [2003-06-02 14:25]:
>
> > Cannot execute /bin/bash: Permission denied
> >
> > So login is possible at the moment only for root. I checked all
> > the user r
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Monday 02 June 2003 14:01, gabriel meier wrote:
> Hi,
>
> I have some strange Problems with my user login here:
> Any time I log in with any user but root I get the following message:
>
> Cannot execute /bin/bash: Permission deni
y time I log in with any user but root I get the following message:
>>
>>
>> Cannot execute /bin/bash: Permission denied
>>
>> So login is possible at the moment only for root.
>> I checked all the user rights of / /bin /bin/bash and its dependend
>>
On Mon, 2 Jun 2003 14:01:27 +0200
"gabriel meier" <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> I have some strange Problems with my user login here:
> Any time I log in with any user but root I get the following message:
>
> Cannot execute /bin/bash: P
* gabriel meier <[EMAIL PROTECTED]> [2003-06-02 14:25]:
> Cannot execute /bin/bash: Permission denied
>
> So login is possible at the moment only for root. I checked all
> the user rights of / /bin /bin/bash and its dependend libs and they
> were OK. etc/passwd is
Hi,
I have some strange Problems with my user login here:
Any time I log in with any user but root I get the following message:
Cannot execute /bin/bash: Permission denied
So login is possible at the moment only for root.
I checked all the user rights of / /bin /bin/bash and its
nate wrote:
Kent West said:
Is there a similar way to get to a shell on a broken Sun Solaris 8 system?
I had to do this once, damn filesystem curroptoion totally screwed the
system. I looked for such a feature but could not find one. So I booted
the install cd and got a shell on that to
Kent West said:
> Is there a similar way to get to a shell on a broken Sun Solaris 8 system?
I had to do this once, damn filesystem curroptoion totally screwed the
system. I looked for such a feature but could not find one. So I booted
the install cd and got a shell on that to do the work I neede
y
at the LILO prompt by entering something like:
linux root=/dev/hda1 init=/bin/bash
Is there a similar way to get to a shell on a broken Sun Solaris 8 system?
Thanks!
Kent
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
)
> -> It makes a big difference on a slow machine, especially when
> -> installing packages ({pre,post}{inst,rm} scripts are always sh).
>
> well, maybe not always. Maybe we should ask developers to use sh and not to
> use bashisms while possible
I thought it was Policy that p
>
> or just install ash and symlink sh -> ash
> It makes a big difference on a slow machine, especially when
> installing packages ({pre,post}{inst,rm} scripts are always sh).
>
> <...>
>> So to this end, Require'ing ash would add to the system overhead since (I
>> reckon) 98% of people would nee
-> All the more reason to streamline the process...
-> why should everything take more time, just because some stuff must.
that's why i prefer ash
-> > > that's it, i don't like scripts that "require" bash if they don't
-> > > have to.
-> >
-> > So have you actually removed bash from your system
On Sun, Apr 01, 2001 at 05:33:42PM +0200, Matus fantomas Uhlar wrote:
> is it ok when acripts start with #!/bin/bash even if they shouldn't ?
[...]
> echo -ne "blahblah\n"
> to
> echo "blahblah"
>
> (wtf do we need the first?)
It took me a second to s
this is perfectly allowable,
>and i think is even a config question on woody's ash)
>
>if the script DOES have a bashism then it should have #!/bin/bash so a
>non-bash /bin/sh does not break it. but using #!/bin/bash for no good
>reason is just lame.
Yeah, it's
ings in pure posix that work perfectly in ash.
initscripts should be plain posix shell scripts with no bashisms, and
should have #!/bin/sh as the interpreter, this way you can link
/bin/sh to ash without any problems. (this is perfectly allowable,
and i think is even a config question on woody&
On Sun, 1 Apr 2001, Gavin Hamill wrote:
> > -> And anyway, why would you want to insist on 'ash' ?
> >
> > faster, smaller etc. it could be ksh or whatever does /bin/sh point to.
>
> Certainly, a 100k binary vs. the 400k of bash is much tighter, and the
> POSIX-compliance feature of ash is certain
On Sun, 1 Apr 2001, Matus "fantomas" Uhlar wrote:
> -> echo -ne "Restarting apache web server: "
>
> "echo -n" is enough for this and works even in ash
OK, yes the -e is just for interpreting \n and friends...
> -> And anyway, why would you want to insist on 'ash' ?
>
> faster, smaller etc. it
-> > it seems apache could run with ash for example w/o problems
-> > - it just needs change all
-> >
-> > echo -ne "blahblah\n"
-> > to
-> > echo "blahblah"
-> >
-> > (wtf do we need the first?)
->
-> The first doesn't take a new line so it's possible to do this:
->
-> echo -ne "Restarting apach
On Sun, 1 Apr 2001, Matus "fantomas" Uhlar wrote:
> it seems apache could run with ash for example w/o problems
> - it just needs change all
>
> echo -ne "blahblah\n"
> to
> echo "blahblah"
>
> (wtf do we need the first?)
The first doesn't take a new line so it's possible to do this:
echo -ne "R
Hello,
is it ok when acripts start with #!/bin/bash even if they shouldn't ?
I found at least /etc/init.d/apache, /etc/init.d/autofs
it seems apache could run with ash for example w/o problems
- it just needs change all
echo -ne "blahblah\n"
to
echo "blahblah"
Ciao Britton,
> SHELL=/bin/bash
> 0 8 * * * prog >/tmp/$(date +%s).extension
>
> and it doesn't work, the command never gets executed. Backtick
maybe date is not in cron PATH, try to use
/bin/date
--
Paolo Pedaletti, Como, ITALYa www.fastflow.it/~paolop
[EMAIL PROT
On Fri, Feb 23, 2001 at 08:11:31PM -0900, Britton wrote:
>
> I am trying to do approximately this in a crontab:
>
> SHELL=/bin/bash
> 0 8 * * * prog >/tmp/$(date +%s).extension
>
> Anyone have any guesses as to what might be going on here?
Someone hasn't read the
On Fri, Feb 23, 2001 at 08:11:31PM -0900, Britton wrote:
>
> I am trying to do approximately this in a crontab:
>
> SHELL=/bin/bash
> 0 8 * * * prog >/tmp/$(date +%s).extension
>
> and it doesn't work, the command never gets executed. Backtick
> substitution do
On Fri, 23 Feb 2001, Britton wrote:
>
> I am trying to do approximately this in a crontab:
>
> SHELL=/bin/bash
> 0 8 * * * prog >/tmp/$(date +%s).extension
>
> and it doesn't work, the command never gets executed. Backtick
> substitution doesn't work eithe
I am trying to do approximately this in a crontab:
SHELL=/bin/bash
0 8 * * * prog >/tmp/$(date +%s).extension
and it doesn't work, the command never gets executed. Backtick
substitution doesn't work either. An identical command with a fixed
string in place of the $(date
On Tue, 22 Feb 2000, Karl M Yerkes wrote:
kmyerk >I add a user blah. blah works fine, can login, etc. . .then, after some
time (minutes, hours, days) blah gets this error:
kmyerk >
kmyerk >cannot execute /bin/bash: Permission denied
kmyerk >
kmyerk >Permissions on /bin/bash are
I add a user blah. blah works fine, can login, etc. . .then, after some time
(minutes, hours, days) blah gets this error:
cannot execute /bin/bash: Permission denied
Permissions on /bin/bash are 755. Has anyone had this problem? What should
I do? Please, help. Send to [EMAIL PROTECTED] --Thanks
>
> On Tue, May 25, 1999 at 03:15:39PM -0400,
> [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> >
> > Can you be specific and point me to what fails. if it is a matter of making
> > ash posix happy, it will be done -- we have the code. Bash is just way too
> > heavy for many things.
> >
> > You
1 - 100 of 128 matches
Mail list logo
