Sponsored Content
Full Discussion: E250 - need to access it
Operating Systems Solaris E250 - need to access it Post 302080979 by e250user on Friday 21st of July 2006 08:00:29 AM
Old 07-21-2006
yeah, im using hyperterminal on port A.
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Need help to access/mount so to access folder/files on a Remote System using Linux OS

Hi I need to access files from a specific folder of a Linux system from an another Linux System Remotely. I know how to, Export a folder on One SCO System & can access the same by using Import via., NFS in the Sco Unix SVR4 System using the scoadmin utility. Also, I know to use mount -t ... (2 Replies)
Discussion started by: S.Vishwanath
2 Replies

2. UNIX for Advanced & Expert Users

Raid A1000 with E450 and E250.

Hi, I'm facing problem in connecting a Raid A1000 to E250 and E450. ( Both machines with Solaris 2.6 OS and patched, with different scsi-initiator-ids - 7 & 3 ). BTW, I'm not using this setup to access raid data from both machines simultaneously. There is Veritas Cluster Server monitoring... (1 Reply)
Discussion started by: shibz
1 Replies

3. UNIX Benchmarks

Sun E250 / 512MB Ram

============================================================== BYTE UNIX Benchmarks (Version 3.11) System -- SunOS xxxxx 5.8 Generic_108528-13 sun4u sparc SUNW,Ultra-250 Start Benchmark Run: Sun Jan 11 19:47:12 EST 2004 1 interactive users. Dhrystone 2 without register variables ... (0 Replies)
Discussion started by: kduffin
0 Replies

4. Solaris

SUN E250 Console connectivity

Hi, I have cisco console cable. One end of the cable is DB9 connector and the other end is RJ45 connector. I would like to use this cable to connect to my SUN E250 system from my pc so that I can access the SUn console directly. I would like to know whether it is possible and also on which... (5 Replies)
Discussion started by: RajaRC
5 Replies

5. Gentoo

Uses for a Sun e250?

We are retiring a Sun e250 at work, and I wondered if I could put it to any good use. Will I have any problems loading Linux as opposed to Solaris? Should I use any particular flavor of Linux that might be more Sun friendly? Assuming I manage to load Linux on this server, then what? Will it be... (9 Replies)
Discussion started by: kccrusher
9 Replies

6. Solaris

SUN E250 Cluster

Hi, I need some help, since I am new to cluster. I am handling a site where I have look after two SUN E250 server. I have been asked to configure Active-Active Clustering on these servers. I would like to know how to configure both the servers for clustering. Below are the things which... (5 Replies)
Discussion started by: RajaRC
5 Replies

7. Solaris

Sun Solaris 9 E250 -- Suggestions For External Hard Drives

Hello, Running a Sun Solaris 9 E250 and need advice or suggestions on what type of external hard disks are compatible and or available. It's an old machine and is due for replacement soon but in the short term need an external hard drive for backup etc as the partner/backup machine has just... (2 Replies)
Discussion started by: KenLynch
2 Replies

8. Solaris

Error LED showing on E250

