:> VM lookup the page again. Always. vm_fault already does this,
:> in fact. We would clean up the code and document it to this effect.
:>
:> This change would allow us to immediately fix the self-referential
:> deadlocks and I think it would also allow me to fix a similar
While installing 2.2.8R (from a CD which I got from cheapbytes) on a
486DX2 66, w/ 16Mb RAM, I get:
> sc0 at 0x60-0x6f irq 1 on motherboard
> sc0: VGA mono <16 virtual consoles, flags=0x0>
>
> Fatal trap 12: page fault while in kernel mode
> fault virtual address = 0xefc0
> fault code
> And have /usr/bin point to /binaries/i386/bin or /binaries/mips/bin
And before people jump on me, let me just clarify in advance that I
was not meaning to imply that Apollo ever used the x86 architecture.
They didn't. It was just an example. :)
- Jordan
To Unsubscribe: send mail to majord...
> Forgive my ignorance, but what exactly is meant by a "variant link", and
> what might one be used for?
Gee, it's refreshing to see someone other than myself bringing this
subject up. :)
Variant symlinks, which many of us fell in love with back in our Apollo
days, are essentially just symlinks w
On 13 Jun 1999, Joel Ray Holveck wrote:
> What, to the reckoning of the resident populace, would happen if
> somebody were to rm a vnconfig'd swapfile while it was in use?
My reckoning is that the dirent would be deleted, and that's it. It would
most likely go away when the system is restarted. D
Forgive my ignorance, but what exactly is meant by a "variant link", and
what might one be used for?
Chuck Youse
Director of Systems
cyo...@cybersites.com
-Original Message-
From: Marc Ramirez
To: hack...@freebsd.org
Date: Sunday, June 13, 1999 1:12 PM
Subject: symlink question
>
>Sor
In article you
write:
>
>Sorry if I'm bothering you busy folk unnecessarily...
>
>If I wanted to add variant symlinks, would that just require modifications
>to namei, or is that way too simplistic?
I've done that part with help of Mike Smith and others.
I still have the changes around somewhere
What, to the reckoning of the resident populace, would happen if
somebody were to rm a vnconfig'd swapfile while it was in use?
Thanks,
joelh
--
Joel Ray Holveck - jo...@gnu.org
Fourth law of programming:
Anything that can go wrong wi
sendmail: segmentation violation - core dumped
To Uns
>Interesting. It's an overlapping same-process deadlock with mmap/write.
>This bug also hits NFS, though in a slightly different way, and also
>occurs with mmap/write when two processes are mmap'ing two files and
>write()ing the other descriptor using the map as a buffer.
>
>I
On Sun, 13 Jun 1999, John S. Dyson wrote:
>
> Remember that you cannot assume that the mappings stay the same during
> almost any I/O mechanism anymore. The issue of wiring pages and assuming
> constant mapping has to be resolved. A careful definition of whether
> or not one is doing I/O to an
Not to pick on Brian, but can we end this pathetic and sorry thread
already? Everybody: Just play nice with your little brother and
stop poking him in the back seat - we'll get to where we're going
soon and then everybody can have a milkshake if they've been good.
Thank you.
- Jordan
To Unsubs
Greetings,
I purchased a 3Com EtherLink III LAN+33.6 Modem PCMCIA card only to find
that FreeBSD does not yet support the 3c562 controller. There was a post a
day or two ago that had this subject line:
sysnewconfig990609-kld990609test8.7.patch.gz
Does this patch give a 3.2-RELEASE support for t
> A permanent vnode locking fix is many months away because core
> decided to ask Kirk to fix it, which was news to me at the time.
> However, I agree with the idea of having Kirk fix VNode locking.
Actually, core did no such thing. Kirk told me a month or so ago that he
inten
Sorry if I'm bothering you busy folk unnecessarily...
If I wanted to add variant symlinks, would that just require modifications
to namei, or is that way too simplistic?
Thanks,
Marc.
--
Marc Ramirez - OwnerGreat Big Throbbing Brains
mr...@gbtb.com http://www.gbtb.c
On Sun, 13 Jun 1999 sth...@nethelp.no wrote:
> > Linux is a Unix clone, while FreeBSD is Unix. Don't confuse people with
> > this.
>
> I'm afraid that attitude isn't going to help Unix agains Windows...
>
> I use FreeBSD for all my systems. I still go around and tell people that
> Linux is one s
On Sun, 13 Jun 1999, Southern Branch of the P.P.Shirshov Institute of
Oceanology wrote:
> Hi !
> I have a problem.
> My program creates UDP-socket and after that it tries to create UDP or
> TCP-socket. But last one doesn't work.
> TCP doesn't execute "accept"
> UDP doesn't execute "recvfrom"
> Wh
> Linux is a Unix clone, while FreeBSD is Unix. Don't confuse people with
> this.
I'm afraid that attitude isn't going to help Unix agains Windows...
I use FreeBSD for all my systems. I still go around and tell people that
Linux is one several Unix variants, and I intend to continue doing this.
F
Hi !
I have a problem.
My program creates UDP-socket and after that it tries to create UDP or
TCP-socket. But last one doesn't work.
TCP doesn't execute "accept"
UDP doesn't execute "recvfrom"
What can I do ?
Answer me via e-mail:pa...@sdios.sea.ru
Thank you
Pavel
To Unsub
:>From the source code of vtruncbuf() in file vfs_subr.c, I find out that
:the code deals with the case when a buffer linked on the clean or dirty
:list of a vnode can change its identity (b_xflags flag, b_vp field, or
:B_DELWRI flag). For example, a buffer's B_VNCLEAN flag is cleared even if
:it i
:On Sun, 13 Jun 1999, Bernd Walter wrote:
:
:> On Sat, Jun 12, 1999 at 12:13:43AM -0500, David Scheidt wrote:
:> > I had a 3.2 stable (from 30 May 1999)machine panic tonight, trying
:> > to load the oss driver, which is not too shocking. What was shocking
:> > was the damage done to my filesystem.
On Sun, 13 Jun 1999, Chuck Robey wrote:
> On Sat, 12 Jun 1999, Bill Huey wrote:
>
> > Well, so far I've heard alot of BS about Linux that isn't exactly true
> > and much of it seems like a bunch of artificial problems that hold
> > against the Linux folks. Most of it is just intentionally misrepr
[ cc'd to -hackers for the archives, reply-to points back to me so that
this doesn't perpetuate on the list ]
On Sat, Jun 12, 1999 at 11:24:11PM -0700, Bill Huey wrote:
> I came on this list initially to just check was the FreeBSD community
> was like,
Then you chose the wrong list.
As the we
On Sat, 12 Jun 1999, Bill Huey wrote:
>
> > The Linux philosophy has always been about simplistic cycle counting
> > exercises without understand whether the data had any meaning or not.
> > You've once again displayed your wholehearted participation in this
> > lack of understanding of what the
Brian Feldman writes:
> On 13 Jun 1999, Dag-Erling Smorgrav wrote:
> > BTW, you should check for errno == EINTR when select() returns -1.
> The perror() is the status report for select() when -1.
Yeah, but EINTR is a normal condition, so I'd ignore it silently
instead of logging it. Of course, th
Dag-Erling Smorgrav writes:
> This still doesn't explain select()'s failure to time out
Found it! If you change:
printf("no select() action");
to:
fprintf(stderr, "no select() action\n");
you'll see that select() does time out.
The moral of this story is to always use an unbuffe
On 13 Jun 1999, Dag-Erling Smorgrav wrote:
> Brian Feldman writes:
> > On 13 Jun 1999, Dag-Erling Smorgrav wrote:
> > > connect() normally uses the 1024-5000 range. Try the following:
> > >
> > > # sysctl -w net.inet.ip.portrange.last=4
> > >
> > > and see if it solves the EAGAIN problem.
>
Brian Feldman writes:
> On 13 Jun 1999, Dag-Erling Smorgrav wrote:
> > connect() normally uses the 1024-5000 range. Try the following:
> >
> > # sysctl -w net.inet.ip.portrange.last=4
> >
> > and see if it solves the EAGAIN problem.
>
> Actually, this is the perfect explanation. I think tha
On 13 Jun 1999, Dag-Erling Smorgrav wrote:
> Brian Feldman writes:
> > Another problem that came up with this: I originally started at port 1024.
> > I monopolized 3 ports (almost all consecutive, of course). When I try to
> > connect() a TCP socket as non-root, it fails with EAGAIN (I only
>
> * We hack a fix to deal with the mmap/write case.
>
> A permanent vnode locking fix is many months away because core
> decided to ask Kirk to fix it, which was news to me at the time.
> However, I agree with the idea of having Kirk fix VNode locking.
>
> But since
Brian Feldman writes:
> Another problem that came up with this: I originally started at port 1024.
> I monopolized 3 ports (almost all consecutive, of course). When I try to
> connect() a TCP socket as non-root, it fails with EAGAIN (I only tracked it
> far enough down as in_pcbbind().) It s
On Sun, 13 Jun 1999, Bernd Walter wrote:
> On Sat, Jun 12, 1999 at 12:13:43AM -0500, David Scheidt wrote:
> > I had a 3.2 stable (from 30 May 1999)machine panic tonight, trying
> > to load the oss driver, which is not too shocking. What was shocking
> > was the damage done to my filesystem. The
Hi,
I have tried getting my system to use DHCP on my local network, but I'm having
trouble.
If I don't use DHCP everything works fine, but if I use DHCP I get the
following messages appearing in my log file when I use ESD, and try and ping
my LAN IP.
Jun 13 17:35:21 guppy /kernel: arplookup 127.0.0
32 matches
Mail list logo
