Try again with {3,4}.0-19990208
>
> I installed 4.0-19990207-SNAP.
> It seems ld.so is missing and it's not possible to run dynamicaly
> linked aout executables.
>
> Val
> _
> DO YOU YAHOO!?
> Get your
On todays cvsup of -current, I get the following
--
/usr/local/src/sys/modules/ibcs2/../../i386/ibcs2/ibcs2_ipc.c:201:
dereferencing pointer to incompl
ete type
/usr/local/src/sys/modules/ibcs2/../../i386/ibcs2/ibcs2_ipc.c:202:
dereferencing pointer to incompl
%>
%> You've probably already seen this:
%>
%> "Scheduler Activations: Effective Kernel Support for the User-Level
%> Management of Parallelism."
%> http://www.acm.org/pubs/citations/proceedings/ops/121132/p95-anderson/>
%>
%And here is the abstract:
%
%
%http://www.acm.org/pubs/toc/Abstracts/07
I installed 4.0-19990207-SNAP.
It seems ld.so is missing and it's not possible to run dynamicaly
linked aout executables.
Val
_
DO YOU YAHOO!?
Get your free @yahoo.com address at http://mail.yahoo.com
To Unsubscribe: send mail to m
Try the following patch. Look for a line in /sys/i386/isa/sio.c that
looks like:
com->fifo_image = t->c_ospeed <= 4800
? FIFO_ENABLE : FIFO_ENABLE | FIFO_RX_HIGH;
Replace FIFO_RX_HIGH with FIFO_RX_MEDH, and if that doesn't work try
FIFO_RX_MEDL inst
Mike Smith writes:
> > This may be oversimplifying, but why wouldn't this work: just do
> > everything at the module level:
> >
> > - All dependencies are inter-*module* dependencies.
> > - Only one *module* with the same name can be loaded at one time.
> > - KLD files (eg, foo.ko) are simply c
I've made a number of medium-sized VM commits today, just FYI:
* The PQ_ZERO page queue has been ripped out and its functionality
merged into PQ_FREE. The code is functionally the same ( or close
to it ), but the kernel is a couple of kilobytes smaller.
* MAP_ENTRY_IS_A_M
> Because rc.conf contains configuration variables, whereas rc contains
> commands to execute at boot time.
Then I would suggest renaming rc.conf to be rc.vars or rc.config-vars
or something more appropriate than rc.conf, which like all the other
*.conf files is intended for local editing and m
[moved to -hackers]
Peter Jeremy writes:
> Dag-Erling Smorgrav wrote:
> > Tcpdump does not work on PLIP links,
> Check out http://www.freebsd.org/cgi/query-pr.cgi?pr=7241
> This includes fixes for PLIP in lpt.c, but the code in ppbus/if_plip.c
> looks virtually the same. Note that lpt.c with Bi
[moving over to -hackers...]
As I mentioned in earlier correspondance on -current, tcpdump is
broken wrt plip connections. The reason for this is that, as I read
the code in src/contrib/libpcap/gencode.c, libpcap expect DLT_NULL-
type interfaces to produce a four-byte header with the link type in
> Then why bother having rc.conf in the first place? Just wire in all
> the defaults straight into /etc/rc and leave rc.conf strictly for
> overriding the defaults only, and eliminate rc.conf.* entirely.
Because rc.conf contains configuration variables, whereas rc contains
commands to execute
On Sun, 7 Feb 1999, Andreas Klemm wrote:
> What do you think ? Or what are your experiences ?
It has caused a lot of grief with my recent install of
3.0-19990205, but I gather I'm supposed to install something
later before complaining.
The main annoyance has been that running /stand/sysinstall a
> Mike Smith writes:
> > > Take the following scenario:
> > >
> > > compiled in: module A
> > >
> > > kldstat -v shows module 'A'
> > >
> > > kldload A
> > > damned thing succeeds.
> >
> > That's correct. There's a fundamental problem here in that there's a
> > confusion between file names a
Of all the gin joints in all the towns in all the world, Dag-Erling
Smorgrav had to walk into mine and say:
> Bill Paul writes:
> > Of all the gin joints in all the towns in all the world, Dag-Erling
> > Smorgrav had to walk into mine and say:
> > > Yes to most of the above. Tcpdump does not wo
Dag-Erling Smorgrav wrote:
> Tcpdump does not work on PLIP links,
Check out http://www.freebsd.org/cgi/query-pr.cgi?pr=7241
This includes fixes for PLIP in lpt.c, but the code in ppbus/if_plip.c
looks virtually the same. Note that lpt.c with Bill Fenner's patch
did not compile and needed the fol
> My opinion is that since we have /etc/rc and /etc/rc.local, we might
> as well use /etc/rc.conf and /etc/rc.conf.local the same way -- that
> is, just as /etc/rc should not be touched by anyone, neither should
> /etc/rc.conf be touched by anyone.
>
> Hmm.. I don't believe this can be true however. I do not program but
> I do run current on my workstation, it's just plain interesting thing
> to do. Just my opinion.
If you're running -current, you should at least be able to apply kernel
patches...
- Mike
To Unsubscribe: send mail to majo
> :>
> :> What do you think ? Or what are your experiences ?
> :
> :I hate it unreservedly. If we need a source of seeded default values,
> :we should have rc.conf.default, uncommented, read-only. rc.conf is
> :where people expect to make their changes, and it is immensely bogus to
> :have sy
On Sun, 7 Feb 1999, Matthew Dillon wrote:
> My opinion is that since we have /etc/rc and /etc/rc.local, we might
> as well use /etc/rc.conf and /etc/rc.conf.local the same way -- that
> is, just as /etc/rc should not be touched by anyone, neither should
> /etc/rc.conf be touched by
> > The correct answer to "how do you low-level format a SCSI disk under
> > FreeBSD" is "if you have to ask, you SHOULD NOT be doing it". It is
> > almost never the right thing to do.
>
> In his case, I think it was. The "medium format corrupted" error message
> can generally be fixed by low-
>
> You've probably already seen this:
>
> "Scheduler Activations: Effective Kernel Support for the User-Level
> Management of Parallelism."
> http://www.acm.org/pubs/citations/proceedings/ops/121132/p95-anderson/>
>
And here is the abstract:
http://www.acm.org/pubs/toc/Abstracts/0734-2071/146
:>
:> What do you think ? Or what are your experiences ?
:
:I hate it unreservedly. If we need a source of seeded default values,
:we should have rc.conf.default, uncommented, read-only. rc.conf is
:where people expect to make their changes, and it is immensely bogus to
:have sysinstall creat
On Sun, Feb 07, 1999 at 12:36:18AM -0500, John Robert LoVerso
wrote:
> > Well, I need to learn a little about programming first, so where do you
> > reccomend I begin learning?
>
> If you don't know about programming, then you just shouldn't be running
> -current. Step back to 2.2.8R and enjoy
On Sun, Feb 07, 1999 at 12:41:17PM -0500, Chuck Robey wrote:
> On Sun, 7 Feb 1999, John Robert LoVerso wrote:
> > Or type "vi /etc/rc.conf /etc/rc.conf.site" and then hit ":N" to split
> > the screen into two sessions, one in /etc/rc.conf and one in
> > /etc/rc.conf.site.
> > Use ^W to toggle betw
On Sun, Feb 07, 1999 at 09:13:27AM -0800, Jordan K. Hubbard wrote:
> > Hmmm, I think your answer is a bit political, or am I really the
> > only person, who hacks rc.conf.site with vi and has to browse through
> > both files at the same time and is a bit annoyed by having to compare
> > every singl
>
> What do you think ? Or what are your experiences ?
I hate it unreservedly. If we need a source of seeded default values,
we should have rc.conf.default, uncommented, read-only. rc.conf is
where people expect to make their changes, and it is immensely bogus to
have sysinstall creating rc.
> This is a multi-part message in MIME format.
> --6331448DC47966073EBB6A88
> Content-Type: text/plain; charset=iso-2022-jp
> Content-Transfer-Encoding: 7bit
>
> Jun Kuriyama wrote:
> > I'm planning to commit these changes into src/sys/pccard/. This adds
> > two features. These featu
You've probably already seen this:
"Scheduler Activations: Effective Kernel Support for the User-Level
Management of Parallelism."
http://www.acm.org/pubs/citations/proceedings/ops/121132/p95-anderson/>
--
Andreas Dobloug : email: andre...@ifi.uio.no
To Unsubscribe: send mail to majord...@free
I haven't used it yet, but I definately think the idea is an
improvement. I hate trying to update /etc after an upgrade.. if it's
been a while, or it's between major versions, it can take a very
significant amount of time. Anything that moves local changes to a
seperate file is a blessing.
Also,
I've been trying to play with the USB support lately, and haven't got
much success. I'm running a 4.0-current freshly CVSUPed, and less
than 24 hours old. In summary, here's excepts from what I'm seeing
when doing a verbose boot that appear to be relevent. During a boot,
there is a few second p
Mike Smith wrote...
> > Thanks..I ended up just pulling my old Atari out of the closet and doing
> > the format on it...that seemed to work and I am now up and running. I
> > would still like to know how to do it under FreeBSD.
>
> If the disk wasn't being probed, then you can't format it, period.
This looks like a good addition to rc.conf(5). A description of what
the inventor(s) intended when adding rc.conf.site and rc.conf.local to
the system.
> Typically I use 'sysinstall' exactly once in one machine's lifetime.
> My old method of dealing with 'rc.conf' and 'rc.conf.local' was:
> =
Hi,
On Sun, Feb 07, 1999 at 06:05:15PM +0100, Andreas Klemm wrote:
> > Sorry to say this, but you really don't understand it. :)
sorry Andreas, ... I have to second this ;)
> > > When we had one central rc.conf file it was fun to browse through
> > > it and having all supported knobs visible at a
> Thanks..I ended up just pulling my old Atari out of the closet and doing
> the format on it...that seemed to work and I am now up and running. I
> would still like to know how to do it under FreeBSD.
If the disk wasn't being probed, then you can't format it, period.
It sounds to me like you man
Bill Paul writes:
> Of all the gin joints in all the towns in all the world, Dag-Erling
> Smorgrav had to walk into mine and say:
> > Yes to most of the above. Tcpdump does not work on PLIP links, and I
> > do not use IP aliases at all.
> Explain to me how you concluded that tcpdump doesn't work
On Sun, 7 Feb 1999, John Robert LoVerso wrote:
> > No I have to use two vi sessions (or one ,more' and one ,vi' session)
> > in two different (!) windows (especially after a new installation,
>
> Or type "vi /etc/rc.conf /etc/rc.conf.site" and then hit ":N" to split
> the screen into two sessions
Of all the gin joints in all the towns in all the world, Dag-Erling
Smorgrav had to walk into mine and say:
> Bill Paul writes:
> > Of all the gin joints in all the towns in all the world, Dag-Erling
> > Smorgrav had to walk into mine and say:
> > > Luna, however, seems absolutely allergic to N
Bill Paul writes:
> Of all the gin joints in all the towns in all the world, Dag-Erling
> Smorgrav had to walk into mine and say:
> > Luna, however, seems absolutely allergic to NIS. Everything is
> > configured correctly as far as I can see
> [chop]
>
> Sure, that's what they all say. The N in
> No I have to use two vi sessions (or one ,more' and one ,vi' session)
> in two different (!) windows (especially after a new installation,
Or type "vi /etc/rc.conf /etc/rc.conf.site" and then hit ":N" to split
the screen into two sessions, one in /etc/rc.conf and one in /etc/rc.conf.site.
Use ^W
Of all the gin joints in all the towns in all the world, Dag-Erling
Smorgrav had to walk into mine and say:
> I have a very simple NIS configuration at home: niobe is the server
> and luna, my scratch box, is the client. Niobe runs 4.0-CURRENT, and
> luna runs 3.0-RELEASE until 'make world' finis
> Hmmm, I think your answer is a bit political, or am I really the
> only person, who hacks rc.conf.site with vi and has to browse through
> both files at the same time and is a bit annoyed by having to compare
> every single line and then to add the knob in rc.conf.site ?!
I still cannot see any
On Sun, Feb 07, 1999 at 08:29:57AM -0800, Jordan K. Hubbard wrote:
> > Sorry to say this, but after having to use rc.conf.site as it is now
> > I really kind of 'hate' it.
>
> Sorry to say this, but you really don't understand it. :)
What ? ;-) Don't tell me that ;-)
> > When we had one cent
I have a very simple NIS configuration at home: niobe is the server
and luna, my scratch box, is the client. Niobe runs 4.0-CURRENT, and
luna runs 3.0-RELEASE until 'make world' finishes on niobe so I can
make installworld over NFS. In addition to being the NIS and NFS
server, niobe is also its own
I have both a an Eagle TR-3 and an old Mountain QIC80 drive which I could donate
to someone stupid^h^h^h^h^hbrave enough to revive the FT driver. I can even
send
along a few tapes for each.
I personally gave up and went Exabyte SCSI.
Christopher Masto wrote:
> I have an Exabyte Eagle TR-3 driv
> I'm planning to commit these changes into src/sys/pccard/. This adds
> two features. These features are obtained from PAO.
>
> o PIOCSVIR
...
> o PIOCSBEEP
...
The patch implementing these changes are adequate in the kernel, but are
incomplete. What about the changes to usr.sbin/pccard/*
> Sorry to say this, but after having to use rc.conf.site as it is now
> I really kind of 'hate' it.
Sorry to say this, but you really don't understand it. :)
> When we had one central rc.conf file it was fun to browse through
> it and having all supported knobs visible at a glance.
And you stil
Hi !
Sorry to say this, but after having to use rc.conf.site as it is now
I really kind of 'hate' it.
When we had one central rc.conf file it was fun to browse through
it and having all supported knobs visible at a glance.
No I have to use two vi sessions (or one ,more' and one ,vi' session)
in
Jun Kuriyama wrote:
> I'm planning to commit these changes into src/sys/pccard/. This adds
> two features. These features are obtained from PAO.
Sorry, I forgot to add patch. :-)
--
Jun Kuriyama // kuriy...@sky.rim.or.jp
// kuriy...@freebsd.orgIndex: cardinfo.h
===
Matthew Dillon said:
>
> Ah, interesting. I understand the second bit. The first bit seems
> somewhat odd, though - the automatic page coloring adjustment made
> by _vm_object_allocate() doesn't work well enough for kmem_object?
>
There appears to be a clash. I haven't really carefu
I'm planning to commit these changes into src/sys/pccard/. This adds
two features. These features are obtained from PAO.
o PIOCSVIR
Virtual insert/remove of pccard. This will be used "pccardc power"
subcommand like as:
# pccardc power [slot] 0<-- power on for [slot]
Matthew Dillon said:
>
> : next_index += PQ_L2_SIZE/4;
> : if (next_index > PQ_L2_MASK)
> : next_index = (next_index + 1) & PQ_L2_MASK;
>
> Oops, make that:
>
> next_index += PQ_L2_SIZE/4;
> if (next_index > PQ_L2_MASK)
> next_index = (next_index
>install -c -s -o root -g wheel -m 555 make /usr/obj/usr/src/tmp
>install: /usr/obj/usr/src/tmp/make: Is a directory
Something set BINDIR (to "") in the environment.
Bruce
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message
Any clues to this one ?
--
>>> Making make
--
mkdir -p /usr/obj/usr/src/tmp/usr/bin /usr/obj/usr/src/tmp/make
[...]
cc -O -pipe -I/usr/src/usr.bin/make -I/usr/obj/usr/src/tmp/
In addition to the below, one [local] file that was open was severely
corrupted [not on disk, it was open in 'vi' and the crash recovery file had
very strange contents -- a few NULs and the standard output of a different
command that I ran sometime before the crash]. On disk, files seem to be
inta
Just curious as to why share/emacs and share/emacs/site-lisp are created by
BSD.local.dist instead of by the emacs ports which might want to use them?
It's not a big deal, but it seems to me that these aren't useful for the
general case of someone not wanting to install an emacs port (strange as th
Brian Feldman wrote:
> The basic problem is that msdosfs panic()s quite easily with a "zone
> not free" error (INVARIANTS is /ON/ in the kernel), when I attempt to do a rw
> mount of a FAT16.
Don't you, by a chance, load msdosfs module dynamically? If so, the
module must also be compiled with INV
On 07-Feb-99 Chris Tubutis wrote:
> Jeroen Ruigrok/Asmodai wrote:
>> whenever I click a mailto: HREF it inadvertly dumps core.
> Does it truly dump core, or does it merely go away?
No, it really dumps core.
---
Jeroen Ruigrok van der Wervenjoin #FreeBSD on Undernet
asmodai(at)wxs.nl
: next_index += PQ_L2_SIZE/4;
: if (next_index > PQ_L2_MASK)
: next_index = (next_index + 1) & PQ_L2_MASK;
Oops, make that:
next_index += PQ_L2_SIZE/4;
if (next_index > PQ_L2_MASK)
next_index = (next_index + PQ_PRIME1) & PQ_L2_MASK;
:Matthew Dillon said:
:>
:> Ah, interesting. I understand the second bit. The first bit seems
:> somewhat odd, though - the automatic page coloring adjustment made
:> by _vm_object_allocate() doesn't work well enough for kmem_object?
:>
:
:The problem with it was that there appeared
Matthew Dillon said:
>
> Ah, interesting. I understand the second bit. The first bit seems
> somewhat odd, though - the automatic page coloring adjustment made
> by _vm_object_allocate() doesn't work well enough for kmem_object?
>
The problem with it was that there appeared to be a
Ah, interesting. I understand the second bit. The first bit seems
somewhat odd, though - the automatic page coloring adjustment made
by _vm_object_allocate() doesn't work well enough for kmem_object?
-Matt
61 matches
Mail list logo
