On Sat, Nov 25, 2000 at 07:39:33AM -0800, Cy Schubert - ITSD Open Systems Group
scribbled:
| In message <1050.974925641@critter>, Poul-Henning Kamp writes:
| >
| > The attached patch is a "proof-of-concept" on which I would like
| > to get some comments:
| >
| > It bugs me big time that the outpu
"David O'Brien" <[EMAIL PROTECTED]> writes:
> On Fri, Nov 24, 2000 at 01:08:37AM +0100, Cyrille Lefevre wrote:
> > > Its in the scrollback buffer.
> >
> > and how do you access the scroll-back buffer if you are not front to the
> > console (read remote) ?
>
> Do you mean remotely loged in acros
Alexander Leidinger <[EMAIL PROTECTED]> writes:
> On 24 Nov, Cyrille Lefevre wrote:
>
> >> >> The attached patch is a "proof-of-concept" on which I would like
> >> >> to get some comments:
> >> >
> >> > I'm only a moronic user, but this would make my life easier. My machine
> >> > switches in
On Fri, Nov 24, 2000 at 01:08:37AM +0100, Cyrille Lefevre wrote:
> > Its in the scrollback buffer.
>
> and how do you access the scroll-back buffer if you are not front to the
> console (read remote) ?
Do you mean remotely loged in across the network, or a serial [remote]
console? If you mean t
In message <[EMAIL PROTECTED]>, Chuck Paterson writes:
>
> Is there reason to believe that we won't have dead lock
>problems from the M_WAITOK? It seems like that if anything in
>the path needed to full fill the malloc needs to log there
>is a problem.
We don't otherwise treat the /dev/cons
Is there reason to believe that we won't have dead lock
problems from the M_WAITOK? It seems like that if anything in
the path needed to full fill the malloc needs to log there
is a problem.
Chuck
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the
In message <1050.974925641@critter>, Poul-Henning Kamp writes:
>
> The attached patch is a "proof-of-concept" on which I would like
> to get some comments:
>
> It bugs me big time that the output from /etc/rc and all other output
> to /dev/console is volatile and lost once it scrolls of your con
On 24 Nov, Cyrille Lefevre wrote:
>> >> The attached patch is a "proof-of-concept" on which I would like
>> >> to get some comments:
>> >
>> > I'm only a moronic user, but this would make my life easier. My machine
>> > switches into 132x43 on startup, and I always lose the output. So this
>>
Alexander Leidinger <[EMAIL PROTECTED]> writes:
> On 22 Nov, Ashley Penney wrote:
>
> >> The attached patch is a "proof-of-concept" on which I would like
> >> to get some comments:
> >
> > I'm only a moronic user, but this would make my life easier. My machine
> > switches into 132x43 on star
On 22 Nov, Ashley Penney wrote:
>> The attached patch is a "proof-of-concept" on which I would like
>> to get some comments:
>
> I'm only a moronic user, but this would make my life easier. My machine
> switches into 132x43 on startup, and I always lose the output. So this
Its in the scrollb
< said:
> In message <[EMAIL PROTECTED]>, Garrett Wollman write
>> They can try, but by the time they do the console has already been
>> revoke()d, so they no longer have access to the real console.
> I don't know what you consider "the real console", but opening
> "/dev/console" and barfing on
In message <[EMAIL PROTECTED]>, Garrett Wollman write
s:
>< said:
>
>> Another particular thing I remember was that some syslog-challenged
>> daemons whine on /dev/console long after /etc/rc has finished.
>
>They can try, but by the time they do the console has already been
>revoke()d, so they no
< said:
> Another particular thing I remember was that some syslog-challenged
> daemons whine on /dev/console long after /etc/rc has finished.
They can try, but by the time they do the console has already been
revoke()d, so they no longer have access to the real console.
I've thought about wri
In message <[EMAIL PROTECTED]>, Dan Nelson writes:
>In the last episode (Nov 22), Poul-Henning Kamp said:
>> The attached patch is a "proof-of-concept" on which I would like to
>> get some comments:
>>
>> It bugs me big time that the output from /etc/rc and all other output
>> to /dev/console is
In the last episode (Nov 22), Poul-Henning Kamp said:
> The attached patch is a "proof-of-concept" on which I would like to
> get some comments:
>
> It bugs me big time that the output from /etc/rc and all other output
> to /dev/console is volatile and lost once it scrolls of your console.
SCO l
On Wed, Nov 22, 2000 at 09:40:41PM +0100, Poul-Henning Kamp said:
>
> The attached patch is a "proof-of-concept" on which I would like
> to get some comments:
I'm only a moronic user, but this would make my life easier. My machine
switches into 132x43 on startup, and I always lose the output.
The attached patch is a "proof-of-concept" on which I would like
to get some comments:
It bugs me big time that the output from /etc/rc and all other output
to /dev/console is volatile and lost once it scrolls of your console.
It particular bugs me for systems which are configured with a modem
17 matches
Mail list logo
