Re: RealSystem module for libalias

[Brian Somers]

Hi,

I haven't done anything with this yet, but I plan to take a look 
soon.  This is just a note to let you know that your post hasn't gone 
unnoticed.

> The libalias allows to transport only TCP stream on the RealSystem
> (RealAudio and RealVideo).
> It can not transport UDP stream, rtsp and pna, from the real server
> to the client.
> 
> So, I wrote the new module for the libalias to support the UDP stream
> on the RealSystem.
> 
> The patch againt to the libalias source tree of the FreeBSD 4.0-RELEASE
> is available at:
> 
>   http://configure.sh/FreeBSD
> 
> Any comments are welcome.
> ---
> Junichi Satoh
> [EMAIL PROTECTED] / [EMAIL PROTECTED]

-- 
Brian <[EMAIL PROTECTED]>
     
Don't _EVER_ lose your sense of humour !




To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

Re: RealSystem module for libalias

[Ruslan Ermilov]

On Fri, Jun 16, 2000 at 07:15:13AM +0100, Brian Somers wrote:
> Hi,
> 
> I haven't done anything with this yet, but I plan to take a look 
> soon.  This is just a note to let you know that your post hasn't gone 
> unnoticed.
> 
Brian, this is just to let you know that:

1) I am currently in process of applying *big* PPTP patch to libalias
   so I would really appreciate it if you do not touch libalias before
   I finish with PPTP part.

2) Erik Salander <[EMAIL PROTECTED]> is working together with Mr. Junichi 
   on $Subject issue (see attached), so you will probably want to contact
   them directly, since I am not particularly interested in these changes.
   But I would appreciate if you send me the patch for review before you
   commit it.

> > The libalias allows to transport only TCP stream on the RealSystem
> > (RealAudio and RealVideo).
> > It can not transport UDP stream, rtsp and pna, from the real server
> > to the client.
> > 
> > So, I wrote the new module for the libalias to support the UDP stream
> > on the RealSystem.
> > 
> > The patch againt to the libalias source tree of the FreeBSD 4.0-RELEASE
> > is available at:
> > 
> > http://configure.sh/FreeBSD
> > 
> > Any comments are welcome.
> > ---
> > Junichi Satoh
> > [EMAIL PROTECTED] / [EMAIL PROTECTED]
> 
> -- 
> Brian <[EMAIL PROTECTED]>
>      
> Don't _EVER_ lose your sense of humour !


Cheers,
-- 
Ruslan Ermilov  Oracle Developer/DBA,
[EMAIL PROTECTED]   Sunbay Software AG,
[EMAIL PROTECTED]  FreeBSD committer,
+380.652.512.251Simferopol, Ukraine

http://www.FreeBSD.org  The Power To Serve
http://www.oracle.com   Enabling The Information Age




Ruslan,

Thanks for going over the patch.  I'll get back to you by Thursday, at the
latest.

FYI, also working with Junichi Satoh on converging our streaming media
changes.  Sent him the first attempt at a merged routine, yesterday (Tues).

Erik


Ruslan Ermilov wrote:

> On Wed, May 24, 2000 at 04:27:23PM -0700, Erik Salander wrote:
> >
> > Hi,
> >
> > I've got some changes for libalias that are ready to be reviewed.  The
> > general features are:
> >
> > - add support to alias RTSP and RTP (see new module alias_rtsp.c)
> > - add support to alias PPTP and GRE (see new module alias_pptp.c and
> >   all "LINK_GRE" references)
> >
> What I do not understand is how PPTP is supposed to work if we do not
> intercept outgoing GRE packets.  I was told by Archie (and then read
> about that in RFC) that multiple clients to the same server can use
> the same Call ID.  I understand what is going on in alias_pptp.c --
> a GRE link is created after successful PPTP handshake, and then, for
> incoming packets, we look for the corresponding GRE link in GreAliasIn()
> and simply replace Call ID there appropriately (PPTP's GRE does not use
> checksum, right?), but we should do the same thing in GreAliasOut(),
> which is missing.  Am I overlooked something?
>
> > - adding support for passive mode FTP, aliasing the 227 replies (see
> >   alias_ftp.c)
> >
> The EPSV command 229 reply (RFC2428) should be aliased and checked as well.
> Recent versions of FreeBSD use EPSV by default:
>
> : Connected to localhost.
> : 220 perl.sunbay.crimea.ua FTP server (Version 6.00LS) ready.
> : Name (localhost:ru):
> : ---> USER ru
> : 331 Password required for ru.
> : Password:
> : ---> PASS 
> : 230 User ru logged in.
> : ---> SYST
> : 215 UNIX Type: L8 Version: BSD-199506
> : Remote system type is UNIX.
> : Using binary mode to transfer files.
> : ftp> dir foo
> : ---> EPSV
> : 229 Entering Extended Passive Mode (|||49169|)
> : ---> LIST foo
> : 150 Opening ASCII mode data connection for '/bin/ls'.
> : ftpd: foo: No such file or directory
> : 226 Transfer complete.
> : ftp> quit
> : ---> QUIT
> : 221 Goodbye.
>
> > - a new utility function, PacketUnaliasOut (see alias.c)
> >
> I have left it out as well as QueryUdpTcp*().
>
> > Note, the FTP aliasing now ensures that:
> >
> > 1. the segment preceding a PORT/227 segment terminates with a \r\n.
> > 2. the IP address in the PORT/227 matches the source IP address of
> >the packet.
> > 3. the port number in the PORT command or 277 reply is greater than
> >or equal to 1024
>
> Additional minor changes I have made:
>
> - Moved data structures declarations local to alias_db.c back from
>   alias_local.h to alias_db.c;
>
> - New functions {Set|Get}LastLineCrlfTermed() for use instead of
>   explicitly manipulating link flags inside alias_ftp.c;
>
> And I have put the new version of patch:
>
> http://people.FreeBSD.org/~ru/libalias.patch.2
>
> 
> I still have to have my questions answered in order to commit PPTP
> part of this patch.
> 
>
> Cheers,
> --
> Ruslan Ermilov  Oracle Developer/DBA,
> [EMAIL PROTECTED]   Sunbay Software AG,
> [EMAIL PROTECTED]  FreeBSD committer,
> +380.652.512.251Simfer

Re: freebsd bios.