I've got an old E250 server where a front error LED is showing. I've read through the Sun docs (Sun Enterprise 250 Server Owner's Guide - Sun Microsystems) but it's only the 'General fault' LED (About the Status and Control Panel (Sun Enterprise 250 Server Owner's Guide) - Sun Microsystems)... (2 Replies)
Discussion started by: aussieos
2 Replies

9. Solaris

Sun Solaris Enterprise E250 x64 Help

Hi everybody, my name is Giulia and for me is the fist time in this forum, i hope write in the correct section for my problem. I have a sun solaris server e250 enterprise with sun 5 versionof O.S. Now i wont format all and install new version of solaris, but i don't know the actual corrent... (7 Replies)
Discussion started by: giulia79
7 Replies

10. Solaris

E250 server not getting ok prompt

E250 server only shows banner when powered on i am not getting OK PROMPT . .In morning it was booting with solaris 7 .i am not able to do STOP-A STOP-D .its not excepting STOP-N also. Please help (1 Reply)
Discussion started by: monu94
1 Replies
Pod::Simple::PullParser(3pm)				 Perl Programmers Reference Guide			      Pod::Simple::PullParser(3pm)

NAME
Pod::Simple::PullParser -- a pull-parser interface to parsing Pod SYNOPSIS
my $parser = SomePodProcessor->new; $parser->set_source( "whatever.pod" ); $parser->run; Or: my $parser = SomePodProcessor->new; $parser->set_source( $some_filehandle_object ); $parser->run; Or: my $parser = SomePodProcessor->new; $parser->set_source( $document_source ); $parser->run; Or: my $parser = SomePodProcessor->new; $parser->set_source( @document_lines ); $parser->run; And elsewhere: require 5; package SomePodProcessor; use strict; use base qw(Pod::Simple::PullParser); sub run { my $self = shift; Token: while(my $token = $self->get_token) { ...process each token... } } DESCRIPTION
This class is for using Pod::Simple to build a Pod processor -- but one that uses an interface based on a stream of token objects, instead of based on events. This is a subclass of Pod::Simple and inherits all its methods. A subclass of Pod::Simple::PullParser should define a "run" method that calls "$token = $parser->get_token" to pull tokens. See the source for Pod::Simple::RTF for an example of a formatter that uses Pod::Simple::PullParser. METHODS
my $token = $parser->get_token This returns the next token object (which will be of a subclass of Pod::Simple::PullParserToken), or undef if the parser-stream has hit the end of the document. $parser->unget_token( $token ) $parser->unget_token( $token1, $token2, ... ) This restores the token object(s) to the front of the parser stream. The source has to be set before you can parse anything. The lowest-level way is to call "set_source": $parser->set_source( $filename ) $parser->set_source( $filehandle_object ) $parser->set_source( $document_source ) $parser->set_source( @document_lines ) Or you can call these methods, which Pod::Simple::PullParser has defined to work just like Pod::Simple's same-named methods: $parser->parse_file(...) $parser->parse_string_document(...) $parser->filter(...) $parser->parse_from_file(...) For those to work, the Pod-processing subclass of Pod::Simple::PullParser has to have defined a $parser->run method -- so it is advised that all Pod::Simple::PullParser subclasses do so. See the Synopsis above, or the source for Pod::Simple::RTF. Authors of formatter subclasses might find these methods useful to call on a parser object that you haven't started pulling tokens from yet: my $title_string = $parser->get_title This tries to get the title string out of $parser, by getting some tokens, and scanning them for the title, and then ungetting them so that you can process the token-stream from the beginning. For example, suppose you have a document that starts out: =head1 NAME Hoo::Boy::Wowza -- Stuff B<wow> yeah! $parser->get_title on that document will return "Hoo::Boy::Wowza -- Stuff wow yeah!". If the document starts with: =head1 Name Hoo::Boy::W00t -- Stuff B<w00t> yeah! Then you'll need to pass the "nocase" option in order to recognize "Name": $parser->get_title(nocase => 1); In cases where get_title can't find the title, it will return empty-string (""). my $title_string = $parser->get_short_title This is just like get_title, except that it returns just the modulename, if the title seems to be of the form "SomeModuleName -- description". For example, suppose you have a document that starts out: =head1 NAME Hoo::Boy::Wowza -- Stuff B<wow> yeah! then $parser->get_short_title on that document will return "Hoo::Boy::Wowza". But if the document starts out: =head1 NAME Hooboy, stuff B<wow> yeah! then $parser->get_short_title on that document will return "Hooboy, stuff wow yeah!". If the document starts with: =head1 Name Hoo::Boy::W00t -- Stuff B<w00t> yeah! Then you'll need to pass the "nocase" option in order to recognize "Name": $parser->get_short_title(nocase => 1); If the title can't be found, then get_short_title returns empty-string (""). $author_name = $parser->get_author This works like get_title except that it returns the contents of the "=head1 AUTHOR Paragraph... " section, assuming that that section isn't terribly long. To recognize a "=head1 Author Paragraph " section, pass the "nocase" otpion: $parser->get_author(nocase => 1); (This method tolerates "AUTHORS" instead of "AUTHOR" too.) $description_name = $parser->get_description This works like get_title except that it returns the contents of the "=head1 DESCRIPTION Paragraph... " section, assuming that that section isn't terribly long. To recognize a "=head1 Description Paragraph " section, pass the "nocase" otpion: $parser->get_description(nocase => 1); $version_block = $parser->get_version This works like get_title except that it returns the contents of the "=head1 VERSION [BIG BLOCK] " block. Note that this does NOT return the module's $VERSION!! To recognize a "=head1 Version [BIG BLOCK] " section, pass the "nocase" otpion: $parser->get_version(nocase => 1); NOTE
You don't actually have to define a "run" method. If you're writing a Pod-formatter class, you should define a "run" just so that users can call "parse_file" etc, but you don't have to. And if you're not writing a formatter class, but are instead just writing a program that does something simple with a Pod::PullParser object (and not an object of a subclass), then there's no reason to bother subclassing to add a "run" method. SEE ALSO
Pod::Simple Pod::Simple::PullParserToken -- and its subclasses Pod::Simple::PullParserStartToken, Pod::Simple::PullParserTextToken, and Pod::Simple::PullParserEndToken. HTML::TokeParser, which inspired this. SUPPORT
Questions or discussion about POD and Pod::Simple should be sent to the pod-people@perl.org mail list. Send an empty email to pod-people-subscribe@perl.org to subscribe. This module is managed in an open GitHub repository, http://github.com/theory/pod-simple/ <http://github.com/theory/pod-simple/>. Feel free to fork and contribute, or to clone git://github.com/theory/pod-simple.git <git://github.com/theory/pod-simple.git> and send patches! Patches against Pod::Simple are welcome. Please send bug reports to <bug-pod-simple@rt.cpan.org>. COPYRIGHT AND DISCLAIMERS
Copyright (c) 2002 Sean M. Burke. This library is free software; you can redistribute it and/or modify it under the same terms as Perl itself. This program is distributed in the hope that it will be useful, but without any warranty; without even the implied warranty of merchantability or fitness for a particular purpose. AUTHOR
Pod::Simple was created by Sean M. Burke <sburke@cpan.org>. But don't bother him, he's retired. Pod::Simple is maintained by: o Allison Randal "allison@perl.org" o Hans Dieter Pearcey "hdp@cpan.org" o David E. Wheeler "dwheeler@cpan.org" perl v5.12.1 2010-05-07 Pod::Simple::PullParser(3pm)
All times are GMT -4. The time now is 10:55 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy