Seems that mdmfs stopped working recently (probably because
of GEOM related changes). One possible fix is to label the
md and newfs the thusly created c partition.
This requires running /sbin/disklabel, which didn't have an
entry in paths.h.
Any objections against me committing the follwoing
On 2003-06-09 19:52 +, Tinderbox [EMAIL PROTECTED] wrote:
cc -c -O -pipe -mcpu=pentiumpro -Wall -Wredundant-decls -Wnested-externs
-Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual
-fformat-extensions -std=c99 -nostdinc -I- -I.
On 2003-06-18 20:41 -0700, Don Lewis [EMAIL PROTECTED] wrote:
On 18 Jun, Chris Shenton wrote:
Don Lewis [EMAIL PROTECTED] writes:
Try the very untested patch below ...
RCS file: /home/ncvs/src/sys/kern/uipc_syscalls.c,v
retrieving revision 1.150
Try the very untested patch below
On 2003-06-19 08:13 -0700, Don Lewis [EMAIL PROTECTED] wrote:
In PR kern/46652 I reported, that DEBUG_VFS_LOCKS does never
check the **vpp parameters. A patch is included in the PR and
it does generate the missing tests.
I asked for feedback on the hackers mail list (IIRC), but did
On 2003-07-14 20:33 -0400, Scott Robbins [EMAIL PROTECTED] wrote:
I installed 5.1 RELEASE on a box with an ASUS A7A266 motherboard. Not
having done enough reading, I had put device apm in the kernel and added
apmd_enable=YES to /etc/rc.conf.
The box wouldn't turn off in response to
On 2003-11-26 08:54 -0600, Thomas T. Veldhouse [EMAIL PROTECTED] wrote:
I have had the problem listed in the article below for years (4.x and 5.x).
I have been unable to use my Lexmark Optra 312 (USB) with FreeBSD (w/cups)
because there is so often a page of trash printed before a print job
I have just re-built world and kernel and get a boot failure:
panic: free: guard2 fail @ 0x412f6c50 + 513 from unknown:0
--> Press a key in the console to reboot <--
I'll try to boot from a memory stick, now, but wanted to let
others know, that there seems to be a problem with the latest
UMA
Am 05.02.20 um 10:14 schrieb Toomas Soome:
>> On 5. Feb 2020, at 11:12, Stefan Eßer > <mailto:s...@freebsd.org>> wrote:
>>
>> I have just re-built world and kernel and get a boot failure:
>>
>> panic: free: guard2 fail @ 0x412f6c50 + 513 from unknown:0
&
Am 05.02.20 um 12:02 schrieb Toomas Soome:
> Fixed, sorry about the mess:)
Hi Toomas,
thank you very much for the quick fix!
My system is healthy again ;-)
Best regards, STefan
___
freebsd-current@freebsd.org mailing list
Am 15.02.20 um 15:40 schrieb Stefan Eßer:
> Am 15.02.20 um 14:47 schrieb Mateusz Guzik:
>> On 2/15/20, Stefan Eßer wrote:
>>> Hi Mateusz,
>>>
>>> your optimization of systrace checks has made KDTRACE_HOOKS mandatory,
>>> since there are unpro
Am 15.02.20 um 14:47 schrieb Mateusz Guzik:
> On 2/15/20, Stefan Eßer wrote:
>> Hi Mateusz,
>>
>> your optimization of systrace checks has made KDTRACE_HOOKS mandatory,
>> since there are unprotected assignments to systrace_enabled (which is
>> defined
Am 15.02.20 um 18:45 schrieb Konstantin Belousov:
> On Sat, Feb 15, 2020 at 03:58:06PM +0100, Stefan Eßer wrote:
>> Am 15.02.20 um 15:40 schrieb Stefan Eßer:
>>> Am 15.02.20 um 14:47 schrieb Mateusz Guzik:
>>>> On 2/15/20, Stefan Eßer wrote:
>>>>&
Am 03.07.20 um 17:24 schrieb O. Hartmann:
> Hello list,
>
> running some scripts caluclating via bc() the expression shown below:
>
> bc -e '6582031 - 1048576 - 0 - 409600 - 1024 - 40 - 4096' -e quit
The bc in -CURRENT has been replaced by a new implementation.
It seems there is one deviation
Am 05.07.20 um 11:25 schrieb Stefan Eßer:
> Am 04.07.20 um 11:50 schrieb Hartmann, O.:
> The author of the new bc has changed the semantics of -e to those
> of the FreeBSD version, since he is very interested in providing
> an implementation that covers all relevant GNU and Free
Am 04.07.20 um 11:50 schrieb Hartmann, O.:
> On Fri, 3 Jul 2020 17:58:27 +0200
> Stefan Eßer wrote:
>> From the bc man-page:
>>
>> The quit statement causes bc(1) to quit, even if it is on a branch
>> that will not be executed (it is a compile-time command).
>>
15 matches
Mail list logo
