> > Ignoring the parts of the shared
> > drm/ttm code that would have to be updated the latest
> > drivers/gpu/drm/amd in linux has over 1.5 million lines of code. Which
> > is multiple times larger than the complete OpenBSD kernel source...
>
Despite everything you replied with, Jonathan's
On Tue, Jul 31, 2018 at 05:51:06PM +0100, Peter Kay wrote:
> On 31 July 2018 at 14:22, Christian Weisgerber wrote:
> > On 2018-07-31, Janne Johansson wrote:
> >
> >>> I see autri(4) is disabled by default in an amd64 kernel, probably
> >>> others too, and has been for a very long time.
> >>
> >>
On 31 July 2018 at 14:22, Christian Weisgerber wrote:
> On 2018-07-31, Janne Johansson wrote:
>
>>> I see autri(4) is disabled by default in an amd64 kernel, probably
>>> others too, and has been for a very long time.
>>
>> Seems like it came over with the initial amd64 port from i386, and noone
On 2018-07-31, Janne Johansson wrote:
>> I see autri(4) is disabled by default in an amd64 kernel, probably
>> others too, and has been for a very long time.
>
> Seems like it came over with the initial amd64 port from i386, and noone
> tested it on amd64, so it never got enabled but remained
On Tue, Jul 31, 2018 at 11:43:37AM +0100, Peter Kay wrote:
> I see autri(4) is disabled by default in an amd64 kernel, probably
> others too, and has been for a very long time.
>
> I can't see any notice of why this is so, anyone know?
>
> My secondary system has a Trident 4DWave in it (yes,
Den tis 31 juli 2018 kl 12:47 skrev Peter Kay :
> I see autri(4) is disabled by default in an amd64 kernel, probably
> others too, and has been for a very long time.
>
> I can't see any notice of why this is so, anyone know?
>
>
>
Seems like it came over with the initial amd64 port from i386, and
> Check out HISTCONTROL[1] and ignorespace in particular. Adding something
> along the lines to your ~/.kshrc should do the trick:
>
> HISTCONTROL=ignorespace
> bind -m '^L'='^U clear^J^Y' # note the intentional space before clear
>
> [1] https://man.openbsd.org/ksh#HISTCONTROL
Actually
I see autri(4) is disabled by default in an amd64 kernel, probably
others too, and has been for a very long time.
I can't see any notice of why this is so, anyone know?
My secondary system has a Trident 4DWave in it (yes, it's an old
soundcard. I grabbed it off ebay to work with Arca Noae, as
Thanks all for not making me feel like I opened a flame war can of worms.
I think the ignore dups solution is probably the most sensible for my purposes
from what I have read from all the responses.
Thank you.
Ken
On July 31, 2018 9:09:05 AM GMT+02:00, Solene Rapenne wrote:
>Ken M wrote:
>> OK, so confession 1, I am a long time bash user
>> confession 2 all of my ksh experience is on solaris
>>
>> However in a when in Rome moment I am realizing how much I like ksh
>in openbsd,
>> but one minor thing.
Ken M wrote:
># I wish this worked
># bind -m '^L'=clear'^J';sed -i '$d' $HISTFILE
You need to make sure that the sed command is inside the argument of bind.
Something like this:
bind -m '^L=^Uclear;sed -i \$d "$HISTFILE"^J^Y'
The ^Y is just there to paste back the current line content when you
Ken M wrote:
> OK, so confession 1, I am a long time bash user
> confession 2 all of my ksh experience is on solaris
>
> However in a when in Rome moment I am realizing how much I like ksh in
> openbsd,
> but one minor thing. I don't like how much clear ends up in my history file.
> So
> I am
On Mon, Jul 30, 2018 at 08:11:44PM -0400, Ken M wrote:
> OK, so confession 1, I am a long time bash user
> confession 2 all of my ksh experience is on solaris
>
> However in a when in Rome moment I am realizing how much I like ksh in
> openbsd,
> but one minor thing. I don't like how much clear
13 matches
Mail list logo
