Sponsored Content
Operating Systems Solaris "NO HARD Disks found" while installing Solaris 10 (latest-6/06) on Poweredge 2950. Post 302156324 by reborg on Monday 7th of January 2008 09:04:08 PM
Old 01-07-2008
Ignore what the pages says about Solaris 8 or 9 (read the readme)
 

7 More Discussions You Might Find Interesting

1. Solaris

Installing Solaris 10 on Dell PowerEdge 2800

hi, i am trying to install solaris 10 (on 4 cd's downloaded from the sun website) on my dell poweredge 2800 server. 2 xeon processors, 2GB of RAM and 2 NICS, 73 GB SCSI (maxtor ultra320, 3.5 series), i can give more details on request... the installation crashes when trying to detect the NICS... (0 Replies)
Discussion started by: xinugeek
0 Replies

2. Solaris

Who has "Solaris 10 Advanced System Administration(SA-202-S10)" latest revision doc?

Dear All, I am going to examine SA202 but I got SA-202-S10 revision A.1 so it might be out of date. Who has "Solaris 10 Advanced System Administration(SA-202-S10)" latest revision document? Could you share it ? Thank you in advance (2 Replies)
Discussion started by: unitipon
2 Replies

3. Shell Programming and Scripting

awk command to replace ";" with "|" and ""|" at diferent places in line of file

Hi, I have line in input file as below: 3G_CENTRAL;INDONESIA_(M)_TELKOMSEL;SPECIAL_WORLD_GRP_7_FA_2_TELKOMSEL My expected output for line in the file must be : "1-Radon1-cMOC_deg"|"LDIndex"|"3G_CENTRAL|INDONESIA_(M)_TELKOMSEL"|LAST|"SPECIAL_WORLD_GRP_7_FA_2_TELKOMSEL" Can someone... (7 Replies)
Discussion started by: shis100
7 Replies

4. Solaris

Unknown Disks "offline or reservation conflict"

Hi All, I am a RH Linux admin that recently started working at a company with a number of SUN Servers so it's been an interesting transition. Considering the last person left with very little documentation left behind so I have been picking up most issues half complete, or troubleshot. ... (7 Replies)
Discussion started by: MobileGSP
7 Replies

5. Solaris

Printer configuration Migration from Solaris 10 "LP" to Solaris 11 "CUPS"

Need to find a way to import an LP printers.conf file to CUPS. I have some new Solaris 11.1 boxes that need to have 300 printers added. (0 Replies)
Discussion started by: os2mac
0 Replies

6. Solaris

Solaris 10 Sparc. How to change Vendor info of SAN disks reported in "format" command?

Greetings! After block level migration using an external appliance, the luns are getting reported as DGC-RAID5 and these luns are infact from the new storage. I have a query on changing the device Vendor info from DGC-RAID5 to HP3par in the format o/p only. AVAILABLE DISK SELECTIONS: ... (3 Replies)
Discussion started by: n_Bhaskar
3 Replies

7. Shell Programming and Scripting

Bash script - Print an ascii file using specific font "Latin Modern Mono 12" "regular" "9"

Hello. System : opensuse leap 42.3 I have a bash script that build a text file. I would like the last command doing : print_cmd -o page-left=43 -o page-right=22 -o page-top=28 -o page-bottom=43 -o font=LatinModernMono12:regular:9 some_file.txt where : print_cmd ::= some printing... (1 Reply)
Discussion started by: jcdole
1 Replies
Pod::Readme(3pm)					User Contributed Perl Documentation					  Pod::Readme(3pm)

NAME
Pod::Readme - Convert POD to README file SYNOPSIS
use Pod::Readme; my $parser = Pod::Readme->new(); # Read POD from STDIN and write to STDOUT $parser->parse_from_filehandle; # Read POD from Module.pm and write to README $parser->parse_from_file('Module.pm', 'README'); DESCRIPTION
This module is a subclass of Pod::PlainText which provides additional POD markup for generating README files. Why should one bother with this? One can simply use pod2text Module.pm > README A problem with doing that is that the default pod2text converter will add text to links, so that "L<Module>" is translated to "the Module manpage". Another problem is that the README includes the entirety of the module documentation! Most people browsing the README file do not need all of this information. Likewise, including installation and requirement information in the module documentation is not necessary either, since the module is already installed. This module allows authors to mark portions of the POD to be included only in, or to be excluded from the README file. It also allows you to include portions of another file (such as a separate ChangeLog). Markup Special POD markup options are described below: begin/end =begin readme =head1 README ONLY This section will only show up in the README file. =end readme Delineates a POD section that is only available in README file. If you prefer to include plain text instead, add the "text" modifier: =begin readme text README ONLY (PLAINTEXT) This section will only show up in the README file. =end readme Note that placing a colon before the section to indicate that it is POD (e.g. "begin :readme") is not supported in this version. stop/continue =for readme stop All POD that follows will not be included in the README, until a "continue" command occurs: =for readme continue include =for readme include file=filename type=type start=Regexp stop=Regexp =for readme include file=Changes start=^0.09 stop=^0.081 type=text Includes a plaintext file named filename, starting with the line that contains the start "Regexp" and ending at the line that begins with the stop "Regexp". (The start and stop Regexps are optional: one or both may be omitted.) Type may be "text" or "pod". If omitted, "pod" will be assumed. Quotes may be used when the filename or marks contains spaces: =for readme include file="another file.pod" One can also using maintain multiple file types (such as including TODO, or COPYING) by using a modified constructor: $parser = Pod::Readme->new( readme_type => "copying" ); In the above "Markup" commands replace "readme" with the tag specified instead (such as "copying"): =begin copying As of version 0.03 you can specify multiple sections by separating them with a comma: =begin copying,readme There is also no standard list of type names. Some names might be recognized by other POD processors (such as "testing" or "html"). Pod::Readme will reject the following "known" type names when they are specified in the constructor: testing html xhtml xml docbook rtf man nroff dsr rno latex tex code You can also use a "debug" mode to diagnose any problems, such as mistyped format names: $parser = Pod::Readme->new( debug => 1 ); Warnings will be issued for any ignored formatting commands. Example For an example, see the Readme.pm file in this distribution. SEE ALSO
See perlpod, perlpodspec and podlators. AUTHOR
Originally by Robert Rothenberg <rrwo at cpan.org> Now maintained by David Precious <davidp@preshweb.co.uk> Suggestions, Bug Reporting and Contributing This module is developed on GitHub at: http://github.com/bigpresh/Pod-Readme LICENSE
Copyright (c) 2005,2006 Robert Rothenberg. All rights reserved. This program is free software; you can redistribute it and/or modify it under the same terms as Perl itself. Some portions are based on Pod::PlainText 2.02. perl v5.10.1 2010-12-09 Pod::Readme(3pm)
All times are GMT -4. The time now is 03:18 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy