I'm confused (and probably wrong), but does the 'shadow_head' field of
the vm_object structure really refer to a list of objects that the
object shadows (as mentioned in the comment)? Looking at the
vm_object_shadow() function (vm/vm_object.c, line 894 in 4.3), it looks
like it's the other way a
Thus spake j mckitrick ([EMAIL PROTECTED]):
> So without having the card for testing, i should just wrap the port access
> calls into bus_xxx calls?
Yes, that's basically what has to be done.
Alex
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of
"Louis A. Mamakos" wrote:
>
> >
> > It seems to me to be kind of moot to check the same value twice, unless
> > you suspect hardware problems. Aren't you talking about two different
> > checks over the same data instead of checksum off-loading?
>
> Suspect hardware problem? Of course you should
| You manually set the correct I/O port in the hints file and then you
Sorry if i misunderstand, but isn't the hints file only for -current? I was
under the impression it was only to simplify driver development.
Since my goal is to clean up the driver under the newbus system, how would
this po
> | You manually set the correct I/O port in the hints file and then you
>
> Sorry if i misunderstand, but isn't the hints file only for -current? I was
> under the impression it was only to simplify driver development.
>
> Since my goal is to clean up the driver under the newbus system, how wo
> Hi,
>
> First of all, sorry for my bad english skills.
>
> As the newbie I am on FreeBSD (4.3), I did a very stupid thing while
> using vipw : I deleted the root account.
>
> I tryed to correct my problem using the "fix it" floppy, but changing
> the /etc/passwd file is not enough.
> Really I a
Mike Smith wrote:
> At this point in time, if you're not up to coding on this project,
> there's not much to be done, I'm afraid. It needs a lot of development
> work before it'll be ready for anything resembling testing.
>
> Regards,
> Mike
Thanks, Mike. It's a matter of knowing my limitati
Hello there!
First, did you edit /etc/passwd or /etc/master.passwd ?
passwd does not hold any passwords and serves only for resolving
name/uid/fullname references, while master.passwd holds actual passwords.
Second, did you run pwd_mkdb(8) after editing that file?
This should be enough IMHO.
Re
On Sat, Jun 02, 2001 at 02:03:38AM -0400, Garance A Drosihn wrote:
>
> It also strikes me that this might be another topic to
> send thru [EMAIL PROTECTED], as Posix
> might have something to say about what's appropriate.
>
How much traffic does this list produce and how many people are on it?
> "Louis A. Mamakos" wrote:
> >
> > >
> > > It seems to me to be kind of moot to check the same value twice, unless
> > > you suspect hardware problems. Aren't you talking about two different
> > > checks over the same data instead of checksum off-loading?
> >
> > Suspect hardware problem? Of c
On Tue, Jun 05, 2001 at 07:04:47PM +0100, Josef Karthauser wrote:
> On Sat, Jun 02, 2001 at 02:03:38AM -0400, Garance A Drosihn wrote:
> >
> > It also strikes me that this might be another topic to
> > send thru [EMAIL PROTECTED], as Posix
> > might have something to say about what's appropriate.
Thank you very much for your help.
I could finally create my root account with your guide lines :)
I booted into single user mode, added a correct entry into the
/etc/master.passwd
file, and used pwd_mkdb -p /etc/master.passwd before changing the root
password.
Sorry again for my newbie questio
Hi:
I am trying to debug a kernel using the steps specified in the Handbook.
I follow the
steps to compile the kernel, reboot with -d option, and in the
other machine, I run gdb -k kernel and so...
I have both machines joined with a serial null-modem cable, but
when I try:
(kgdb) target remote
I'm not sure if you're already doing this but, on the machine being
debugged, you must switch to gdb mode by typing 'gdb' at the DDB
prompt. Then, after running gdb -k on your debugging box, go back to
the machine being debugged and type 's'. If you're already doing this,
then it looks like you'
In message <70325.991758797@critter> Poul-Henning Kamp writes:
: In message <[EMAIL PROTECTED]>, "David O'Brien" writes:
: >On Mon, Jun 04, 2001 at 07:46:18PM -0700, Dima Dorfman wrote:
: >> Is there any reason not to MFC the new md(4) functionality
: >
: >Zero reason not to.
:
: Others see it di
In message <[EMAIL PROTECTED]> j mckitrick writes:
: The newbus routines use a certain amount of overhead, but once done, you
: forget about it. In some device drivers, the probe methods often need to
: try a variety of hardware ports. In the past, inb/outb was used, along with
: an often hardco
In message Nick Hibma writes:
: > > - Some dummy driver which grabs the resource. The dummy driver would
: > >need to be unloaded when the actual driver needs the resources.
: >
: > This sounds attractive, but it's hard to find the dum
In message <[EMAIL PROTECTED]> j mckitrick writes:
: How would you recommending fixing this, taken from the ex driver?
By deleting it.
Warner
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
In message <[EMAIL PROTECTED]> j mckitrick writes:
: | You manually set the correct I/O port in the hints file and then you
:
: Sorry if i misunderstand, but isn't the hints file only for -current? I was
: under the impression it was only to simplify driver development.
Hints will be in -stable
In message <[EMAIL PROTECTED]> Warner Losh writes:
: In message <[EMAIL PROTECTED]> j mckitrick writes:
: : How would you recommending fixing this, taken from the ex driver?
:
: By deleting it.
Let me expand a little. The reason I advocate deleting it is because
there are too many old hunks of
Hi-
< Please cc: me on any answer as I am not subscribed! Thx! >
< Also, if this is the wrong list please redirect me! Thx! >
I am experimenting with porting an application
from the FreeBSD 2.2.x series to a more modern release,
and as such I have occaision to debug kernel core files
under the
On one of our servers, deleted space is not being freed and causing is to
run out of disk space. To test this, I copied a 200 meg file to the /usr
partition and then deleted it. I checked df before copying, after copying,
and after deleting it. After deleting it, the space never became
available
Hi Everybody,
I would like to inquire about what it would take to make a driver for a specific
ADSL board with direct PCI interface to FreeBSD
First, lets assume that I will supply boards, and that all necessery
documentation will be available.
How good is FreeBSD current structures for run
Looks like you forgot to set the 'flags 080' on the sio device of the
machine being debugged. This is a logical OR with what was set before. So,
for me, I changed the line in my kernel config
device sio0at isa? port IO_COM1 flags 0x10 irq 4
to
device sio0at isa
> How good is FreeBSD current structures for running ADSL, I'm thinking about the
> ATM support already present, and probably using netgraph ? I would need support
> for the most common protocols used worldwide, t.ex PPPoATM, IPoATM
You'd also need to support PPPoE, which on most ADSL system
Louis,
Thanks for your reply.
"Louis A. Mamakos" wrote:
>
> You'd also need to support PPPoE, which on most ADSL systems appears
> as PPP on Ethernet as RFC-1490 bridged encapsulation of the ethernet
> frames in AAL5 ATM cells. It's unclear that this is worth doing at
> the ATM level since the
I have a problem, I installed a bunch of machines with a very stripped
down set of distributions (bin, man, dict, krb5). I'd like to update the
machines, but when I do an installworld, it's going to install a bunch
more than that. Is there some way of only upgrading only the bin
distribution (a la
> Louis,
>
> Thanks for your reply.
>
> "Louis A. Mamakos" wrote:
> >
> > You'd also need to support PPPoE, which on most ADSL systems appears
> > as PPP on Ethernet as RFC-1490 bridged encapsulation of the ethernet
> > frames in AAL5 ATM cells. It's unclear that this is worth doing at
> > the
I'm working on a project that will be using a whole lot of gif(4) devices.
Since I'd written an almost-clone patch for snp and gif's current lack of
cloning annoyed me, I figured I'd take a look at writing a patch for it.
Unfortunately, it appears to be rather more complicated then I had hoped.
W
In message <[EMAIL PROTECTED]>, Brooks Davis writes:
>With network devices that are also normal devices the way tun is,
>you do this by just implementing a dev_clone event handler so when the
>user attempts to open a non-existent instance it's created. The problem
>with gif is that there's no de
As the originator of this thread (sorry), I thought I'd clear up some of
the speculation as to what I'm trying to do. :-)
Our adapter card is a GSN adapter, focused on the ST protocol over a
hippi-6400 link. We support IP on this adapter as well but that's not
its expected primary use. In asking
On Wed, 6 Jun 2001, Soren Kristensen wrote:
If you will give all neccessary documentation and microcode (for
chipsets), then it is definitely interesting. I have unsuccessfully
discussed writing drivers for ADSL cards with several vendors (alcatel,
adi, efficient) but no one have not had courage
4.3-RELEASE/src/usr.sbin/pkg_install/sign/ from cdrom needs to include:
openssl/err.h openssl/evp.h openssl/objects.h openssl/pem.h
openssl/rsa.h openssl/sha.h openssl/ssl.h openssl/x509.h
They are not on cdrom src/, But are in src/ from CVS.
src/crypto/heimdal/lib/roken/er
I appear to have missed some of this thread. Dang.
> : > > - Some dummy driver which grabs the resource. The dummy driver would
> : > >need to be unloaded when the actual driver needs the resources.
> : >
> : > This sounds attractive, but it's hard to find the dummy driver when
> : > y
On Wed, Jun 06, 2001 at 10:32:39AM -0700, Dorr H. Clark wrote:
> Interestingly, the 4.16 distribution archived at ftp://www.gnu.org
> does not exactly match the version in the FreeBSD 2.2.x release,
> and doesn't build cleanly either.
Not sure why you find this so surprising. Install the 2.2.x s
Poul-Henning Kamp <[EMAIL PROTECTED]> writes:
> In message <[EMAIL PROTECTED]>, "David O'Brien" writes:
> >On Mon, Jun 04, 2001 at 07:46:18PM -0700, Dima Dorfman wrote:
> >> Is there any reason not to MFC the new md(4) functionality
> >
> >Zero reason not to.
>
> Others see it differently, it wou
Warner Losh <[EMAIL PROTECTED]> writes:
> In message <70325.991758797@critter> Poul-Henning Kamp writes:
> : In message <[EMAIL PROTECTED]>, "David O'Brien" writes:
> : >On Mon, Jun 04, 2001 at 07:46:18PM -0700, Dima Dorfman wrote:
> : >> Is there any reason not to MFC the new md(4) functionality
Many have had problems with the XFree86 and i810 or i815 chipsets under
FreeBSD. Specifically, the server crashes after switching to a text
console and switching back to the console X is running on. Unlike
versions 4.0.2 and 4.0.3 (4.0.1 magically works for me), 4.1.0 prints an
error message:
Jun 6 18:48:10 www rpc.statd: invalid hostname to
sm_stat: ^X^X^Z
^Z%8x%8x%8x%8x%8x%8x%8x%8x%8x%62716x%hn%51859x%hnM-^PM-^PM-^PM-^PM-^PM-^PM-^PM-^PM-
^PM-^PM-^PM-^PM-^PM-^PM-^PM-^PM-^PM-^PM-^PM-^PM-^PM-^PM-^PM-^PM-^PM-^PM-^PM-^PM-^PM-^PM-^PM-^PM-^PM
-^PM-^PM-^PM-^PM-^PM-^PM-^PM-^PM-^PM-^PM-^PM-^
On Wed, 6 Jun 2001, Dan Phoenix wrote:
>
> Jun 6 18:48:10 www rpc.statd: invalid hostname to
> sm_stat: ^X^X^Z
>
>^Z%8x%8x%8x%8x%8x%8x%8x%8x%8x%62716x%hn%51859x%hnM-^PM-^PM-^PM-^PM-^PM-^PM-^PM-^PM-
[ snip ]
It's some l33t h4x0r attemting to use a Linux RPC exploit against your
FreeBSD machin
On Wed, Jun 06, 2001 at 11:20:45PM -0500, Andrew Hesford wrote:
> I hope somebody can provide more information. I am in the process of
> fetching and extracting the XFree86 4.0.1 sources, I will take a look at
> how they handled the ioctl. Unfortunately, I do not know enough about
> the design of
On Wed, 6 Jun 2001, Dima Dorfman wrote:
> I don't think anybody is even remotely suggesting that MFS be removed,
> but someone (other than you) might get bitten by a change of this
> sort. I guess it's just a matter of whether the new functionality
> (and giving people a head start integrating
>The TCP checksum protects more than just the contents of the packet
>on the wire; it's also a (somewhat) weak check on the contents
>of your packet sitting in memory, and as it's going over the bus
>in your computer between memory and peripherals and for other end-to-end
>sorts of issues.
In f
In message <[EMAIL PROTECTED]>, Dima Dorfman write
s:
>Poul-Henning Kamp <[EMAIL PROTECTED]> writes:
>> In message <[EMAIL PROTECTED]>, "David O'Brien" writes:
>> >On Mon, Jun 04, 2001 at 07:46:18PM -0700, Dima Dorfman wrote:
>> >> Is there any reason not to MFC the new md(4) functionality
>> >
>>
> >I don't think it would be much of a practical problem for anyone since
> >the old behvior can be emulated with the new md pretty easily, but
> >you're right that it isn't appropriate to break compatibility in
> >-stable. It's probably possible to retrofit the old behavior into the
> >new code,
On Wed, Jun 06, 2001 at 12:42:15PM -0700, Gordon Tetlow wrote:
> I have a problem, I installed a bunch of machines with a very stripped
> down set of distributions (bin, man, dict, krb5). I'd like to update the
> machines, but when I do an installworld, it's going to install a bunch
> more than th
On Wed, Jun 06, 2001 at 09:39:39PM -0700, Dan Phoenix wrote:
>
> Jun 6 18:48:10 www rpc.statd: invalid hostname to
> sm_stat: ^X^X^Z
>
>^Z%8x%8x%8x%8x%8x%8x%8x%8x%8x%62716x%hn%51859x%hnM-^PM-^PM-^PM-^PM-^PM-^PM-^PM-^PM-
[snip]
>
> this is a message in messages before a kernel paniced on freebs
On Wed, 6 Jun 2001, Warner Losh wrote:
> Let me expand a little. The reason I advocate deleting it is because
> there are too many old hunks of random hardware that interact badly
> with this probe. I've often had to delete the ex driver so that they
> start working due to this probe. I'd keep
In message <[EMAIL PROTECTED]> "Matthew N.
Dodd" writes:
: Except that the 'ex' driver uses a non-destructive probe.
I just know that I've had some hardware start working by deleting ex
from the kernel. I'll see if I was wise enough to document said
hardware...
Warner
To Unsubscribe: send mai
In message <[EMAIL PROTECTED]> Mike Smith writes:
: Actually, I do recall discussion over 'wd' being end-of-lifed in 4.x. I
: suspect that it would make sense to EOL 'mfs' in a similar fashion. I
: don't think there's a lot of good sense in pulling it out at an arbitrary
: point, though, any
Mike Smith <[EMAIL PROTECTED]> writes:
> > >I don't think it would be much of a practical problem for anyone since
> > >the old behvior can be emulated with the new md pretty easily, but
> > >you're right that it isn't appropriate to break compatibility in
> > >-stable. It's probably possible to
On Thu, Jun 07, 2001 at 09:34:36AM +0300, Peter Pentchev wrote:
> On Wed, Jun 06, 2001 at 12:42:15PM -0700, Gordon Tetlow wrote:
> > I have a problem, I installed a bunch of machines with a very stripped
> > down set of distributions (bin, man, dict, krb5). I'd like to update the
> > machines, but
On Wed, 6 Jun 2001, Warner Losh wrote:
> In message <[EMAIL PROTECTED]> j mckitrick writes:
> : How would you recommending fixing this, taken from the ex driver?
>
> By deleting it.
Uh, what?
Non PnP devices that can be autodetected should be autodetected.
Relying on the user to wire down hint
53 matches
Mail list logo