On Friday 12 February 2010 02:02:27 Neil Bothwick wrote:
> > You owe me a year's subscription from your employer for that
> > wise-crack. Postage paid by sender, naturally.
>
> This year, I seem to be working mainly for the Inland Revenue. I'll give
> them your address :P
How odd. I do the same w
On Fri, 12 Feb 2010 00:35:37 +0200, Alan McKinnon wrote:
> > It's not, if it were reset the second and fourth characters would be
> > the same :P
>
> Smartass :-)
You're too kind :)
> You owe me a year's subscription from your employer for that
> wise-crack. Postage paid by sender, naturally.
Iain Buchanan wrote:
> On Fri, 2010-02-12 at 01:58 +0800, ubiquitous1980 wrote:
>
>> With this command or similar, I made my directory and one file in /
>> unreadable:
>>
>> for entry in $(find $HOME); do $entry >> found; done
>>
>
> er... you just executed everything in your home directory
On Friday 12 February 2010 01:18:33 Iain Buchanan wrote:
> On Fri, 2010-02-12 at 01:58 +0800, ubiquitous1980 wrote:
> > With this command or similar, I made my directory and one file in /
> > unreadable:
> >
> > for entry in $(find $HOME); do $entry >> found; done
>
> er... you just executed ever
On Fri, 2010-02-12 at 01:58 +0800, ubiquitous1980 wrote:
> With this command or similar, I made my directory and one file in /
> unreadable:
>
> for entry in $(find $HOME); do $entry >> found; done
er... you just executed everything in your home directory and piped the
output to a file... I thin
On Friday 12 February 2010 00:26:56 Neil Bothwick wrote:
> On Thu, 11 Feb 2010 22:32:44 +0200, Alan McKinnon wrote:
> > > In which case, running reset in the affected terminal should clear
> > > it.
> >
> > Every time I've tried to tell people to do that, they tell me they
> > can't do it because
On Thu, 11 Feb 2010 22:32:44 +0200, Alan McKinnon wrote:
> > In which case, running reset in the affected terminal should clear
> > it.
>
> Every time I've tried to tell people to do that, they tell me they
> can't do it because
>
> %#!*^
>
> obviously is not a valid command.
It's not, if i
On Thursday 11 February 2010 21:47:33 Neil Bothwick wrote:
> On Thu, 11 Feb 2010 20:18:29 +0200, Alan McKinnon wrote:
> > Switch to a text console (Ctrl-Alt-Fx) and ls things there, perhaps the
> > garbage dumped to the screen in your for simply upset the terminal
> > emulation.
>
> In which case,
On Thursday 11 February 2010 18:18:29 Alan McKinnon wrote:
> perhaps the garbage dumped to the screen in your for simply upset the
> terminal emulation.
...in which case, perhaps typing RESET in the terminal will help.
--
Rgds
Peter.
On Thu, 11 Feb 2010 20:18:29 +0200, Alan McKinnon wrote:
> Switch to a text console (Ctrl-Alt-Fx) and ls things there, perhaps the
> garbage dumped to the screen in your for simply upset the terminal
> emulation.
In which case, running reset in the affected terminal should clear it.
--
Neil B
On Thursday 11 February 2010 19:58:25 ubiquitous1980 wrote:
> With this command or similar, I made my directory and one file in /
> unreadable:
>
> for entry in $(find $HOME); do $entry >> found; done
>
> the same of output for ls is similar:
>
> -k?x?B?{U?I?3s??
> ???N???Q
> ?ܝw?Ϭw?
With this command or similar, I made my directory and one file in /
unreadable:
for entry in $(find $HOME); do $entry >> found; done
the same of output for ls is similar:
-k?x?B?{U?I?3s??
???N???Q
?ܝw?Ϭw??9c̃}}WzǸ??t
Ƿ~???
?^8?O?
?^????cB?f???vV?!?@
???8%??{??8?y
12 matches
Mail list logo