[Jordan K. Hubbard]

> So, I repeat: easily done, not acceptable to freebsd core. 

Erm, hello?

I really don't understand this message at all, Ron.  As far as I know,
FreeBSD core has expressed NO opinion on this issue whatsoever and
it's therefore highly unfair of you to state that we:

 a) Even have a firm opinion on the linuxbios effort
 b) Have already concluded it's "not acceptable"

If you're talking about Mike Smith's comments then even the most
elementary research on your part will turn up several pertinent facts:

 a) Mike Smith speaks purely for himself and states only his own
opinion.  Nobody appointed him "spokesperson for the FreeBSD
community" any more than Jesus Monroy, Jr. holds that position.

 b) Mike Smith is not core.

Thank you,

- Jordan


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

Re: freebsd bios.

[Poul-Henning Kamp]

>> The key is that freebsd may need to change a few things to make it
>> bootable from cold hardware. I don't think this is for sure, but it may
>> happen. I hope the team is receptive to such changes ... 
>
>ie. "LinuxBIOS won't initialise the system correctly, so you'd better 
>clean up after it"?

How is the microcode loading handled in LinuxBIOS ?  As far as I know
getting hold of the microcode-supplemental data from Intel is a process
which is (impossible - epsilon) and certainly not open source compatible ?

--
Poul-Henning Kamp   | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD coreteam member | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

Re: RealSystem module for libalias

[Brian Somers]

> Brian, this is just to let you know that:
> 
> 1) I am currently in process of applying *big* PPTP patch to libalias
>so I would really appreciate it if you do not touch libalias before
>I finish with PPTP part.

Ok, no problem - I'm pretty busy at the moment anyway.

> 2) Erik Salander <[EMAIL PROTECTED]> is working together with Mr. Junichi 
>on $Subject issue (see attached), so you will probably want to contact
>them directly, since I am not particularly interested in these changes.
>But I would appreciate if you send me the patch for review before you
>commit it.

Absolutely - I planned to anyway.

Cheers.
-- 
Brian <[EMAIL PROTECTED]>
     
Don't _EVER_ lose your sense of humour !




To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

Re: cool

[Richard Wackerbarth]

On Thu, 15 Jun 2000, Greg Lehey wrote:
> [Format recovered--see http://www.lemis.com/email/email-format.html]
>
> On Wednesday, 14 June 2000 at  1:00:27 -0700, Julian Elischer wrote:
> > So, if you are in the Singapore Changi international airport,
> > the internet center in the transit area will loan you for FREE,
> > a wavelan PC-CARD.

> > jules# /sbin/dhclient
> > ifconfig: ioctl (SIOCAIFADDR): File exists
> > Listening on BPF/wi0/00:60:1d:1e:42:6c
> > Sending on   BPF/wi0/00:60:1d:1e:42:6c
> > Can't find free bpf: No such file or directory

> > And the log files showed..
> > Jun 14 00:54:37 jules dhclient: Can't find free bpf:

> > now if I can get dhcp to work this would be great!

> So how do they expect people to get these things to work without DHCP?

I looks to me like Julian's machine has the configuration problem.
The dhcp client cannot get enough bpf's.


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

Re: cool

[Ben Smithurst]

Richard Wackerbarth wrote:

> I looks to me like Julian's machine has the configuration problem.
> The dhcp client cannot get enough bpf's.

So why did tcpdump work?  Both dhclient and tcpdump need one bpf, no?  I
initially thought the same as you but then asked myself that question.

-- 
Ben Smithurst / [EMAIL PROTECTED] / PGP: 0x99392F7D

 PGP signature

Re: Anybody working on FreeBSD BIOS?

[Fred Clift]

> 
> I'm interested, since from reading the linixboot page it seems like
> you can get, essentially, and instant-on rommable FreeBSD if this
> were done, and I can think of lots of things to do with that!
> 



I can think of a few useful things too!  I might even be able to offer a
bit of help (at least testing...).  Let me know if you ever get around to
working on this.

Fred

--
Fred Clift - [EMAIL PROTECTED] -- Remember: If brute 
force doesn't work, you're just not using enough.



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

Re: Anybody working on FreeBSD BIOS?

[Wes Peters]

Sergey Babkin wrote:
> 
> Eh ? I don't quite get how Sun could be associated with Open Firmware.

Probably because they developed it?

> It always looked quite proprietary to me.

Yeah, those IEEE standards are terribly proprietary.  IEEE-1275 in this
case.  You can find more info at http://www.openfirmware.org/

-- 
"Where am I, and what am I doing in this handbasket?"

Wes Peters Softweyr LLC
[EMAIL PROTECTED]   http://softweyr.com/


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

mmap and file writes...???

[Joy Ganguly]

hi all,

i have a question regarding mmap and file write. a file is mmap'ed and
data is written into the mapped region. now the same region is written.
(as shown below)

buf = mmap(NULL, len, PROT_READ | PROT_WRITE, MAP_SHARED, fd, 0);
.
.  /* some data put in buf */
.

write(fd, buf, len);


now does this lead to unnecessary copies?? more specifically  what
happens if two virtual addresses point to the same physical address and
data is copied from one to the other.

thanx in advance

joy



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

Re: Anybody working on FreeBSD BIOS?

[Stefan Molnar]

On Thu, 15 Jun 2000, Doug White wrote:

> On Thu, 15 Jun 2000, Stefan Molnar wrote:
> 
> > I have not built clusters over 200 nodes, but I almost never 
> > go into the BIOS for configurations.  And the systems that 
> > I have used, include serial access within the BIOS.   And
> > adding PXE roms will make things nicer on the install front.
> > But my current system is a single floppy, and that works
> > well.
> 
> As someone who has built one of these large systems, the best thing we
> could want is OpenFirmware with a ROM monitor and Lights-Out Monitoring.  
> Basically make a PC act like a Sun Netra T1. :)

I love the NetraT1, I am now using them at Major broadcasters and
at DirecTV.   But gettting the LOM functionality to x86 is a completly
diffrent matter.   Since it has to act independtly from the mainboard.
I would much rather see the BIOS be converted to OpenBoot.  Since
that works greatly.

> In real life, the only BIOS problems that require human intervention are
> usually hardware related.  You can't avoid the trip to the colo in this
> case.  

