Oddity in libufs.

[Frank Mayhar]

I've been using libufs as the I/O mechanism for my (heavy) modification
of sysutils/ffsrecov.  It's working to my needs and now I'm poking at
other bits and pieces to maybe get it suitable for release into the
wild.  I just looked at cgread() to see what it does and noticed that
there seems to be a redundant line:

.
.
if (c >= fs->fs_ncg) {
return (0);
}
ccg = fsbtodb(fs, cgtod(fs, c)) * disk->d_bsize;
if (bread(disk, fsbtodb(fs, cgtod(fs, c)),
disk->d_cgunion.d_buf,
.
.

That assignment up there looks redundant, as ccg is never used.  I
suspect that it's a relic of an old lseek()/read() pair that's long
gone.
-- 
Frank Mayhar [EMAIL PROTECTED] http://www.exit.com/
Exit Consulting http://www.gpsclock.com/
http://www.exit.com/blog/frank/
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Filesystem access from a KLD causes "vrele: negative ref cnt" panic

[Sebastien]

> [ please don't write such long lines ]

What's the correct line length ? I have at most 78 characters per line, which 
displays correcly on most terminals, doesn't it ?

> Should not rootvnode get reference, when fd_rdir or fd_cdir
> begins to point to it?  Try to VREF() it. 

No change.

> Which vnode gets negative reference counter?

I tell you ASAP (need to reboot...)
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: interprocessor communication

[victor cruceru]

A good idea is to use TIPC
http://tipc.sourceforge.net/
Probably not ported to BSD yet.


On 9/24/05, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>
> Good afternoon list,
> I have a single board computer with 2 cpu each running their own freebsd
> kernel:
>
> PHY--CPU1---logic-CPU2---PHY
> mii bus mii bus
>
> Packets should flow from cpu1 to cpu2.
> after I'm done processing a packet on CPU1 how can I address it
> to CPU2?
> Is there a kernel level interface to the MII bus I could
> use for this (i.e read/write)?
> Or any other idea, like shared memory, anything that you think could
> work?
> Should this be implemented in the ethernet driver?
>
> FYI, we can't use SMP.
>
> Thanks a lot.
> Jerry
> ___
> freebsd-hackers@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
> To unsubscribe, send any mail to "[EMAIL PROTECTED]"
>


--
victor cruceru
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Fwd: Re: Linksys WRT54G with freebsd

[Joao Barros]

On 9/23/05, Scott Long <[EMAIL PROTECTED]> wrote:
> Bruno Ducrot wrote:
> > On Fri, Sep 23, 2005 at 01:50:45PM +0200, Florent Thoumie wrote:
> >
> >>Le Vendredi 23 septembre 2005 à 12:16 +0200, Bachilo Dmitry a écrit :
> >>
> >>>Forwarding to FreeBSD hackers. (Because i am hacking WRT right now and only
> >>>Linux flashes work)
> >>>--  ?? ??  --
> >>>
> >>>Subject: Re: Linksys WRT54G with freebsd
> >>>Date: ?? 23  2005 17:06
> >>>From: Thierry Herbelot <[EMAIL PROTECTED]>
> >>>To: freebsd-current@freebsd.org
> >>>Cc: "Marcos Biscaysaqu - ThePacific.net" <[EMAIL PROTECTED]>
> >>>
> >>>Le Friday 23 September 2005 11:08, vous avez écrit :
> >>>
> On the other hand, it's the wireless thing.  If not needed, this
> should  be fun to do a port, somehow, even though it's a wireless
> router.
> >>>
> >>>The "cool factor" of porting FreeBSD to the WRT54G cannot be 
> >>>underestimated,
> >>>but Linux ports were enormously helped by the opening of the sources of the
> >>>Linksys Linux port (which is absent for FreeBSD) and the big number of
> >>>willing developpers (just have a look at the *number* of different Linux
> >>>ports to the WRT).
> >>>
> >>>The latest 6.0 release would be an excellent target, with its brand-new
> >>>support for WPA and virtual APs ... who volunteers ?
> >>
> >>  The Linksys WRT54g wireless router is based on a Broadcom CPU
> >>  (derived from MIPS) and FreeBSD/mips seems to be a dead
> >>  project :-(
> >
> >
> > Indeed.  It's targeted to SGI platforms anyway.  Maybe there is a need to
> > start a new port if there is enough people interrested?
> >
>
> There has been talk of doing this in the past year from some people, but
> I don't know if it got very far.  If you're inspired, go for it!  There
> are plenty of docs on the web about how to attach a serial port header
> and bootstrap it.  And, don't underestimate the mips32 work that is
> already in the tree; it's likely a good starting point.
>
> And, it's more than just a 'coolness' factor.  I'd really like to have
> pf running on mine, that way I could rid of the clunky machine doing
> static NAT + firewall on my DSL line.
>
> Scott

m0n0wall or it's version on steroids pfsense would be real cool to
have on a WRT54g 8)

>THe linux firewall capabilities are soo last century =-)
Except for some nice projects/patches that do Layer 7 and allow
filtering or queueing on specific traffic. ALTQ applied to marked
packets would be lovely :)
This would be very nice to have, except everyone (Daniel Hartmeier
included) tells it's a bad ideia to have protocol inspection at the
firewall level well, going off topic but couldn't resist ;)

--
Joao Barros
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"