Re: Difference between RELENG_* and RELENG_*_BP

2002-05-11 Thread David Schultz

Thus spake Brandon D. Valentine <[EMAIL PROTECTED]>:
> I know we've got gnats, but gnats doesn't really provide any of the
> Request for Enhancement/voting features that Bugzilla does.  FreeBSD
> seems to have grown to a point where maybe some of Bugzilla's workflow
> benefits could be realized.  The ability for developers and users to
> vote for or against a specific feature certainly wouldn't hurt.

I don't know about that; the current system seems to work pretty well.
Best of all, things actually get done without there being religious
wars about the colors of various bikesheds.  When an issue comes up
that people *really* care about, it finds its way to the lists anyway.
If people had to vote about every little change, I imagine there'd be
chaos.  Voting isn't the right way to settle a disagreement anyway.

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



Re: nextboot loader diff

2002-05-11 Thread Terry Lambert

Gordon Tetlow wrote:

[ ... ]

You *did* ask for comments...


> > There should be a list, so that in a brown-out or whatever, you
> > don't end up toggling back to the previous version accidently.
> 
> This is not something that is meant for you to massage which root
> partition you are going to boot up off of.

I don't understand what it does, then.  The original Whistle code
was intended to attempt to boot 3 times from one partition, and
then 3 times from another.

If a boot was successful, then in the last rc file before the getty's
were started, it reset the list to 3 times the current root and 3
times the alternate root.

That way, on each success, the counter was reset, so in general, a
given root was sticky.

When the failure occurred, then the alternate root was the one whose
rc files ran, and it became the sticky one.

Worst case, you could power cycle a box three times quickly to force
a switch back to an older version.

The general failure case is not an indefinite hang, but a reset before
the rc file runs.  This is particularly true when you have a hardware
watchdog, where the first thing that happens is the watchdog is set.

Note that images are tested before they are shipped, so the worst
case failure is "out of memory" or some other installation failure
related problem, and not a kernel problem, anyway.

I've personally had to solve this same problem several times now.


> > You should only ever rewrite the contents of a single file, and
> > it shouldn't be an important file.
> 
> Yes, that's exactly what my patch does.

I don't understand the "YES"/"NO" thing, then.  There is one byte
difference in the file length, which I don't think can be properly
accounted, if you do the "YES"/"NO" thing.


> > The existance/non-existance of the single file should be enough
> > to trigger/suppress the nextboot behaviour.
> 
> I can't unlink files in the loader, so the presence of such a file
> wouldn't help.

The file is the nextboot.conf file.  And unlinking it is not something
which you want to do, actually.  I think we are misunderstanding each
other's intent here.


> > Don't assume that the nextboot file will be on the same disk and/or
> > partition as the boot and other config file code.
> 
> Well, I'm assuming it's on the root partition. It would be kinda silly for
> it to anywhere else.

Not really.  Consider that if I switch root partitions, then, by
definition, I switch nextboot files.

Basically, the InterJet was laid out:

boot code (including nextboot list)
/ #1<- version X of the system (read only)
/ #2<- version Y of the system (read only)
swap
/var<- log files and /tmp
/data   <- user data (config, user files, etc.)

The fstab's on #1 and #2 were opposite, so that you could mount and
overwrite the contents with a new release of the software.

An upgrade was:

mount opposite "root"
unpack new system image onto opposite root
set up opposite root fstab
sync
unmount
nextboot "opposite opposite opposite this this this"
reboot

Each revision had data management upgrade/downgrade scripts; these
were written to /data, so that opposite versions could downgrade.


> > Together, these things will allow the new code to solve the same
> > problem that the old code solved on the InterJet.
> 
> I've never heard nor seen the old code. I don't know what it did, and I
> don't particularly care. I did this because I thought the way Wes Peters
> did his implementation was rather hackish (not saying mine is any better
> =) and suboptimal if the machine doesn't make it to multi-user. Please
> refer to the commit logs from earlier this month if you don't know of the
> commit I'm referring to.

I do.  He committed some, but not all, of the code that Jon Mini
and James wrote (Jon says some of it was based on code I wrote).
The design I did at ClickArray was based on the Whistle design
from when I worked at Whistle with Julian and Archie.

The ClickArray code, if it was intended to solve the problem that
the code it was supposedly derived from was intended to solve is
for solving the remote upgrade problem, with no local removable
media that can be used to recover from a catastrophic failure
(the only recovery from such a failure is a fallback to a working
previous revision, per the InterJet).

The code you are talking about seems limited to replacing only the
kernel.  Frankly, that's recoverable via the serial console, if
you put the "-p" in the right file in /.

This isn't really sufficient for any embedded system that needs to
get at netstat, ps, or other data which involves examination of
kernel structures, which may change between kernel versions.  You
pretty much have to have two system images to solve that problem,
or you'll find youself incredibly screwed, when the web UI, the
CLI, SNMP, and the front panel LCD all start reporting random bogus
data.  8-(.

I

Re: Difference between RELENG_* and RELENG_*_BP

2002-05-11 Thread Terry Lambert

David Schultz wrote:
> Thus spake Brandon D. Valentine <[EMAIL PROTECTED]>:
> > I know we've got gnats, but gnats doesn't really provide any of the
> > Request for Enhancement/voting features that Bugzilla does.  FreeBSD
> > seems to have grown to a point where maybe some of Bugzilla's workflow
> > benefits could be realized.  The ability for developers and users to
> > vote for or against a specific feature certainly wouldn't hurt.
> 
> I don't know about that; the current system seems to work pretty well.
> Best of all, things actually get done without there being religious
> wars about the colors of various bikesheds.  When an issue comes up
> that people *really* care about, it finds its way to the lists anyway.
> If people had to vote about every little change, I imagine there'd be
> chaos.  Voting isn't the right way to settle a disagreement anyway.

Doesn't bugzilla still have that remote exploit problem that
was reported on Bugtraq?

Also, I think voting is generally done by "write the code".
You really can't demand volunteers work on what you want them
to work on.

If someone asks for comments, feel free to comment, and if
they start a public discussion, feel free to discuss, but I
think "voting on bug fixes" has the ring of imposing management
on people who you are not paying enough to put up with it.  It
worked for Mozilla because Netscape paid people to put up with
doing work they didn't want to do and getting input from people
who were unwilling to write the code themselves.  Pure volunteer
efforts are different.  To persuade, you can't just vote, you
actually have to be persuasive.  8-).

-- Terry

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



Re: Difference between RELENG_* and RELENG_*_BP

2002-05-11 Thread David Schultz

Thus spake Terry Lambert <[EMAIL PROTECTED]>:
...
> Doesn't bugzilla still have that remote exploit problem that
> was reported on Bugtraq?
> 
> Also, I think voting is generally done by "write the code".
> You really can't demand volunteers work on what you want them
> to work on.

I think you're on to something here.  Just imagine:

  A: ``I'll give you $200 to add $foo to the base system.''
  B: ``No, *I* bid $300 to get someone to work on $bar.''
  ...

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



ÉϺ£¹ú¼Ê»·±£¡¢Ë®Õ¹-¼´½«¿ªÄ»ÁË

2002-05-11 Thread zmzl

2002Öйú£¨ÉϺ££©¹ú¼Ê¸øÅÅˮˮ´¦ÀíÕ¹ÀÀ»á¼°2002Öйú£¨ÉϺ££©¹ú¼Ê»·
±£¼¼ÊõÉ豸չÀÀ»á"½«ÓÚ2002Äê5ÔÂ15ÈÕ-17ÈÕÔÚÉϺ£ÊÀóÉ̳ÇÂ¡ÖØ¾Ù°ì¡£
±¾½ìÕ¹»áÏÖÒÑÎüÒýÁËÀ´×ÔÃÀ¹ú¡¢º«¹ú¡¢ÈÕ±¾¡¢µÂ¹ú¡¢Òâ´óÀû¡¢·¨¹ú¡¢¼Ó
Äôó¼°Öйų́ÍåµØÇøµÈ¹ú¼ÒÓëµØÇø400¶à¼Ò³§É̲ÎÕ¹£¬Õ¹³öÃæ»ý³¬¹ý1ƽ
Ã×£¬Í¬Ê±Ö÷°ì»ú¹¹»¹½«ÑûÇëÏà¹ØÐÐҵȨÍþÈËÊ¿¼°ÖªÃûÆóÒµ¾Ù°ìרÌⱨ¸æ»áºÍ
¼¼Êõ½»Á÷»á¡£
»¶Ó­¸÷Ïà¹Øµ¥Î»Ç°À´²Î¹Û

²¿·ÖÕ¹ÉÌĿ¼