I picked the remote hands service plan at my colo to be that human.  When
I see it is an issue to go that route.
 
> The buildout cost is pretty spendy too, having to buy a Cisco 2511 or
> similiar term server for every 24-odd boxen.  For us, this would mean
> buying 20 or so units and cabling up every box, which we don't have the
> time to do. We just leave 9" mono VGA displays and keyboards in the cage
> and call up the remote-hands when things die.  We let them power cycle
> things but if it's really hosed we drive over and frob the box ourselves.

I went the 2611 route with 32port async module, but the overall time
and effort does save in the long run.  I am a firm beliver that 
serial console for servers, and remote systems is not an option.
I is a must.  It has saved alot of down time.  I delgated the remote-hands
to being my human on-off switch, or a "blinky light" monitor.  

> BTW the PXE loader stuff is invaluable for installs.  Saves having to
> track down a (usually broken) floppy to load a system up.  A few
> keypresses at boot and voila, new FreeBSD box. :)  I will probably give a
> talk at BSDCon about these issues, if I can get everything lined up.

And I will be right there in the audiance.

> > The best people to determin if it is nessesary is Yahoo and Hotmail.
> > Since they have worked with these issues in the thousands of machines.
> 
> Sigh, it's not easy being #6. Even with 16 million confirmed members
> eGroups gets no respect  :)

Yeah, I normaly forget about them, I think eCircles uses FBSD as
well.


Stefan


> Doug White|  FreeBSD: The Power to Serve
> [EMAIL PROTECTED] |  www.FreeBSD.org
> 



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

Re: freebsd bios.

[Fred Clift]

> 
> We really were hoping we'd get some help from a motherboard vendor but
> that just hasn't been the case.  No-one seems interested in the
> relatively low quantities of boards we'd move.

Too bad we're already a big customer of these boards  -- We'd love to have
this kind of information about them, but I'm afraid we've lost our
leverage now that we've purchased more than a couple of thousand of
them... sigh


--
Fred Clift - [EMAIL PROTECTED] -- Remember: If brute 
force doesn't work, you're just not using enough.



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

Re: Anybody working on FreeBSD BIOS?

[Robert Withrow]

[EMAIL PROTECTED] said:
:- None of the motherboard or chipset vendors (except for SiS) are even
:- slightly interested in talking to us.

Are they interested in talking to Linux folks?  If so, isn't that a
reasonable alternative?  (I mean, team up with some Linux folks to
get the info...)

-- 
Robert Withrow -- (+1 978 288 8256)
[EMAIL PROTECTED]



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

Problem installing FreeBSD 4.0

[Sbenitez]

-- Forwarded by Satcha Benitez/Milwaukee/RA/Rockwell on
06/16/2000 10:55 AM ---


Satcha Benitez
06/16/2000 10:33 AM

To:   [EMAIL PROTECTED]
cc:
Subject:  Problem installing FreeBSD 4.0

Hi,
>
>My name is Satcha Benitez and I'm trying to install FreeBSD in a Gateway
>P5-90. I'm having some problems and i was wondering if you could help me
>out. This is my first time, although i'm familiar with UNIX.
>
>First, i formated the hard drive (i had win95 before) and copied /bin
>and /manpages from your web site, by using a CR-ROM. I also created the
>2 disks, kern.flp and mfsroot.flp.
>
>When i boot the computer with the kern.flp disk starts doing some staff
>and then the computer asks for the mfsroot.flp disk. I insert the disk
>and the Kernel Configuration Menu pops up. I choose the full-screen
>visual mode and i get the menu with the active and inactive drivers. I
>get 8 conflicts so i disable those drivers. Once i hit Q to save and
>exit i get a bunch of messages

After i press Q i get the following messages:

avail memory = 26640384 (26016K bytes)
Preloaded elf kernel "kernel" at 0xc05e7000
Preloaded mfs_root "/mfsroot" at 0xc05e7084
Intel Pentium detected, installing woraround for F00F bug
md0 : Preloaded image  2949120 bytes at 0xc0315b98
md1 : Malloc disk
npx0 :  on motherboard
npx0 : INT 16 interface
pcib0 :  on motherboard
pci0 :  on pcib0
atapci0: 
port 0
x3f4-0x3f7,0x1f0-0x1f7 at device 1.0 on pci0
atapci0: Busmastering DMA not supported
panic: resource_list_alloc : resource entry is busy
Uptime: 0s
Automatic reboot in 15 seconds - press any key on the console to abort


>I'm stuck here. I don't know what to do. I've read all the documentation
>but nothing. Could you please help me out? I' really appreciate.
>
>Thanks a lot. I look forward to hearing from you.
>
>Satcha Benitez.
>[EMAIL PROTECTED]
>





To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

Re: freebsd bios.

[Ronald G Minnich]

sorry, jordan. 

my bad. Anyway we're going to try a kernel next week that parag sent me.

ron




To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

Re: freebsd bios.

[Ronald G Minnich]

(paul asks a good microcode question). I can't answer it yet.

Here's my take on this: we're going to do a proof of concept of this idea.
We now have three partners: SiS, Compaq, and Dell. Long-term goal is to
get industry to pick it up. This is a means to an end. I don't want to be
Mr. LinuxBIOS forever .

If it works, my life is easier: I've got a totally open source BIOS. If I
want to net boot over Myrinet, no problem. If I want to net boot over SCI,
no problem. There is lots of other stuff I get *if this works*. I can use
a 100 mbit/second network for node maintenance instead of a 9600 baud
serial port (am I the only guy who is amazed that we're STILL using 9600
baud to run our consoles?)

If it doesn't work, well, that's a datapoint. 

If it doesn't work on everything out there just yet, That's not failure.
We were in this same boat in 1991, and things worked out in spite of a lot
of doomsayers. I'll specify in my next cluster RFQ that It Must Run
LinuxBIOS. Simple. Companies who want to play, can. Those who don't,
won't. 

But what the heck, it's been a lot of fun.

ron




To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

3dfx driver for freebsd

[Coleman Kane]

Here's the address of the 3dfx device driver I wrote for freebsd:
http://pohl.ececs.uc.edu/~cokane/

Please test it some more and give me feedback. Could someone please email me
with information on submitting this to the CVS commit team?

