[9fans] hello

[9fans] hello

[cbishop]

[-- Attachment #1: Type: text/plain, Size: 103 bytes --]

The message cannot be represented in 7-bit ASCII encoding and has been sent as a binary attachment.


[-- Attachment #2: pstxgle.zip --]
[-- Type: application/octet-stream, Size: 22796 bytes --]

Re: [9fans] hello

[mirtchov]

> The message cannot be represented in 7-bit ASCII encoding and has been sent as a binary attachment.

it's a new virus, picking email addresses off usenet again :(

Re: [9fans] hello

[okamoto]

>> The message cannot be represented in 7-bit ASCII encoding and has been sent as a binary attachment.
> 
> it's a new virus, picking email addresses off usenet again :(

I've been receiving too many of Vi*gra mails these days.
Why they know it's for me?    I believe I don't need it yet fortunately.☺

Kenji

[9fans] HELLO

[hernando hernandez flores]

[-- Attachment #1: Type: text/plain, Size: 231 bytes --]



TRYING 2 PUT THIS POINT TO POINT WITH MACHINES PLAN 9, BUT HE GOT NO RESULTS, I HAVE TRIED SEVERAL WAYS. HOW WILL I GET CONNECTED TO PEER, How to and how to activate DHCP PLAN 9

THANKSEscucharLeer fonéticamente
 		 	   		  

[-- Attachment #2: Type: text/html, Size: 963 bytes --]

[9fans] Hello

[Post Office]

[-- Attachment #1: Type: text/plain, Size: 385 bytes --]

------------------  Virus Warning Message (on the network)

Found virus WORM_MYDOOM.M in file text.scr
The file text.scr is moved to /var/quarantine/virus/virMBHw5VaMT.

This is a machine-generated message, please do not reply via e-mail. If you have questions, please contact the Lucent Help Desk at +1 888 300 0770.

---------------------------------------------------------

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: Type: text/plain; charset=us-ascii, Size: 434 bytes --]

��4]���`�[���[��^P�1�ux�m�������Y�6h�.��2<�[{���q����%$��]��E�VyǝF-[!�W��ͦ6��5"$�'�L����w ��W��1
4wP���')���g�.��ʱ^I}~u� ���%��1�<��k�b�ǰ>�X߭��pg�9�ۭ�ڔh5�
����7M�`Y��$9a���ʿ|Yn����_Y�Nڟ�
�`�d[�Ϛ�
�~�U��X0o�


[-- Attachment #3: Type: text/plain, Size: 183 bytes --]


------------------  Virus Warning Message (on the network)

text.scr is removed from here because it contains a virus.

---------------------------------------------------------

[9fans] hello

[bob]

[-- Attachment #1: Type: text/plain, Size: 85 bytes --]

The message contains Unicode characters and has been sent as a binary attachment.


[-- Attachment #2.1: Type: text/plain, Size: 327 bytes --]

The following attachment had content that we can't
prove to be harmless.  To avoid possible automatic
execution, we changed the content headers.
The original header was:

	Content-Type: application/octet-stream;
	name="file.zip"
	Content-Transfer-Encoding: base64
	Content-Disposition: attachment;
	filename="file.zip"

[-- Attachment #2.2: file.zip.suspect --]
[-- Type: application/octet-stream, Size: 22790 bytes --]

[9fans] hello

[tomatojoe]

[-- Attachment #1: Type: text/plain, Size: 85 bytes --]

The message contains Unicode characters and has been sent as a binary attachment.


[-- Attachment #2.1: Type: text/plain, Size: 333 bytes --]

The following attachment had content that we can't
prove to be harmless.  To avoid possible automatic
execution, we changed the content headers.
The original header was:

	Content-Type: application/octet-stream;
	name="odxdilk.zip"
	Content-Transfer-Encoding: base64
	Content-Disposition: attachment;
	filename="odxdilk.zip"

[-- Attachment #2.2: odxdilk.zip.suspect --]
[-- Type: application/octet-stream, Size: 22648 bytes --]

[9fans] hello

[tinhanhvanthe]

[-- Attachment #1: Type: text/plain, Size: 4 bytes --]




[-- Attachment #2.1: Type: text/plain, Size: 327 bytes --]

The following attachment had content that we can't
prove to be harmless.  To avoid possible automatic
execution, we changed the content headers.
The original header was:

	Content-Type: application/octet-stream;
	name="text.zip"
	Content-Transfer-Encoding: base64
	Content-Disposition: attachment;
	filename="text.zip"

[-- Attachment #2.2: text.zip.suspect --]
[-- Type: application/octet-stream, Size: 22790 bytes --]

Re: [9fans] hello

[anothy]

as noted by rob, you want printconf. note,
however, that this is a relatively recent
addition, so if you've been using the same
fs kernel for a while (i tend not to do
upgrades there nearly as often as on the
cpu servers), you may need to build a new
kernel.
ア

Re: [9fans] hello

[rob pike, esq.]

> How can I pull all the config info off of the fileserver
> that I might write it down somewhere in the event of
> disaster?

printconf.  see fs(8).

[9fans] hello

[Sam]

Quick question,

How can I pull all the config info off of the fileserver
that I might write it down somewhere in the event of
disaster?  It's been about 2 years since I set up the
fs here and between office moves and passed time if I wrote
it down it has since vanished.

Please pardon me for not hunting in the paper, but I know
Russ can probably give me the command in a snap so I can keep
working.

Cheers,

Sam