DongSuh Environment Technology Co, Ltd 
»Æº£µç»ú   
Hwang Hae Electric
º«¹ú»úе²úÒµÕñÐË»á
Korea Association Of Machinery Industry
º«¹úµÚÒ»»·±£¼¼ÊõÓÐÏÞ¹«Ë¾
CHEIL ENTECCO, LTD SHENYANG OFFICE
µÂ¹ú¸¥À¼µÂ¼¯ÍÅ
A FRIEDRFLENDERGMBH
ÈÕ±¾ÎéÒâÖêʽ»áÉç
SATSUKI CO, LTD SHANGHAI OFFICE
ÈÕ±¾Öêʽ»áÉç˜ÙÒ°
KASHINO & CO, LTD SHANGHAI REPRESENTATIVE OFFICE
ÃÀ¹úŵÓþ»¯¹¤ÑÇÌ«ÇøÓÐÏÞ¹«Ë¾
Noveon Chemicals Asia Pacific Ltd
º£Ë¹¶Ù»·±£É豸ÓÐÏÞ¹«Ë¾
Beijing Hi-Standard Environmental Equipment Co, Ltd
±±¾©É£µÂ»·±£²úÒµ¼¯ÍÅ
Beijing SOUND Environmental Industry Group Corporation
̨ž³…^­h±£ÔO‚乤˜Iͬ˜I¹«•þ
TAIWAN ENVIRONMENTAL MANUFACTURERS ASSOCIATION
´óÒã¼¼Ðg¹¤³Ì£¨¹É£©¹«Ë¾
DIAMOND TECHNICAL & TRADING CORP
ÉϺ£Á¼™CÀä…sÔO‚äÓÐÏÞ¹«Ë¾
SHANGHAILIANG CHI COOLING EQUIPMENT CO, LTD
ÓýŠ¿Æ¼¼£¨¹É£©¹«Ë¾
GASTECH CO, LTD
·â¹ÌÆó˜I£¨¹É£©¹«Ë¾
FENG GUH ENTERPRISE CO, LTD
†ÃÀÏÈßM¿Æ¼¼£¨¹É£©¹«Ë¾
YEAMEEI ADVANCED TECHNOLOGY CO, LTD 
ÏàͬÆó˜IÓÐÏÞ¹«Ë¾
SAME CO,LTD
ÓѺÍÄÍ»ð²ÄÁϹɷÝÓÐÏÞ¹«Ë¾
YUHO REFRACTORIES CO, LTD
ºÓҊ늙C¹¤˜I£¨¹É£©¹«Ë¾
HCP PUMP MANUFACTURER CO, LTD
¿µ½Ý­h±£¿Æ¼¼£¨¹É£©¹«Ë¾
KJ ENVIRONMENTAL TECHNDOGY CO, LTD
¹¢¿ì£¨¹É£©¹«Ë¾
TRUSTEWLL INDUSTRIAL LTD
¶«Ý¸Êг¤°²ÁâÕý»úµç­h±£ÔO‚ä¾­Óª²¿
RYOSEI NACGUBE UBDYSTRAK EBTERORUSE CO, LTD
Á¦“]Æó˜IÓÐÏÞ¹«Ë¾
BAG FILTER ENTERPRISE CO, LTD
ȫʢÐË×ÊÔ´¿Æ¼¼¹É·ÝÓÐÏÞ¹«Ë¾
EverGlory Resource Technology CO, LTD (ERT)
̨ÍåÆóÒµÓÀÐø·¢Õ¹Ð­»á£¨BCSD-Taiwan£©
¼ÑÁú¿Æ¼¼¹¤³Ì¹É·ÝÓÐÏÞ¹«Ë¾
ÈÙ¼¼¹«Ë¾
²ÆÍÅ·¨È˹¤ÑÐÔº»·°²ÖÐÐÄ
²ÆÍÅ·¨ÈËÖйú·ÄÖ¯¹¤ÒµÑо¿ÖÐÐÄ
China Textile Institute
²ÆÍÅ·¨ÈËÉúÎï¼¼Êõ¿ª·¢ÖÐÐÄ
Development Center for Biotechnology
²ÆÍÅ·¨ÈĘ̈ÍåÂÌÉ«Éú²úÁ¦»ù½ð»á
Taiwan Green Productivity Foundation
ÉϺ£Ôó°²ÊµÒµÓÐÏÞ¹«Ë¾
Shanghai Zean Industrial Co, Ltd
µÂ¹ú±¦µÃ£¨Öйú/Ïã¸Û£©ÓÐÏÞ¹«Ë¾
Burkert Contromatic (China/HK) Ltd
ÉϺ£´¨Ô´»úе¹¤³ÌÓÐÏÞ¹«Ë¾
Shanghai Chuan Yuan Mechanical Engineering Co,Ltd
ÑÇ´óËÜÁÏÖÆÆ·ÓÐÏÞ¹«Ë¾
CHINAUST PLASTICS CORPLTD
»ìÔª¹ú¼Ê¿ª·¢¹ËÎʹɷÝÓÐÏÞ¹«Ë¾
HUN-YUAN INTERNATIONAL DEVELOP CONSULTING CO, LTD
¸£½¨Íò´ïµç»úÓÐÏÞ¹«Ë¾
Wonder Electric Co, Ltd
ÉϺ£ÃÀÖÞÐÇʵҵÓÐÏÞ¹«Ë¾
Shanghai Amstar Enterprises Co, Ltd   
ÉϺ£âýÐÇ»·±£¿Æ¼¼·¢Õ¹ÓÐÏÞ¹«Ë¾
Shanghai KATHY Environmental Protection Technology Development Co, Ltd
ÉϺ£»ª¹Ä¹Ä·ç»úÓÐÏÞ¹«Ë¾
Shanghai Huagu Blower Manufactory 
Æô¶«ÊÐÕ×Ãñ»·¾³¹¤³ÌÉ豸ÓÐÏÞ¹«Ë¾
Zhaomin Environmental Engineering Equipment Co
½­ËÕÊ¡Öñóå»úе³§
Jiangsu Province Zhuze Machinery Factory
±±¾©°²ÆÕÌ©¿ËÒÇÆ÷ÓÐÏÞ¹«Ë¾
Beijing Ample Technology Instrument Co, Ltd
µÂ¿ÆÌؼ¯ÍÅ
Daifu MO Group Ltd
ÉϺ£·¨ÑÅ»·±£²úÆ·ÓÐÏÞ¹«Ë¾
SHANGHAI FAYA ENVIRONMENTAL PRODUCTS CO, LTD
½ÜÊÀ»·±£¿Æ¼¼¹¤³ÌÓÐÏÞ¹«Ë¾
JC EnvorTech Engineering Co, Ltd
ÄÚÃɹű±·½Öع¤Òµ¼¯ÍÅÓÐÏÞ¹«Ë¾
INNER MONGOLIA NORTH HEAVY INDUSTRIES GROUP CO, LTD
ÄϾ©Ê¥Ô´Ë®´¦Àí¼¼ÊõÓÐÏÞ¹«Ë¾
NANJING SHENG YUAN WATER TREATMENT TECHNOLOGY CO, LTD
ËÕÖݹ¤ÒµÔ°ÇøË¹ÌØÀͲª¹Ü½ÓÍ·ÓÐÏÞ¹«Ë¾
Suzhou Industrial Park Straub Pipe-Joint Co, Ltd
ÖеºÏ×ÊÉϺ£¿­Ê¿±È±ÃÓÐÏÞ¹«Ë¾
KSB SHANGHAI PUMP CO, LTD
ÈÕ¶«»¯¹¤»úе£¨ÉϺ££©ÓÐÏÞ¹«Ë¾
NITTO P & M ENGINEERING (SHANGHAI)CO, LTD
ºÓ±±ºêÒµ»úе¹É·ÝÓÐÏÞ¹«Ë¾
²´Í·ºêÑïÖýÔìÓÐÏÞÔðÈι«Ë¾
ÉîÛÚÊÐÖÐÈóË®¹¤Òµ¼¼Êõ·¢Õ¹ÓÐÏÞ¹«Ë¾
Shenzhen ZhongRun Water Industry Technology Development Co ,Ltd
¶àԪˮ»·±£¼¼Êõ²úÒµ£¨Öйú£©ÓÐÏÞ¹«Ë¾
DUO YUAN CLEAN WATER TECHNOLOGY INDUSTRIES £¨CHINA£© CO£¬LTD
ÉÏ º£ ¼ª ¾® »· ±£ Éè ±¸ ÓÐ ÏÞ ¹« ˾HANGHAI YOSI I ENVIRONMENTAL PROTECTION ENQUIPMENT 
CO,LTD
ÉϺ£Çȶ¦·§ÃÅÓÐÏÞ¹«Ë¾
Shanghai Chaiodin Valve Trading Co, Ltd
ÉϺ£»³Àû»·±£É豸ÓÐÏÞ¹«Ë¾
SHANGHAI WIDELEE ENVIRONTEC CO, LTD
ÉϺ£Ò°Âí»·±£¹¤³ÌÓÐÏÞ¹«Ë¾
Shanghai Ye Ma EPE Co, Ltd
ÉϺ£°®»ÝÆÖÉúÒûÉ豸ÓÐÏÞ¹«Ë¾
Everpure Shanghai Water Treatment Co, Ltd
º¼ÖÝÄþ´ï»úеÓÐÏÞ¹«Ë¾
Hangzhou Ningda Machinery Co, Ltd
½­ÃÅÊÐÈðÈÙ±ÃÒµÓÐÏÞ¹«Ë¾
Jiangmen Ruirong Pump Industry , Ltd Guangdong
¸»ÑôÊÐÊ¢´ó»úµçÖÆÔìÓÐÏÞ¹«Ë¾
Fuyang Shengda Mechanical And Electrical Manufacturing Co, Ltd
ɽ¶«´óѧɽ¶«»ªÌØÊÂÒµ×ܹ«Ë¾
SHANDONG HEART GENERAL COMPANY
ÉϺ£¿µ×¿×Ô¶¯»¯ÏµÍ³¹¤³Ì·þÎñÓÐÏÞ¹«Ë¾
Shang ACS Co, Ltd
ÈðºÃÓÐÏÞ¹«Ë¾ÉϺ£´ú±í´¦
REHAU LIMITED, SHANGHAI REPOFFICE
ÉϺ£ÊÐÀͶ¯¸Ö¹Ü³§
Shanghai Laodong Steel Pipe Works
£¨ÈÕ±¾¶À×Ê£©³É¶¼´óºÍÈÈÄÜ»úеÓÐÏÞ¹«Ë¾
CHENGDU YAMATO HEAT ENERGY MACHINERY CO, LTD
ÄϾ©±Ì¶Ü»·±£×°±¸ÓÐÏÞÔðÈι«Ë¾
Nanjing Bidun Environmental Protection Equipment Co, Ltd
ÉϺ£ÓÓÀû¹ÜÒµÓÐÏÞ¹«Ë¾
SHANGHAI YOULI PIPES CO, LTD
ºþÖݰîµÂË®´¦ÀíÉ豸ÓÐÏÞ¹«Ë¾
Huzhou Bangde Water Treatment Equipment Co, Ltd
¸£ÁÖ˹£¨ÐìÖÝ£©Éú»¯¼¼ÊõÓÐÏÞ¹«Ë¾
Frings Xuzhou Bio-and Chemical Technology Co, Ltd
¹ã¶«Ê¡¶«Ý¸Êкñ½Ö¸£Ôª»úе³§
Fu Yuan Machinery Plant Hou-jie Town, Dong Guan Guang Dong-China 
±±¾©Àï¿ý¸£ÌØÐ²ÄÁϼ¼ÊõÓÐÏÞ¹«Ë¾
Beijing Liquid Filter New Material Technique Co, Ltd
ÎߺþÊлªÌ©ÊµÒµÓÐÏÞ¹«Ë¾
Wuhu Huatai Industry Co, Ltd
ÕżҸÛÊкêÐË»·±£É豸ÓÐÏÞ¹«Ë¾
Hongxing Environmental Protection Equipment Co, Ltd