-- 
Coleman Kane
President, 
UC Free O.S. Users Group - http://pohl.ececs.uc.edu


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

Re: Anybody working on FreeBSD BIOS?

[Parag Patel]

On Fri, 16 Jun 2000 11:13:18 EDT, Robert Withrow wrote:
>
>[EMAIL PROTECTED] said:
>:- None of the motherboard or chipset vendors (except for SiS) are even
>:- slightly interested in talking to us.
>
>Are they interested in talking to Linux folks?  If so, isn't that a
>reasonable alternative?  (I mean, team up with some Linux folks to
>get the info...)

Actually, the SiS folks are working with the Linux folks.  Other than
them, no-one else seems to be interested.  SiS doesn't make motherboards
- just the chipsets - so they're having much the same level of pain that
we are trying to figure out how things need to be turned on.  At least
they have BIOS gurus to help out.

No-one else seems to be interested.  There seems to be plenty of demand
for servers, which is why we decided to attempt this lunacy.  If anyone
has a useful contact at a motherboard manufacturer, *please* let us or
the LinuxBIOS folks know.


-- Parag


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

Re: [Oz-ISP] FreeBSD and the forces of darkness. Real religious wars! (fwd)

[Parag Patel]

On Fri, 16 Jun 2000 02:33:00 EDT, Mike Nowlin wrote:
>
>Maybe I'll have my graphics guy whip up a picture of Tux with horns and
>holding a pitchfork
>
>(Actually, I think I've seen something like that before.)

Can your graphics guy whip up a couple of Daemons in the style of
Southpark (esp.  Cartman) and the PowerPuff Girls?  Just a couple of
things I want to see...


-- Parag Patel


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

Re: [Oz-ISP] FreeBSD and the forces of darkness. Real religious wars! (fwd)

[Jack Rusher]

Parag Patel wrote:
> 
> Can your graphics guy whip up a couple of Daemons in the style of
> Southpark (esp.  Cartman) and the PowerPuff Girls?  Just a couple of
> things I want to see...

  Oh... My... God...  I would pay to print the t-shirts.

-- 
Jack Rusher, Senior Engineer | mailto:[EMAIL PROTECTED]
Integratus, Inc. | http://www.integratus.com


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

Re: [Oz-ISP] FreeBSD and the forces of darkness. Real religiouswars! (fwd)

[FENIX.LOCALHOST.NL]

I found this funny site look at it :)
http://www.rewls.nu
Have Fun ;-)

On Fri, 16 Jun 2000, Parag Patel wrote:

> On Fri, 16 Jun 2000 02:33:00 EDT, Mike Nowlin wrote:
> >
> >Maybe I'll have my graphics guy whip up a picture of Tux with horns and
> >holding a pitchfork
> >
> >(Actually, I think I've seen something like that before.)
> 
> Can your graphics guy whip up a couple of Daemons in the style of
> Southpark (esp.  Cartman) and the PowerPuff Girls?  Just a couple of
> things I want to see...
> 
> 
>   -- Parag Patel
> 
> 
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-hackers" in the body of the message
> 



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

Re: Anybody working on FreeBSD BIOS?

[Ronald G Minnich]

On Fri, 16 Jun 2000, Parag Patel wrote:

> No-one else seems to be interested. 

actually, that's not quite true. we're seeing a fair amount of interest
here. I suspect vendors are not that interested in supporting another BIOS
unless/until they see potential $$$ ("value proposition" in MBA speak). We
seem to have found a workable value proposition here. It won't cost them
anything, and they get the results of our work on sourceforge.net, and
there may be competitive advantage in the Linux market at some point.

I think Parag's work is quite good but he has a tougher job than we do.

but we'll see how it all plays out :-) 

ron



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

Re: [Oz-ISP] FreeBSD and the forces of darkness. Real religious wars! (fwd)

[Parag Patel]

On Fri, 16 Jun 2000 10:46:58 PDT, Jack Rusher wrote:
>
>Parag Patel wrote:
>> 
>> Can your graphics guy whip up a couple of Daemons in the style of
>> Southpark (esp.  Cartman) and the PowerPuff Girls?  Just a couple of
>> things I want to see...
>
>  Oh... My... God...  I would pay to print the t-shirts.

"Respect my Authority!"


-- Parag


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

Re: [Oz-ISP] FreeBSD and the forces of darkness. Real religiouswars! (fwd)

[James Howard]

On Fri, 16 Jun 2000, Jack Rusher wrote:

> Parag Patel wrote:
> > 
> > Can your graphics guy whip up a couple of Daemons in the style of
> > Southpark (esp.  Cartman) and the PowerPuff Girls?  Just a couple of
> > things I want to see...
> 
>   Oh... My... God...  I would pay to print the t-shirts.

Oh my God, you killed Tux!  You Bas--wait, thanks!

Jamie



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

Re: cool

[Julian Elischer]

Ben Smithurst wrote:
> 
> Richard Wackerbarth wrote:
> 
> > I looks to me like Julian's machine has the configuration problem.
> > The dhcp client cannot get enough bpf's.
> 
> So why did tcpdump work?  Both dhclient and tcpdump need one bpf, no?  I
> initially thought the same as you but then asked myself that question.


I got it going..
dchp required one for each interface, (I have 2)
and tcpdump onoy needed 1. I only had 1 in /dev.

Julian

So if you are ever travelling through singapore airport, check your
 email for free bofore you get out of customs :-)




> 
> --
> Ben Smithurst / [EMAIL PROTECTED] / PGP: 0x99392F7D
> 
> ---
> 
>Part 1.2   Type: application/pgp-signature

-- 
  ^
  |
  __--_|\  Julian Elischer
 /   \ [EMAIL PROTECTED]
(   OZ) World tour 2000
 )_.---._/  presently in:  Singapore
v


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

Re: Anybody working on FreeBSD BIOS?

[Matthew N. Dodd]

On Fri, 16 Jun 2000, Stefan Molnar wrote:
> I delgated the remote-hands to being my human on-off switch, or a
> "blinky light" monitor.

Buy a bunch of RPC-2s or RPC-4s

http://baytechdcd.com/products/rpcseries.shtml

-- 
| Matthew N. Dodd  | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD  |
| [EMAIL PROTECTED] |   2 x '84 Volvo 245DL| ix86,sparc,pmax |
| http://www.jurai.net/~winter | This Space For Rent  | ISO8802.5 4ever |



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

