Re: conversion
The Bios of the Interjet was never tested or compiled with Microsoft in mind. it is specifically tailored to boot FreeBSD with some special hacks to support the LCD on COM2 (or was that com1?) it is a 133MHz (or was that 233?) MHz chip for crying out aloud. why on EARTH would you wnat to run windows on it? (not to mention that it only has 32 MB of ram.) You cannot get access to the exisiting FreeBSD because it is hacked too much. The binaries are altered to use a database for many things FreeBSd uses flat files for. but the following should work for you: install the drive on a regular PC. install FreeBSD 4.6 from scratch. Set it to have a console on COM1 reinstall it on the machine log in on the serial port.. You should now have a standard FreeBSD machine with serial console COM2 at (hmm I forget the exact baud rate) should print to the LCD. On Sun, 7 Jul 102, JM wrote: > Anyone know how to convert an interjet to run windows 98?? or at least > to get root access on the exisiting freebsd? > > I have a Whistle Interjet 200 server. I am looking into converting this > over to windows 98, but one problem, the Interjet has a special bios. If > I install windows 98 on the HD, then it won't boot. Other than the > special bios, the interjet is made out of a "single board computer", > which is a motherboard packed on a half size ISA card. Do you know > anything about Interets? Can they be converted to windows just by > changing the bios chip? or is there something else that has to be done? > > > 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
conversion
Anyone know how to convert an interjet to run windows 98?? or at least to get root access on the exisiting freebsd? I have a Whistle Interjet 200 server. I am looking into converting this over to windows 98, but one problem, the Interjet has a special bios. If I install windows 98 on the HD, then it won't boot. Other than the special bios, the interjet is made out of a "single board computer", which is a motherboard packed on a half size ISA card. Do you know anything about Interets? Can they be converted to windows just by changing the bios chip? or is there something else that has to be done? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: 'make release' tries to build a port?
On Sun, Jul 07, 2002 at 03:18:55PM +0900, Makoto Matsushita wrote: > > > WORLD_FLAGS and/or KERNEL_FLAGS don't work for you? > > reichert> 'make -j 10 release' didn't work. > > Again, WORLD_FLAGS and/or KERNEL_FLAGS don't work for you? Sorry, you did ask a specific question. No, I hadn't tried those flags, so I can't say that they would have worked... > Yes, it would be better that whole release procedure works with make > -jN, but most of the time spent is "make buildworld/buildkernel" during > "make release," so setting WORLD_FLAGS/KERNEL_FLAGS may be enough to do. > > reichert> ===> Patching for ghostscript-gnu-nox11-7.05_1 > reichert> ===> Applying FreeBSD patches for ghostscript-gnu-nox11-7.05_1 > reichert> /usr/local/bin/sed_inplace: not found > > IMHO it is a ports issue. That it might be. :/ Again, thanks for the advice... > -- - > Makoto `MAR' Matsushita -- Brian 'you Bastard' Reichert<[EMAIL PROTECTED]> 37 Crystal Ave. #303Daytime number: (603) 434-6842 Derry NH 03038-1713 USA Intel architecture: the left-hand path To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
[광고] freebsd-hackers님 안녕하십니까? 평생동안,당신을 왕으로 모십니다!
Title: Çѱ¹°æÁ¦ ¸®Ä¡¿þÀÌ Å¬·´ ±ÍÇÏÀÇ ½Â¶ô¾øÀÌ È«º¸¼º ÀüÀÚ ¿ìÆíÀ» º¸³»°Ô µÈ Á¡ Á¤ÁßÈ÷ »ç°ú µå¸³´Ï´Ù. Á¤º¸Åë½Å¸ÁÀÌ¿ëÃËÁø¹ý ±ÔÁ¤À» ÁؼöÇÏ¿© ±¤°í¸ÞÀÏÀÓÀ» Ç¥½ÃÇÏ¿´À¸¸ç, ¼ö½Å°ÅºÎ ÀåÄ¡¸¦ ¸¶·ÃÇÏ°í ÀÖ½À´Ï´Ù. ±ÍÇÏÀÇ ÀüÀÚ ¿ìÆí ÁÖ¼Ò´Â ÀÎÅÍ³Ý »óÀÇ °ø°³µÈ Àå¼Ò¿¡¼ ½ÀµæÇÏ¿´À¸¸ç, ÀúÈñ´Â ±ÍÇÏÀÇ ÀüÀÚ¿ìÆí ÁÖ¼Ò ¿Ü ¾î¶°ÇÑ °³ÀÎÁ¤º¸µµ °¡Áö°í ÀÖÁö ¾ÊÀ¸¹Ç·Î ¾È½ÉÇϽñ⠹ٶø´Ï´Ù. ¼ö½ÅÀ» ¿øÄ¡ ¾ÊÀ¸½Ã¸é ¼ö½Å°ÅºÎ¸¦ Ŭ¸¯ÇØ Áֽʽÿä.
Re: multi-link 802.11b through netgraph yields poor performance.
In message:John Kozubik <[EMAIL PROTECTED]> writes: ... : laptops. Both are 4.5-RELEASE, one has two aironet LMC352 cards, and one : has two Lucent gold cards. ... : packet is dropped. Further, echo response time is between 2.2 and 2.5 : milliseconds, which seems very high. If these are in ISA PCMCIA adapters, then the ping times seem very reasonable to me. And even if they aren't, my laptop -> Lucent AP -> desktop has a ping time of 2.6ms - 2.7ms (my signal quality is 29 at the moment). Also, before blaming netgraph, which may well be to blame, could it be that you have interference from some other source that's making things bad? The exactly every other packet being dropped does seem to be a big clue. Also, if you set things up to be a routing situation (for experimental purposes), does the problem go away? Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: multi-link 802.11b through netgraph yields poor performance.
John Kozubik wrote: > Julian, Archie, et al, > > I have experimented with a multi-link 802.11b connection between two > laptops. Both are 4.5-RELEASE, one has two aironet LMC352 cards, and > one has two Lucent gold cards. > > I have successfully used ng_one2many, etc., to establish a working > multi-link between the two systems - however, I would appreciate any > comments regarding the very poor performance I see when networked in > this manner. > > The problem I see is that, when using `ping` on either machine, > exactly every other packet is dropped. After running `ping` for many > minutes, trying it from both machines, it is clear that _exactly_ > every other packet is dropped. Further, echo response time is > between 2.2 and 2.5 milliseconds, which seems very high. > Any comments as to why the problems I am seeing (half of packets > dropped and high latency) exist are appreciated. I am using a multilink connection between a fileserver and a switch, and it works fine. This is with regular 100Mbit ethernet cards. On one occasion I unplugged the "secondary" NIC from the switch without undoing the one2many setup. And every other packet to the machine was dropped. I saw the same thing you were seeing with your pings. So.. I would think that netgraph is doing its thing, distributing packets evenly between your two interfaces, but that one of the interfaces isn't behaving. My one2many script is essentially the same as yours except for the order. I don't know if it makes a difference (it _shouldn't_), but in my script I bring the secondary interface up before doing anything else (and then I load the ng_ether and ng_one2many modules, but I assume you're doing that elsewhere). I don't know a great deal about any of this, but I thought this might give you a clue as to what to look for. Good luck, JN To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
freebsd-hackers님, 한국상품 필요하세요? [광고]
Title: Untitled Document Made in Korea, ÀÚ¶û½º·± Çѱ¹ÀÎ!!! ÇÑ°Ü·¹ ÀåÅÍ(www.zhangter.com)´Â ÇØ¿Ü¿¡ °è½Å Çѱ¹ÀÎÀ» À§ÇÏ¿© ¸¶·ÃµÈ °í±¹ÀÇ ÇâÃë°¡ ³ª´Â Çѱ¹ »óÇ° Àü¹® ¼îÇθô ÀÔ´Ï´Ù. ¹«°ü¼¼, À¯Åë ¸¶Áø ¹èÁ¦·Î Àú·ÅÇÑ °¡°Ý, Çѱ¹ Á÷°ø±Þ¿¡ ÀÇÇÑ ½Å¼±ÇÑ »óÇ°À» ÀüÇØ µå¸³´Ï´Ù. ÇÑ°è·¹ ÀåÅÍ(www.zhangter.com)¿¡¼ ÇØ¿Ü µ¿Æ÷¿¡°Ô °³ÀÎ ¼Òºñ¿ëÀ¸·Î ±¹Á¦ ¿ìÆí¼ÒÆ÷¸¦ ÅëÇÏ¿© Çѱ¹¿¡¼ Á÷°ø±ÞÇÔÀ¸·Î½á Åë°ü ¼¼±ÝÀÌ ¾øÀ» »Ó´õ·¯ ¼öÀÔ¾÷ÀÚ ¹× Áß°£ À¯Åë¾÷ÀÚÀÇ À¯Åë ¸¶ÁøÀ» ¹èÁ¦ÇÏ¿© ¸Å¿ì Àú·ÅÇÑ °¡°ÝÀ¸·Î ½Å¼±ÇÑ Çѱ¹ »óÇ°À» »ç¿ëÇϽǼö ÀÖÀ¾´Ï´Ù. Çѱ¹ ±èÄ¡, ¹Ø¹ÝÂùµîÀÇ ½Ä·áÇ°À» ºñ·ÔÇÏ¿© Çѱ¹ ÈÀåÇ°, ¾Ç¼¼»ç¸®, À½¹Ýµî »ýÈ° ÇʼöÇ°À» ¸ðµÎ Áغñ ÇÏ¿´À¾´Ï´Ù. Çѹø ¹æ¹®ÇÏ¿© °í±¹ÀÇ ÇâÃëµµ ´À³¢½Ã°í, ÇÊ¿äÇÑ ÀÏ¿ëÇ°µµ ¸¶·ÃÇϽñ⠹ٶø´Ï´Ù. ¢¾¢¾¢¾ Çѱ¹¿¡¼ ÁÖ¹®, ÇØ¿Ü·Î ¹è¼Ûµµ °¡´ÉÇÕ´Ï´Ù. ÇØ¿Ü¿¡ °è½Å °¡Á·, Ä£Áö ¹× Ä£±¸¿¡°Ô °í±¹ÀÇ Á¤À» ÀüÇØ º¸½Ê½Ã¿ä. ¢¾¢¾¢¾ ´Ü ÇѹøÀÇ ClickÀ¸·Î Çѱ¹ »óÇ°À» ±¸ÇϽǼö ÀÖÀ¾´Ï´Ù. !!! ÇÑ°Ü·¹ ÀåÅÍ(www.zhangter.com)·Î ¿À½Ê½Ã¿ä. ¢À »çÀü¿¡ Çã¶ô¾øÀÌ ¸ÞÀÏÀ» º¸³»¼ Á˼ÛÇÕ´Ï´Ù. º» ¸ÞÀÏÀº Á¤º¸Åë½Å¸Á ÀÌ¿ëÃËÁø ¹× Á¤º¸º¸È£ µî¿¡ °üÇÑ ¹ý·ü Á¦ 50Á¶¿¡ ÀÇ°ÅÇÑ [±¤°í] ¸ÞÀÏÀÔ´Ï´Ù. freebsd-hackers´ÔÀÇ e-mail ÁÖ¼Ò´Â ÀÎÅͳݻ󿡼 ÃëµæÇÏ¿´À¸¸ç, ¸ÞÀÏÁÖ¼Ò¿Ü¿¡ ¾î¶°ÇÑ °³ÀÎ Á¤º¸µµ °¡Áö°í ÀÖÁö ¾Ê½À´Ï´Ù. ¢À We inform you, in accordance with the advice of Ministry of Information and Communication, that this e-mail is a advertisement and the address of which has been gathered from bulletin board on internet as not wish to receive this e-mail click "Deny" . [¼ö½Å°ÅºÎ( Deny )]
multi-link 802.11b through netgraph yields poor performance.
Julian, Archie, et al, I have experimented with a multi-link 802.11b connection between two laptops. Both are 4.5-RELEASE, one has two aironet LMC352 cards, and one has two Lucent gold cards. I have successfully used ng_one2many, etc., to establish a working multi-link between the two systems - however, I would appreciate any comments regarding the very poor performance I see when networked in this manner. The problem I see is that, when using `ping` on either machine, exactly every other packet is dropped. After running `ping` for many minutes, trying it from both machines, it is clear that _exactly_ every other packet is dropped. Further, echo response time is between 2.2 and 2.5 milliseconds, which seems very high. I have configured the multi-link using the examples found in the ng_one2many(4) man page - the only difference is that I have only two cards in each machine, so in addition to running fewer `ngctl` commands, I also had fewer links in my setconfig msg ([ 1 1 ] instead of [ 1 1 1 1 ]). `ngctl list` on both machines yields this (seemingly correct) information: There are 4 total nodes: Name: ngctl338Type: socketID: 0013Num hooks: 0 Name:Type: one2many ID: 0009Num hooks: 3 Name: an1 Type: ether ID: 0002Num hooks: 1 Name: an0 Type: ether ID: 0001Num hooks: 2 Finally, I should point out that one card in each machine is on channel 1, and one card in each machine is on channel 11 - thus there are two card pairs crossing each machine and each card pair shares not only a frequency/channel, but also a SSID. The purely wireless networking portion of this experiment seems to be correct. (I posted a few weeks ago to freebsd-mobile a correct mechanism to get wi cards talking to an cards in ad-hoc mode). Theoretically interference should not be an issue as I am using channels 1 and 11. The behavior does not change regardless of how close the two laptops are or what their relative vertical/horizontal orientation is ... moving around the external antennas attached to the LMC352s has no effect. Therefore, since the every other packet echo response and the high latency continues without missing a beat regardless of what I do to try to affect the interference (if any) I must conclude that I am witnessing either: a) a problem in the wireless drivers that causes them to be confused when two of the same card is configured in the system using different frequencies or SSIDs b) a problem or misconfiguration on my part in the netgraph configuration --- (a) seems unlikely as I feel that unspecific "issues" with the wireless drivers would cause effects that were less regular than "drop exactly every other packet". However (b) also seems unlikely - if I had misconfigured netgraph and ng_one2many, it seems unlikely that this would work at all. It's possible that my netgraph configuration is not even being used, and that an0 is simply talking to wi0 over a non-multi-link, and that everything else that is going on just happens to cause problems for that normal ad-hoc, one card to one card operation. However, my netgraph commands you will see below, and the output of my `ngctl list` commands suggest that netgraph is configured correctly. Here are the network and netgraph related commands I entered, in order: On machine A: ifconfig an0 10.10.10.10 netmask 255.255.255.0 ngctl mkpeer an0: one2many upper one ngctl connect an0: an0:upper lower many0 ngctl connect an1: an0:upper lower many1 ifconfig an1 up ngctl msg an1: setpromisc 1 ngctl msg an1: setautosrc 0 ngctl msg an0:upper setconfig "{ xmitAlg=1 failAlg=1 enabledLinks=[ 1 1 ] }" On machine B: ifconfig wi0 10.10.10.20 netmask 255.255.255.0 ngctl mkpeer wi0: one2many upper one ngctl connect wi0: wi0:upper lower many0 ngctl connect wi1: wi0:upper lower many1 ifconfig wi1 up ngctl msg wi1: setpromisc 1 ngctl msg wi1: setautosrc 0 ngctl msg wi0:upper setconfig "{ xmitAlg=1 failAlg=1 enabledLinks=[ 1 1 ] }" Any comments as to why the problems I am seeing (half of packets dropped and high latency) exist are appreciated. - John Kozubik - [EMAIL PROTECTED] - http://www.kozubik.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message