ÉϺ£¹ú¼Ê»·±£¡¢Ë®Õ¹-¼´½«¿ªÄ»ÁË

2002-05-11 Thread zmzl

2002Öйú£¨ÉϺ££©¹ú¼Ê¸øÅÅˮˮ´¦ÀíÕ¹ÀÀ»á¼°2002Öйú£¨ÉϺ££©¹ú¼Ê»·
±£¼¼ÊõÉ豸չÀÀ»á"½«ÓÚ2002Äê5ÔÂ15ÈÕ-17ÈÕÔÚÉϺ£ÊÀóÉ̳ÇÂ¡ÖØ¾Ù°ì¡£
±¾½ìÕ¹»áÏÖÒÑÎüÒýÁËÀ´×ÔÃÀ¹ú¡¢º«¹ú¡¢ÈÕ±¾¡¢µÂ¹ú¡¢Òâ´óÀû¡¢·¨¹ú¡¢¼Ó
Äôó¼°Öйų́ÍåµØÇøµÈ¹ú¼ÒÓëµØÇø400¶à¼Ò³§É̲ÎÕ¹£¬Õ¹³öÃæ»ý³¬¹ý1ƽ
Ã×£¬Í¬Ê±Ö÷°ì»ú¹¹»¹½«ÑûÇëÏà¹ØÐÐҵȨÍþÈËÊ¿¼°ÖªÃûÆóÒµ¾Ù°ìרÌⱨ¸æ»áºÍ
¼¼Êõ½»Á÷»á¡£
»¶Ó­¸÷Ïà¹Øµ¥Î»Ç°À´²Î¹Û

²¿·ÖÕ¹ÉÌĿ¼