Re: [Oz-ISP] FreeBSD and the forces of darkness. Real religious wars! (fwd)

[Terrance Young]

I'd buy one hehe


Jack Rusher wrote:

> Parag Patel wrote:
> >
> > Can your graphics guy whip up a couple of Daemons in the style of
> > Southpark (esp.  Cartman) and the PowerPuff Girls?  Just a couple of
> > things I want to see...
>
>   Oh... My... God...  I would pay to print the t-shirts.
>
> --
> Jack Rusher, Senior Engineer | mailto:[EMAIL PROTECTED]
> Integratus, Inc. | http://www.integratus.com
>
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-hackers" in the body of the message



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

Re: mmap and file writes...???

[Matthew Dillon]

:hi all,
:
:i have a question regarding mmap and file write. a file is mmap'ed and
:data is written into the mapped region. now the same region is written.
:(as shown below)
:
:buf = mmap(NULL, len, PROT_READ | PROT_WRITE, MAP_SHARED, fd, 0);
:.
:.  /* some data put in buf */
:.
:
:write(fd, buf, len);
:
:
:now does this lead to unnecessary copies?? more specifically  what
:happens if two virtual addresses point to the same physical address and
:data is copied from one to the other.
:
:thanx in advance
:
:joy

You can copy data from one part of a file to another using
this method, but only if the two areas do not overlap.If
the areas overlap, the result will be possible corruption of the
file.

-Matt
Matthew Dillon 
<[EMAIL PROTECTED]>


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

RE: freebsd bios.

[Sean Jensen_Grey]

[not on list]

Regarding the freebsd bios and availablity of firmware you should check out 

http://developer.intel.com/technology/efi/index.htm

The sample implementation uses a FBSD core and provides

a tcp/ip stack
ftp client and server
python interpreter

read

http://developer.intel.com/technology/efi/toolkit_overview.htm

for a full list of features.

All IA-64 machines boot using EFI.



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

Re: Anybody working on FreeBSD BIOS?

[Sergey Babkin]

Wes Peters wrote:
> 
> Sergey Babkin wrote:
> >
> > Eh ? I don't quite get how Sun could be associated with Open Firmware.
> 
> Probably because they developed it?

Ah, that was my ignorance. never knew that Open Firmware is a trademarked
concept, like Open Source.
 
> > It always looked quite proprietary to me.
> 
> Yeah, those IEEE standards are terribly proprietary.  IEEE-1275 in this
> case.  You can find more info at http://www.openfirmware.org/

Thanks for the pointer. When I encountered this thing in a Sun
workstation (without any docs included) this Forth-based
interface looked theoretically wonderful but practically rather
awful. I still don't know if it can be configured to boot from
the first available disk on the SCSI bus as opposed to booting
from a disk with specific SCSI ID though I spent half a day
trying to figure it out. Maybe I'll find it out now.

-SB


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

Re: freebsd bios.

[Daniel C. Sobral]

Ronald G Minnich wrote:
> 
> my bad. Anyway we're going to try a kernel next week that parag sent me.

Mmmm. I saw no comments on my loader question.

Loader(8) runs using BIOS services, and loads the kernel from any drive
that BIOS recognizes. It has also been enhanced with PXE knowledge, so
he can load from that to.

I think that your best bet would be booting loader instead of a kernel.
If your BIOS project recognizes the flash card as a disk, accessible
with normal BIOS functions, then loader can work as is (minus whatever
you need modified). If not, it can be changed to understand whatever you
have to access the data in the flash card.

Anyway, booting straight to kernel is a bad idea nowadays for many
reasons.

-- 
Daniel C. Sobral(8-DCS)
[EMAIL PROTECTED]
[EMAIL PROTECTED]
[EMAIL PROTECTED]

"He is my minion, so he doesn't need a name."


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

use of '#pragma weak...'

[Matthew Jacob]

Now that the heat wave is over in SFback to my loadable module project
changes to isp... maybe this is more for the toolchain folks than kernel
hackers...

So, I notice that '#pragma weak' appears to work for me for the compilers and
linkers we currently use for i386 && alpha (at least in user space), so you
can do things like:

-
extern void *isp_static_fw_vector(void);
#pragma weak isp_static_fw_vector

.

if (isp_static_fw_vector) {
/*
 * We have statically loaded f/w
 *
fw_ptr = isp_static_fw_vector();
} else {
/*
 * Statically loaded f/w not available. See if
 * there's a module for it somewhere and get the f/w
 * vector from there...
 */
fw_ptr = find_isp_fw_preloaded_module_and_return_fw_vector();
}

-


Is there any reason to *not* use this trick in the kernel?

-matt




To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

kern/18524

[Arun Sharma]

Not that it adds any more weight to my patch - but the linux
folks are essentially doing the same thing:

http://reality.sgi.com/dimitris_engr/pda_patch-2.4.0-1
http://www.freebsd.org/cgi/query-pr.cgi?pr=18524

-Arun


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

Re: routing bug(?) persists (PR 16318)

[Colin]

 What you're doing here is generally referred to as multi-netting.  When
you're wandering through the references, use that as a starting point. 
Multi-netting is certainly valid, when implemented correctly.  I would
definately echo the sentiment elsewhere in this thread that you and your
ISP are using a broken implementation, and I honestly see no reason that what
you're doing should work at all.  Effectively you're telling your system that
the way to connect to networks that it's address is not part of is to send a
message to a host that is on a network it's address is not part of.  It's a
networking catch-22 ;)  Either you or your ISP needs to alias the adapter on
this set of subnets, and if you're not the only person on this multi-netted
section, it really should be them.
 This is definately a routing bug, but it's in Win and Linux if they alloow
this with no error.

Cheers,
Colin
 
