On Wed, Oct 06, 2004 at 09:33:50PM +0200, John Oxley wrote:
I want to extend the disk quota system:
- Implement a user space daemon to control it.
- Pass control from the kernel to the user space daemon.
[skipped]
Is this at all possible, and if so, where should I start looking for
coding
On Monday 04 October 2004 04:04 pm, Jim Durham wrote:
On Monday 04 October 2004 03:06 pm, Doug Russell wrote:
On Mon, 4 Oct 2004, Jim Durham wrote:
The reboots started out happening at 5.15 pm or so. I had them unplug
the server completely from AC and restart it and now it's happening
Can this be some kind of misbehaved hardware watchdog (say, built into
motherboard or network card)?
So, to recap:
Machine reboots at aprox 23hrs 57 minutes of uptime at
~12:30pm.. Upgraded to latest 4.10p3 sources. Still reboots
at 23hrs 57mins, but at different time of day, ~8:15am.
On 4.10-RELEASE with real memory = 10485760 (10240K bytes)
big disc partition:disklabel ad0s1 sectors/unit: 160071597
#size offsetfstype [fsize bsize bps/cpg]
h: 156613309 34582884.2BSD 2048 1638489 # (Cyl. 215*- 9963*)
On a dirty reboot, fsck hangs single
On 2004-10-07 07:20, Marc Balmer [EMAIL PROTECTED] wrote:
1) openlog() must be called before any threads that use syslog() are
started.
2) The first argument to openlog() must not be NULL.
3) The %m Format String must not be used in syslog() calls.
Can (3) this be solved by changing all the
Bernd Walter writes:
On Wed, Oct 06, 2004 at 03:30:05PM +0300, Niki Denev wrote:
Hello everyone!,
The last 1-2 days i've been trying to make some userspace OBEX utilities to
work with a USB based Nokia GSM phone and doing this i discovered something
that confuses me a little:
The phone in
On Thu, Oct 07, 2004 at 04:22:12PM +0300, Niki Denev wrote:
Bernd Walter writes:
On Wed, Oct 06, 2004 at 03:30:05PM +0300, Niki Denev wrote:
If you already an interface driver atatched then ugen fails to attach
the whole device.
well, i think that this can be a problem sometimes.
Yes -
Søren Schmidt wrote:
Roman Kurakin wrote:
Hi,
I have some problems with printing from kernel.
At first I think that my problems was cause I use printf,
but changed all of them to log cause it safe to use from
interrupt handlers. The situation become better but I still
observe system lockup in
Don Lewis wrote:
On 7 Oct, Roman Kurakin wrote:
Hi,
I have some problems with printing from kernel.
At first I think that my problems was cause I use printf,
but changed all of them to log cause it safe to use from
interrupt handlers. The situation become better but I still
observe
Greg 'groggy' Lehey wrote:
On Thursday, 7 October 2004 at 0:31:33 +0400, Roman Kurakin wrote:
Hi,
I have some problems with printing from kernel.
At first I think that my problems was cause I use printf,
but changed all of them to log cause it safe to use from
interrupt handlers. The
Hi Folks,
I'm trying to automate a sequence of BTX commands and I'm hitting some
snags. I've got some minor forth experience, but it isn't enough.
My machine uses the standard bootloader and doesn't present a menu for
the user. By default, the machine boots a standard kernel and fs-image
On Thu, Oct 07, 2004 at 11:00:06AM -0700, Kelly Hall wrote:
Hi Folks,
I'm trying to automate a sequence of BTX commands and I'm hitting some
snags. I've got some minor forth experience, but it isn't enough.
My machine uses the standard bootloader and doesn't present a menu for
the
Hello list,
I have tried and done everything to have this remote debugging working, with
no success.
Any BSD hacker in the bay area that know how to do this, shoot me an email. I
will come meet you with a monetary donation if you can make this work.
Thank you,
Jerry.
Well, I eventually got this SCO system working. But today, some errors
appeared:
505k:unrecover error reading SCSI disk on 0 Dev 1/42
cha = 0 id = 0 1 on = 0
Block 6578
medium error unrecovered read error
HTFS i/o failure occurred while trying to upgrade 1 node 26302 on
HTFS. Dev hd 1/42
Well, I eventually got this SCO system working. But today, some errors
appeared:
505k:unrecover error reading SCSI disk on 0 Dev 1/42
cha = 0 id = 0 1 on = 0
Block 6578
medium error unrecovered read error
HTFS i/o failure occurred while trying to upgrade 1 node 26302 on
HTFS. Dev hd
On Thu, 7 Oct 2004, John Von Essen wrote:
Well, I eventually got this SCO system working. But today, some errors
appeared:
505k:unrecover error reading SCSI disk on 0 Dev 1/42
cha = 0 id = 0 1 on = 0
Block 6578
medium error unrecovered read error
HTFS i/o failure occurred while
16 matches
Mail list logo
