From: Andrei Ivanov <andrei.ivanov@ines.ro>
To: Helge Hafting <helgehaf@aitel.hist.no>
Cc: linux-kernel@vger.kernel.org
Subject: Re: oops in 2.5.68-mm1
Date: Sun, 20 Apr 2003 19:25:43 +0300 (EEST) [thread overview]
Message-ID: <Pine.LNX.4.50L0.0304201924490.1931-100000@webdev.ines.ro> (raw)
In-Reply-To: <20030420161306.GA16656@hh.idb.hist.no>
It may be so, but I don't think the kernel should oops...
On Sun, 20 Apr 2003, Helge Hafting wrote:
> On Sun, Apr 20, 2003 at 06:58:33PM +0300, Andrei Ivanov wrote:
> [...]
> > -r-------- 1 root root 48281 Apr 11 21:05 Cats & Dogs (RO).txt
> > -r-------- 1 root root 730341376 Apr 11 21:04 Cats And Dogs.avi
> >
> > I typed less Cats<tab>, and then &<tab>, and here it was stuck, and the
> > kernel oopsed. If I type less Cats<tab>, and then \&<tab>, it works, but
> > without the \ in front of the &, the shell gets stuck in D state.
>
> Typing
> <any command> &<TAB>
> gives the shell and the fs some work to do. The "&" ends one
> command and starts a new one (similiar to ";") so typing
> nothing more after "&" and pressing <TAB> makes the shell search the entire
> path and consider all the commands available.
> (Press tab some more times and see the list, 2078 possibilities
> in my case. :-) This sort of thing can easily
> take some time (in D state) if your PATH includes network drives.
>
> Helge Hafting
>
prev parent reply other threads:[~2003-04-20 16:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-20 15:48 Andrei Ivanov
2003-04-20 15:58 ` Andrei Ivanov
2003-04-20 16:13 ` Helge Hafting
2003-04-20 16:25 ` Andrei Ivanov [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.50L0.0304201924490.1931-100000@webdev.ines.ro \
--to=andrei.ivanov@ines.ro \
--cc=helgehaf@aitel.hist.no \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®