On August 27, 2017 6:28:12 PM GMT+02:00, Alessandro DE LAURENZIS
wrote:
>Folks,
>
>On Sat 12/08/2017 18:36, Alessandro DE LAURENZIS wrote:
>>Dear misc@ readers,
>>
>>I'm lost with the subject... From the man page I see that, differently
>
>>from standard ksh, OpenBSD implementation by default d
On Sun, Aug 27, 2017 at 07:18:55PM -0500, Kris Katterjohn wrote:
> On Mon, Aug 21, 2017 at 09:04:33AM +0200, Gilles Chehade wrote:
> > On Sat, Aug 19, 2017 at 04:20:31PM -0500, Kris Katterjohn wrote:
> > > On Fri, Aug 18, 2017 at 09:24:33AM -0700, Chris Cappuccio wrote:
> > > > This looks correct.
Am 27. August 2017 23:43:38 MESZ schrieb Jeremie Courreges-Anglas
:
>On Sun, Aug 27 2017, Florian Ermisch
>wrote:
>> Hi Jeremie,
>>
>> Am 27. August 2017 17:57:57 MESZ schrieb Jeremie Courreges-Anglas
>:
>>>On Sun, Aug 27 2017, Jan Stary wrote:
This is current/amd64. I am using ksh(1) as
On Mon, Aug 21, 2017 at 09:04:33AM +0200, Gilles Chehade wrote:
> On Sat, Aug 19, 2017 at 04:20:31PM -0500, Kris Katterjohn wrote:
> > On Fri, Aug 18, 2017 at 09:24:33AM -0700, Chris Cappuccio wrote:
> > > This looks correct. Also, there's more:
> >
> > Thanks for looking and catching what I misse
On Sun, Aug 27 2017, Florian Ermisch wrote:
> Hi Jeremie,
>
> Am 27. August 2017 17:57:57 MESZ schrieb Jeremie Courreges-Anglas
> :
>>On Sun, Aug 27 2017, Jan Stary wrote:
>>> This is current/amd64. I am using ksh(1) as a shell.
>>> Using ^R opens a search in the command history.
>>> However, wi
Hi Jeremie,
Am 27. August 2017 17:57:57 MESZ schrieb Jeremie Courreges-Anglas
:
>On Sun, Aug 27 2017, Jan Stary wrote:
>> This is current/amd64. I am using ksh(1) as a shell.
>> Using ^R opens a search in the command history.
>> However, with 'export EDITOR=vi', pressing ^R
>> just literarily ty
No idea about ^R, but typing ESC /pattern in vi mode looks for
earlier commands containing pattern ...
On Sun, Aug 27, 2017 at 05:02:36PM +0200, Jan Stary wrote:
> This is current/amd64. I am using ksh(1) as a shell.
> Using ^R opens a search in the command history.
> However, with 'export EDITOR
Folks,
On Sat 12/08/2017 18:36, Alessandro DE LAURENZIS wrote:
Dear misc@ readers,
I'm lost with the subject... From the man page I see that, differently
from standard ksh, OpenBSD implementation by default do *not* send
SIGHUP signals to child processes when a SIGHUP is received by the
pare
On Sun, Aug 27 2017, Jan Stary wrote:
> This is current/amd64. I am using ksh(1) as a shell.
> Using ^R opens a search in the command history.
> However, with 'export EDITOR=vi', pressing ^R
> just literarily types '^R' and does not open
> the history search. Is that expected?
EDITOR=vi puts the
This is current/amd64. I am using ksh(1) as a shell.
Using ^R opens a search in the command history.
However, with 'export EDITOR=vi', pressing ^R
just literarily types '^R' and does not open
the history search. Is that expected?
Jan
On Sun, Aug 27, 2017 at 03:04:58PM +0200, Remi Locherer wrote:
> Hi,
>
> recently I bought a Asus UX390. It's very small and light notebook
> (less than 1 kg!). OpenBSD runs fine on it. Only its touchpad is not
> supported.
>
> In the dmesg this is shown (full dmesg at the bottom):
> "ELAN1301" a
Tell us about the webmail…. ;)
Regards
Patrick
> On Aug 27, 2017, at 5:41 AM, leo_...@volny.cz wrote:
>
> *curses* this pos webmail poop hid from me that that was a private msg,
> so I sent to the list. grrr!
>
> another reason to drop the matter, though :/
>
>--schaafuit.
>
*curses* this pos webmail poop hid from me that that was a private msg,
so I sent to the list. grrr!
another reason to drop the matter, though :/
--schaafuit.
choc...@jtan.com wrote:
> Excuse me, I apologise to butt in on what clearly of great importance to
> the future development of OpenBSD but I've not really been paying this
> argument much attention and I want to clear something up.
>
> Is this farce all because you're upset that a machine insulted
Hi Florian,
On Sun 27/08/2017 08:56, Florian Ermisch wrote:
[...]
In case nobody pointed this out off-list:
You should add your fileserver's IP to to
your /etc/hosts so its name can be
resolved during boot when there's no
DNS available (or you're outside your
LAN).
Great! I was giving up on th
Hi Florian,
On Sun 27/08/2017 08:56, Florian Ermisch wrote:
[...]
In case nobody pointed this out off-list:
You should add your fileserver's IP to to
your /etc/hosts so its name can be
resolved during boot when there's no
DNS available (or you're outside your
LAN).
Great! I was giving up on th
Hi Florian,
On Sun 27/08/2017 08:56, Florian Ermisch wrote:
Hi Alessandro,
[...]
In case nobody pointed this out off-list:
You should add your fileserver's IP to to
your /etc/hosts so its name can be
resolved during boot when there's no
DNS available (or you're outside your
LAN).
Great! I wa
leo_...@volny.cz writes:
>
> Lesson: never configure a public machine to misbehave. People might be
> trying to get work done and take offense if they're stopped in that rude
> manner (just a huge delay, 'permission denied' and closing the connection
> would've IMO certainly sufficed).
Excuse me,
I wrote:
> Look at the uproar it created here...
Okay *sigh*, I can see how this can be misinterpreted; what I meant was
that someone offended (in this case somewhat unwittingly) created the
uproar, specifically, me.
I'm never too good to shoot flak at myself, don't worry...
--schaafuit.
Hi,
bytevolc...@safe-mail.net wrote:
> Just a tip from an outsider.
Those are always more than welcome :)
> I would suggest you show a little sympathy for those who are getting
> spammed by useless Nigerian scammers, cryptovirus authors, and the
> like, claiming to be some kind of "Head of Finan
20 matches
Mail list logo
