> I had checked ftp.stardiv.com and found that there are several star office 5.0
> under the directory /pub/so5. I would like to know which one works with
> -current.
The different "versions" are really different languages. "01" is
English. Others are German, French, and __.
--
-- David
In message , Conrad Sabatier writes:
>
>On 04-Feb-99 Jaroslaw Bazydlo wrote:
>> After yesterdays 'make world' I am having such warnings:
>>
>> FreeBSD 4.0-CURRENT #0: Thu Feb 4 17:19:09 GMT 1999
>> jar...@ent.freebsd.org.pl:/usr/src/sys/compile/ENT
>> [...]
>> ep0 at 0x300-0x30f irq 10 on isa
Joao Carlos Mendes Luis wrote:
>
> 2) Update it for the last changes in /boot/loader by Daniel Sobral.
> IIRC: @, # and - are gone. BTW: If variables were identified by
> a $ sign, and the $ sign is now an "echo on execute" command, how will
> variables be identified now ? Or have I misunderstoo
On 5 Feb 1999, John Saunders wrote:
> In nlc.lists.freebsd-current you wrote:
> > It succeeds as per allocating the memory until the swap is full. But, when
>
> Malloc's don't cause swap space allocation. Theoretically a process can
> malloc all of it's virtual address space so long as it doesn't
Hi,
On Sat, 30 Jan 1999, Richard Seaman, Jr. wrote:
> You need to:
>
> 1) Upgrade your source tree to Jan 28 or later for 3.X or Jan 26
> or later for 4.0 current, and "make world" and config and remake
> and install a new kernel,
>
> or
>
> 2) Take your existing source and add -DCOMPAT_LINUX_
just curious...
anything i could look at?
i'm almost done with make-release and this message popped up:
Feb 5 11:07:55 bright /kernel: /mnt: optimization changed from SPACE to
TIME
i know what that means, however:
~ % mount
/dev/wd0s1a on / (local, soft-updates, writes: sync 3 async 15144)
/
Is it correct to assume that StarOffice 5.0 works with current now?
--
E-Mail: William Woods
Date: 05-Feb-99 / Time: 08:40:59
FreeBSD 4.0 -Current
--
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-curre
> > My locale is set do de_DE.ISO_8859-1, not de_DE.ASCII
> > If I type 2 characters ss, I mean 2 characters ss. If I type ß I
> > mean the single character ß.
> > This sorting behaviour is just wrong. Not every apperence of "ss"
> > even in pure ASCII does mean "ß".
>
> I suggest you set LC_COLL
In article ,
notso wrote:
>
> just curious...
>
> anything i could look at?
>
> i'm almost done with make-release and this message popped up:
>
> Feb 5 11:07:55 bright /kernel: /mnt: optimization changed from SPACE to
> TIME
>
> i know what that means, however:
>
> ~ % mount
> /dev/wd0s1a
In nlc.lists.freebsd-current you wrote:
> If you looked at the "prgram" (term used loosely) it touches every bit of
> memory it allocates.
I seemed to have overlooked the bit where you wrote deadbeef. I took a
closer look.
What I think is happening is that as the blocks are allocated and then
tou
> It was rather annoying to update my 2.2.8-STABLE machine a day or two
> after being told that cvsuping ports on a 2.2 machine might cause
> breakage (re: the no more 2.2 support announcement) to find that *not*
Generally, you shouldn't be CVSup'ing in that case. Rather visit
www.freebsd.org/por
Here's more. I seem to be getting stale NFS handle replies on the NFS-V3
commits and writes.
I am guessing that the problem is due, somehow, to install's writing or
renaming over of the original file, probably after stat'ing the original
file.
doing a mount -u -o acdirmin
This is very odd. This is the approximate backtrace that I get
when I throw my test machine into DDB:
--- interrupt, ...
nfs_* routines
cluster_wbuild
vfs_bio_awrite
flushdirtybuffers
bdwrite
nfs_write
vn_write
write
syscall
What is happeni
I ubderstand that StarOffice 5.0 now works with FreeBSD 4.0-current. Where
would I find the instructions for implementing this?
--
E-Mail: William Woods
Date: 05-Feb-99 / Time: 11:19:15
FreeBSD 4.0 -Current
--
To Unsubscribe: send m
test.
--
E-Mail: William Woods
Date: 05-Feb-99 / Time: 11:48:00
FreeBSD 4.0 -Current
--
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message
Hello!
I've recently fetched and built XFree86 3.3.3.1, and some programs (most
notably xterm and xemacs 20.4, built from ports also) fails to input Russian
letters, using either locale or .xmodmap method.
What should I set up? I've tried config file from my (_working_) XFree 3.3.3,
but it did
We're getting lots of negative reference counts for 3.0-STABLE. We've been
getting them since long before Christmas. We have 3 SMP machines, all heavy
NFS clients, which are dieing about 1 per day with this panic.
Several of these hangs have been provoked by me logging out - you can see
the ^D in
Quoth Matt Dillon:
[make world over nfs breakage]
> It is very odd. I don't suppose very many people try to make install
> over NFS ( it works, you just have to chflags -R noschg the destination
> on the NFS server before you run make install on the NFS client ).
Actually, I did, thi
1. Userconfig parameter saving should work again, albeit somewhat
differently than before. Rather than having a program (dset) pound
bits directly into your kernel, a /boot/kernel.conf file is written
out by sysinstall, along with a set of /boot/loader.rc file entries
to make use of it
:> on the NFS server before you run make install on the NFS client ).
:
:Actually, I did, this broke somewhere at the end of January in 3.0-STABLE.
:Unfortunately I first built a kernel, rebooted with that, and tried to
:build the world, but /usr/bin/ps was the wrong version so I couldn't
:eas
I think I've found the general area where the problem is occuring.
It appears to some sort of weird write()/remove() interaction.
In the make install, the problem appears to only occurs when
install -s ( install and strip binary ) is used.
This causes an NFS file to be writt
Matt wrote:
> This is very odd. This is the approximate backtrace that I get
> when I throw my test machine into DDB:
[..]
> What is happening is that I am doing a 'make installworld' on my
> test machine with / and /usr NFS V3 mounted R+W.
I also have come to the conclusion tha
On 5 Feb 1999 17:19:44 -0500, in sentex.lists.freebsd.misc you wrote:
>
>I was trying to install SKIP on a 3.0 STABLE box and I am having problems
>getting it to boot up. The port compliles cleanly, but when I reboot, I
>get the following
>
>ruby# /usr/local/etc/rc.d/skip.sh
> skipld: /kernel: ma
Sorry for the long lines, I want to show garbled/split messages.
I am running an SMP kernel, -current as of last night.
I can look through logs back to early April, 1998, if necessary.
If I use reboot or shutdown -r, the top part of dmesg does not appear
in /var/log/messages. The amount of dmes
Ok, I think I found the problem.
I believe what is going on is that dirty buffers are being held across
an nfs_rename() call under NFS V3. Under NFS V2, most such buffers are
written synchronously.
Under NFS V3, however, it appears to work differently. One of the
follo
Running 4.0 -Current build as of a few miniutesd ago, I go to run top and I
get.
top: cannot read *swapblist: kvm_read: Bad address
top: cannot read blmeta_t: kvm_read: Bad address
Floating point exception
--
E-Mail: William Woods
Date: 05-Feb-99 / Time
On Fri, 5 Feb 1999, William Woods wrote:
> Running 4.0 -Current build as of a few miniutesd ago, I go to run top and I
> get.
>
> top: cannot read *swapblist: kvm_read: Bad address
> top: cannot read blmeta_t: kvm_read: Bad address
> Floating point exception
Try "kvm_mkdb" yet?
>
>
To go along with my other message about the top problem,
When I try to run top in a current box, compiled a few moments ago I get:
top: cannot read *swapblist: kvm_read: Bad address
top: cannot read blmeta_t: kvm_read: Bad address
Floating point exception
And, in /var/log/messages I see:
Feb
Ahhh...not sure what you mean here...
On 06-Feb-99 Brian Feldman wrote:
> On Fri, 5 Feb 1999, William Woods wrote:
>
>> Running 4.0 -Current build as of a few miniutesd ago, I go to run top and I
>> get.
>>
>> top: cannot read *swapblist: kvm_read: Bad address
>> top: cannot read blm
:
:Ahhh...not sure what you mean here...
:
:On 06-Feb-99 Brian Feldman wrote:
:> On Fri, 5 Feb 1999, William Woods wrote:
:>> Floating point exception
:...
:>
:> Try "kvm_mkdb" yet?
:>
:--
:E-Mail: William Woods
Try this:
cd /usr/src/lib/libk
Just tried that, same error.
On 06-Feb-99 Matthew Dillon wrote:
>
>:
>:Ahhh...not sure what you mean here...
>:
>:On 06-Feb-99 Brian Feldman wrote:
>:> On Fri, 5 Feb 1999, William Woods wrote:
>:>> Floating point exception
>:...
>:>
>:> Try "kvm_mkdb" yet?
>:>
>:-
>When I try to run top in a current box, compiled a few moments ago I get:
>
>top: cannot read *swapblist: kvm_read: Bad address
>top: cannot read blmeta_t: kvm_read: Bad address
>Floating point exception
kvm_getswapinfo() is broken when there is no swap. It falls into its
own compatibility cruf
Hmmm...I have a swap, although it is mounted /tmp as mfs, here is my fstab:
# DeviceMountpoint FStype Options DumpPass#
/dev/wd0s1b /tmpmfs rw 0 0
#/dev/wd0s1bnoneswapsw 0
:>When I try to run top in a current box, compiled a few moments ago I get:
:>
:>top: cannot read *swapblist: kvm_read: Bad address
:>top: cannot read blmeta_t: kvm_read: Bad address
:>Floating point exception
:
:kvm_getswapinfo() is broken when there is no swap. It falls into its
:own compatibi
And the fix is.
On 06-Feb-99 Matthew Dillon wrote:
>
>:>When I try to run top in a current box, compiled a few moments ago I get:
>:>
>:>top: cannot read *swapblist: kvm_read: Bad address
>:>top: cannot read blmeta_t: kvm_read: Bad address
>:>Floating point exception
>:
>:kvm_getswapinfo() i
:And the fix is.
:
:On 06-Feb-99 Matthew Dillon wrote:
:>
:>:
:>:Bruce
:>
:> Ahhh. Easy to fix.
:>
:
This this patch to /usr/src/lib/libkvm/kvm_getswapinfo.c. Then
recompile libkvm and try top and pstat -s again.
-Matt
#define quoting(Mike Tancsa)
// Are there any other options for VPN on the 3.0 branch ? SKIP wasnt/isnt
// the greatest, but I had decent luck with it on the 2.2 branch of things...
Have you tried the ssh+ppp combo ? IIRC, there's a small example in
the file /etc/ppp/ppp.conf.sample.
Ahh.and exactly how do I use this?
On 06-Feb-99 Matthew Dillon wrote:
>:And the fix is.
>:
>:On 06-Feb-99 Matthew Dillon wrote:
>:>
>:>:
>:>:Bruce
>:>
>:> Ahhh. Easy to fix.
>:>
>:
>
> This this patch to /usr/src/lib/libkvm/kvm_getswapinfo.c. Then
> recompile lib
>Hmmm...I have a swap, although it is mounted /tmp as mfs, here is my fstab:
You have swap commented out. mfs isn't swap.
>
># DeviceMountpoint FStype Options DumpPass#
>/dev/wd0s1b /tmpmfs rw 0 0
>#/dev/wd0s1b
>This this patch to /usr/src/lib/libkvm/kvm_getswapinfo.c. Then
>recompile libkvm and try top and pstat -s again.
>Index: kvm_getswapinfo.c
>===
>RCS file: /home/ncvs/src/lib/libkvm/kvm_getswapinfo.c,v
>retrieving revision 1.
Yah yah. I had to get a machine up without any configured swap, it
took a little while. Fixes have been comitted.
SWIF_DUMP_TREE is not used for error reporting. It's used to dump
the radix tree.
While one could argue that printf()'s should not exist in libkvm,
I am not
Mike Tancsa once stated:
=Are there any other options for VPN on the 3.0 branch ? SKIP wasnt/isnt
=the greatest, but I had decent luck with it on the 2.2 branch of things...
User ppp over ssh pipe?
-mi
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current
Well, I was able to successfully 'make buildworld' and 'make installworld'
on an NFS-V3 mounted / and /usr with this patch in place, so I am going to
commit it to -4.x in liu of an NFS hacker figuring out what exactly was
going on with delayed-write buffers.
I think it's prett
43 matches
Mail list logo
