Except that I must be root to do that, it does not hurt me, so I did
not investigate further.
Give sudo a try.
I will do. But I will also find how to only give me su rights for stuff
like networkpower, not for everything, becoming su for system
administration reminds me to take care when my
berenger.mo...@neutralite.org wrote:
Bob Proulx wrote:
I have seen various wifi drivers not be happy across a
suspend/hibernate resume. I have needed to unload them on the way
down and reload them on the way up. Or unload and reload them after
the resume.
Generally speaking, my computer
I have seen various wifi drivers not be happy across a
suspend/hibernate resume. I have needed to unload them on the way
down and reload them on the way up. Or unload and reload them after
the resume.
Generally speaking, my computer have some troubles to automatically
change used networks,
berenger.mo...@neutralite.org wrote:
Wow. 1-4 times a day?
Usually:
1: when I am moving from train to work
2: when I am leaving work to train
3: when I am moving from train to home
4: when I am leaving computer for bed
:)
Ah, I see. It isn't because the machine is unstable or needs it
Wow. 1-4 times a day?
Usually:
1: when I am moving from train to work
2: when I am leaving work to train
3: when I am moving from train to home
4: when I am leaving computer for bed
:)
Why is it necessary to reboot? I would like to understand this use
case better.
I am using
berenger.mo...@neutralite.org wrote:
Bob Proulx a écrit:
berenger.mo...@neutralite.org wrote:
The immediate problem to change the symlink to bash instead of dash
is that it will slow down his system boot sequence, ...
I sometimes hear this but I disagree that boot speed causes this to
Le 20.12.2012 01:32, Bob Proulx a écrit :
berenger.mo...@neutralite.org wrote:
Bob Proulx a écrit :
Don't change the symlink. Change the #! line to #!/bin/bash. That
is the correct way to use bash specific features. Then it will
work
on the next system that you run it on. If you change
Good morning,
Can anyone help me understand why the following two console commands each
produce output, but only one of them produces output when both are called in a
shell script?
$ /bin/echo Shell: $SHELL
Shell: /bin/bash
$ /bin/echo Random: $RANDOM
Random: 29707
$ cat output.sh
#!/bin/sh
Nelson Green grabbed a keyboard and wrote:
Good morning,
Can anyone help me understand why the following two console commands each
produce output, but only one of them produces output when both are called in a
shell script?
$ /bin/echo Shell: $SHELL
Shell: /bin/bash
$ /bin/echo
On Dec 19, 2012, at 9:07 AM, David Guntner wrote:
'Cause /bin/sh points to dash, not bash, in Debian.
In squeeze, but not in lenny. It's bash in lenny:
ls -la /bin/sh
lrwxrwxrwx 1 root root 4 Oct 27 14:09 /bin/sh - dash
ls -la /bin/sh
lrwxrwxrwx 1 root root 4 2008-11-26 11:33 /bin/sh -
Nelson Green grabbed a keyboard and wrote:
Good morning,
Can anyone help me understand why the following two console commands each
produce output, but only one of them produces output when both are called
in a
shell script?
$ /bin/echo Shell: $SHELL
Shell: /bin/bash
$
On Dec 19, 2012, at 9:07 AM, David Guntner wrote:
'Cause /bin/sh points to dash, not bash, in Debian.
In squeeze, but not in lenny. It's bash in lenny:
ls -la /bin/sh
lrwxrwxrwx 1 root root 4 Oct 27 14:09 /bin/sh - dash
ls -la /bin/sh
lrwxrwxrwx 1 root root 4 2008-11-26 11:33
Thanks Dave!
PS, I'm getting ready to post a request for help in capturing the output of
time
to a script variable. I can't seem to make it work despite many different
attempts. I don't think that's a dash issue, but if you know that it is, let
me
know.
Well, that didn't take long. I'm
Glenn English grabbed a keyboard and wrote:
On Dec 19, 2012, at 9:07 AM, David Guntner wrote:
'Cause /bin/sh points to dash, not bash, in Debian.
In squeeze, but not in lenny. It's bash in lenny:
ls -la /bin/sh
lrwxrwxrwx 1 root root 4 Oct 27 14:09 /bin/sh - dash
ls -la /bin/sh
[You know, it would be *really* nice if you set your mail program to
include an attribute line at the top, indicating who you're replying
to/quoting :-)]
Nelson Green grabbed a keyboard and wrote:
[I said...]
Nelson Green grabbed a keyboard and wrote:
$ cat output.sh
#!/bin/sh
/bin/echo
Nelson Green wrote:
Nelson Green grabbed a keyboard and wrote:
Change your shebang line to #!/bin/bash to make it work right and then
set the executable bit on the script. Then you can just do ./output.sh
to get the expected results (don't do sh output.sh, since that will
just invoke
Le 20.12.2012 00:22, Bob Proulx a écrit :
Nelson Green wrote:
Nelson Green grabbed a keyboard and wrote:
Change your shebang line to #!/bin/bash to make it work right and
then
set the executable bit on the script. Then you can just do
./output.sh
to get the expected results (don't do sh
Nelson Green wrote:
Well, that didn't take long. I'm posting a simple script that captures the
system time output of the time command to a variable in case anyone else
has spent a good bit of time trying to get this to work, like me.
I have a few comments. Many eyes make all bugs visibile!
berenger.mo...@neutralite.org wrote:
Bob Proulx a écrit :
Don't change the symlink. Change the #! line to #!/bin/bash. That
is the correct way to use bash specific features. Then it will work
on the next system that you run it on. If you change the symlink on
The immediate problem to
19 matches
Mail list logo
