Re: Unix Philosophers Please!
Bernd Walter [EMAIL PROTECTED] writes: In short: The data is tranfered into the kernel and dropped there. The data is never transferred into the kernel. There is no copyin() or uiomove() there. DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: forwarding
Martin Vana [EMAIL PROTECTED] writes: The problem is when I try to retrive any files from users. Than DC tryies to establish direct connection to user on ports from 410-415. How could I somehow 'catch' this request (SYN_SENT foo.foobar.com 41x) and forward it through ssh tunnel and back? You can't. Don't limit yourself to just one box, I also have another FreeBsd machine ready to serve. Is the other box outside the firewall? In that case, set up PPP on both boxen (see /usr/share/examples/ppp/ppp.conf.sample) and run PPP over SSH. On the inside box, set up a single static route to the outside box and let PPP take care of the default route. The outside box should run natd or ipnat unless you have a spare IP address you can use for the PPP link. DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: devfs?
In message [EMAIL PROTECTED] Dag-Erling Smorgrav writes: : Kevin D.Wooten [EMAIL PROTECTED] writes: : Well the linux devfs has a compatibility mode that maintains a /dev : that looks exactly like pre-devfs ( the actual list of files is : static ), and only links up ( mknod ) the newly added devices to the : pre-existing files. There is also the non-compatible mode which only : has files for the devices you actually have, and creates the files : on demand. : : What's the point with having device nodes for devices you don't have? So open return -1 with errno set to ENXIO rater than ENOENT. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: devfs?
What's the point with having device nodes for devices you don't have? A warm fuzzy feeling of having all the device nodes you're used to, even if the devices don't exist? :-) Steinar Haug, Nethelp consulting, [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: devfs?
On Tue, Nov 06, 2001 at 05:16:31PM +0100, Dag-Erling Smorgrav wrote: Kevin D.Wooten [EMAIL PROTECTED] writes: Well the linux devfs has a compatibility mode that maintains a /dev that looks exactly like pre-devfs ( the actual list of files is static ), and only links up ( mknod ) the newly added devices to the pre-existing files. There is also the non-compatible mode which only has files for the devices you actually have, and creates the files on demand. What's the point with having device nodes for devices you don't have? Historical sensitivity? Anyone in for a RK05 dev node? ;) -- | / o / /_ _ email: [EMAIL PROTECTED] |/|/ / / /( (_) Bulte Arnhem, The Netherlands To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
