Bartosz Giza wrote:
I have found quite interesting feature on one of router that lately i have
taken to administer.
What i knew was that file /var/run/dmesg.boot holds data from kernel buffer
that is taken right after file system(s) are mounted.
Lately i have found that one router
Jeremy Chadwick wrote:
Oliver Fromme wrote:
Upon a reboot, the kernel is usually loaded to the same
physical addresses in RAM where it was before, so the
dmesg buffer will be at the same location, too (unless
you built a new kernel, of course). So all the contents
from before
On Feb 22, 2008, at 02:25 , Jeremy Chadwick wrote:
[...]
Interesting tidbit: We have one production machine which when booted
into single-user via serial console for a world install, retains all
of
the output from that single-user session even once rebooted and
brought
back into
On Fri, Feb 22, 2008 at 09:28:35AM +0100, Oliver Fromme wrote:
Bartosz Giza wrote:
I have found quite interesting feature on one of router that lately i have
taken to administer.
What i knew was that file /var/run/dmesg.boot holds data from kernel
buffer
that is taken right after
On Fri, Feb 22, 2008 at 10:52:54AM +0100, Oliver Fromme wrote:
Jeremy Chadwick wrote:
Oliver Fromme wrote:
Upon a reboot, the kernel is usually loaded to the same
physical addresses in RAM where it was before, so the
dmesg buffer will be at the same location, too (unless
you
Jeremy Chadwick wrote:
Oliver Fromme wrote:
[...]
Either way, it's a feature with major security implications. So, for
those of us who are concerned about master.passwd changes via
mergemaster being stuffed into msgbuf, how do we disable said feature?
(Before answering, see below as
On Fri, Feb 22, 2008 at 11:31:36AM +0100, Oliver Fromme wrote:
If you insist on writing a patch, then please make it
default off.
rink@ just provided one, and it does default to off. I fully agree with
defaulting it to off as well; those of us that want it on can set it as
such in loader.conf.
On Fri, Feb 22, 2008 at 02:46:31AM -0800, Jeremy Chadwick wrote:
I'll try out said patch this weekend. Assuming it works, and does get
committed, I'll be more than happy to submit a PR along with a patch to
update the loader.8 manpage, documenting kern.ignore_old_msgbuf.
Sounds good to me.
Hi Guys,
Does usleep work for you? i just saw it is implemented over nanosleep
which
passes a struct timeval to select.
on my system, one of instance for usleep and select sleep value.
provided
(sec).(microsec) = select (sleep) usleep (sleep)
0.00 = select: 0.04 usleep:
Hi,
How does dual port star fire nic card time stamp? Is the sheduling
round
robin. if it is, there can be chances, a frame comes later than other can get
lesser timestamp.
--
Thanks
Sharad Chandra
___
freebsd-hackers@freebsd.org mailing
On Fri, Feb 22, 2008 at 02:09:24AM -0800, Jeremy Chadwick wrote:
Maybe I should look into writing a patch that does in fact clear the
buffer immediately before reboot, and tie it to a sysctl.
I suggest just making a loader tunable to do this. I think the following
should do it (untested):
---
On Fri, Feb 22, 2008 at 11:31:36AM +0100, Oliver Fromme wrote:
If you insist on writing a patch, then please make it
default off.
rink@ just provided one, and it does default to off. I fully agree with
defaulting it to off as well; those of us that want it on can set it as
such in
Am Freitag, 22. Februar 2008 11:28:42 schrieb Sharad Chandra:
Does usleep work for you? i just saw it is implemented over nanosleep
which passes a struct timeval to select.
Quoting from POSIX:
The usleep() function will cause the calling thread to be suspended from
execution until
Sharad,
Additionally, this C routine is considered obsolete (unlike shell
command by the same name). The interaction of this function with SIGALRM
and other timer functions such as sleep(), alarm(), setitimer(), and
nanosleep() is unspecified. Additionally, its use in multi-threaded
programs can
on 20/02/2008 20:33 Andriy Gapon said the following:
on 19/02/2008 23:42 Andriy Gapon said the following:
The last result most probably means that RTC IRQ was not the interrupt
to wake CPU from sleeping state.
The first possibility that comes to mind is that on this particular
hardware RTC
It was suggested that this list may be a better place to post my
request.
I have started work on a WinBond chip driver (currently only the
W83627HF chip) to provide access to the chips watchdog timer and
sensors. I have never written a driver before and my C is rather
rusty so I figured
F A S T T R A C K D E G R E E P R O G R A M
Obtain the degree you deserve, based on your present knowledge and
life experience.
A prosperous future, money earning power, and the Admiration of all.
Degrees from an Established, Prestigious, Leading Institution.
Your Degree will
On Fri, Feb 22, 2008 at 05:14:47PM +0200, Andrew Pogrebennyk wrote:
Additionally, this C routine is considered obsolete
Can you provide a reference for this please.
(unlike shell command by the same name).
I've never seen a shell function called usleep. Which shell are you using?
The
I'll handle this. Thanks!
On Feb 22, 2008, at 4:04 PM, Andriy Gapon wrote:
on 20/02/2008 20:33 Andriy Gapon said the following:
on 19/02/2008 23:42 Andriy Gapon said the following:
The last result most probably means that RTC IRQ was not the
interrupt
to wake CPU from sleeping state.
The
Marcel Moolenaar wrote:
[Oliver explains bitblit, then Marcel explains bitblt.]
OK, so we mean the same thing, bascially.
The higher lever TTY code simply calls bitblt with a
bit mask of the glyph to be printed and doesn't need to
know about the details of the display. As such, simple
On Feb 22, 2008, at 12:39 PM, Oliver Fromme wrote:
At the same time the VGA driver is abstracted from any
high-level details, like fonts or character sets. This
means that it's easy to write an accelerated driver for
some graphics hardware. You simply implement mode
setting and bitblt and
On Fri, 22 Feb 2008, Heiko Wundram (Beenic) wrote:
Am Freitag, 22. Februar 2008 11:28:42 schrieb Sharad Chandra:
Does usleep work for you? i just saw it is implemented over nanosleep
which passes a struct timeval to select.
Quoting from POSIX:
The usleep() function will cause the
On Fri, Feb 22, 2008 at 09:53:09AM -0600, David Duchscher wrote:
It was suggested that this list may be a better place to post my request.
I have started work on a WinBond chip driver (currently only the W83627HF
chip) to provide access to the chips watchdog timer and sensors. I have
never
Please find enclosed a patch that implements -lname and -ilname in
FreeBSD's find. There's some shell scripts that insist on these gnu
findtools features.
Comments?
Warner
Index: find.1
===
RCS file:
Sorry to be lame and follow up to my original email, but Ruslan was
way too quick to give me feedback :-)
I also did a few more of the really easy ones, and added a list of
ones that we haven't implemented yet.
Comments?
Warner
Index: extern.h
25 matches
Mail list logo
