You wrote:
> > I need to know the exact format of the /proc/*/cmdline of
> > FreeBSD. Actually I'm using 4.1 and I have discovered that at the
> > end of cmdline file there are always 2 NULL characters.
>
> I'm not seeing that on my 4.x-stable system from about a month ago:
Sorry, I just found
Ciao.
I need to know the exact format of the /proc/*/cmdline of FreeBSD. Actually
I'm using 4.1 and I have discovered that at the end of cmdline file there are
always 2 NULL characters.
Is this a standard behaviour of FBSD cmdline ? From 3.0 is it changed or
it will change ?
Thanks.
--
Bye,
On Sat, 08 Apr 2000, Mike Heffner wrote:
> | I'm testing the __builtin_apply() to make a patch to GNUstep, but I'm
> | getting
> | in troubles.
>
> Since you're on the subject, there are also two other bugs with
> __builtin_apply() in FBSD that I know of.
Always better... :(
> The easy hack to
You wrote:
> Try
> 1:da(3,a)/boot/loader
Maybe I'm a bit boring but it does not work ! :(
After some tests, these are the results:
1:da(0 to 3,a)/boot/loader
Invalid label
Invalid label
No /boot/loader
2:da(0 to 3,a)/boot/loader (NEXTSTEP disk)
LBA error (don't remember correctly)
Ciao!
I'm testing the __builtin_apply() to make a patch to GNUstep, but I'm getting
in troubles.
rey:/tmp/tmp> gcc -v
Using builtin specs.
gcc version 2.95.2 19991024 (release)
rey:/tmp/tmp> uname -a
FreeBSD rey.procom2.it 4.0-STABLE FreeBSD 4.0-STABLE #0: Fri Apr 7 01:02:03
CEST 2000
[EMA
You wrote:
> If
>
> 1:da(1,a)/boot/loader
>
> does not work, what is in the /boot directory on da1?
rey:/usr/home/mirko> list /boot
total 514
drwxr-xr-x 3 root wheel 512 Apr 7 02:02 ./
drwxr-xr-x 27 root wheel1024 Apr 7 11:29 ../
-r--r--r-- 1 root wheel 512 Apr 7 02:02
You wrote:
> Try 1:da(1,a)/boot/loader
>
>
> :(,)
>1 da 1 a/boot/loader
It does not work:
Invalid label
Invalid label
No /boot/loader
FYI I have an AHA 2940UW with 2 hd:
- ID 0: NEXTSTEP
- ID 1: FreeBSD and others
To boot FreeBSD I change the boot ID in t
On Fri, 7 Apr 2000, "Thomas D. Dean" wrote:
> It was caused by my booting the kernel directly.
>
> 0:da(0,a)/kernel
>
> Using
>
> 0:da(0,a)/boot/loader
>
> cures the symptoms.
But here it doesn't seem to work... :(
0:da(1,a)/boot/loader
loaded...
ok boot
can't load 'kernel'
no bootable kerne
You wrote:
> > rey:/usr/home/mirko> top
> > top: nlist failed
> > rey:/usr/home/mirko> vmstat
> > vmstat: undefined symbols:
> > _cp_time _kmemstatistics _bucket _zlist
>
> I heard rumors that this problem occurs when you doesn't use /boot/loader to
> boot your
> kernel. If so, it is bad practi
Ciao!
I've upgraded my system from 3.4 to 4.0-stable last night, with new /dev
and new /etc but now I'm getting these errors:
rey:~/Sources/gnustep/core/base> uname -a
FreeBSD rey.procom2.it 4.0-STABLE FreeBSD 4.0-STABLE #0: Fri Apr 7 01:02:03
CEST 2000
[EMAIL PROTECTED]:/mnt/amy/lpub/free
Ciao.
As stated in gdb mlist, gdb 5.0 is on the way but it hasn't support for
freebsd-elf in
the package. Is there anyone that could explain me why ?
Thanks.
---
Bye,
Mirko <[EMAIL PROTECTED]> (NeXTmail, MIME)
<[EMAIL PROTECTED]>
To Unsubscribe: send mail to [EMA
Ciao.
Is it possible to apply the gnu/17433 patch before the 4.0-STABLE ?
Related to this I'm excepting some strange behaviour with prgs linked with libc_r
under 3.4 and I would like to know if they are also in 4.0.
1. In a prg linked with libc I can use a local buffer up to 65 MB, but if the s
12 matches
Mail list logo