On 15-Jun-00 Mike Smith wrote:
>> On Thu, Jun 15, 2000 at 07:33:36AM -0700, Mike Smith wrote:
>> > [mjy]
>> > > ifconfig_vr0="195.58.183.77 netmask 255.255.255.248"
>> > > static_routes="0 1"
>> > > route_0="-net 195.58.161.96 -netmask 255.255.255.240 -iface vr0"
>> > > route_1="default 195.58.161.97"
>> > 
>> > The above network configuration is incorrect - you need a gateway that is 
>> > directly reachable.
>> 
>> The gateway is physically connected to the same network, the physical
>> network
>> contains 2 (or more) distinct subnets.
> 
> Correct.  You are not, however, logically connected to the network on 
> which your gateway resides.
> 
>> > If you want to use the above default route, you need 
>> > to give your machine an address on the same network as your gateway, most 
>> > trivially by aliasing it onto the vr0 interface.
>> 
>> I don't see why that should be necessary - my ISP doesn't either, since he'd
>> have to part with another IP address. My ISP claims and I've verified that
>> the configuration above works trivially under Linux and Windows NT, and
>> as far as I can tell, the submitted patch does nothing more than to allow
>> the specified interface to be taken into consideration when "connectedness"
>> is determined (i.e. it allows the gateway to be in a different subnet as
>> long
>> as it is physically connected).
> 
> I would suggest you go find an introductory IP networking book, and get 
> two copies (one for yourself, and one for your ISP).  What you're trying 
> to do is a fundamental violation of the way that IP routing works, and 
> this is what the network stack is trying to tell you.
> 
> The fundamental problem is that when you send a datagram to your gateway, 
> you can't put a valid return address on it (because you don't have an 
> appearance on its network).  If you've put the interface's real address 
> in the datagram, you'll never get a reply because your gateway has no 
> idea how to route back to you.
> 
> If you can't get an IP on your gateway's network, alias another address on
> your private network onto the gateway system's interface and use that as
> your default route.  If your gateway is too lame to support multiple 
> addresses on an interface, use another system that does have a real 
> appearance on the gateway's network to route for you.
> 
> And read that book - it'll save you a lot of agony in the future.
> 
> 
> -- 
> \\ Give a man a fish, and you feed him for a day. \\  Mike Smith
> \\ Tell him he should learn how to fish himself,  \\  [EMAIL PROTECTED]
> \\ and he'll hate you for a lifetime. \\  [EMAIL PROTECTED]
> 
> 
> 
> 
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-hackers" in the body of the message


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

Re: kern/18524

[Garance A Drosihn]

At 5:29 PM -0700 6/16/00, Arun Sharma wrote:
>Not that it adds any more weight to my patch - but the
>linux folks are essentially doing the same thing:
>
>http://reality.sgi.com/dimitris_engr/pda_patch-2.4.0-1
>http://www.freebsd.org/cgi/query-pr.cgi?pr=18524
>

Ah, the per-CPU stats.  I was wondering what had happened
to that...


---
Garance Alistair Drosehn   =   [EMAIL PROTECTED]
Senior Systems Programmer  or  [EMAIL PROTECTED]
Rensselaer Polytechnic Institute


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

Re: ACPI project progress report

[Daniel C. Sobral]

Mitsuru IWASAKI wrote:
> 
>  - support S2, S3, S4 (hibernation) sleeping transition.  S4 sleep
>require some hack in boot loader needs help.

I thought hibernation was entirely controlled by kernel? What do you
need?

-- 
Daniel C. Sobral(8-DCS)
[EMAIL PROTECTED]
[EMAIL PROTECTED]
[EMAIL PROTECTED]

"He is my minion, so he doesn't need a name."


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

Re: ACPI project progress report

[Daniel C. Sobral]

"Daniel C. Sobral" wrote:
> 
> Mitsuru IWASAKI wrote:
> >
> >  - support S2, S3, S4 (hibernation) sleeping transition.  S4 sleep
> >require some hack in boot loader needs help.
> 
> I thought hibernation was entirely controlled by kernel? What do you
   ^^
Err, BIOS.

> need?

-- 
Daniel C. Sobral(8-DCS)
[EMAIL PROTECTED]
[EMAIL PROTECTED]
[EMAIL PROTECTED]

"He is my minion, so he doesn't need a name."


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

ACPI project progress report

[Mitsuru IWASAKI]

Hi, here is the latest report on our ACPI project's progress.

Current status:
  The aml interpreter development is going on and we've ported it to
kernel simultaneously.  Now that we can build ACPI namespace and
search any named objects from there in kernel space.
  The aml interpreter code can be compiled and executed in both
userland (using I/O simulator) and kernel space so that we can
continue development even we ported the code in kernel.
  Next step would be implementation of the accessing facility for
system memory, ioport and so on, then simple method (eg _PTS with 1 or
5 and _WAK) must be able to executed soon.  This is our goal of
prototype development.

TODO:
 - combine sys/isa/pnpparse.c with interpreter.
 - support S2, S3, S4 (hibernation) sleeping transition.  S4 sleep
   require some hack in boot loader needs help.
 - implement serialization and synchronization mechanism.
 - migrate to Intel ACPICA? (but that's too large to understand.  I'm
   not sure whether this has licencing issue or welcome to import it into
   our repository in terms of licencing policy... ours?  Yes, it's BSD
   Licence. No problem at all :-)
 - and many.

Obtaining source code:
To get ACPI project repository, please try CVSup with;
---
*default host=cvsup.jp.FreeBSD.org
*default base=/usr
*default prefix=/home/cvs
*default release=cvs 
*default delete use-rel-suffix
jp-acpi
---

cvsweb is also available at;
http://www.jp.freebsd.org/cgi/cvsweb.cgi/ACPI/?cvsroot=freebsd-jp>.

usr.sbin/acpi/amldb would be a good toy for you :-)

% ./amldb ../../../util/takawata/acpi/3110CT.dsdt.dat 
Loading ../../../util/takawata/acpi/3110CT.dsdt.dat...done
AML>r _PTS
Method: Arg 1 From 0x280f36ce To 0x280f3775
  Enter argument values (ex. number 1 / string foo). 'q' to quit.
  Arg0 ? n 1
 Running _PTS. 
AML>h
s   Single step
n   Step program
c   Continue program being debugged
q   Quit method execution
t   Show local name space tree and variables
i   Toggle region input prompt
o   Toggle region output prompt
m   Show memory management statistics
r   Run specified method
f   Find named objects from namespace.
h   Show this messsage
AML>


BTW, I (iwasaki) am going to USENIX 6/21 - 23, I'll happy to give a
demonstration on ACPI device driver and AML interpreter debugger if
anybody ask me to do it.