DongSuh Environment Technology Co, Ltd 
»Æº£µç»ú   
Hwang Hae Electric
º«¹ú»úе²úÒµÕñÐË»á
Korea Association Of Machinery Industry
º«¹úµÚÒ»»·±£¼¼ÊõÓÐÏÞ¹«Ë¾
CHEIL ENTECCO, LTD SHENYANG OFFICE
µÂ¹ú¸¥À¼µÂ¼¯ÍÅ
A FRIEDRFLENDERGMBH
ÈÕ±¾ÎéÒâÖêʽ»áÉç
SATSUKI CO, LTD SHANGHAI OFFICE
ÈÕ±¾Öêʽ»áÉç˜ÙÒ°
KASHINO & CO, LTD SHANGHAI REPRESENTATIVE OFFICE
ÃÀ¹úŵÓþ»¯¹¤ÑÇÌ«ÇøÓÐÏÞ¹«Ë¾
Noveon Chemicals Asia Pacific Ltd
º£Ë¹¶Ù»·±£É豸ÓÐÏÞ¹«Ë¾
Beijing Hi-Standard Environmental Equipment Co, Ltd
±±¾©É£µÂ»·±£²úÒµ¼¯ÍÅ
Beijing SOUND Environmental Industry Group Corporation
̨ž³…^­h±£ÔO‚乤˜Iͬ˜I¹«•þ
TAIWAN ENVIRONMENTAL MANUFACTURERS ASSOCIATION
´óÒã¼¼Ðg¹¤³Ì£¨¹É£©¹«Ë¾
DIAMOND TECHNICAL & TRADING CORP
ÉϺ£Á¼™CÀä…sÔO‚äÓÐÏÞ¹«Ë¾
SHANGHAILIANG CHI COOLING EQUIPMENT CO, LTD
ÓýŠ¿Æ¼¼£¨¹É£©¹«Ë¾
GASTECH CO, LTD
·â¹ÌÆó˜I£¨¹É£©¹«Ë¾
FENG GUH ENTERPRISE CO, LTD
†ÃÀÏÈßM¿Æ¼¼£¨¹É£©¹«Ë¾
YEAMEEI ADVANCED TECHNOLOGY CO, LTD 
ÏàͬÆó˜IÓÐÏÞ¹«Ë¾
SAME CO,LTD
ÓѺÍÄÍ»ð²ÄÁϹɷÝÓÐÏÞ¹«Ë¾
YUHO REFRACTORIES CO, LTD
ºÓҊ늙C¹¤˜I£¨¹É£©¹«Ë¾
HCP PUMP MANUFACTURER CO, LTD
¿µ½Ý­h±£¿Æ¼¼£¨¹É£©¹«Ë¾
KJ ENVIRONMENTAL TECHNDOGY CO, LTD
¹¢¿ì£¨¹É£©¹«Ë¾
TRUSTEWLL INDUSTRIAL LTD
¶«Ý¸Êг¤°²ÁâÕý»úµç­h±£ÔO‚ä¾­Óª²¿
RYOSEI NACGUBE UBDYSTRAK EBTERORUSE CO, LTD
Á¦“]Æó˜IÓÐÏÞ¹«Ë¾
BAG FILTER ENTERPRISE CO, LTD
ȫʢÐË×ÊÔ´¿Æ¼¼¹É·ÝÓÐÏÞ¹«Ë¾
EverGlory Resource Technology CO, LTD (ERT)
̨ÍåÆóÒµÓÀÐø·¢Õ¹Ð­»á£¨BCSD-Taiwan£©
¼ÑÁú¿Æ¼¼¹¤³Ì¹É·ÝÓÐÏÞ¹«Ë¾
ÈÙ¼¼¹«Ë¾
²ÆÍÅ·¨È˹¤ÑÐÔº»·°²ÖÐÐÄ
²ÆÍÅ·¨ÈËÖйú·ÄÖ¯¹¤ÒµÑо¿ÖÐÐÄ
China Textile Institute
²ÆÍÅ·¨ÈËÉúÎï¼¼Êõ¿ª·¢ÖÐÐÄ
Development Center for Biotechnology
²ÆÍÅ·¨ÈĘ̈ÍåÂÌÉ«Éú²úÁ¦»ù½ð»á
Taiwan Green Productivity Foundation
ÉϺ£Ôó°²ÊµÒµÓÐÏÞ¹«Ë¾
Shanghai Zean Industrial Co, Ltd
µÂ¹ú±¦µÃ£¨Öйú/Ïã¸Û£©ÓÐÏÞ¹«Ë¾
Burkert Contromatic (China/HK) Ltd
ÉϺ£´¨Ô´»úе¹¤³ÌÓÐÏÞ¹«Ë¾
Shanghai Chuan Yuan Mechanical Engineering Co,Ltd
ÑÇ´óËÜÁÏÖÆÆ·ÓÐÏÞ¹«Ë¾
CHINAUST PLASTICS CORPLTD
»ìÔª¹ú¼Ê¿ª·¢¹ËÎʹɷÝÓÐÏÞ¹«Ë¾
HUN-YUAN INTERNATIONAL DEVELOP CONSULTING CO, LTD
¸£½¨Íò´ïµç»úÓÐÏÞ¹«Ë¾
Wonder Electric Co, Ltd
ÉϺ£ÃÀÖÞÐÇʵҵÓÐÏÞ¹«Ë¾
Shanghai Amstar Enterprises Co, Ltd   
ÉϺ£âýÐÇ»·±£¿Æ¼¼·¢Õ¹ÓÐÏÞ¹«Ë¾
Shanghai KATHY Environmental Protection Technology Development Co, Ltd
ÉϺ£»ª¹Ä¹Ä·ç»úÓÐÏÞ¹«Ë¾
Shanghai Huagu Blower Manufactory 
Æô¶«ÊÐÕ×Ãñ»·¾³¹¤³ÌÉ豸ÓÐÏÞ¹«Ë¾
Zhaomin Environmental Engineering Equipment Co
½­ËÕÊ¡Öñóå»úе³§
Jiangsu Province Zhuze Machinery Factory
±±¾©°²ÆÕÌ©¿ËÒÇÆ÷ÓÐÏÞ¹«Ë¾
Beijing Ample Technology Instrument Co, Ltd
µÂ¿ÆÌؼ¯ÍÅ
Daifu MO Group Ltd
ÉϺ£·¨ÑÅ»·±£²úÆ·ÓÐÏÞ¹«Ë¾
SHANGHAI FAYA ENVIRONMENTAL PRODUCTS CO, LTD
½ÜÊÀ»·±£¿Æ¼¼¹¤³ÌÓÐÏÞ¹«Ë¾
JC EnvorTech Engineering Co, Ltd
ÄÚÃɹű±·½Öع¤Òµ¼¯ÍÅÓÐÏÞ¹«Ë¾
INNER MONGOLIA NORTH HEAVY INDUSTRIES GROUP CO, LTD
ÄϾ©Ê¥Ô´Ë®´¦Àí¼¼ÊõÓÐÏÞ¹«Ë¾
NANJING SHENG YUAN WATER TREATMENT TECHNOLOGY CO, LTD
ËÕÖݹ¤ÒµÔ°ÇøË¹ÌØÀͲª¹Ü½ÓÍ·ÓÐÏÞ¹«Ë¾
Suzhou Industrial Park Straub Pipe-Joint Co, Ltd
ÖеºÏ×ÊÉϺ£¿­Ê¿±È±ÃÓÐÏÞ¹«Ë¾
KSB SHANGHAI PUMP CO, LTD
ÈÕ¶«»¯¹¤»úе£¨ÉϺ££©ÓÐÏÞ¹«Ë¾
NITTO P & M ENGINEERING (SHANGHAI)CO, LTD
ºÓ±±ºêÒµ»úе¹É·ÝÓÐÏÞ¹«Ë¾
²´Í·ºêÑïÖýÔìÓÐÏÞÔðÈι«Ë¾
ÉîÛÚÊÐÖÐÈóË®¹¤Òµ¼¼Êõ·¢Õ¹ÓÐÏÞ¹«Ë¾
Shenzhen ZhongRun Water Industry Technology Development Co ,Ltd
¶àԪˮ»·±£¼¼Êõ²úÒµ£¨Öйú£©ÓÐÏÞ¹«Ë¾
DUO YUAN CLEAN WATER TECHNOLOGY INDUSTRIES £¨CHINA£© CO£¬LTD
ÉÏ º£ ¼ª ¾® »· ±£ Éè ±¸ ÓÐ ÏÞ ¹« ˾HANGHAI YOSI I ENVIRONMENTAL PROTECTION ENQUIPMENT 
CO,LTD
ÉϺ£Çȶ¦·§ÃÅÓÐÏÞ¹«Ë¾
Shanghai Chaiodin Valve Trading Co, Ltd
ÉϺ£»³Àû»·±£É豸ÓÐÏÞ¹«Ë¾
SHANGHAI WIDELEE ENVIRONTEC CO, LTD
ÉϺ£Ò°Âí»·±£¹¤³ÌÓÐÏÞ¹«Ë¾
Shanghai Ye Ma EPE Co, Ltd
ÉϺ£°®»ÝÆÖÉúÒûÉ豸ÓÐÏÞ¹«Ë¾
Everpure Shanghai Water Treatment Co, Ltd
º¼ÖÝÄþ´ï»úеÓÐÏÞ¹«Ë¾
Hangzhou Ningda Machinery Co, Ltd
½­ÃÅÊÐÈðÈÙ±ÃÒµÓÐÏÞ¹«Ë¾
Jiangmen Ruirong Pump Industry , Ltd Guangdong
¸»ÑôÊÐÊ¢´ó»úµçÖÆÔìÓÐÏÞ¹«Ë¾
Fuyang Shengda Mechanical And Electrical Manufacturing Co, Ltd
ɽ¶«´óѧɽ¶«»ªÌØÊÂÒµ×ܹ«Ë¾
SHANDONG HEART GENERAL COMPANY
ÉϺ£¿µ×¿×Ô¶¯»¯ÏµÍ³¹¤³Ì·þÎñÓÐÏÞ¹«Ë¾
Shang ACS Co, Ltd
ÈðºÃÓÐÏÞ¹«Ë¾ÉϺ£´ú±í´¦
REHAU LIMITED, SHANGHAI REPOFFICE
ÉϺ£ÊÐÀͶ¯¸Ö¹Ü³§
Shanghai Laodong Steel Pipe Works
£¨ÈÕ±¾¶À×Ê£©³É¶¼´óºÍÈÈÄÜ»úеÓÐÏÞ¹«Ë¾
CHENGDU YAMATO HEAT ENERGY MACHINERY CO, LTD
ÄϾ©±Ì¶Ü»·±£×°±¸ÓÐÏÞÔðÈι«Ë¾
Nanjing Bidun Environmental Protection Equipment Co, Ltd
ÉϺ£ÓÓÀû¹ÜÒµÓÐÏÞ¹«Ë¾
SHANGHAI YOULI PIPES CO, LTD
ºþÖݰîµÂË®´¦ÀíÉ豸ÓÐÏÞ¹«Ë¾
Huzhou Bangde Water Treatment Equipment Co, Ltd
¸£ÁÖ˹£¨ÐìÖÝ£©Éú»¯¼¼ÊõÓÐÏÞ¹«Ë¾
Frings Xuzhou Bio-and Chemical Technology Co, Ltd
¹ã¶«Ê¡¶«Ý¸Êкñ½Ö¸£Ôª»úе³§
Fu Yuan Machinery Plant Hou-jie Town, Dong Guan Guang Dong-China 
±±¾©Àï¿ý¸£ÌØÐ²ÄÁϼ¼ÊõÓÐÏÞ¹«Ë¾
Beijing Liquid Filter New Material Technique Co, Ltd
ÎߺþÊлªÌ©ÊµÒµÓÐÏÞ¹«Ë¾
Wuhu Huatai Industry Co, Ltd
ÕżҸÛÊкêÐË»·±£É豸ÓÐÏÞ¹«Ë¾
Hongxing Environmental Protection Equipment Co, Ltd

ÉϺ£¹ú¼Ê»·±£¡¢Ë®Õ¹-¼´½«¿ªÄ»ÁË

2002-05-11 Thread zmzl

2002Öйú£¨ÉϺ££©¹ú¼Ê¸øÅÅˮˮ´¦ÀíÕ¹ÀÀ»á¼°2002Öйú£¨ÉϺ££©¹ú¼Ê»·
±£¼¼ÊõÉ豸չÀÀ»á"½«ÓÚ2002Äê5ÔÂ15ÈÕ-17ÈÕÔÚÉϺ£ÊÀóÉ̳ÇÂ¡ÖØ¾Ù°ì¡£
±¾½ìÕ¹»áÏÖÒÑÎüÒýÁËÀ´×ÔÃÀ¹ú¡¢º«¹ú¡¢ÈÕ±¾¡¢µÂ¹ú¡¢Òâ´óÀû¡¢·¨¹ú¡¢¼Ó
Äôó¼°Öйų́ÍåµØÇøµÈ¹ú¼ÒÓëµØÇø400¶à¼Ò³§É̲ÎÕ¹£¬Õ¹³öÃæ»ý³¬¹ý1ƽ
Ã×£¬Í¬Ê±Ö÷°ì»ú¹¹»¹½«ÑûÇëÏà¹ØÐÐҵȨÍþÈËÊ¿¼°ÖªÃûÆóÒµ¾Ù°ìרÌⱨ¸æ»áºÍ
¼¼Êõ½»Á÷»á¡£
»¶Ó­¸÷Ïà¹Øµ¥Î»Ç°À´²Î¹Û

²¿·ÖÕ¹ÉÌĿ¼

DongSuh Environment Technology Co, Ltd 
»Æº£µç»ú   
Hwang Hae Electric
º«¹ú»úе²úÒµÕñÐË»á
Korea Association Of Machinery Industry
º«¹úµÚÒ»»·±£¼¼ÊõÓÐÏÞ¹«Ë¾
CHEIL ENTECCO, LTD SHENYANG OFFICE
µÂ¹ú¸¥À¼µÂ¼¯ÍÅ
A FRIEDRFLENDERGMBH
ÈÕ±¾ÎéÒâÖêʽ»áÉç
SATSUKI CO, LTD SHANGHAI OFFICE
ÈÕ±¾Öêʽ»áÉç˜ÙÒ°
KASHINO & CO, LTD SHANGHAI REPRESENTATIVE OFFICE
ÃÀ¹úŵÓþ»¯¹¤ÑÇÌ«ÇøÓÐÏÞ¹«Ë¾
Noveon Chemicals Asia Pacific Ltd
º£Ë¹¶Ù»·±£É豸ÓÐÏÞ¹«Ë¾
Beijing Hi-Standard Environmental Equipment Co, Ltd
±±¾©É£µÂ»·±£²úÒµ¼¯ÍÅ
Beijing SOUND Environmental Industry Group Corporation
̨ž³…^­h±£ÔO‚乤˜Iͬ˜I¹«•þ
TAIWAN ENVIRONMENTAL MANUFACTURERS ASSOCIATION
´óÒã¼¼Ðg¹¤³Ì£¨¹É£©¹«Ë¾
DIAMOND TECHNICAL & TRADING CORP
ÉϺ£Á¼™CÀä…sÔO‚äÓÐÏÞ¹«Ë¾
SHANGHAILIANG CHI COOLING EQUIPMENT CO, LTD
ÓýŠ¿Æ¼¼£¨¹É£©¹«Ë¾
GASTECH CO, LTD
·â¹ÌÆó˜I£¨¹É£©¹«Ë¾
FENG GUH ENTERPRISE CO, LTD
†ÃÀÏÈßM¿Æ¼¼£¨¹É£©¹«Ë¾
YEAMEEI ADVANCED TECHNOLOGY CO, LTD 
ÏàͬÆó˜IÓÐÏÞ¹«Ë¾
SAME CO,LTD
ÓѺÍÄÍ»ð²ÄÁϹɷÝÓÐÏÞ¹«Ë¾
YUHO REFRACTORIES CO, LTD
ºÓҊ늙C¹¤˜I£¨¹É£©¹«Ë¾
HCP PUMP MANUFACTURER CO, LTD
¿µ½Ý­h±£¿Æ¼¼£¨¹É£©¹«Ë¾
KJ ENVIRONMENTAL TECHNDOGY CO, LTD
¹¢¿ì£¨¹É£©¹«Ë¾
TRUSTEWLL INDUSTRIAL LTD
¶«Ý¸Êг¤°²ÁâÕý»úµç­h±£ÔO‚ä¾­Óª²¿
RYOSEI NACGUBE UBDYSTRAK EBTERORUSE CO, LTD
Á¦“]Æó˜IÓÐÏÞ¹«Ë¾
BAG FILTER ENTERPRISE CO, LTD
ȫʢÐË×ÊÔ´¿Æ¼¼¹É·ÝÓÐÏÞ¹«Ë¾
EverGlory Resource Technology CO, LTD (ERT)
̨ÍåÆóÒµÓÀÐø·¢Õ¹Ð­»á£¨BCSD-Taiwan£©
¼ÑÁú¿Æ¼¼¹¤³Ì¹É·ÝÓÐÏÞ¹«Ë¾
ÈÙ¼¼¹«Ë¾
²ÆÍÅ·¨È˹¤ÑÐÔº»·°²ÖÐÐÄ
²ÆÍÅ·¨ÈËÖйú·ÄÖ¯¹¤ÒµÑо¿ÖÐÐÄ
China Textile Institute
²ÆÍÅ·¨ÈËÉúÎï¼¼Êõ¿ª·¢ÖÐÐÄ
Development Center for Biotechnology
²ÆÍÅ·¨ÈĘ̈ÍåÂÌÉ«Éú²úÁ¦»ù½ð»á
Taiwan Green Productivity Foundation
ÉϺ£Ôó°²ÊµÒµÓÐÏÞ¹«Ë¾
Shanghai Zean Industrial Co, Ltd
µÂ¹ú±¦µÃ£¨Öйú/Ïã¸Û£©ÓÐÏÞ¹«Ë¾
Burkert Contromatic (China/HK) Ltd
ÉϺ£´¨Ô´»úе¹¤³ÌÓÐÏÞ¹«Ë¾
Shanghai Chuan Yuan Mechanical Engineering Co,Ltd
ÑÇ´óËÜÁÏÖÆÆ·ÓÐÏÞ¹«Ë¾
CHINAUST PLASTICS CORPLTD
»ìÔª¹ú¼Ê¿ª·¢¹ËÎʹɷÝÓÐÏÞ¹«Ë¾
HUN-YUAN INTERNATIONAL DEVELOP CONSULTING CO, LTD
¸£½¨Íò´ïµç»úÓÐÏÞ¹«Ë¾
Wonder Electric Co, Ltd
ÉϺ£ÃÀÖÞÐÇʵҵÓÐÏÞ¹«Ë¾
Shanghai Amstar Enterprises Co, Ltd   
ÉϺ£âýÐÇ»·±£¿Æ¼¼·¢Õ¹ÓÐÏÞ¹«Ë¾
Shanghai KATHY Environmental Protection Technology Development Co, Ltd
ÉϺ£»ª¹Ä¹Ä·ç»úÓÐÏÞ¹«Ë¾
Shanghai Huagu Blower Manufactory 
Æô¶«ÊÐÕ×Ãñ»·¾³¹¤³ÌÉ豸ÓÐÏÞ¹«Ë¾
Zhaomin Environmental Engineering Equipment Co
½­ËÕÊ¡Öñóå»úе³§
Jiangsu Province Zhuze Machinery Factory
±±¾©°²ÆÕÌ©¿ËÒÇÆ÷ÓÐÏÞ¹«Ë¾
Beijing Ample Technology Instrument Co, Ltd
µÂ¿ÆÌؼ¯ÍÅ
Daifu MO Group Ltd
ÉϺ£·¨ÑÅ»·±£²úÆ·ÓÐÏÞ¹«Ë¾
SHANGHAI FAYA ENVIRONMENTAL PRODUCTS CO, LTD
½ÜÊÀ»·±£¿Æ¼¼¹¤³ÌÓÐÏÞ¹«Ë¾
JC EnvorTech Engineering Co, Ltd
ÄÚÃɹű±·½Öع¤Òµ¼¯ÍÅÓÐÏÞ¹«Ë¾
INNER MONGOLIA NORTH HEAVY INDUSTRIES GROUP CO, LTD
ÄϾ©Ê¥Ô´Ë®´¦Àí¼¼ÊõÓÐÏÞ¹«Ë¾
NANJING SHENG YUAN WATER TREATMENT TECHNOLOGY CO, LTD
ËÕÖݹ¤ÒµÔ°ÇøË¹ÌØÀͲª¹Ü½ÓÍ·ÓÐÏÞ¹«Ë¾
Suzhou Industrial Park Straub Pipe-Joint Co, Ltd
ÖеºÏ×ÊÉϺ£¿­Ê¿±È±ÃÓÐÏÞ¹«Ë¾
KSB SHANGHAI PUMP CO, LTD
ÈÕ¶«»¯¹¤»úе£¨ÉϺ££©ÓÐÏÞ¹«Ë¾
NITTO P & M ENGINEERING (SHANGHAI)CO, LTD
ºÓ±±ºêÒµ»úе¹É·ÝÓÐÏÞ¹«Ë¾
²´Í·ºêÑïÖýÔìÓÐÏÞÔðÈι«Ë¾
ÉîÛÚÊÐÖÐÈóË®¹¤Òµ¼¼Êõ·¢Õ¹ÓÐÏÞ¹«Ë¾
Shenzhen ZhongRun Water Industry Technology Development Co ,Ltd
¶àԪˮ»·±£¼¼Êõ²úÒµ£¨Öйú£©ÓÐÏÞ¹«Ë¾
DUO YUAN CLEAN WATER TECHNOLOGY INDUSTRIES £¨CHINA£© CO£¬LTD
ÉÏ º£ ¼ª ¾® »· ±£ Éè ±¸ ÓÐ ÏÞ ¹« ˾HANGHAI YOSI I ENVIRONMENTAL PROTECTION ENQUIPMENT 
CO,LTD
ÉϺ£Çȶ¦·§ÃÅÓÐÏÞ¹«Ë¾
Shanghai Chaiodin Valve Trading Co, Ltd
ÉϺ£»³Àû»·±£É豸ÓÐÏÞ¹«Ë¾
SHANGHAI WIDELEE ENVIRONTEC CO, LTD
ÉϺ£Ò°Âí»·±£¹¤³ÌÓÐÏÞ¹«Ë¾
Shanghai Ye Ma EPE Co, Ltd
ÉϺ£°®»ÝÆÖÉúÒûÉ豸ÓÐÏÞ¹«Ë¾
Everpure Shanghai Water Treatment Co, Ltd
º¼ÖÝÄþ´ï»úеÓÐÏÞ¹«Ë¾
Hangzhou Ningda Machinery Co, Ltd
½­ÃÅÊÐÈðÈÙ±ÃÒµÓÐÏÞ¹«Ë¾
Jiangmen Ruirong Pump Industry , Ltd Guangdong
¸»ÑôÊÐÊ¢´ó»úµçÖÆÔìÓÐÏÞ¹«Ë¾
Fuyang Shengda Mechanical And Electrical Manufacturing Co, Ltd
ɽ¶«´óѧɽ¶«»ªÌØÊÂÒµ×ܹ«Ë¾
SHANDONG HEART GENERAL COMPANY
ÉϺ£¿µ×¿×Ô¶¯»¯ÏµÍ³¹¤³Ì·þÎñÓÐÏÞ¹«Ë¾
Shang ACS Co, Ltd
ÈðºÃÓÐÏÞ¹«Ë¾ÉϺ£´ú±í´¦
REHAU LIMITED, SHANGHAI REPOFFICE
ÉϺ£ÊÐÀͶ¯¸Ö¹Ü³§
Shanghai Laodong Steel Pipe Works
£¨ÈÕ±¾¶À×Ê£©³É¶¼´óºÍÈÈÄÜ»úеÓÐÏÞ¹«Ë¾
CHENGDU YAMATO HEAT ENERGY MACHINERY CO, LTD
ÄϾ©±Ì¶Ü»·±£×°±¸ÓÐÏÞÔðÈι«Ë¾
Nanjing Bidun Environmental Protection Equipment Co, Ltd
ÉϺ£ÓÓÀû¹ÜÒµÓÐÏÞ¹«Ë¾
SHANGHAI YOULI PIPES CO, LTD
ºþÖݰîµÂË®´¦ÀíÉ豸ÓÐÏÞ¹«Ë¾
Huzhou Bangde Water Treatment Equipment Co, Ltd
¸£ÁÖ˹£¨ÐìÖÝ£©Éú»¯¼¼ÊõÓÐÏÞ¹«Ë¾
Frings Xuzhou Bio-and Chemical Technology Co, Ltd
¹ã¶«Ê¡¶«Ý¸Êкñ½Ö¸£Ôª»úе³§
Fu Yuan Machinery Plant Hou-jie Town, Dong Guan Guang Dong-China 
±±¾©Àï¿ý¸£ÌØÐ²ÄÁϼ¼ÊõÓÐÏÞ¹«Ë¾
Beijing Liquid Filter New Material Technique Co, Ltd
ÎߺþÊлªÌ©ÊµÒµÓÐÏÞ¹«Ë¾
Wuhu Huatai Industry Co, Ltd
ÕżҸÛÊкêÐË»·±£É豸ÓÐÏÞ¹«Ë¾
Hongxing Environmental Protection Equipment Co, Ltd

[Gathering.org #2257] AutoReply: Senior Vice President

2002-05-11 Thread PT-help


Greetings,
This message has been automatically generated in response to the
creation of a trouble ticket regarding:
"Senior Vice President", 

a summary of which appears below.

**
*It might take up to 48 hours for us to get to your case.*
**

There is no need to reply to this message right now.  Your ticket has been
assigned an ID of [Gathering.org #2257].

Please include the string:

 [Gathering.org #2257]

in the subject line of all future correspondence about this issue. To do so, 
you may reply to this message.

Thank you,
[EMAIL PROTECTED]
-
Hei,
Denne meldingen er automatisk sendt til deg for å indikere at en sak har blitt laget i 
vårt system ang:
  "Senior Vice President", 

En kopi av saken er nedenfor.

*
*Det kan ta opptil 48 timer før du får svar.*
*

Det er ikke nødvendig å svare på denne meldingen akkurat nå. Din sak har fått en ID i 
vårt system : [Gathering.org #2257].

Venligst inkluder følgene i Emne/Subject i all vidre korrespondanse:
   [Gathering.org #2257]

Takk,[EMAIL PROTECTED]
-

cid:MQi592kF height=0 width=0>




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



USB to serial converter support?

2002-05-11 Thread Wilko Bulte

Hi there,

I'm to get a laptop without serial port. Now did I find a USB-serial
adapter, which reports itself as:

ugen0: ATEN International Serial adapter, rev 1.10/0.01, addr 2

I also found (in -stable):

# Firmware download for Entrega Serial DB25 adapter.
#
device "Entrega Serial with UART"
product 0x8001
vendor  0x1645
release 0x0101
attach "if ! kldstat -n usio > /dev/null 2>&1 ; then kldload usio;
fi"
attach "/usr/sbin/ezdownload -v -f
/usr/share/usb/firmware/1645.8001.010
1 /dev/${DEVNAME}"

Is that kld usio something that is generically usable for USB-serial
converters? If yes, where can I find it, I don't seem to have an usio
around.

tia (and please bear with me, this is my first USB device)

Wilko

-- 
|   / o / /_  _ [EMAIL PROTECTED]
|/|/ / / /(  (_)  Bulte Arnhem, the Netherlands

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



Re: nextboot loader diff

2002-05-11 Thread John Baldwin


On 11-May-2002 Terry Lambert wrote:
> I don't understand the "YES"/"NO" thing, then.  There is one byte
> difference in the file length, which I don't think can be properly
> accounted, if you do the "YES"/"NO" thing.

He could make it NES for all it matters.

Terry, please see that Gordon isn't trying to reimplement Whistle's nextboot.

Personally, I'm tired of missing the window in the loader to boot a test
kernel, so what I want is to do 'nextboot foo -s' to boot /boot/foo/kernel
into single user mode on the next boot and fall back to /boot/kernel/kernel
on the next boot after that.

>> > Don't assume that the nextboot file will be on the same disk and/or
>> > partition as the boot and other config file code.
>> 
>> Well, I'm assuming it's on the root partition. It would be kinda silly for
>> it to anywhere else.
> 
> Not really.  Consider that if I switch root partitions, then, by
> definition, I switch nextboot files.
> 
> Basically, the InterJet was laid out:

Repeat after me: This nextboot != Interjet nextboot.

-- 

John Baldwin <[EMAIL PROTECTED]>  <><  http://www.FreeBSD.org/~jhb/
"Power Users Use the Power to Serve!"  -  http://www.FreeBSD.org/

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



Re: nextboot loader diff

2002-05-11 Thread Terry Lambert

John Baldwin wrote:
> Terry, please see that Gordon isn't trying to reimplement Whistle's nextboot.
> 
> Personally, I'm tired of missing the window in the loader to boot a test
> kernel, so what I want is to do 'nextboot foo -s' to boot /boot/foo/kernel
> into single user mode on the next boot and fall back to /boot/kernel/kernel
> on the next boot after that.

[ ... ]

> Repeat after me: This nextboot != Interjet nextboot.

Repeat after Gordon:

Gordon Tetlow writes:
] Is there anything that is wrong with the conceptual implementation of the
] nextboot loader code that I've submitted? It definitely needs a code
] cleanup on the forth side (which I'm not qualified to do), but if there
] are no other objections, I'd really like to see this code committed.

He solicited comments/objections.  I've commented/objected.

-- Terry

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



Memory and Reality

2002-05-11 Thread Ed Hall

At Yahoo! we use a lot of shared memory, both in the form of .so's and
for IPC.  It would be very useful to be able to accurately measure the
amount of shared and private memory associated with a process, the
number of references to a given shared memory object, resident vs. non-
resident pages, and so forth.

Determining just what is shared and by how many is the hardest part.
When I asked Peter Wemm about sussing out this sort of info from
proc/*/map, he made some comments about the difficulty of knowing what
actually was shared and what wasn't, how the refcounts aren't exactly
what one might think they are, and so forth.  The same sort of ambiguity
seemed to exist regarding just what is resident (with the term defined
as "in RAM with no need to retrieve from secondary storage") and what
isn't.

Are things really this bad?  Is there a tool out there that can make
sense of FreeBSD's memory state with more accuracy and detail than
"ps" or "top"?  This is a serious issue.  Whether this is exclusively
a FreeBSD problem or not, developers tend to see it that way.

-Ed



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



Re: USB to serial converter support?

2002-05-11 Thread Wilko Bulte

On Sat, May 11, 2002 at 05:14:43PM +0200, Wilko Bulte wrote:

Nevermind, I found uplcom on -current. Not on -stable though (yet?)

Wilko

> Hi there,
> 
> I'm to get a laptop without serial port. Now did I find a USB-serial
> adapter, which reports itself as:
> 
> ugen0: ATEN International Serial adapter, rev 1.10/0.01, addr 2
> 
> I also found (in -stable):
> 
> # Firmware download for Entrega Serial DB25 adapter.
> #
> device "Entrega Serial with UART"
> product 0x8001
> vendor  0x1645
> release 0x0101
> attach "if ! kldstat -n usio > /dev/null 2>&1 ; then kldload usio;
> fi"
> attach "/usr/sbin/ezdownload -v -f
> /usr/share/usb/firmware/1645.8001.010
> 1 /dev/${DEVNAME}"
> 
> Is that kld usio something that is generically usable for USB-serial
> converters? If yes, where can I find it, I don't seem to have an usio
> around.
> 
> tia (and please bear with me, this is my first USB device)
> 
> Wilko
> 
> -- 
> |   / o / /_  _   [EMAIL PROTECTED]
> |/|/ / / /(  (_)  Bulte   Arnhem, the Netherlands
> 
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-hackers" in the body of the message
---end of quoted text---

-- 
|   / o / /_  _ [EMAIL PROTECTED]
|/|/ / / /(  (_)  Bulte Arnhem, the Netherlands

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



gethostbyname2 and AF_INET6

2002-05-11 Thread Peter Haight


Recently mozilla has been really slow resolving some DNS queries. I tracked
this down to a call to gethostbyname2. For some addresses (e.g.
'www.vanguard.com'), gethostbyname2 with AF_INET6 will fail and takes more
than a minute.  I verified this with my own short program that does nothing
but call gethostbyname2.

I've attached a tcpdump of two DNS lookups. One is against
'www.vanguard.com' which takes about a minute and thirty seconds to come
back with an 'Host name lookup failure'.

The second log is against 'www.google.com' and it returns almost immediately
with 'No address associated with name'.

Can someone explain to me what's going on?

Thanks.

--- Log of gethostbyname2('www.vanguard.com', AF_INET6) ---

15:43:20.359250 255.128.174.zip > 0.0.zip: at-#6 25
15:43:21.033482 talri.sapros.com.1640 > wartch.sapros.com.domain:  20502+ ? 
www.vanguard.com. (34)
15:43:21.358839 talri.sapros.com.1641 > wartch.sapros.com.domain:  42707+ PTR? 
1.1.10.10.in-addr.arpa. (40)
15:43:21.359253 wartch.sapros.com.domain > talri.sapros.com.1641:  42707* 1/1/1 
PTR[|domain]
15:43:21.359618 talri.sapros.com.1642 > wartch.sapros.com.domain:  42708+ PTR? 
9.1.10.10.in-addr.arpa. (40)
15:43:21.359965 wartch.sapros.com.domain > talri.sapros.com.1642:  42708* 1/1/1 
PTR[|domain]
15:43:21.408548 255.128.174.zip > 0.0.zip: at-#6 25
15:43:22.458620 255.128.174.zip > 0.0.zip: at-#6 25
15:43:24.258444 0:40:1:80:22:d6 > Broadcast sap e0 ui/C
>>> Unknown IPX Data: (79 bytes)
[000] FF FF 00 60 00 04 00 00  00 00 FF FF FF FF FF FF  ...` 
[010] 04 52 00 00 00 00 00 40  01 80 22 D6 04 52 00 02  .R.@ .."..R..
[020] 55 AA 5A 4F 54 2D 50 53  38 30 32 32 44 36 00 00  U.ZOT-PS 8022D6..
[030] 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00   
[040] 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00  ...
 len=97
  0060 0004     
 0452   0040 0180 22d6 0452 0002
 55aa 5a4f 542d 5053 3830 3232 4436 
        
        00
15:43:26.037875 talri.sapros.com.1643 > mxrelay.lanminds.com.domain:  20502+ ? 
www.vanguard.com. (34)
15:43:26.358016 talri.sapros.com.1644 > wartch.sapros.com.domain:  42709+ PTR? 
6.88.25.208.in-addr.arpa. (42)
15:43:26.358693 wartch.sapros.com.domain > talri.sapros.com.1644:  42709 1/4/4 
PTR[|domain]
15:43:26.922809 wartch.sapros.com.11512 > talri.sapros.com.1074: . 
1417795364:1417795365(1) ack 1842336180 win 33304  
(DF)
15:43:26.922873 talri.sapros.com.1074 > wartch.sapros.com.11512: . ack 0 win 0 
 (DF)
15:43:31.047974 talri.sapros.com.1645 > ns2.lmi.net.domain:  20502+ ? 
www.vanguard.com. (34)
15:43:31.358121 talri.sapros.com.1646 > wartch.sapros.com.domain:  42710+ PTR? 
5.64.25.208.in-addr.arpa. (42)
15:43:31.359089 wartch.sapros.com.domain > talri.sapros.com.1646:  42710 1/3/2 
PTR[|domain]
15:43:36.058129 talri.sapros.com.1647 > wartch.sapros.com.domain:  20502+ ? 
www.vanguard.com. (34)
15:43:37.358336 talri.sapros.com.1648 > wartch.sapros.com.domain:  42711+ PTR? 
47.203.186.198.in-addr.arpa. (45)
15:43:37.360077 wartch.sapros.com.domain > talri.sapros.com.1648:  42711 1/3/0 (149)
15:43:39.068217 talri.sapros.com.1649 > mxrelay.lanminds.com.domain:  20502+ ? 
www.vanguard.com. (34)
15:43:42.078303 talri.sapros.com.nkd > ns2.lmi.net.domain:  20502+ ? 
www.vanguard.com. (34)
15:43:45.088393 talri.sapros.com.shiva_confsrvr > wartch.sapros.com.domain:  20502+ 
? www.vanguard.com. (34)
15:43:51.098565 talri.sapros.com.xnmp > mxrelay.lanminds.com.domain:  20502+ ? 
www.vanguard.com. (34)
15:43:53.163592 wartch.sapros.com.11512 > talri.sapros.com.1074: . 0:1(1) ack 1 win 
33304  (DF)
15:43:53.163683 talri.sapros.com.1074 > wartch.sapros.com.11512: . ack 0 win 0 
 (DF)
15:43:57.108743 talri.sapros.com.1653 > ns2.lmi.net.domain:  20502+ ? 
www.vanguard.com. (34)
15:44:03.118926 talri.sapros.com.1654 > wartch.sapros.com.domain:  20502+ ? 
www.vanguard.com. (34)
15:44:16.129309 talri.sapros.com.1655 > mxrelay.lanminds.com.domain:  20502+ ? 
www.vanguard.com. (34)
15:44:19.404375 wartch.sapros.com.11512 > talri.sapros.com.1074: . 0:1(1) ack 1 win 
33304  (DF)
15:44:19.404469 talri.sapros.com.1074 > wartch.sapros.com.11512: . ack 0 win 0 
 (DF)
15:44:26.016010 255.128.174.zip > 0.0.zip: at-#6 25
15:44:26.765395 0:40:1:80:22:d6 > Broadcast sap e0 ui/C
>>> Unknown IPX Data: (79 bytes)
[000] FF FF 00 60 00 04 00 00  00 00 FF FF FF FF FF FF  ...` 
[010] 04 52 00 00 00 00 00 40  01 80 22 D6 04 52 00 02  .R.@ .."..R..
[020] 55 AA 5A 4F 54 2D 50 53  38 30 32 32 44 36 00 00  U.ZOT-PS 8022D6..
[030] 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00   
[040] 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00  ...
 len=97
  0060 0004     
 

Re: It's not fun anymore. (Mike resigns from core)

2002-05-11 Thread Brandon D. Valentine

On Fri, 10 May 2002, Conrad Minshall wrote:

>Reading this thread I see rationale, considerate responses and a general
>lack of flamage.  Very cool... pun intended, sorry :)

Indeed.

There are some excellent ideas wrt development methodologies in this
paper:

http://martinfowler.com/articles/newMethodology.html

I've found this paper insightful in the sense that it highlights some
weaknesses in my own personal development methodology.  `The members of
the FreeBSD project who are working to develop the, for lack of a better
term, bureaucracy might find this paper illuminating as to alternatives
which don't "take the fun out of it" for too many people.

Brandon D. Valentine
-- 
"Time to resign from the human race, wipe those tears
from your lovely face.  Baby, wave to the man in the
ol' red caboose before all hell breaks loose."
 - Kinky Friedman


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



Problems

2002-05-11 Thread Lunatic

Hi,

I have some troubles with my computer (Abit BD7, P4 1.7Ghz, 512MB DDR,
Tekram U2W, IBM 18GB 160MB/S SCSI, 3Com 3C905TX 10/100, Cirus Logic SVGA
PCI, CD IDE Sony 52X). I have compiled my freebsd kernel in debug mode and i
get this message :



s3# gdb -k kernel.0 vmcore.0
GNU gdb 4.18
Copyright 1998 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain
conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "i386-unknown-freebsd"...(no debugging symbols
found)...
IdlePTD 3624960
initial pcb at 2ec980
panicstr: integer divide fault
panic messages:
---
Fatal trap 18: integer divide fault while in kernel mode
instruction pointer = 0x8:0xc0262e32
stack pointer   = 0x10:0xc02c28dc
frame pointer   = 0x10:0x0
code segment= base 0x0, limit 0xf, type 0x1b
= DPL 0, pres 1, def32 1, gran 1
processor eflags= interrupt enabled, IOPL = 0
current process = Idle
interrupt mask  = none
trap number = 18
panic: integer divide fault

syncing disks... 97 97 97 97 97 97 97 97 97 97 97 97 97 97 97 xl0: watchdog
timeout
97 97 97 97 97
giving up on 97 buffers
xl0: watchdog timeout
Uptime: 24m1s

dumping to dev #da/0x20001, offset 1151552
dump 511 510 509 508 507 506 505 504 503 502 501 500 499 498 497 496 495 494
493 492 491 490 489 488 487 486 485 484 483 482 481 480 479 478 477 476 475
474 473 472 471 470 469 468 467 466 465 464 463 462 461 460 459 458 457 456
455 454 453 452 451 450 449 448 447 446 445 444 443 442 441 440 439 438 437
436 435 434 433 432 431 430 429 428 427 426 425 424 423 422 421 420 419 418
417 416 415 414 413 412 411 410 409 408 407 406 405 404 403 402 401 400 399
398 397 396 395 394 393 392 391 390 389 388 387 386 385 384 383 382 381 380
379 378 377 376 375 374 373 372 371 370 369 368 367 366 365 364 363 362 361
360 359 358 357 356 355 354 353 352 351 350 349 348 347 346 345 344 343 342
341 340 339 338 337 336 335 334 333 332 331 330 329 328 327 326 325 324 323
322 321 320 319 318 317 316 315 314 313 312 311 310 309 308 307 306 305 304
303 302 301 300 299 298 297 296 295 294 293 292 291 290 289 288 287 286 285
284 283 282 281 280 279 278 277 276 275 274 273 272 271 270 269 268 267 266
265 264 263 262 261 260 259 258 257 256 255 254 253 252 251 250 249 248 247
246 245 244 243 242 241 240 239 238 237 236 235 234 233 232 231 230 229 228
227 226 225 224 223 222 221 220 219 218 217 216 215 214 213 212 211 210 209
208 207 206 205 204 203 202 201 200 199 198 197 196 195 194 193 192 191 190
189 188 187 186 185 184 183 182 181 180 179 178 177 176 175 174 173 172 171
170 169 168 167 166 165 164 163 162 161 160 159 158 157 156 155 154 153 152
151 150 149 148 147 146 145 144 143 142 141 140 139 138 137 136 135 134 133
132 131 130 129 128 127 126 125 124 123 122 121 120 119 118 117 116 115 114
113 112 111 110 109 108 107 106 105 104 103 102 101 100 99 98 97 96 95 94 93
92 91 90 89 88 87 86 85 84 83 82 81 80 79 78 77 76 75 74 73 72 71 70 69 68
67 66 65 64 63 62 61 60 59 58 57 56 55 54 53 52 51 50 49 48 47 46 45 44 43
42 41 40 39 38 37 36 35 34 33 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18
17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
---
#0  0xc019545a in dumpsys ()
(kgdb) where
#0  0xc019545a in dumpsys ()
#1  0xc019527b in boot ()
#2  0xc0195611 in panic ()
#3  0xc0263d92 in trap_fatal ()
#4  0xc026377a in trap ()
(kgdb)



This panic often happened, it happens when i download or when i do nothing
on the computer please help me.

Tks a lot.

Rémi.


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



Re: Memory and Reality

2002-05-11 Thread Alfred Perlstein

* Ed Hall <[EMAIL PROTECTED]> [020511 13:13] wrote:
> At Yahoo! we use a lot of shared memory, both in the form of .so's and
> for IPC.  It would be very useful to be able to accurately measure the
> amount of shared and private memory associated with a process, the
> number of references to a given shared memory object, resident vs. non-
> resident pages, and so forth.
> 
> Determining just what is shared and by how many is the hardest part.
> When I asked Peter Wemm about sussing out this sort of info from
> proc/*/map, he made some comments about the difficulty of knowing what
> actually was shared and what wasn't, how the refcounts aren't exactly
> what one might think they are, and so forth.  The same sort of ambiguity
> seemed to exist regarding just what is resident (with the term defined
> as "in RAM with no need to retrieve from secondary storage") and what
> isn't.
> 
> Are things really this bad?  Is there a tool out there that can make
> sense of FreeBSD's memory state with more accuracy and detail than
> "ps" or "top"?  This is a serious issue.  Whether this is exclusively
> a FreeBSD problem or not, developers tend to see it that way.

You'd have to write it yourself, I'm not sure exactly what you sort
of information you're trying to pull, however the easiest way to
do this would be to look at
p->p_vmspace->vm_map->{list of vm_map_entries}
you can then walk this list looking at the object referenced by the
map, I think most of the information "shared"/"nonshared" etc
can be pulled from the vm_map_entry.

-Alfred

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



Re: nextboot loader diff

2002-05-11 Thread Gordon Tetlow

On Sat, 11 May 2002, Terry Lambert wrote:

> > This is not something that is meant for you to massage which root
> > partition you are going to boot up off of.
> 
> I don't understand what it does, then.  The original Whistle code
> was intended to attempt to boot 3 times from one partition, and
> then 3 times from another.

I was thinking different kernel/kernel flags not different root
partitions.  You could probably work something up to make it do different
root partitions, but this was sufficient for my needs.

[snip]

> I don't understand the "YES"/"NO" thing, then.  There is one byte
> difference in the file length, which I don't think can be properly
> accounted, if you do the "YES"/"NO" thing.

Well, it's actually "YES"/"NO" but the loader is smart enough to 
ignore spaces.

[snip]

> The code you are talking about seems limited to replacing only the
> kernel.  Frankly, that's recoverable via the serial console, if
> you put the "-p" in the right file in /.

Exactly. That was all this was meant to do. Look at it as a first 
implementation. If you would like to take the patch I submitted and do 
some more work to have the same functionality as InterJet's code, be my 
guest. There would be alot of work, the first piece being an unbufferred 
string searching function in Forth.

> This isn't really sufficient for any embedded system that needs to

This wasn't for embedded systems, this was for developer convenience.

> I'm not trying to dump on your code; I'm just saying that it's
> not solving the problem that the original code was added to be
> able to solve, and that the original nextboot itself was intended
> to resolve.

Yup, I know that.

Let's lay this discussion to rest and see what we need to do to get the 
code committed and used.

-gordon


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