[I'm catching up on a bunch of FreeBSD mail since being out on vacation, so
perhaps I've missed the essence of this thread..]
I've also had the desire to capture the output produced when /etc/rc is
run for all the reasons mentioned. I always thought that perhaps init
would simply capture stdou
[I'm catching up on a bunch of FreeBSD mail since being out on vacation, so
perhaps I've missed the essence of this thread..]
I've also had the desire to capture the output produced when /etc/rc is
run for all the reasons mentioned. I always thought that perhaps init
would simply capture stdout
> "Rodney W. Grimes" wrote:
>
> > It dawned on me what can be done. Look, we get all the kernel printf's
> > from the dmesg output saved in a buffer and pull that out later with
> > syslog, looks like we could just slip a pipe fitting into /dev/console
> > that copies all it's output into the me
> "Rodney W. Grimes" wrote:
>
> > It dawned on me what can be done. Look, we get all the kernel printf's
> > from the dmesg output saved in a buffer and pull that out later with
> > syslog, looks like we could just slip a pipe fitting into /dev/console
> > that copies all it's output into the mes
"Rodney W. Grimes" <[EMAIL PROTECTED]> writes:
> > No. The scrollback may be too short (especially after an fsck of a
> > large filesystem after a crash), and it may even be empty (if you put
> > something like VESA_132x60 in allscreens_flags in rc.conf)
> We can tune the size of the scroll back b
"Rodney W. Grimes" writes:
> > No. The scrollback may be too short (especially after an fsck of a
> > large filesystem after a crash), and it may even be empty (if you put
> > something like VESA_132x60 in allscreens_flags in rc.conf)
> We can tune the size of the scroll back buffer can't we?
Yes
"Rodney W. Grimes" wrote:
> It dawned on me what can be done. Look, we get all the kernel printf's
> from the dmesg output saved in a buffer and pull that out later with
> syslog, looks like we could just slip a pipe fitting into /dev/console
> that copies all it's output into the mesgbuf as wel
"Rodney W. Grimes" wrote:
> It dawned on me what can be done. Look, we get all the kernel printf's
> from the dmesg output saved in a buffer and pull that out later with
> syslog, looks like we could just slip a pipe fitting into /dev/console
> that copies all it's output into the mesgbuf as well
> "Rodney W. Grimes" wrote:
> >
> > > [moving to -hackers]
> > [I'm going to loose the rest of this thread since I am not on hackers :-(]
>
> Shame on you. :)
The volume of mail became too high for my time a long while ago. :-(
> > > "Rodney W. Grimes" <[EMAIL PROTECTED]> writes:
>
> >
> "Rodney W. Grimes" wrote:
> >
> > > [moving to -hackers]
> > [I'm going to loose the rest of this thread since I am not on hackers :-(]
>
> Shame on you. :)
The volume of mail became too high for my time a long while ago. :-(
> > > "Rodney W. Grimes" writes:
>
> > Actually I would li
"Rodney W. Grimes" wrote:
>
> > [moving to -hackers]
> [I'm going to loose the rest of this thread since I am not on hackers :-(]
Shame on you. :)
> > "Rodney W. Grimes" <[EMAIL PROTECTED]> writes:
> Actually I would like _all_ the output from /etc/rc* to be avaliable
> after boot.
"Rodney W. Grimes" wrote:
>
> > [moving to -hackers]
> [I'm going to loose the rest of this thread since I am not on hackers :-(]
Shame on you. :)
> > "Rodney W. Grimes" writes:
> Actually I would like _all_ the output from /etc/rc* to be avaliable
> after boot.
One of the th
> "Rodney W. Grimes" <[EMAIL PROTECTED]> writes:
> > > One thing I'd like very much, though, would be to have the output of
> > > fsck -p logged somehow [...]
> > Actually I would like _all_ the output from /etc/rc* to be avaliable
> > after boot. It should be in the syscons scroll back buffer, [
> "Rodney W. Grimes" writes:
> > > One thing I'd like very much, though, would be to have the output of
> > > fsck -p logged somehow [...]
> > Actually I would like _all_ the output from /etc/rc* to be avaliable
> > after boot. It should be in the syscons scroll back buffer, [...]
>
> No. The sc
"Rodney W. Grimes" <[EMAIL PROTECTED]> writes:
> > One thing I'd like very much, though, would be to have the output of
> > fsck -p logged somehow [...]
> Actually I would like _all_ the output from /etc/rc* to be avaliable
> after boot. It should be in the syscons scroll back buffer, [...]
No.
"Rodney W. Grimes" writes:
> > One thing I'd like very much, though, would be to have the output of
> > fsck -p logged somehow [...]
> Actually I would like _all_ the output from /etc/rc* to be avaliable
> after boot. It should be in the syscons scroll back buffer, [...]
No. The scrollback may b
> [moving to -hackers]
[I'm going to loose the rest of this thread since I am not on hackers :-(]
>
> "Rodney W. Grimes" <[EMAIL PROTECTED]> writes:
> > So when can we see this commited
>
> Already done (-CURRENT only). I've had requests (notably from Yan
> Koum) to backport it to -STABLE,
> [moving to -hackers]
[I'm going to loose the rest of this thread since I am not on hackers :-(]
>
> "Rodney W. Grimes" writes:
> > So when can we see this commited
>
> Already done (-CURRENT only). I've had requests (notably from Yan
> Koum) to backport it to -STABLE, but I won't do it so
[moving to -hackers]
"Rodney W. Grimes" <[EMAIL PROTECTED]> writes:
> So when can we see this commited
Already done (-CURRENT only). I've had requests (notably from Yan
Koum) to backport it to -STABLE, but I won't do it so close to a
release.
> the only
[moving to -hackers]
"Rodney W. Grimes" writes:
> So when can we see this commited
Already done (-CURRENT only). I've had requests (notably from Yan
Koum) to backport it to -STABLE, but I won't do it so close to a
release.
> the only thing I would like
>
20 matches
Mail list logo