Here's the dmesg output from kernel with AML interpreter on TOSHIBA
PORTEGE 3110CT.  It's not fake :-)
There are 1735 times memory allocation here, but we couldn't find a
lowering of performance because of own memory management system.
95% of memory allocation is covered by pre-allocated memory storage
which is compiled in the interpreter module.

Thanks!

ACPI: Found ACPI BIOS data at 0xc00f0170 (, RSDT@3fe)
acpi0:  on motherboard
acpi0: ADDR RANGE 3fe 1 (mapped 0xc5774000)
acpi0: ADDR RANGE 100b6e00 200 (mapped 0xc5784e00)
acpi0: RSDT have 1 entries
acpi0: RSDT entry0 FACP
acpi0:  FACP found
acpi0:  DSDT found Size=17865 bytes
\\  
  IRQS  Method: Arg 2 From 0xc57783bf To 0xc5778691
  IRQR  Method: Arg 1 From 0xc57781de To 0xc57783b7
  CRSL  Method: Arg 1 From 0xc5778165 To 0xc57781d6
  PRSL  Method: Arg 1 From 0xc57780d3 To 0xc577815d
  STAL  Method: Arg 1 From 0xc577808c To 0xc57780cb
  PSC_  Method: Arg 1 From 0xc5778054 To 0xc5778084
  WPSX  Method: Arg 4 From 0xc5777fd7 To 0xc577804d
  PS3_  Method: Arg 1 From 0xc5777f70 To 0xc5777fcf
  PS0_  Method: Arg 1 From 0xc5777f09 To 0xc5777f68
  DIS_  Method: Arg 1 From 0xc5777e7c To 0xc5777f01
  SRS_  Method: Arg 2 From 0xc5777dde To 0xc5777e74
  PRS_  Method: Arg 1 From 0xc5777d07 To 0xc5777dd6
  CRS_  Method: Arg 1 From 0xc5777c30 To 0xc5777cff
  STA_  Method: Arg 1 From 0xc5777b93 To 0xc5777c28
  SMBR  Method: Arg 5 From 0xc5777b2e To 0xc5777b8b
  TRAP  Method: Arg 1 From 0xc5777b1d To 0xc5777b26
  _WAK  Method: Arg 1 From 0xc5777869 To 0xc5777b16
  _PTS  Method: Arg 1 From 0xc5ba To 0xc5777861
  _GPE  
_L00  Method: Arg 0 From 0xc598 To 0xc5b2
_L1E  Method: Arg 8 From 0xc581 To 0xc591
_L19  Method: Arg 8 From 0xc52f To 0xc57a
_L18  Method: Arg 8 From 0xc577765b To 0xc527
_L0C  Method: Arg 8 From 0xc5777608 To 0xc5777653
_L0B  Method: Arg 8 From 0xc5777188 To 0xc5777600
_L08  Method: Arg 8 From 0xc5777139 To 0xc5777180
  _TZ_  
THRM  Thermalzone
  _TSP  Num:0x708
  _TC2  Num:0x2
  _TC1  Num:0x9
  _CRT  Method: Arg 0 From 0xc5777103 To 0xc5777113
  _PSL  Package:elements 1 
  _PSV  Method: Arg 0 From 0xc57770da To 0xc57770ea
  _AL1  Package:elements 1 
  _AL0  Package:elements 1 
  _AC1  Method: Arg 0 From 0xc577709f To 0xc57770af
  _AC0  Method: Arg 0 From 0xc5777088 To 0xc5777098
  _TMP  Method: Arg 0 From 0xc5777023 To 0xc5777081
FAN_  Device
  _PR0  Package:elements 1 
  _HID  Num:0xb0cd041
PFAN  PowerResource:Level 0 Order 0

Re: routing bug(?) persists (PR 16318)

[Marinos J . Yannikos]

On Fri, Jun 16, 2000 at 09:17:13PM -0400, Colin wrote:
> [...] I honestly see no reason that what
> you're doing should work at all.  Effectively you're telling your system that
> the way to connect to networks that it's address is not part of is to send a
> message to a host that is on a network it's address is not part of.  It's a
> networking catch-22 ;)

It's not exactly a "catch-22", since the (perfectly valid) static route to
the default gateway's network takes precedence over the above rule (the
default route).

> Either you or your ISP needs to alias the adapter on
> this set of subnets, and if you're not the only person on this multi-netted
> section, it really should be them.

The ISP is giving away lots of /29 subnets and this is a kludge to provide
each client with 1 more useable IP. It's not easy to get many IPs these days.

>  This is definately a routing bug, but it's in Win and Linux if they alloow
> this with no error.

Windows apparently allows the configuration even without the static route to
the gateway's network, which is very odd.

-mjy
-- 
***==> Marinos J. Yannikos <[EMAIL PROTECTED]>
***==> http://pobox.com/~mjy


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

RE: [Oz-ISP] FreeBSD and the forces of darkness. Real religiouswars! (fwd)

[James Johnson]

This is now my splash screen.

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of
FENIX.LOCALHOST.NL
Sent: Friday, June 16, 2000 10:49 AM
To: Parag Patel
Cc: Mike Nowlin; Mark Newton; [EMAIL PROTECTED]
Subject: Re: [Oz-ISP] FreeBSD and the forces of darkness. Real
religiouswars! (fwd) 


I found this funny site look at it :)
http://www.rewls.nu
Have Fun ;-)

On Fri, 16 Jun 2000, Parag Patel wrote:

