Annotation of www/mail.html, Revision 1.92
1.57 horacio 1: <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
1.1 deraadt 2: <html>
3: <head>
1.2 deraadt 4: <title>OpenBSD Mailing lists</title>
1.22 wvdputte 5: <link rev="made" href= "mailto:www@openbsd.org">
1.57 horacio 6: <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
1.22 wvdputte 7: <meta name= "resource-type" content= "document">
1.28 louis 8: <meta name= "description" content= "the OpenBSD mailing list page">
1.22 wvdputte 9: <meta name= "keywords" content= "openbsd,mail">
10: <meta name= "distribution" content= "global">
1.74 jose 11: <meta name= "copyright" content= "This document copyright 1996-2004 by OpenBSD.">
1.1 deraadt 12: </head>
13:
1.76 david 14: <body bgcolor="#ffffff" text="#000000">
1.1 deraadt 15:
1.58 jsyn 16: <a href="index.html"><img alt="[OpenBSD]" height="30" width="141" src="images/smalltitle.gif" border="0"></a>
1.25 deraadt 17: <p>
1.66 nick 18: <h1><font color="#e00000">Mailing Lists</font></h1>
1.57 horacio 19: <hr>
1.7 downsj 20:
1.66 nick 21: Mailing lists are an important means of communication among users and
22: developers of OpenBSD. With the exceptions of <b>announce</b> and
1.70 nick 23: <b>security-announce</b>, the lists are not moderated. We deliberately
1.66 nick 24: restrict the number of different mailing lists.
25: This helps reduce the amount of cross-posting and makes sure that the
26: information gets distributed to a wide audience.
27:
1.28 louis 28: <p>
1.66 nick 29: <a name="Netiquette"></a>
30: <h2><font color="#e00000">Netiquette</font></h2>
1.28 louis 31: <p>
32: Be considerate of other subscribers on the mailing lists.
33: <dl>
1.66 nick 34: <dt><b>Plain text, 72 characters per line</b>
35: <dd>Many subscribers and developers read their mail on text-based mailers
36: (mail(1), emacs, Mutt)
1.45 millert 37: and they find HTML-formatted messages, or lines that stretch beyond 72
38: characters often unreadable.
39: Most OpenBSD mailing lists strip messages of MIME content before
40: sending them out to the rest of the list.
41: If you don't use plain text your messages will be reformatted or,
42: if they cannot be reformatted, summarily rejected.
1.66 nick 43: The only mailing list that allows attachments is the <b>ports</b> list,
1.45 millert 44: they will be removed from messages on the other mailing lists.
1.66 nick 45:
46: <dt><b>Do your homework before you post</b>
1.28 louis 47: <dd>If you have an installation question, make sure that you have read the relevant
48: documents such as the INSTALL.* text files in the FTP installation directories, the
1.57 horacio 49: <a href="faq/index.html">FAQ</a> and the relevant man pages (start with
1.66 nick 50: <a href= "http://www.openbsd.org/cgi-bin/man.cgi?query=afterboot&sektion=8">afterboot(8)</a>),
51: and check the mailing list <a href="#Archives">archives</a>.
52: We want to help, but we wouldn't want to deprive you of a valuable
53: learning experience, and no one wants to see the same question on the
54: lists for the fifth time in a month.
55:
56: <dt><b>Include a useful Subject line</b>
1.45 millert 57: <dd>Messages with an empty Subject will get bounced to the list manager and
1.57 horacio 58: so they will take longer to show up. Including a relevant Subject in the message
1.45 millert 59: will ensure that more people actually read what you've written.
60: Also, avoid Subject lines with excessive capitalization.
1.66 nick 61: "Help!" or "I can't get it to work!" are not a useful subject lines.
62: Do not change the subject line while on the same topic. YOU may know
63: what it is regarding, the rest of us who get several hundred messages a
64: day will have no idea.
65:
66: <dt><b>Trim your signature</b>
67: <dd>Keep the signature lines at the bottom of your mail to a reasonable
68: length. PGP signatures, and those automatic address cards are merely
69: annoying and are stripped out. Legal disclaimers and advisories are
70: very annoying, and inappropriate to public mailing lists.
71:
72: <dt><b>Stay on topic</b>
1.28 louis 73: <dd>Please keep the subject of the post relevant to users of OpenBSD.
1.66 nick 74:
75: <dt><b>Include important information</b>
76: <dd>Don't waste everyone's time with a hopelessly incomplete question.
77: No one other than you has the information needed to resolve your
78: problem, it is better to provide more information than needed than one
79: detail too little. Any question should include at least the
80: <a href="faq/faq5.html#Flavors">version</a> of OpenBSD (i.e.,
81: "3.2-stable", "3.3-current as of July 20, 2003"). Any hardware related
1.69 nick 82: questions should mention the platform (i.e., sparc,
1.66 nick 83: alpha, etc.), and provide a full
1.70 nick 84: <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=dmesg&sektion=8">dmesg(8)</a>.
1.66 nick 85: Hardware model numbers, unfortunately, don't indicate much about the
86: actual content of a particular machine or accessory, and are useless to
87: anyone who doesn't have that exact machine sitting where they can easily
88: recognize it. The dmesg(8) tells us exactly what is IN your machine,
89: not what stickers are on the outside.
90:
91: <dt><b>Respect differences in opinion and philosophy</b>
92: <dd>Intelligent people may look at the same set of facts and come to
93: very different conclusions. Repeating the same points that didn't
94: convince someone previously rarely changes their mind and irritates all
95: the other readers.
96:
97: <dt><b>Do not cross-post or repeat post</b>
98: <dd>Posting the same message to multiple lists and/or multiple times
99: does not increase the likelihood of getting a useful response, but is
100: likely to irritate the people you want to help you. If you didn't get a
101: satisfactory response the first time you posted to an appropriate list,
102: it is usually because you provided insufficient or unclear information.
103: Don't simply repost the same message.
104:
1.28 louis 105: </dl>
1.1 deraadt 106:
1.33 millert 107: <p>
1.66 nick 108: <a name="spam"></a>
109: <h2><font color="#e00000">Spam</font></h2>
1.33 millert 110: <p>
1.66 nick 111: The OpenBSD mailing lists use
1.78 millert 112: <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=spamd&sektion=8">spamd(8)</a> in greylisting mode as well as
1.66 nick 113: <a href="http://www.spamassassin.org">SpamAssassin</a> to keep down the
1.87 millert 114: spam volume but things do sneak through--deal with it.
1.66 nick 115: In addition, the list server also has regex-based rules to reject
1.87 millert 116: based on some common spam and virus telltales.
117: If you get spam through one of the OpenBSD mailing lists, you don't need to
118: send a copy to the list owner--chances are he's already seen it.
119: Also, please do <b>not</b> submit spam received through the
120: mailing lists to <a href="http://spamcop.net">spamcop</a>
121: as this will result in the list server being added to their RBL.
122: Complaining about and commenting upon spam on the list proper
123: is counter-productive as it generates more traffic than the spam itself.
124: <p>
1.77 millert 125: Note that if you are sending mail from a dynamic IP address you
126: will probably <b>not</b> be able to post to the mailing lists.
127: In this case you should use a <em>smart host</em> sendmail configuration
128: that utilizes your ISP's mail server. See the comments in
129: <tt>/usr/share/sendmail/cf/openbsd-proto.mc</tt> for how to do this.
1.66 nick 130:
131:
132: <a name="Lists"></a>
133: <h2><font color="#e00000">The Mailing Lists</font></h2>
1.33 millert 134:
1.66 nick 135: <h3>General Interest Lists</h3>
136: These lists are of interest to most users of OpenBSD.
1.1 deraadt 137: <dl>
1.66 nick 138:
139: <dt><b>misc</b>
140: <dd>User questions and answers, general questions. This is the most
141: active list. Please, <a href="faq/index.html">read the FAQ</a> and the
142: installation documents, and see <a href="report.html">How to report a
143: Problem</a> before posting.
144:
145: <dt><b>advocacy</b>
146: <dd>Promoting the use of OpenBSD. Non-technical discussions in
147: <i>misc</i> often get shunted here.
148:
149: <dt><b>announce</b>
150: <dd>Important announcements. This low volume list is excellent for
151: people who just want occasional news about the project.
152:
153: <dt><b>security-announce</b>
1.31 millert 154: <dd>Security announcements. This low volume list receives OpenBSD
155: security advisories and pointers to security patches as they become
156: available.
1.66 nick 157:
158: <dt><b>ports</b>
159: <dd>Discussions about using and contributing to the 'ports' source tree.
160:
1.80 pvalchev 161: <dt><b>ports-security</b>
162: <dd>Security announcements for ports and packages. This low volume
163: list receives OpenBSD security advisories concerning the ports tree
164: and packages with more information about the vulnerabilities and
165: patches.
166:
1.66 nick 167: <dt><b>www</b>
168: <dd>Discussion of the OpenBSD Website.</dd>
169: </dl>
170:
171: <h3>Developer's Lists</h3>
172: These lists are for technical discussions of aspects of OpenBSD. They
173: are NOT for beginning or average users, they are not for problem
174: reporting (unless you are including a good fix), and they are not for
175: installation problems. If you have any question about if a message
176: should be posted to any of these lists, almost invariably, it should not
177: be. Use <b>misc</b>, above, instead. <b>Please</b> do not cross post
178: to multiple lists.
179:
180: <dl>
181: <dt><b>bugs</b>
1.57 horacio 182: <dd><a href="report.html">Bug reports</a> as sent in via
1.66 nick 183: <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=sendbug&sektion=1">sendbug(1)</a>
184: and follow-up discussions. If you wish to have your message logged
185: by the <a href="query-pr.html">GNATS</a> bug tracking system, reply
186: to <i>gnats@openbsd.org</i>, gnats@ will then forward to <i>bugs@</i>.
187:
188: <dt><b>ipv6</b>
189: <dd>Discussion of IPv6 and IPsec in OpenBSD
190:
191: <dt><b>ports-bugs</b>
192: <dd>Discussion regarding bugs within the OpenBSD ports tree
193:
194: <dt><b>smp</b>
195: <dd>Development of <a href="faq/faq8.html#SMP">multiprocessor</a>
196: support in OpenBSD. Offers to "help test" and complaints about it not
197: being completed yet are not appreciated. Code, however, is welcome.
198:
199: <dt><b>tech</b>
200: <dd>Discussion of technical topics for OpenBSD developers and advanced
201: users. This is <b>not</b> a "tech support" forum, do not use it as
202: such.
1.86 nick 203: OpenBSD developers will often make patches to implement new features
204: and other important changes available for public testing through this
205: list.
1.66 nick 206:
207: <dt><b>x11</b>
208: <dd>Discussion of X11 development within OpenBSD
209: </dl>
210:
211: <h3>Platform Specific Lists</h3>
212: These lists are focused on user issues and development on individual
213: platforms.
214: <dl>
215: <dt><b>alpha</b>
216: <dd>OpenBSD/alpha port
217:
1.75 miod 218: <dt><b>arm</b>
219: <dd>OpenBSD/cats port and other ARM porting efforts
220:
1.66 nick 221: <dt><b>hppa</b>
222: <dd>OpenBSD/hppa port
223:
224: <dt><b>mac68k</b>
225: <dd>OpenBSD/mac68k port (not PowerPC Macintosh systems)
226:
227: <dt><b>ppc</b>
1.81 nick 228: <dd>OpenBSD/macppc and other PowerPC porting efforts
1.66 nick 229:
230: <dt><b>sparc</b>
231: <dd>OpenBSD/sparc and OpenBSD/sparc64 ports
232:
233: <dt><b>vax</b>
234: <dd>OpenBSD/vax port
235: </dl>
236:
237: <h3>CVS Changes Mailing Lists</h3>
238: Every time a developer commits a change to the OpenBSD
1.69 nick 239: <a href="why-cvs.html">CVS tree</a>, a message is mailed out to all the subscribers
1.66 nick 240: of these lists, containing the commit comments.
241:
242: <dl>
243: <dt><b>source-changes</b>
244: <dd>Automated mail-out of CVS source tree changes in all the repositories
245: other than <i>ports</i>.
246:
247: <dt><b>ports-changes</b>
248: <dd>Automated mail-out of ports-specific CVS source tree changes.
1.1 deraadt 249: </dl>
250:
1.66 nick 251: <h3>CTM Lists</h3>
252: A number of mailing lists are used by the <a href="ctm.html">CTM</a>,
253: an alternative source change distribution system. See the
254: <a href="ctm.html">CTM page</a> for details.
255:
256:
257: <a name="Majordomo"></a>
258: <h2><font color="#e00000">Managing Mailing List Membership via
259: Majordomo</font></h2>
1.1 deraadt 260: <p>
1.57 horacio 261: If you want to be sent a complete list with all mailing lists available
1.66 nick 262: at openbsd.org, send the command "<tt>lists</tt>" on the body of
1.57 horacio 263: a message to
264: <a href="mailto:majordomo@OpenBSD.org">majordomo@OpenBSD.org</a>.
1.28 louis 265:
266: <p>
1.66 nick 267: To subscribe to a given list, send mail to
268: <a href="mailto:majordomo@OpenBSD.org">majordomo@OpenBSD.org</a>
269: with a message body of "<b>subscribe mailing-list-name</b>".
270:
271: <p>
272: For further assistance, send a message body of "<b>help</b>"
1.57 horacio 273: to <a href="mailto:majordomo@OpenBSD.org">majordomo@OpenBSD.org</a>
1.13 deraadt 274: and you will receive a reply outlining all your options. Your domain
1.66 nick 275: <b>MUST</b> resolve properly or the mail will not go through!
1.1 deraadt 276:
1.66 nick 277:
278: <a name="Web"></a>
279: <h2><font color="#e00000">Managing Mailing List Membership via
280: Web</font></h2>
281: Your membership to the OpenBSD mailing lists can also be managed via
282: a web interface at:
283: <blockquote>
284: <a href="http://lists.openbsd.org/">http://lists.openbsd.org/</a>
285: </blockquote>
286:
287:
288: <a name="Tricks"></a>
289: <h2><font color="#e00000">Mailing Lists Tricks</font></h2>
290: There are a number of very useful options that can be selected, either
291: by the <a href="http://lists.openbsd.org">web interface</a> or through
292: <a href="mailto:majordomo@openbsd.org">Majordomo</a>. You can change
293: your email address without having to unsubscribe and resubscribe, you
1.69 nick 294: can temporarily disable your message delivery for a few days while you go on
1.66 nick 295: vacation, and much more. The user is invited to spend some time reading
296: through the options, available by sending
297: <a href="mailto:majordomo@openbsd.org">Majordomo</a> a message
298: containing "<tt>help</tt>" as the body text, or through the
299: "<tt>Help</tt>" tab of the <a href="http://lists.openbsd.org">web
300: interface</a>.
301:
302: <p>
303: As an example, if you were going on vacation for two weeks and didn't
1.69 nick 304: wish to come back to several thousand e-mails, you can disable
1.70 nick 305: message delivery by the mail server for the time of your vacation and have
306: delivery automatically resume upon your scheduled return using the command:
1.66 nick 307: <pre>
1.82 nick 308: set ALL nomail-14d
1.66 nick 309: </pre>
1.68 nick 310: This will suspend your subscription to all mail lists for 14 days
311: (<tt>-14d</tt>). More details and options can be seen on the
1.90 grunk 312: <a href="http://lists.openbsd.org/cgi-bin/mj_wwwusr?&user=&passw=&list=GLOBAL&func=help&extra=overview">Majordomo
1.68 nick 313: overview page</a>.
314:
1.66 nick 315:
316: <h3>Digests</h3>
317: If you would prefer to see a "digest" (a consolidated listing of all the
318: messages for a time period), rather than getting messages individually
319: in "real-time" form, you can use the commands:
320: <pre>
321: set misc digest-daily
322: set source-changes digest-weekly
323: </pre>
324: for daily digests of the <b>misc</b> list, and weekly digests of the
325: <b>source-changes</b> list. Yes, multiple commands can be placed in one
326: Majordomo email.
327:
328:
329: <a name="OtherLists"></a>
330: <h2><font color="#e00000">Other Mailing Lists</font></h2>
331: <p>
332: The fine folks at
333: <a href="http://www.squish.net/openbsd/">squish.net</a> run mailing
334: lists with daily and weekly digests of the OpenBSD <b>source-changes</b>
335: and <b>ports-changes</b> mailing list. This is handy for those who
1.72 nick 336: don't like the typically high volume of these lists.
1.42 millert 337:
338: <p>
1.39 horacio 339: The clever monkeys at <a href="http://www.monkey.org/openbsd-mobile/">monkey.org</a>
1.66 nick 340: maintain the <b>openbsd-mobile</b> list for people using OpenBSD
1.29 louis 341: on mobile and laptop computers. To subscribe:
342: <br>
343: echo subscribe | mail openbsd-mobile-request@monkey.org
344:
1.50 jufi 345: <p>
1.61 dhartmei 346: The insomniac at <a href="http://www.benzedrine.cx/pf/">benzedrine.cx</a>
1.66 nick 347: maintains the <b>pf</b> list for people using the OpenBSD
1.61 dhartmei 348: packet filter. To subscribe:
349: <br>
350: echo subscribe | mail pf-request@benzedrine.cx
351:
352: <p>
1.50 jufi 353: A mailing list for OpenBSD FTP, Web, AnonCVS and CVSup mirror maintainers is
354: available at <a href="http://rt.fm/openbsd-mirrors/">rt.fm</a>.
355:
1.66 nick 356: <a name="nonEnglish"></a>
357: <h2><font color="#e00000">Non-English Lists</font></h2>
1.28 louis 358:
1.66 nick 359: Several non-English speaking mailing lists related to OpenBSD are available
1.59 miod 360: separately. Here is a list of the currently known mailing lists:
361:
362: <!--
363: PLEASE KEEP THIS LIST SORTED, EXCEPT FOR TRANSLATIONS, WHERE YOU SHOULD PUT
364: THE LIST IN YOUR LANGUAGE, IF ONE EXISTS, HEAD OF LIST.
365: -->
1.63 nick 366: <!--
1.59 miod 367: <p>
368: Chinese:
1.66 nick 369: <b>openbsd@shellhung.org</b>
1.59 miod 370: <br>To subscribe, visit the URL at:
371: <a href="http://www.shellhung.org/mailman/listinfo/openbsd/">http://www.shellhung.org/mailman/listinfo/openbsd/</a>.
1.63 nick 372: -->
1.59 miod 373:
374: <p>
375: Czech:
1.66 nick 376: <b>users@openbsd.cz</b>
1.59 miod 377: <br>To subscribe, visit the URL at:
378: <a href="http://openbsd.cz/mailman/listinfo/users/">http://openbsd.cz/mailman/listinfo/users/</a>.
379:
380: <p>
1.84 otto 381: Dutch:
382: <b>openbsd@list.ii.nl</b>
383: <br>To subscribe, visit the URL at:
384: <a href="http://list.ii.nl/listinfo/openbsd">http://list.ii.nl/listinfo/openbsd</a>.
385:
386: <p>
1.71 todd 387: French:
388: <b>openbsd-france-misc@openbsd-france.org</b>
389: <br>To subscribe, visit the URL at:
390: <a href="http://www.openbsd-france.org/mailing-list.php">http://www.openbsd-france.org/mailing-list.php</a>.
391:
392: <p>
1.64 nick 393: German:
1.69 nick 394: <b>liste@openbsd.de</b>
1.64 nick 395: <br>To subscribe, please visit the URL at:
1.89 grunk 396: <a href="http://www.openbsd.de/mailingliste.shtml">http://www.openbsd.de/mailingliste.shtml</a>.
1.64 nick 397:
398: <p>
1.59 miod 399: Greek:
1.66 nick 400: <b>openbsd@bsd.gr</b>
1.83 saad 401: <br>To subscribe, please visit the URL at:
402: <a href="http://www.bsd.gr/mailman/listinfo/openbsd/">http://www.bsd.gr/mailman/listinfo/openbsd/</a>.
1.18 deraadt 403:
404: <p>
1.59 miod 405: Italian:
1.66 nick 406: <a href="http://www.sikurezza.org/">sikurezza.org</a>, an Italian language
407: non-commercial security portal hosts <b>openbsd@sikurezza.org</b>.
1.59 miod 408: <br>To subscribe just send an empty message to <a
409: href="mailto:openbsd-subscribe@sikurezza.org">openbsd-subscribe@sikurezza.org</a>.
410:
411: <p>
412: Japanese: Please visit the URL at:
413: <a href="http://www.openbsd.ics.nara-wu.ac.jp/wakakusa">http://www.openbsd.ics.nara-wu.ac.jp/wakakus</a>
414: for more information.
415:
416: <p>
417: Polish: to subscribe, send mail to
1.55 miod 418: <a href="mailto:OpenBSD-request@bsdzine.org">OpenBSD-request@bsdzine.org</a>.
1.24 deraadt 419:
420: <p>
1.59 miod 421: Portuguese:
1.66 nick 422: <b>openbsd@neei.uevora.pt</b>
1.59 miod 423: <br>To subscribe, visit the URL at:
424: <a href="http://neei.uevora.pt/mailman/listinfo/openbsd/">http://neei.uevora.pt/mailman/listinfo/openbsd/</a>.
425:
426: <p>
1.60 miod 427: Russian:
1.66 nick 428: <b>openbsd@openbsd.ru</b>
1.47 form 429: <br>To subscribe, send mail to
430: <a href="mailto:minimalist@openbsd.ru">minimalist@openbsd.ru</a> with
1.66 nick 431: subject "<b>subscribe openbsd</b>".
1.34 form 432:
433: <p>
1.73 nick 434: Slovenian:
435: to subscribe please visit the URL at
436: <a href="http://obsd.17slon.org/mailinglist.php"
437: >http://obsd.17slon.org/mailinglist.php</a>
438:
439: <p>
1.62 fgsch 440: Spanish:
1.91 grunk 441: <b>OpenBSD-Mexico@googlegroups.com</b>, run from Mexico.
442: <br>To subscribe, please visit
443: <a href="http://groups.google.com.mx/group/OpenBSD-Mexico">
444: http://groups.google.com.mx/group/OpenBSD-Mexico</a>
1.49 horacio 445:
446: <p>
1.66 nick 447: <a name="Archives"></a>
448: <h2><font color="#e00000">Mailing List Archives:</font></h2>
449: These mailing list archives are not managed by the OpenBSD project.
450: Take the time to look at more than one -- each is a little different,
451: and has different search abilities. If you don't find an answer in
452: one, check another.
453:
454: <p>
455: General search engines, such as
456: <a href="http://www.google.com">Google</a> also prove very effective at
457: finding answers to OpenBSD questions.
458:
1.19 deraadt 459: <ul>
1.57 horacio 460: <li><a href="http://www.sigmasoft.com/~openbsd/">USA</a>
1.66 nick 461: <!-- seemingly not working any longer
1.27 ericj 462: <li><a href="http://www.geocrawler.com/lists/4/OpenBSD">Geocrawler Archive</a>
1.66 nick 463: -->
1.39 horacio 464: <li><a href="http://www.monkey.org/openbsd/">The primates at monkey.org</a>
1.41 avsm 465: <li><a href="http://marc.theaimsgroup.com/">MARC</a>
1.88 david 466: <li><a href="http://dir.gmane.org/index.php?prefix=gmane.os.openbsd">Gmane</a>
1.51 heko 467: <li><a href="http://bsdsearch.com/eao/phorum/index.php?f=2">BSDSearch.com</a>
468: <li><a href="http://www.netsys.com/archives.html">@netsys.com</a>
1.57 horacio 469: <li>Neohapsis has a
470: <a href="http://archives.neohapsis.com/archives/openbsd/">mixed archive
471: for tech@, misc@ and ports@</a> and a
472: <a href="http://archives.neohapsis.com/archives/openbsd/cvs/">mixed
473: archive for CVS commits</a>
1.92 ! grunk 474: <li><a href="http://archive.openbsd.nu/">archive.openbsd.nu</a>
1.19 deraadt 475: </ul>
1.1 deraadt 476:
477: <hr>
1.57 horacio 478: <a href="index.html"><img height=24 width=24 src="back.gif" border=0 alt="OpenBSD"></a>
479: <a href="mailto:www@openbsd.org">www@openbsd.org</a>
1.92 ! grunk 480: <br><small>$OpenBSD: mail.html,v 1.91 2005/07/11 17:16:21 grunk Exp $</small>
1.1 deraadt 481:
482: </body>
483: </html>
![[BACK]](/icons/back.gif){kind=icon}
Return to mail.html CVS log ![[TXT]](/icons/text.gif){kind=icon}
![[DIR]](/icons/dir.gif){kind=icon}
Up to [local] / www