Sponsored Content
Special Forums IP Networking Installation Problem in Unix Openserver Post 10888 by S.Vishwanath on Friday 23rd of November 2001 03:49:46 AM
Old 11-23-2001
What is ur Problem, define it ??

Please proceed with ur problem defination & what else u have tried. Some body or the other will be able to reply if addressable.
 

10 More Discussions You Might Find Interesting

1. SCO

Problem during unix installation

i have a problem with installing unix after booting system by itself floppy , during checking the hardware devices computer hangs , and stops. it checks: %fpu %serial %floppy %console %pci %adapter %tape %cd-rom G hd_config in this place system got stop. remember i passed this step at... (1 Reply)
Discussion started by: uranium
1 Replies

2. SCO

sco openserver 5.07 installation problem

Hi everyone, We r installing sco openserver 5.07 on dell poweredge 2800 but we are facing problem when installing SCSI-raid drivers. Dell provide Perc4 raid card and we dont found raid drivers for this specific raid card. So we r stuck up on primary stage and we also dont know the... (2 Replies)
Discussion started by: mineshkoli
2 Replies

3. SCO

OpenServer 6.0 installation hangs on FSC L200

Hello! I made a try to install SCO OS 6.0 on Fujitsu-Siemens L200 server. The installation hangs on the logo screen after the very fast rotating of the small circles. On another simple PC everything went OK. Any idias will be greatly appreciated. (0 Replies)
Discussion started by: olht
0 Replies

4. SCO

SCO OpenServer 5.0.7 Installation problem

we are installing Openserver 5.0.7, system have SAS controller (Hard Disk Attached) as well as Adaptec ultra 320 controller (Tape Drive Attached). At the time of installation we link both driver BTLD Boot: Defbootstr link=accraid ad320 Aftes succesfully installation of accraid btld... (6 Replies)
Discussion started by: hafizurr
6 Replies

5. SCO

openserver 6.0 installation PANIC

I'm trying to install openserver 6.0 on a locally assembled ACPI Multiprocessor PC with an intel core 2 dou e4400 @ 2 ghx and a WD8000JD SATA HD. Immediately after the startup screen I get "PANIC: kernel-mode address fault on kernel address 0xf000ff53". I get this message even if the drive is... (1 Reply)
Discussion started by: tvmccorm
1 Replies

6. SCO

SCO OpenServer 5.0.7 Installation problem on HP ML310 G4

can not for the life of me workout which BTLD to load allways shows no HDD available can any one give me a clue tried hpsas aacraid lsil a160 a320 server is a ML310 G4 ?????:confused::confused: (7 Replies)
Discussion started by: wildginger
7 Replies

7. SCO

unix installation problem

hi, im tring installaing sco unix 5.05 in my pc but it is showing an "memory error loading kernel fd(64)unix.text loading ram disk image fd(64)rootfs" can anybody tell me how to solve this problem. my system configuration is 3.2ghz processor,1gb ram,d101ggc mother board thank u bln (1 Reply)
Discussion started by: blnprasad
1 Replies

8. UNIX for Advanced & Expert Users

Installation of Sco Openserver 5.0.7 on HP DC 7600

Hi All , I wanted to install SCO Open server 5.0.7 on HP DC7600 Desktop Machine, is there any bootloader and which site i can find it to enable me install it because the system is not recognizing the Hard disk just like the ML G Series machine installations. Please help if you have done this... (4 Replies)
Discussion started by: davosky
4 Replies

9. UNIX for Advanced & Expert Users

OpenServer 6.0v installation

Hi: I'm installing SCO Open Server 6.0v on VMWare ESXi, The instalation procedure giving by UnXis is using OVF deploy template and it create a primary partition of 10gb only. Any one know, if the OVF template could be edited to create a larger partition?? Thanks (0 Replies)
Discussion started by: Ccarballo
0 Replies

10. SCO

Installation on SCO Openserver 5.0.5

Hello all, First off- great forum! I have learned a lot just by reading some of the questions and answers. Good to see there are good people out there still willing to help! Here is my dilemma- I have a fairly new server running an Activant product on it, which runs SCO openserver 5.0.5... (9 Replies)
Discussion started by: crt001
9 Replies
Mail::Message::Construct::Reply(3pm)			User Contributed Perl Documentation		      Mail::Message::Construct::Reply(3pm)

