Going with the lockd code on builder is great with me. The last I had
looked it had some of the same issues as the lockd developed here (no
handling of grace periods, etc.), so on a featureset we are even. The rpics
lockd has the advantage of being known by some of us to a much greater extent
th
I'm not going to take such an action w/o the blessing of -core. :)
--
David Cross | email: [EMAIL PROTECTED]
Lab Director | Rm: 308 Lally Hall
Rensselaer Polytechnic Institute, | Ph: 518.276.2860
Department of Compute
I pruned the Cc: list a bit...
One of the email messages that you quoted has the URL for the latest
development of the lockd code. As far as tests go it appears to be mostly
complete (there appears to be an issue with RPC64 on little endian machines,
but I have not yet had a chance to crawl thro
> On May 21/2000, Clive Lin wrote to -current&-i18n:
> > > The only way i found to link motif programs is by using
> > >
> > > http://www.cs.rpi.edu/~crossd/FreeBSD/wcs-19990606.tar.gz
> >
> >This seems the solution of wc* routines in FreeBSD.
> >
> >Could any one tell us, is this project dead ?
Oops, I seem to have made a mistake in the XDR patch that I included
with lockd-0.2. I have re-rolled the patch with a corrected patch.
As such, and to avoid confusion, I have re-labeled this as lockd-0.2a.
Once again, the URL is:
http://www.cs.rpi.edu/~crossd/FreeBSD/lockd-0.2a.tar.gz
Have fun.
I apologize profusely for the delay of this, but lockd-0.2 is out.
The URL is: http://www.cs.rpi.edu/~crossd/FreeBSD/lockd-0.2.tar.gz
A couple of notes on this release:
1) the statd hooks to lockd are not yet done (or started)
2) you need a patched libc (for XDR64 types). I have included the x
> Meaning no offense, but I can't think of a single good reason to write a
> device driver for one of these cards. (Unless you're trying to do
> pattern generation, and an 8255 is a terrible choice for that.) Worse
> than that though, there's _no_ standard for these cards' implementation,
>
I am just about finished with a device driver for PCI DIO boards based
around the 8C255 (number may be wrong ;). Specifically this is for the
ComputerBoards DIO-24H DIO board. I have been using the 'development' major
#, and I am ready to go about getting it committed into the CVS tree for
whoev
Now that the code freeze is over, can the 64Bit XDR changes be made? This
is the only thing preventing the next release of the rpc.lockd code at this
point.
--
David Cross | email: [EMAIL PROTECTED]
Acting Lab Director | NYSLP: FREEBSD
Syste
I followed the suggestions from people earlier today. That is to
say that I have upgraded my BIOS to 1012, disabled APM in the BIOS,
and removed 'device apm' from the kernel config, however I still
receive lines like:
calcru: negative time of 20585525 usec for pid 477 (cvsup)
and also lines
I have had these problems ever since upgrading to -current about a
month ago. The kernel very regularly spews out messages like:
> Mar 13 14:23:39 gemini /kernel: calcru: negative time of -2663631 usec for pid 568
>(sshd2)
or a message that "microuptime() went backwards'. I have noticed that
t
Version 2 of the lock manager is ready to be released. Amitha
says that it passes all of the tests in the suite posted by Drew (thanks
Drew). A noteable exception to this is on SGI where some lock requests
are never even received from the remote host. Also DOS sharing is not
yet complete.
On a
Mine is on 0x8b. Following some sugestions I hacked my boot/loader to look
specifically at 0x8b it didn't work. I even went so far as to force
0x8b even though the autodetect did not work... it still didn't work. I then
looked at the 1st stage boot loader as that *was* able to load boot/lo
This is a problem with the thinkpad BIOS that I have not had the time to be
able to track down. It would *appear* to be that the BIOS does not do
int 13 handling on boot cdroms, and the boot/loader makes much use of that
for loading the kernel and drivers.
I am, however, out of my league on th
I have 2 issues with 4.0-CURRENT. The first is the plethora of
"microuptime() went backwards..." errors that scroll on my console.
The second is that I have DDB compiled into my kernel (and a USB keyboard)
either on vga or serial console, if I trip DDB (control-shift-esc), I will
either get the
> Well, I'd first be very interested to know if anyone has even seen
> this work. :)
>
> I have seen regrettably little feedback about it so far.
>
> - Jordan
I can understand part of the reason for this... 4.0-RELEASE is right
arround the corner, and people are focusing on delivering a stable p
I realize that we are all very busy and the coming 4.0-RELEASE has also
compounded things, but I have heard nothing back on the rpc.lockd that
was released just a short time ago. I take it no news is good news and
we can start the process of bringing it into the source tree? :)
--
David Cross
Amitha (the person who has been working on the lockd code) has finished
most of his work. There are still some issues with handling async locks
and cancel messages. Also we were not able to implement the full NLM
protocol as the FreeBSD kernel does not currently request NFS locks (we
should f
It is almost done. A working and very lightly tested version of the code will
be made available on Monday (Jan 24). It should be considered alpha quality,
I would not recommend running important NFS servers with this code.
--
David Cross | email: [EMAIL PROTECTED]
> > How are PCI interrupts routed in CURRENT/NewBus? For example almost all of
> > my PCI devices are mapped to IRQ11. I understand this is "normal" in the PCI
> > world, but how does the interrupt dispatch routine decide which ints to
> > route where? I recently put a panic() in a intr routin
How are PCI interrupts routed in CURRENT/NewBus? For example almost all of
my PCI devices are mapped to IRQ11. I understand this is "normal" in the PCI
world, but how does the interrupt dispatch routine decide which ints to
route where? I recently put a panic() in a intr routine of mine just t
I am purposely panic()ing the system early in boot so I can get a look at some
startup information... unfortunately the 'config kernel dumps on...' no
longer works. how is one supposed to get crash dumps from early in the boot
process?
--
David Cross | email: [EMA
Ok I just tried some other mods... the first was to hard-wire disk0 to
be bios device 0x8b. no-go. The second was to patch to 'continue' if it
missed a probe, and to limit the probe to the first 0x10 entries... for
example: 0x00-0x0f and 0x80-0x8f.
How is it that the old boot code works? Wha
I modified the biosdisk.c code as follows
(first part of function)
for (unit=0;unitbi_bios_dev)
break;
if ((unit == nbdinfo ) && (nbdinfo < MAXBDDEV) ) {
unit=initial_bootinfo->bi_bios_dev;
bdinfo[nbdinfo].bd_unit=unit;
bdinfo[nbdinfo].bd_flags=(unit <
I attempt to boot a CD off of the TP600E and I get the following errors:
"Can't work out which disk we are booting from."
"Guessed BIOS device 0x8b not found by probes, defaulting to disk0:"
Then whenever it attmpts to access "disk0:" it goes to the floppy drive.
Suggestions?
--
David Cross
Ok... needless to say, I am having problems...
1: any access to the serial port (/dev/cuaa0) locks the machine.
2: I cannot get the ethernet card to work.
2a: It is sort-a recognized by the system, It senses the insert and remove,
but it cannot get the CIS. I remember reading somewhere
I have a threaded appilcation that is only running on one processor.
I remember there was discussion about this in the past, and there was a
solution, I think it involved a patch.
Any pointers?
--
David Cross | email: [EMAIL PROTECTED]
Systems Administrator/Resea
> IIRC, mount permissions (i.e., what IP addresses, root UID mangling, etc)
> are set per filesystem. Given a filesystem structure like this:
>
> > df
> Filesystem 1K-blocks UsedAvail Capacity Mounted on
> /dev/da0s1a127023271518971123%/
> /dev/ccd0c8321099 23
To export a single filesystem multiple times, *all* of the attributes must
be the same. If they aren't the only person you are fooling is yourself,
since once a filesystem is NFS exported, it is open to the world.
anyway the syntax for what you want is:
/var /var/mail some.machine
--
David C
This is yet another problem that we have run into here. If you check the
digest for -hackers it was reported awhile ago (mike smith even cc-ed it
to security since it may have been a kernel stack overflow) . Anyway, the
problem is that IRIX defaults to 32K packets on TCP NFSv3 mounts, and
16K on
> > Jordan stopped including CVS directories in the /usr/ports tarball.
>
> I don't think a transfer rate can be affected by that, though the
> total transfer time certainly would.
>
> Anyway... Jordan did it? Thanks God!
Ports is 20,000 some odd different files, the transfer rate is limited by
> > http://thc.pimmel.com/
> >
> I actually found the article a very good source of documentation on
> programming loadable modules for FreeBSD. Granted, I'm not sure of it's
> accuracy, but it was a worthwhile read for someone like myself who has
> only coded LKMs for Linux. Very interesting.
> If you haven't /.'d today, there's a news article purporting that
> FreeBSD can be exploited via kernel modules:
>
>
> http://thc.pimmel.com/
I did a quick read of that, I don't see how the system is being exploited
at all. All of their tricks need to be able to load a kernel module in
order
This is a bit of a tangent from the original post, but when did the FreeBSD
kernel start supporting ELF natively (not talking about Linux emulation).
I made the mistake of attempting to run a 3.0 ELF world with a 2.2.5 kernel,
and it worked (mostly). I was unaware that anything that "old" support
You have more than enough space to do it to. Swap memory is not dumped, only
RAM is... typicall it is dumped to the swap partition. In this case you
have well more than enough.
If your /etc/fstab showed "/dev/da3s1b" as your 1.6 gig swap partition, you
would add "dumpon=/dev/da3s1b" to your /et
by "break" I mean a serial break condition. Take the Tx line out of your
box and bring it negative 3-5 volts for a short time, that will be a break.
Seriously, the break will need to be sent from the piece of equipment that is
connected to the other end of the serial line. It isn't a telnet iss
I believe I stumbled over this as well. (As a side note, you can run DDB
over a serial console too, just compile with DDB, and DDB_UNATTENDED so your
system will come back if it unexpectedly panics; on the serial console send
a 'break').
Anyway, I have a simple program that mmap()s a 1Gig file i
The latest snapshot can be grabbed from:
http://www.cs.rpi.edu/~crossd/FreeBSD/wcs-19990606.tar.gz
New in this release...
1) Man pages (I don't think I included them prior to this)
2) Makefile that sorta works (makes a dynamic library.. I don't recommend
people use the dynamic, it is convienien
> There are several Japanese people working on stateful multibyte char
> support. Existing codebase like glibc only supports stateless
> multibyte char. People using iso-2022 variants (Japan, Korea,
> China, you name it) need stateful multibyte char support.
> We hav
> Is there anything in current that provides wide character support? I'm
> messing around with document formatting, and I have to be involved with
> wide character things. One example: wcscat(). It's not the only one, I
> just need to know if it's in *any* library, and declared in any include
>
Lets also consider the case of a root partition exists on a device which the
BIOS does not support, but DOS and FreeBSD do. A good example of this may be
a SCSI controller without a BIOS, or maybe a network style load. A person
could have just the kernel on the DOS parition, or have the driver for
Won't fbsdboot.exe be able to boot /boot/loader? (maybe I am just naive)
(or could it be modified to do so with little effort?)
--
David Cross | email: cro...@cs.rpi.edu
Systems Administrator/Research Programmer | Web: http://www.cs.rpi.edu/~crossd
Rensselaer Pol
> > The major number passed to the kernel is a product of a lot of
> > guesswork, because the loader has simply not enough information. I
> > have added a bit of code to my version of loader so you can use the
> > variable root_device_major_number to override the major number to be
> > passed to t
I posted this awhile ago to -questions, but never received a reply.
We have a number of FreeBSD NFS servers here. Occasionally we need to
change the exports list on the servers and send mountd a SIGHUP. This
leads to a condition that in many ways is much worse than a server reboot.
What happens
Yes, indeed, I have looked at nsd in Irix 6.5 and I like it. What Irix does
well, Irix does very well (save a couple of PRs I have filed with SGI of
course ;).
--
David Cross
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message
I think the 2.88MB suggestion was an alternative to going to a 'Hard Drive'
type solution for bootable CDROMs (from a jkh post earlier). Since most
bioses support 2.88MB floppies (regardless of if the hardware exists on the
person's machine), wouldn't it be possible to have the 'boot.flp' for a
46 matches
Mail list logo
