Olicom Token Ring Cards
-
It does not … :(
-
FWIW, it's probably because we don't enable the oltr(4) driver:
http://www.freebsd.org/cgi/man.cgi?query=oltr&sektion=4&apropos=0&manpath=FreeBSD+6.1-RELEASE
in our kernel. I don't see much use for it in general in our tree though - it's outdated hardware and it's not worth putting a driver that maybe one person on this planet might use in the tree. I'd suggest pulling down the dev iso and rolling your own - the build process is relatively simple and all you need to do is add the driver to the kernel config. Or get a token ring -> ethernet translational bridge from Olicom (er eBay - hell I can probably dig a few out of the scrap pile at work sigh).–Bill
-
I'd suggest pulling down the dev iso and rolling your own - the build process is relatively simple and all you need to do is add the driver to the kernel config. Or get a token ring -> ethernet translational bridge from Olicom (er eBay - hell I can probably dig a few out of the scrap pile at work sigh).
–Bill
Can you give me the brief howto on that …
... do you mean down load the dev tar or just modify an install of rc1Might just take you up on the bridge offer.
Thanks
-
1. Download the developer ISO
2. Load the developer iso and then login to console
3. Wait for the developer bootstrap process to finish
3. Edit /home/pfsense/tools/builder_scripts/conf/pfSense.6 and add the device
5. cd /home/pfsense/tools/builder_scripts/
6. ./build_iso.shWait for it to finish and then you will see an ISO (it will tell you the location).
Please keep in mind this is unsupported territory you are in.
-
But it's gloriously FUN unsupported territory. :D
Really. This will get your foot into the burgening token-ring marketplace. It's about to boom I tell ya. ;D
-
Yeah legacy is a drag. Beats mass conversion ( $$$ and headache ) Sure Cobol programmers feel the same way. It nice to be able to make the transition tranparent.
Don't like it either, but it sure goes a long way when you can say "no problem can do that" to the people with the money.
With a poor attitude open source can leave a bad taste in Power that be. Open source is about just making it work, and work well. With the added bonus of not spending an arm and a leg.
On to real stuff …..
the script that graps the CVS file for pfSense inside of build_iso.sh just fails really not much information
-
The Freesbie server is currently offline. This data is needed to build a CD.
-
Ok, thanks
.. ETA … is there big problem or just routine up when u done?
-
Not sure what the problem is. I don't admin their server.
-
1. Download the developer ISO
2. Load the developer iso and then login to console
3. Wait for the developer bootstrap process to finish
3. Edit /home/pfsense/tools/builder_scripts/conf/pfSense.6 and add the device
5. cd /home/pfsense/tools/builder_scripts/
6. ./build_iso.shWait for it to finish and then you will see an ISO (it will tell you the location).
Please keep in mind this is unsupported territory you are in.
I know this is unsupported but could I get a little assistance so I can learn how this works …
I did as above, but update_cvs_depot function from inside build_iso.sh
complained
"move away pfSense/RELENG_1; it is in the way.
so I did some digging
added export SKIP_CHECKOUT=yes
and export SKIP_RSYNC=yes
to my pfsense_local.shbut it still tries to get CVS files
... so I commented out the call ( cvs is not important to me this point )
... so now when freebsd build is running I notice that it complained about not having
bsdinstaller
cpdup
lua
lighttpdhow do you get the these packages into the build process ????
thanks .......... ahead of time
-
Skip checkout and skip rsync?
You should probably allow one of those to run. I'd leave the checkout in there and set rsh=ssh.
That's the FreeBSD admin in me talking and not a pfSense dev, so YMMV. :)
Side note, I have a Token Ring Jetdirect card for a color laserjet sitting here that mistakenly shipped with my printer. Have a use for it? :D