NAME
Mail::Message::Construct::Reply - reply to a Mail::Message SYNOPSIS
my Mail::Message $reply = $message->reply; my $quoted = $message->replyPrelude($head->get('From')); DESCRIPTION
Complex functionality on Mail::Message objects is implemented in different files which are autoloaded. This file implements the functionality related to creating message replies. METHODS
Constructing a message $obj->reply(OPTIONS) Start a reply to this message. Some of the header-lines of the original message will be taken. A message-id will be assigned. Some header lines will be updated to facilitate message-thread detection (see Mail::Box::Thread::Manager). You may reply to a whole message or a message part. You may wish to overrule some of the default header settings for the reply immediately, or you may do that later with "set" on the header. ADDRESSES may be specified as string, or a Mail::Address object, or as array of Mail::Address objects. All OPTIONS which are not listed below AND start with a capital, will be added as additional headers to the reply message. -Option --Default Bcc undef Cc <'cc' in current> From <'to' in current> Message-ID <uniquely generated> Subject replySubject() To <sender in current> body undef group_reply <true> include 'INLINE' max_signature 10 message_type Mail::Message postlude undef prelude undef quote '> ' signature undef strip_signature qr/^--s/ Bcc => ADDRESSES Receivers of blind carbon copies: their names will not be published to other message receivers. Cc => ADDRESSES The carbon-copy receivers, by default a copy of the "Cc" field of the source message. From => ADDRESSES Your identification, by default taken from the "To" field of the source message. Message-ID => STRING Supply a STRING as specific message-id for the reply. By default, one is generated for you. If there are no angles around your id, they will be added. Subject => STRING|CODE Force the subject line to the specific STRING, or the result of the subroutine specified by CODE. The subroutine will be called passing the subject of the original message as only argument. By default, Mail::Message::replySubject() is used. To => ADDRESSES The destination of your message. By default taken from the "Reply-To" field in the source message. If that field is not present as well, the "From" line is scanned. If they all fail, "undef" is returned by this method: no reply message produced. body => BODY Usually, the reply method can create a nice, sufficient message from the source message's body. In case you like more complicated reformatting, you may also create a body yourself first, and pass this on to this "reply" method. Some of the other options to this method will be ingored in this case. group_reply => BOOLEAN Will the people listed in the "Cc" headers (those who received the message where you reply to now) also receive this message as carbon copy? include => 'NO'|'INLINE'|'ATTACH' Must the message where this is a reply to be included in the message? If "NO" then not. With "INLINE" a reply body is composed. "ATTACH" will create a multi-part body, where the original message is added after the specified body. It is only possible to inline textual messages, therefore binary or multipart messages will always be enclosed as attachment. max_signature => INTEGER Passed to "stripSignature" on the body as parameter "max_lines". Only effective for single-part messages. message_type => CLASS Create a message with the requested type. By default, it will be a Mail::Message. This is correct, because it will be coerced into the correct folder message type when it is added to that folder. postlude => BODY|LINES The line(s) which to be added after the quoted reply lines. Create a body for it first. This should not include the signature, which has its own option. The signature will be added after the postlude when the reply is INLINEd. prelude => BODY|LINES The line(s) which will be added before the quoted reply lines. If nothing is specified, the result of the replyPrelude() method is taken. When "undef" is specified, no prelude will be added. quote => CODE|STRING Mangle the lines of an "INLINE"d reply with CODE, or by prepending a STRING to each line. The routine specified by CODE is called when the line is in $_. By default, '> ' is added before each line. Specify "undef" to disable quoting. This option is processed after the body has been decoded. signature => BODY|MESSAGE The signature to be added in case of a multi-part reply. The mime-type of the signature body should indicate this is a used as such. However, in INLINE mode, the body will be taken, a line containing '-- ' added before it, and added behind the epilogue. strip_signature => REGEXP|STRING|CODE Remove the signature of the sender. The value of this parameter is passed to Mail::Message::Body::stripSignature(pattern) unless the source text is not included. The signature is stripped from the message before quoting. When a multipart body is encountered, and the message is included to ATTACH, the parts which look like signatures will be removed. If only one message remains, it will be the added as single attachment, otherwise a nested multipart will be the result. The value of this option does not matter, as long as it is present. See Mail::Message::Body::Multipart. example: my $reply = $msg->reply ( prelude => "No spam, please! " , postlude => " Greetings " , strip_signature => 1 , signature => $my_pgp_key , group_reply => 1 , 'X-Extra' => 'additional header' ); $obj->replyPrelude([STRING|FIELD|ADDRESS|ARRAY-OF-THINGS]) Produces a list of lines (usually only one), which will preceded the quoted body of the message. STRING must comply to the RFC822 email address specification, and is usually the content of a "To" or "From" header line. If a FIELD is specified, the field's body must be compliant. Without argument -or when the argument is "undef"- a slightly different line is produced. An characteristic example of the output is On Thu Oct 13 04:54:34 1995, him@example.com wrote: $obj->replySubject(STRING) Mail::Message->replySubject(STRING) Create a subject for a message which is a reply for this one. This routine tries to count the level of reply in subject field, and transform it into a standard form. Please contribute improvements. example: subject --> Re: subject Re: subject --> Re[2]: subject Re[X]: subject --> Re[X+1]: subject subject (Re) --> Re[2]: subject subject (Forw) --> Re[2]: subject <blank> --> Re: your mail DIAGNOSTICS
Error: Cannot include reply source as $include. Unknown alternative for the "include" option of reply(). Valid choices are "NO", "INLINE", and "ATTACH". SEE ALSO
This module is part of Mail-Box distribution version 2.105, built on May 07, 2012. Website: http://perl.overmeer.net/mailbox/ LICENSE
Copyrights 2001-2012 by [Mark Overmeer]. For other contributors see ChangeLog. This program is free software; you can redistribute it and/or modify it under the same terms as Perl itself. See http://www.perl.com/perl/misc/Artistic.html perl v5.14.2 2012-05-07 Mail::Message::Construct::Reply(3pm)
All times are GMT -4. The time now is 06:37 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy