Alt-BEAM Archive
Message #06940
To: beam@sgiblab.sgi.com
From: "onald Burn" phantomfx@hotmail.com
Date: Wed, 20 Oct 1999 09:19:14 PDT
Subject: [alt-beam] Re: Majordomo results
>From: external-majordomo@corp.sgi.com
>Reply-To: external-majordomo@corp.sgi.com
>To: phantomfx@hotmail.com
>Subject: Majordomo results
>Date: Tue, 12 Oct 1999 13:24:01 -0700 (PDT)
>
>--
>
> >>>> "unsubscribe phantomfx@hotmail.com beam"
>**** Command '"unsubscribe' not recognized.
> >>>>
> >>>> ______________________________________________________
>**** Command '______________________________________________________' not
>recognized.
> >>>> Get Your Private, Free Email at http://www.hotmail.com
>**** get: unknown list 'Your'.
>**** Help for external-majordomo:
>
>
>This help message is being sent to you from the Majordomo mailing list
>management system at external-majordomo.
>
>This is version 1.94.4 of Majordomo.
>
>If you're familiar with mail servers, an advanced user's summary of
>Majordomo's commands appears at the end of this message.
>
>Majordomo is an automated system which allows users to subscribe
>and unsubscribe to mailing lists, and to retrieve files from list
>archives.
>
>You can interact with the Majordomo software by sending it commands
>in the body of mail messages addressed to "external-majordomo".
>Please do not put your commands on the subject line; Majordomo does
>not process commands in the subject line.
>
>You may put multiple Majordomo commands in the same mail message.
>Put each command on a line by itself.
>
>If you use a "signature block" at the end of your mail, Majordomo may
>mistakenly believe each line of your message is a command; you will
>then receive spurious error messages. To keep this from happening,
>either put a line starting with a hyphen ("-") before your signature,
>or put a line with just the word
>
> end
>
>on it in the same place. This will stop the Majordomo software from
>processing your signature as bad commands.
>
>Here are some of the things you can do using Majordomo:
>
>I. FINDING OUT WHICH LISTS ARE ON THIS SYSTEM
>
>To get a list of publicly-available mailing lists on this system, put the
>following line in the body of your mail message to external-majordomo:
>
> lists
>
>Each line will contain the name of a mailing list and a brief description
>of the list.
>
>To get more information about a particular list, use the "info" command,
>supplying the name of the list. For example, if the name of the list
>about which you wish information is "demo-list", you would put the line
>
> info demo-list
>
>in the body of the mail message.
>
>II. SUBSCRIBING TO A LIST
>
>Once you've determined that you wish to subscribe to one or more lists on
>this system, you can send commands to Majordomo to have it add you to the
>list, so you can begin receiving mailings.
>
>To receive list mail at the address from which you're sending your mail,
>simply say "subscribe" followed by the list's name:
>
> subscribe demo-list
>
>If for some reason you wish to have the mailings go to a different address
>(a friend's address, a specific other system on which you have an account,
>or an address which is more correct than the one that automatically appears
>in the "From:" header on the mail you send), you would add that address to
>the command. For instance, if you're sending a request from your work
>account, but wish to receive "demo-list" mail at your personal account
>(for which we will use "jqpublic@my-isp.com" as an example), you'd put
>the line
>
> subscribe demo-list jqpublic@my-isp.com
>
>in the mail message body.
>
>Based on configuration decisions made by the list owners, you may be added
>to the mailing list automatically. You may also receive notification
>that an authorization key is required for subscription. Another message
>will be sent to the address to be subscribed (which may or may not be the
>same as yours) containing the key, and directing the user to send a
>command found in that message back to external-majordomo. (This can be
>a bit of extra hassle, but it helps keep you from being swamped in extra
>email by someone who forged requests from your address.) You may also
>get a message that your subscription is being forwarded to the list owner
>for approval; some lists have waiting lists, or policies about who may
>subscribe. If your request is forwarded for approval, the list owner
>should contact you soon after your request.
>
>Upon subscribing, you should receive an introductory message, containing
>list policies and features. Save this message for future reference; it
>will also contain exact directions for unsubscribing. If you lose the
>intro mail and would like another copy of the policies, send this message
>to external-majordomo:
>
> intro demo-list
>
>(substituting, of course, the real name of your list for "demo-list").
>
>III. UNSUBSCRIBING FROM MAILING LISTS
>
>Your original intro message contains the exact command which should be
>used to remove your address from the list. However, in most cases, you
>may simply send the command "unsubscribe" followed by the list name:
>
> unsubscribe demo-list
>
>(This command may fail if your provider has changed the way your
>address is shown in your mail.)
>
>To remove an address other than the one from which you're sending
>the request, give that address in the command:
>
> unsubscribe demo-list jqpublic@my-isp.com
>
>In either of these cases, you can tell external-majordomo to remove
>the address in question from all lists on this server by using "*"
>in place of the list name:
>
> unsubscribe *
> unsubscribe * jqpublic@my-isp.com
>
>IV. FINDING THE LISTS TO WHICH AN ADDRESS IS SUBSCRIBED
>
>To find the lists to which your address is subscribed, send this command
>in the body of a mail message to external-majordomo:
>
> which
>
>You can look for other addresses, or parts of an address, by specifying
>the text for which Majordomo should search. For instance, to find which
>users at my-isp.com are subscribed to which lists, you might send the
>command
>
> which my-isp.com
>
>Note that many list owners completely or fully disable the "which"
>command, considering it a privacy violation.
>
>V. FINDING OUT WHO'S SUBSCRIBED TO A LIST
>
>To get a list of the addresses on a particular list, you may use the
>"who" command, followed by the name of the list:
>
> who demo-list
>
>Note that many list owners allow only a list's subscribers to use the
>"who" command, or disable it completely, believing it to be a privacy
>violation.
>
>VI. RETRIEVING FILES FROM A LIST'S ARCHIVES
>
>Many list owners keep archives of files associated with a list. These
>may include:
>- back issues of the list
>- help files, user profiles, and other documents associated with the list
>- daily, monthly, or yearly archives for the list
>
>To find out if a list has any files associated with it, use the "index"
>command:
>
> index demo-list
>
>If you see files in which you're interested, you may retrieve them by
>using the "get" command and specifying the list name and archive filename.
>For instance, to retrieve the files called "profile.form" (presumably a
>form to fill out with your profile) and "demo-list.9611" (presumably the
>messages posted to the list in November 1996), you would put the lines
>
> get demo-list profile.form
> get demo-list demo-list.9611
>
>in your mail to external-majordomo.
>
>VII. GETTING MORE HELP
>
>To contact a human site manager, send mail to majordomo-owner.
>To contact the owner of a specific list, send mail to that list's
>approval address, which is formed by adding "-approval" to the user-name
>portion of the list's address. For instance, to contact the list owner
>for demo-list@postofc.corp.sgi.com, you would send mail to
>demo-list-approval@postofc.corp.sgi.com.
>
>To get another copy of this help message, send mail to external-majordomo
>with a line saying
>
> help
>
>in the message body.
>
>VIII. COMMAND SUMMARY FOR ADVANCED USERS
>
>In the description below items contained in []'s are optional. When
>providing the item, do not include the []'s around it. Items in angle
>brackets, such as , are meta-symbols that should be replaced
>by appropriate text without the angle brackets.
>
>It understands the following commands:
>
> subscribe []
> Subscribe yourself (or if specified) to the named .
>
> unsubscribe []
> Unsubscribe yourself (or if specified) from the named .
> "unsubscribe *" will remove you (or ) from all lists. This
> _may not_ work if you have subscribed using multiple addresses.
>
> get
> Get a file related to .
>
> index
> Return an index of files you can "get" for .
>
> which []
> Find out which lists you (or if specified) are on.
>
> who
> Find out who is on the named .
>
> info
> Retrieve the general introductory information for the named .
>
> intro
> Retrieve the introductory message sent to new users. Non-subscribers
> may not be able to retrieve this.
>
> lists
> Show the lists served by this Majordomo server.
>
> help
> Retrieve this message.
>
> end
> Stop processing commands (useful if your mailer adds a signature).
>
>Commands should be sent in the body of an email message to
>"external-majordomo". Multiple commands can be processed provided
>each occurs on a separate line.
>
>Commands in the "Subject:" line are NOT processed.
>
>If you have any questions or problems, please contact
>"majordomo-owner".
>
______________________________________________________
6941 Wed, 20 Oct 1999 09:24:40 PDT [alt-beam] this is not working, i still cant get off this list beam@sgiblab.sgi.com "onald Burn"
>From: "Richard Caudle"
>Reply-To: beam@sgiblab.sgi.com
>To:
>Subject: Re: Suspended Microcore?
>Date: Tue, 12 Oct 1999 16:30:09 -0500
>
>I've experimented with suspended tricores with little success. For some
>reason it would stay saturated when suspended. It would oscillate after
>grounding resistors.
>
>----- Original Message -----
>From: Richard Piotter
>To: BEAM
>Sent: Tuesday, October 12, 1999 10:05 AM
>Subject: Suspended Microcore?
>
>
> > Has anyone ever used a 240 chip and the suspended Bicore design to
> > create a 4 Nv version? Would it work? I'm trying it out, but if someone
> > else has tried it, I'd love some input. Also if anone here has worked
> > with the circuit, how easy/dificult is it to run it in 1 process mode?
> > I've never seen the 240 used with more than 2 Nvs. Also, is it possible
> > to use the back to back photodiodes like in a suspended bicore on
> > diagonal Nvs if the thing is in saturation. How will this affect time
> > constants, as it's something that NEVER happens in a Bicore unless there
> > is a problem. I thought of joining adjacent Nvs, but then there is the
> > question of both being the same again, and if that would have an effect
> > on the time constants, if it would even DO anything, as 2 cycles would
> > leave half the suspended circuit dead.
> >
> > One more... What would happen if all 4 photodiodes had a common floating
> > cathode. just like in a suspended bicore??? what would suspending a pair
> > of 2 Nvs seprately, or suspending all 4 together result in. I suppose if
> > no one else has done any work with this, I'll have to expiriment.
> > --
> >
> >
> > Richard Piotter
> > richfile@rconnect.com
> >
> > The Richfiles Robotics & TI web page:
> > http://richfiles.calc.org
> >
> > For the BEAM Robotics list:
> > BEAM Robotics Tek FAQ
> > http://people.ne.mediaone.net/bushbo/beam/FAQ.html
> >
>
______________________________________________________
6942 Wed, 20 Oct 1999 09:50:17 -0700 [alt-beam] bicore beam@sgiblab.sgi.com Robert Stein Hello all. I hava a quick question. I just breadboarded a bicore. I
was watching the motor go and I noticed something peculiar. I was
watching the gear that eventually will be attached to the legs, and
noticed that the gear was indexing around as well as the oscellation
that it is suppose to do. I am assuming it is because in the difference
in the two .22 uf caps. Am I wrong, or is there something else going on
that I havn't thought about? Thanks for any input!
Home