Joel Newkirk wrote:
> On Thu, 16 Oct 2008 14:12:26 +0200, Xavier Cremaschi
> <[EMAIL PROTECTED]> wrote:
>> papa-piet a écrit :
Fox Mulder schrieb:
I didn't try it with 2008.9 because i only use debian
>>> I did.
>>> shh into your Neo workerd for me, but scp didn't, it looked like a
>>> t
Hi,
Am Donnerstag 16. Oktober 2008 9:41:33 am schrieb DJDAS:
> I use ~/.profile and it seems to work :)
yes, this works good, thank you. Now I can use aliases :-)
Greetings, Carsten
--
Hier ist mein öffentlicher GPG-Schlüssel:
http://daswaldhorn.funpic.de/gpg.html
On Thu, 16 Oct 2008 14:12:26 +0200, Xavier Cremaschi
<[EMAIL PROTECTED]> wrote:
> papa-piet a écrit :
>>> Fox Mulder schrieb:
>>> I didn't try it with 2008.9 because i only use debian
>>
>> I did.
>> shh into your Neo workerd for me, but scp didn't, it looked like a
>> timeout.
>>
>> Greetings
>
papa-piet a écrit :
>> Fox Mulder schrieb:
>> I didn't try it with 2008.9 because i only use debian
>
> I did.
> shh into your Neo workerd for me, but scp didn't, it looked like a
> timeout.
>
> Greetings
Same behavior here, with bash I can ssh, but not scp.
Here is the end of a scp -vvv with s
Carsten Gerlach ha scritto:
Hi,
Am Dienstag 14. Oktober 2008 3:13:14 am schrieb Joel Newkirk:
On Mon, 13 Oct 2008 22:26:10 +0100, Stroller wrote
Isn't it in .bashrc or .bash_profile?
Stroller.
it is for bash, but OM distros are using an sh/ash repla
Hi,
Am Dienstag 14. Oktober 2008 3:13:14 am schrieb Joel Newkirk:
> On Mon, 13 Oct 2008 22:26:10 +0100, Stroller wrote
> > Isn't it in .bashrc or .bash_profile?
> >
> > Stroller.
>
> it is for bash, but OM distros are using an sh/ash replacement builtin to
> busybox.
~/.bashrc is for bash. What is
> Fox Mulder schrieb:
> I didn't try it with 2008.9 because i only use debian
I did.
shh into your Neo workerd for me, but scp didn't, it looked like a
timeout.
Greetings
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.op
W.Kenworthy wrote:
> On Mon, 2008-10-13 at 22:21 -0400, Joel Newkirk wrote:
>> On Tue, 14 Oct 2008 12:29:59 +1100, "Sarton O'Brien"
>> <[EMAIL PROTECTED]> wrote:
>>> On Tuesday 14 October 2008 12:17:06 Joel Newkirk wrote:
On Mon, 13 Oct 2008 23:21:18 +0200, Fox Mulder <[EMAIL PROTECTED]>
>>> w
On Mon, 2008-10-13 at 22:21 -0400, Joel Newkirk wrote:
> On Tue, 14 Oct 2008 12:29:59 +1100, "Sarton O'Brien"
> <[EMAIL PROTECTED]> wrote:
> > On Tuesday 14 October 2008 12:17:06 Joel Newkirk wrote:
> >> On Mon, 13 Oct 2008 23:21:18 +0200, Fox Mulder <[EMAIL PROTECTED]>
> > wrote:
> >> > If you use
On Tuesday 14 October 2008 13:21:21 Joel Newkirk wrote:
> > vi /etc/passwd?
> >
> > Sarton
>
> (Ok, I'll go sit in the corner for five minutes wearing the stupid hat...
> I already knew that from desktop/server context but for some reason my
> brain just didn't make the connection...)
>
> Thanks.
On Tue, 14 Oct 2008 12:29:59 +1100, "Sarton O'Brien"
<[EMAIL PROTECTED]> wrote:
> On Tuesday 14 October 2008 12:17:06 Joel Newkirk wrote:
>> On Mon, 13 Oct 2008 23:21:18 +0200, Fox Mulder <[EMAIL PROTECTED]>
> wrote:
>> > If you use bash on OM than do it the same way how it is done in a
> normal
>>
On Tuesday 14 October 2008 12:17:06 Joel Newkirk wrote:
> On Mon, 13 Oct 2008 23:21:18 +0200, Fox Mulder <[EMAIL PROTECTED]> wrote:
> > If you use bash on OM than do it the same way how it is done in a normal
> > linux pc. You must "export HISTFILESIZE=1000" to set the number of lines
> > saved to
On Mon, 13 Oct 2008 23:21:18 +0200, Fox Mulder <[EMAIL PROTECTED]> wrote:
> If you use bash on OM than do it the same way how it is done in a normal
> linux pc. You must "export HISTFILESIZE=1000" to set the number of lines
> saved to 1000. Just put this command in an adequate file to be executed
>
On Mon, 13 Oct 2008 22:26:10 +0100, Stroller
<[EMAIL PROTECTED]> wrote:
>
> On 13 Oct 2008, at 22:02, Joel Newkirk wrote:
>
>> How can I enlarge the console command history? I'm used to being
>> able to
>> peruse hundreds of lines of previous commands in
On 13 Oct 2008, at 22:02, Joel Newkirk wrote:
> How can I enlarge the console command history? I'm used to being
> able to
> peruse hundreds of lines of previous commands in bash, the limit to
> ~16
> lines is maddening.
Isn't it in .bashrc or
rote:
> El lun, 13-10-2008 a las 17:02 -0400, Joel Newkirk escribió:
>> How can I enlarge the console command history? I'm used to being able to
>> peruse hundreds of lines of previous commands in bash, the limit to ~16
>> lines is maddening.
>>
>> j
>>
&g
El lun, 13-10-2008 a las 17:02 -0400, Joel Newkirk escribió:
> How can I enlarge the console command history? I'm used to being able to
> peruse hundreds of lines of previous commands in bash, the limit to ~16
> lines is maddening.
>
> j
>
I want to know how to do is too
How can I enlarge the console command history? I'm used to being able to
peruse hundreds of lines of previous commands in bash, the limit to ~16
lines is maddening.
j
___
Openmoko community mailing list
community@lists.openmoko.org
18 matches
Mail list logo