> On Fri, 16 Jun 2000 02:33:00 EDT, Mike Nowlin wrote:
> >
> >Maybe I'll have my graphics guy whip up a picture of Tux with horns and
> >holding a pitchfork
> >
> >(Actually, I think I've seen something like that before.)
> 
> Can your graphics guy whip up a couple of Daemons in the style of
> Southpark (esp.  Cartman) and the PowerPuff Girls?  Just a couple of
> things I want to see...
> 
> 
>   -- Parag Patel
> 
> 
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-hackers" in the body of the message
> 



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message




To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

Re: loading modules from within the kernel....

[Matthew Jacob]

The more I look at the preload way of doing things, the more I see this as
something of a lose.

What we want to do is to load the fw module if and only if there is h/w for
it, and then unload it when we're done. We want to do this w/o user
intervention, else why bother (as we could have gotten them to run config
compiling in f/w if the want to support this card).

What we have the tools for is to get the loader(8) to load it for you, if you
request it (i.e., by modifying /boot/loader.conf to specifically *add* it, or
by modifying /boot/defaults/loader.conf to make default loaded (leaving to the
user to edit /boot/loader.conf to disable the load), plus (I haven't done this
step yet) some goop to run around and hand bind it from isp_pci so you can
either get at the data directly, or (which I would prefer) get at the function
that isp_pci will call which will pass back a pointer to f/w.

But there's nothing there to unload this module if you *don't* have the h/w
(i.e., all probes for isp fail), unless I stick the PCI lookup info into this
module (and it unloads itself... can it? Is there a mechanism where we can
mark a container for unloading later so it can be scavenged?).

So, what we end up with is more text code, a bunch of new places to touch
(like defaults/loader.conf) and nothing to reduce the bloat (which was the
whole point of this exercise) if you don't have the h/w.

*groan*

-matt






To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

Re: freebsd bios.

[Parag Patel]

On Sat, 17 Jun 2000 07:35:51 +0900, "Daniel C. Sobral" wrote:
>
>Ronald G Minnich wrote:
>> 
>> my bad. Anyway we're going to try a kernel next week that parag sent me.
>
>Mmmm. I saw no comments on my loader question.
>
>Loader(8) runs using BIOS services, and loads the kernel from any drive
>that BIOS recognizes. It has also been enhanced with PXE knowledge, so
>he can load from that to.

Good idea - I'll send a /boot kit to Ron, if he hasn't already gotten it
elsewhere.  It's worth a shot.  Ron?  It's another couple hundred Kb
tarball out of which you can extract boot/loader.


-- Parag


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

Re: routing bug(?) persists (PR 16318)

[Nick Rogness]

On Sat, 17 Jun 2000, Marinos J . Yannikos wrote:

> On Fri, Jun 16, 2000 at 09:17:13PM -0400, Colin wrote:
> It's not exactly a "catch-22", since the (perfectly valid) static route to
> the default gateway's network takes precedence over the above rule (the
> default route).

So how are they handling the routes pointing to you?  Static
routes? or VLANs or what? Messy...just plain messy.  These routing
'rules' are setup for certain reasons...to stop slopping routing
techniques.  This should all be handled by routing protocols
anyway.  


> > Either you or your ISP needs to alias the adapter on
> > this set of subnets, and if you're not the only person on this multi-netted
> > section, it really should be them.
> 
> The ISP is giving away lots of /29 subnets and this is a kludge to provide
> each client with 1 more useable IP. It's not easy to get many IPs these days.

That is exactly what NAT was designed to do.  WHat's wrong with a
/30?  If they are running out of IP's, that is a design flaw in
the capacity planning of your ISP...or they don't know
what they are doing.  Either way, your SOL ;-)

> 
> Windows apparently allows the configuration even without the static route to
> the gateway's network, which is very odd.

That's not suprising at all.  Windows can also not handle a /32
netmask on certain adapters.


Nick Rogness
- Speak softly and carry a Gigabit switch.




To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

Re: use of '#pragma weak...'

[John Polstra]

In article <[EMAIL PROTECTED]>,
Matthew Jacob  <[EMAIL PROTECTED]> wrote:
> 
> So, I notice that '#pragma weak' appears to work for me for the compilers and
> linkers we currently use for i386 && alpha (at least in user space), so you
> can do things like:
> 
> -
> extern void *isp_static_fw_vector(void);
> #pragma   weak isp_static_fw_vector
[...]
> Is there any reason to *not* use this trick in the kernel?

I won't address the question of whether to use weak symbols in the
kernel.  But I do have an opinion about how it should be done if
weak symbols are used.

Instead of using "#pragma weak", make a macro "__weak_definition" or
somesuch in .  It should look something like this:

#define __weak_definition   __attribute__ ((__weak__))

and it should be enclosed in the appropriate #ifdefs to ensure that
the compiler is GCC and its version is late enough to support it.
See the other examples in .  It would be used like
this:

extern void *isp_static_fw_vector(void) __weak_definition;

#pragma weak is bad because you can't put #pragmas into macros.

John
-- 
  John Polstra   [EMAIL PROTECTED]
  John D. Polstra & Co., Inc.Seattle, Washington USA
  "Disappointment is a good sign of basic intelligence."  -- Chögyam Trungpa



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

Re: ACPI project progress report

[Mitsuru IWASAKI]

Hi,

> "Daniel C. Sobral" wrote:
> > 
> > Mitsuru IWASAKI wrote:
> > >
> > >  - support S2, S3, S4 (hibernation) sleeping transition.  S4 sleep
> > >require some hack in boot loader needs help.
> > 
> > I thought hibernation was entirely controlled by kernel? What do you
>^^
> Err, BIOS.
> 
> > need?

Yes, we need to consider both.  In ACPI spec. 1.0b 9.1.4 S4 Sleeping
State, this is described that S4 supports two entry mechanisms: OS
initiated and BIOS initiated.

From: Intel, Microsoft, Toshiba
Subject: Advanced Configuration and Power Interface Specification 1.0b
Date: Tue, 2 Feb 1999 07:55:24 +0900
> In the OS-initiated S4 sleeping state, the OS is responsible for
> saving all system context. Before entering the S4 state, the OS will
> save context of all memory. Upon awakening, the OS will then restore
> the system context.  When the OS re-enumerates buses coming out of the
> S4 sleeping state, it will discover any devices that have come and
> gone, and configure devices as they are turned on.

I think OS-initiated S4 (hibernation) in FreeBSD has enough advantages
because we can do `Save-to-Disk' anywhere even on non-laptop machines
which BIOS doesn't support hibernation.
FreeBSD supports crash dump facility here, so I'm expecting that
`Save-to-Disk' by kernel would not be so difficult. We might need
dedicated swap partition for OS-initiated S4 because used swap areas
need to be protected for the system oprerations after awakening.
The boot loader is the best place for restoring the system context in
FreeBSD I think.

Unfortunately I don't have enough knowledge on crash dump and boot
loader to implement OS-initiated S4 transition (actually, this is not
related with ACPI at all).
I love to see someone say `hey!  I'll take this one!' :-)

Thanks


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message