/[gentoo]/xml/htdocs/doc/en/gentoo-alpha-faq.xml
Gentoo

Contents of /xml/htdocs/doc/en/gentoo-alpha-faq.xml

Parent Directory Parent Directory | Revision Log Revision Log


Revision 1.3 - (show annotations) (download) (as text)
Thu Jun 22 20:01:26 2006 UTC (8 years ago) by nightmorph
Branch: MAIN
Changes since 1.2: +122 -37 lines
File MIME type: application/xml
Updated alpha FAQ (yay, cool arch) for bug #137583. thanks to tcort for reporting and the patch.

1 <?xml version="1.0" encoding="UTF-8"?>
2 <!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/gentoo-alpha-faq.xml,v 1.2 2006/04/04 00:44:33 nightmorph Exp $ -->
3
4 <!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
5 <guide link="/doc/en/gentoo-alpha-faq.xml">
6
7 <title>Gentoo Linux/Alpha Frequently Asked Questions</title>
8 <author title="Author">
9 <mail link="tcort@gentoo.org">Thomas Cort</mail>
10 </author>
11
12 <abstract>
13 This FAQ is intended to answer some of the most frequently asked questions
14 relating to Gentoo/Alpha and Linux/Alpha in general.
15 </abstract>
16
17 <!-- The content of this document is licensed under the CC-BY-SA license -->
18 <!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
19 <license/>
20
21 <version>1.2</version>
22 <date>2006-06-21</date>
23
24 <chapter>
25 <title>About this Document</title>
26
27 <section>
28 <title>Introduction</title>
29 <body>
30
31 <p>
32 This document contains answers to the most commonly asked questions about
33 Gentoo/Alpha and Alpha/Linux. It's aimed at both new users and experienced
34 users alike.
35 </p>
36
37
38 </body>
39 </section>
40
41 <section>
42 <title>Content</title>
43 <body>
44
45 <p>
46 <b>About the Gentoo/Alpha Project</b>
47 </p>
48
49 <ul>
50 <li><uri link="#what">What is Gentoo/Alpha?</uri></li>
51 <li>
52 <uri link="#status">
53 What is the current status of the Gentoo/Alpha Project?
54 </uri>
55 </li>
56 </ul>
57
58 <p>
59 <b>The Alpha Architecture</b>
60 </p>
61
62 <ul>
63 <li><uri link="#dead">Isn't the Alpha architecture dead?</uri></li>
64 <li><uri link="#bitapps">Can I run 32-bit applications?</uri></li>
65 <li><uri link="#endian">Is Alpha big endian or little endian?</uri></li>
66 <li><uri link="#i386">Can I run Linux/x86 applications on Alpha?</uri></li>
67 <li><uri link="#why">Why install Gentoo on Alpha?</uri></li>
68 <li><uri link="#where">Where can I buy Alpha hardware?</uri></li>
69 </ul>
70
71 <p>
72 <b>Hardware</b>
73 </p>
74
75 <ul>
76 <li>
77 <uri link="#ascase">I opened up the case on an AlphaServer and now it won't
78 power on, what do I do?</uri>
79 </li>
80 </ul>
81
82 <p>
83 <b>Alpha Specific Compiler Flags</b>
84 </p>
85
86 <ul>
87 <li>
88 <uri link="#CFLAGS">
89 Is the use of Alpha specific compiler flags recommended?
90 </uri>
91 </li>
92 <li>
93 <uri link="#MCPU">
94 How do I optimize for a specific instruction set and scheduling model?
95 </uri>
96 </li>
97 <li>
98 <uri link="#MTUNE">
99 How do I specify the scheduling model without changing the instruction
100 set?
101 </uri>
102 </li>
103 <li>
104 <uri link="#mieee">
105 How do I enable software assisted floating point numbers?
106 </uri>
107 </li>
108 <li>
109 <uri link="#MEMLAT">How do I specify the memory latency of my system?</uri>
110 </li>
111 <li>
112 <uri link="#SMALLDATA">
113 How do I specify that static data should be placed in the small data area?
114 </uri>
115 </li>
116 <li>
117 <uri link="#SMALLTEXT">
118 How do I specify that object code should be placed in the small text area?
119 </uri>
120 </li>
121 <li>
122 <uri link="#CFLAGSERR">
123 What do I do if any of these compiler flags cause a compile, linker, or
124 runtime error?
125 </uri>
126 </li>
127 </ul>
128
129 <p>
130 <b>Alpha Booting and Bootloaders</b>
131 </p>
132
133 <ul>
134 <li><uri link="#SRM">What is SRM?</uri></li>
135 <li><uri link="#ARC">What is ARC?</uri></li>
136 <li>
137 <uri link="#ARCvsSRM">
138 How can I tell if which firmware my Alpha has, ARC or SRM?
139 </uri>
140 </li>
141 <li><uri link="#whichbootloader">Which bootloader do I use?</uri></li>
142 <li>
143 <uri link="#abootfs">
144 Can aboot boot kernels from xfs, reiserfs, or jfs partitions?
145 </uri>
146 </li>
147 </ul>
148
149 <p>
150 <b>Software</b>
151 </p>
152
153 <ul>
154 <li><uri link="#javasupport">How is Java support in Gentoo/Alpha?</uri></li>
155 <li><uri link="#compaqjava">What's wrong with compaq-jdk?</uri></li>
156 <li>
157 <uri link="#currentjava">Will there ever be working Java support?</uri>
158 </li>
159 <li><uri link="#dotnetsupport">How is .NET support in Gentoo/Alpha?</uri></li>
160 <li>
161 <uri link="#dotnetneeded">What is needed for .NET support?</uri>
162 </li>
163 </ul>
164
165 <p>
166 <b>Alpha Linux Kernel</b>
167 </p>
168
169 <ul>
170 <li><uri link="#whichkernel">Which kernel sources should I use?</uri></li>
171 <li><uri link="#selinux">Are hardened-sources supported?</uri></li>
172 <li><uri link="#smpkernel">Does the 2.6 kernel support Alpha SMP?</uri></li>
173 </ul>
174
175 <p>
176 <b>Helping out the Gentoo/Alpha Project</b>
177 </p>
178
179 <ul>
180 <li><uri link="#bugs">How do I report bugs?</uri></li>
181 <li><uri link="#project">How can I help the Gentoo/Alpha Project?</uri></li>
182 <li><uri link="#archtest">Is there an Alpha Arch Testers Project?</uri></li>
183 </ul>
184
185 <p>
186 <b>Other Resources</b>
187 </p>
188
189 <ul>
190 <li><uri link="#noforum">Why is there no Gentoo on Alpha forum?</uri></li>
191 <li>
192 <uri link="#othergentoo">
193 Where can I get more help or information about Gentoo/Alpha?
194 </uri>
195 </li>
196 <li>
197 <uri link="#other">
198 Where can I get more help or information about Alpha/Linux?
199 </uri>
200 </li>
201 </ul>
202
203 </body>
204 </section>
205 </chapter>
206
207 <chapter>
208 <title>About the Gentoo/Alpha Project</title>
209 <section id="what">
210 <title>What is Gentoo/Alpha?</title>
211 <body>
212
213 <p>
214 The Gentoo/Alpha project is responsible for keeping the Gentoo distribution
215 updated and current for the Alpha platform. This primarily includes keywording
216 packages, porting software, and making new releases. The Gentoo/Alpha project
217 aims to provide a usable environment for both desktops and servers.
218 </p>
219
220 </body>
221 </section>
222 <section id="status">
223 <title>What is the current status of the Gentoo/Alpha Project?</title>
224 <body>
225
226 <p>
227 You can find out about the current status of the Gentoo/Alpha project via
228 status reports. These reports inform the public about what we've been up to.
229 New status reports will be posted about once every 6 months. Current and past
230 status report can be found on the <uri
231 link="/proj/en/base/alpha/status/index.xml">Status Reports Project page</uri>.
232 </p>
233
234 </body>
235 </section>
236 </chapter>
237
238 <chapter>
239 <title>The Alpha Architecture</title>
240 <section id="dead">
241 <title>Isn't the Alpha architecture dead?</title>
242 <body>
243
244 <p>
245 Not yet! HP will be taking orders for new Alpha systems until October 27, 2006
246 and Alpha options and upgrades until November 2, 2007. See their <uri
247 link="http://h18002.www1.hp.com/alphaserver/planning2005.html">planning
248 page</uri> for more details.
249 </p>
250
251 </body>
252 </section>
253 <section id="bitapps">
254 <title>Can I run 32-bit applications?</title>
255 <body>
256
257 <p>
258 No, all Alpha systems use a pure 64 bit kernel and a pure 64 bit userland. You
259 cannot even force gcc to output 32 bit code using the <c>-m32</c> compiler
260 flag.
261 </p>
262
263 </body>
264 </section>
265 <section id="endian">
266 <title>Is Alpha big endian or little endian?</title>
267 <body>
268
269 <p>
270 All Alpha systems support both little and big endian. However, Linux only uses
271 little endian.
272 </p>
273
274 </body>
275 </section>
276 <section id="i386">
277 <title>Can I run Linux/x86 applications on Alpha?</title>
278 <body>
279
280 <p>
281 No, not without a full x86 system emulator like <uri
282 link="http://bochs.sourceforge.net/">bochs</uri>. In the past DEC/Compaq/HP
283 maintained a program called <c>em86</c> which allowed Linux/x86 applications to
284 be run on Linux/Alpha systems. However, the program is closed source and no
285 longer maintained upstream. There are no <c>em86</c> binaries available that
286 are compatible with gcc3's ABI.
287 </p>
288
289 </body>
290 </section>
291 <section id="why">
292 <title>Why install Gentoo on Alpha?</title>
293 <body>
294
295 <p>
296 Admittedly, you can find faster 64-bit systems out there, like amd64. However,
297 that doesn't mean that Alpha systems are useless. The following are a few good
298 reasons why you'd want to install Linux on this sort of hardware:
299 </p>
300
301 <ul>
302 <li>
303 You can turn an old computer into something useful. Older Alphas make great
304 routers and servers. Their desktop performance isn't that bad either.
305 </li>
306 <li>You will learn about unusual computer hardware.</li>
307 <li>
308 It's cool. How many people can say they've got Linux running on an Alpha?
309 </li>
310 </ul>
311
312 </body>
313 </section>
314 <section id="where">
315 <title>Where can I buy Alpha hardware?</title>
316 <body>
317
318 <p>
319 Alpha hardware generally isn't available at your local computer store. If you
320 want a new Alpha you're going to have to contact <uri
321 link="http://h18002.www1.hp.com/alphaserver/">HP</uri>. If you want a used
322 Alpha (more economical), <uri link="http://ebay.com">eBay</uri> is usually a
323 good option, assuming that the shipping doesn't cost you too much. There are
324 several used equipment dealers that can be found via google, however most of
325 them charge too much.
326 </p>
327
328 </body>
329 </section>
330 </chapter>
331
332 <chapter>
333 <title>Hardware</title>
334 <section id="ascase">
335 <title>I opened up the case on an AlphaServer and now it won't power
336 on, what do I do?</title>
337 <body>
338
339 <p>
340 Make sure the top panel of the case is on and properly in place. The middle of
341 the top panel of the case has a small piece of metal oriented downwards. When
342 the top panel is put back in place properly, the small piece of metal will
343 press down on a switch. When the switch isn't pressed down, the system will
344 refuse to power on.
345 </p>
346
347 </body>
348 </section>
349 </chapter>
350
351 <chapter>
352 <title>Alpha Specific Compiler Flags</title>
353 <section id="CFLAGS">
354 <title>Is the use of Alpha specific compiler flags recommended?</title>
355 <body>
356
357 <p>
358 As with all compiler optimizations, don't over do it. Use these flags with care
359 and they will give you a stable, speedy system; use them too aggressively and
360 you could seriously break your system. When in doubt, leave it out. If you need
361 further clarification, check the <c>gcc</c> man page.
362 </p>
363
364 </body>
365 </section>
366 <section id="MCPU">
367 <title>
368 How do I optimize for a specific instruction set and scheduling model?
369 </title>
370 <body>
371
372 <p>
373 You can optimize for a specific instruction set and scheduling model with
374 <c>-mcpu=XXX</c>, where XXX is your cpu type. Valid cpu types are <c>ev4</c>,
375 <c>ev45</c>, <c>ev5</c>, <c>ev56</c>, <c>pca56</c>, <c>ev6</c> and <c>ev67</c>.
376 If you do not use the <c>-mcpu=XXX</c> flag, then <c>gcc</c> will default to
377 the cpu type of the machine it was compiled on. <c>-mcpu=</c> is equivalent to
378 the <c>-march=</c> flag on x86.
379 </p>
380
381 </body>
382 </section>
383 <section id="MTUNE">
384 <title>
385 How do I specify the scheduling model without changing the instruction set?
386 </title>
387 <body>
388
389 <p>
390 You can specify the scheduling model without changing the instruction set with
391 <c>-mtune=XXX</c>, where XXX is your cpu type. Valid cpu types are <c>ev4</c>,
392 <c>ev45</c>, <c>ev5</c>, <c>ev56</c>, <c>pca56</c>, <c>ev6</c> and <c>ev67</c>.
393 <c>-mtune=</c> is implied by <c>-mcpu=</c>, so you don't need to specify this
394 with if you set <c>-mcpu=</c>. <c>-mtune=</c> is equivalent to the
395 <c>-mcpu=</c> flag on x86.
396 </p>
397
398 </body>
399 </section>
400 <section id="mieee">
401 <title>How do I enable software assisted floating point numbers?</title>
402 <body>
403
404 <p>
405 You can enable software assisted floating point numbers with <c>-mieee</c>.
406 This will enable software assistance to correctly support denormalized numbers
407 and exceptional IEEE values such as not-a-number and plus/minus infinity.
408 </p>
409
410 <p>
411 This should be in your global <c>CFLAGS</c> unless you really know what you are
412 doing.
413 </p>
414
415 </body>
416 </section>
417 <section id="MEMLAT">
418 <title>How do I specify the memory latency of my system?</title>
419 <body>
420
421 <p>
422 You can specify the memory latency of your system with
423 <c>-mmemory-latency=XXX</c>, where XXX is the number of clock cycles. This sets
424 the latency time that the scheduler should assume for memory references.
425 <c>gcc</c> has some predefined "typical" values that are also accepted by
426 <c>-mmemory-latency=XXX</c>. Those values are <c>L1</c> for Dcache, <c>L2</c>
427 for Scache, <c>L3</c> for Bcache, and <c>main</c> for main memory.
428 </p>
429
430 <p>
431 This flag should probably not be use in your global <c>CFLAGS</c> as the value
432 you choose is highly dependent on the memory access pattern of the application
433 you are compiling.
434 </p>
435
436 </body>
437 </section>
438 <section id="SMALLDATA">
439 <title>
440 How do I specify that static data should be placed in the small data area?
441 </title>
442 <body>
443
444 <p>
445 You can specify that static data should be placed in the small data area with
446 <c>-msmall-data</c>. This will cause <c>gcc</c> to take advantage of some
447 features of the Alpha architecture by storing heavily used pieces of data in
448 specific sections called the small memory sections. The sections are limited to
449 64kb which means accessing anything stored in them will only take one
450 instruction.
451 </p>
452
453 <p>
454 <c>-fPIC</c> will override <c>-msmall-data</c>, so you should use the
455 <c>-fpic</c> flag instead if you do not want <c>-msmall-data</c> to be
456 overridden.
457 </p>
458
459 <p>
460 This flag should probably not be used in your global <c>CFLAGS</c> as some
461 objects require more than 64kb to be stored, and this will cause a gp_overflow
462 ld error.
463 </p>
464
465 </body>
466 </section>
467 <section id="SMALLTEXT">
468 <title>
469 How do I specify that object code should be placed in the small text area?
470 </title>
471 <body>
472
473 <p>
474 You can specify that object code should be placed in the small text area with
475 <c>-msmall-text</c>. This will cause <c>gcc</c> to assume that the entire
476 program (or library) fits in 4MB, and is thus reachable with a branch
477 instruction. This reduces the number of instructions required for a function
478 call from 4 to 1.
479 </p>
480
481 <p>
482 This flag should probably not be used in your global <c>CFLAGS</c> as some
483 programs (or libraries) are larger than 4MB, and this will cause an ld error.
484 </p>
485
486 </body>
487 </section>
488 <section id="CFLAGSERR">
489 <title>
490 What do I do if any of these compiler flags cause a compile, linker, or
491 runtime error?
492 </title>
493 <body>
494
495 <p>
496 As <uri link="#CFLAGS">already mentioned</uri>, please use these <c>CFLAGS</c>
497 cautiously. They may break your system. If you experience problems, try using
498 less aggressive <c>CFLAGS</c> before <uri link="#bugs">filing a bug
499 report</uri>.
500 </p>
501
502 </body>
503 </section>
504 </chapter>
505
506 <chapter>
507 <title>Alpha Booting and Bootloaders</title>
508 <section id="SRM">
509 <title>What is SRM?</title>
510 <body>
511
512 <p>
513 SRM is based on the Alpha Console Subsystem specification, which provides an
514 operating environment for OpenVMS, Tru64 UNIX, and Linux operating systems. See
515 the <uri link="http://www.alphalinux.org/faq/SRM-HOWTO/"> SRM Howto</uri> for
516 more information about SRM.
517 </p>
518
519 </body>
520 </section>
521 <section id="ARC">
522 <title>What is ARC?</title>
523 <body>
524
525 <p>
526 ARC is based on the Advanced RISC Computing (ARC) specification, which provides
527 an operating environment for Windows NT.
528 </p>
529
530 </body>
531 </section>
532 <section id="ARCvsSRM">
533 <title>How can I tell if which firmware my Alpha has, ARC or SRM?</title>
534 <body>
535
536 <p>
537 When you power your system on you will see a screen with a blue background and
538 white text if it is using SRM. You will see a graphical boot system if it is
539 using ARC.
540 </p>
541
542 </body>
543 </section>
544 <section id="whichbootloader">
545 <title>Which bootloader do I use?</title>
546 <body>
547
548 <p>
549 If your Alpha system supports SRM, then you should use aboot. If your system
550 supports both SRM and ARCs (ARC, AlphaBIOS, ARCSBIOS), then you should follow
551 <uri link="http://www.alphalinux.org/faq/x31.html">the SRM Firmware Howto</uri>
552 for switching to SRM and use aboot. If your system can only use ARCs (Ruffian,
553 nautilus, xl, etc.) then you will need to choose milo.
554 </p>
555
556 </body>
557 </section>
558 <section id="abootfs">
559 <title>Can aboot boot kernels from xfs, reiserfs, or jfs partitions?</title>
560 <body>
561
562 <p>
563 No, <c>aboot</c> only supports booting kernels from <c>ext2</c> and <c>ext3</c>
564 partitions. You may still use other files systems for your root partition, you
565 just need to create a <path>/boot</path> partition with either <c>ext2</c> or
566 <c>ext3</c> on it.
567 </p>
568
569 <p>
570 Support for reiserfs and xfs is planned. In fact, there are patches floating
571 around that add support for those two file systems. However, the use of those
572 patches is unsupported.
573 </p>
574
575 </body>
576 </section>
577 </chapter>
578 <chapter>
579 <title>Software</title>
580
581 <section id="javasupport">
582 <title>How is Java support in Gentoo/Alpha?</title>
583 <body>
584
585 <p>
586 Currently, there is only one option for Java VM and Java SDK on Gentoo/Alpha.
587 The packages are called <c>compaq-jre</c> and <c>compaq-jdk</c>.
588 </p>
589
590 </body>
591 </section>
592 <section id="compaqjava">
593 <title>What's wrong with compaq-jdk?</title>
594 <body>
595
596 <p>
597 <c>compaq-jre</c> and <c>compaq-jdk</c> are not very desirable because they are
598 unsupported upstream and obsolete. They only provide Java 1.3.1 and are binary
599 only. The binaries are compiled against an older glibc which causes some
600 unexpected results when you are using a recent glibc. See <uri
601 link="https://bugs.gentoo.org/84306">bug #84306</uri> for our attempts at
602 workarounds.
603 </p>
604
605 </body>
606 </section>
607 <section id="currentjava">
608 <title>Will there ever be working Java support?</title>
609 <body>
610
611 <p>
612 We really hope so. We are following the development of the jdk from <uri
613 link="http://sablevm.org">SableVM</uri>. It isn't ready yet, but we hope with
614 time that it will be a full drop in replacement jdk.
615 </p>
616
617 </body>
618 </section>
619 <section id="dotnetsupport">
620 <title>How is .NET support in Gentoo/Alpha?</title>
621 <body>
622
623 <p>
624 Neither of the two main open source efforts, <uri
625 link="http://www.mono-project.com/Main_Page">mono</uri> nor <uri
626 link="http://www.dotgnu.org/">DotGNU</uri>, support the alpha architecture.
627 </p>
628
629 </body>
630 </section>
631 <section id="dotnetneeded">
632 <title>What is needed for .NET support?</title>
633 <body>
634
635 <p>
636 Bringing .NET to alpha isn't a simple task. It requires coding all of the
637 assembly language code generation macros for the JIT (just in time) compiler
638 and coding architecture specific functions (register allocators, etc).
639 </p>
640
641 </body>
642 </section>
643 </chapter>
644
645 <chapter>
646 <title>Alpha Linux Kernel</title>
647 <section id="whichkernel">
648 <title>Which kernel sources should I use?</title>
649 <body>
650
651 <p>
652 <c>gentoo-sources</c> and <c>vanilla-sources</c> are both supported. You
653 should read the <uri link="/doc/en/gentoo-kernel.xml">Gentoo Kernel Guide</uri>
654 to determine which one is right for your needs.
655 </p>
656
657 </body>
658 </section>
659 <section id="selinux">
660 <title>Are hardened-sources supported?</title>
661 <body>
662
663 <p>
664 <c>hardened-sources</c> and SELinux support is being worked on by Stephen
665 Bennett (<mail link="spb@gentoo.org">spb</mail>). <c>hardened-sources</c> is
666 currently keyworded for alpha. We hope to see an SELinux profile for Alpha in
667 the tree as soon as we feel confident about it.
668 </p>
669
670 </body>
671 </section>
672 <section id="smpkernel">
673 <title>Does the 2.6 kernel support Alpha SMP?</title>
674 <body>
675
676 <p>
677 There were some times in the past when it was broken. However, <c>2.6.15.1</c>
678 and <c>2.6.16.19</c> are both known to work well. If you find that SMP is
679 broken and want SMP support you will need revert to the one of the versions
680 mentioned above or use a 2.4 kernel. If you really need to run the latest 2.6
681 kernel on an SMP box and you don't care that only one of your processors is
682 getting used, then you could configure the 2.6 kernel without SMP support.
683 </p>
684
685 </body>
686 </section>
687 </chapter>
688
689 <chapter>
690 <title>Helping out the Gentoo/Alpha Project</title>
691 <section id="bugs">
692 <title>How do I report bugs?</title>
693 <body>
694
695 <p>
696 If you find a bug or you want to send us patches, then you need to file a bug
697 report. It only takes you a little bit of your time, and your help is really
698 appreciated. Please follow the <uri link="/doc/en/bugzilla-howto.xml">Gentoo
699 Bug Reporting Guide</uri>.
700 </p>
701
702 </body>
703 </section>
704 <section id="project">
705 <title>How can I help the Gentoo/Alpha Project?</title>
706 <body>
707
708 <p>
709 Users can help us by:
710 </p>
711
712 <ul>
713 <li>Filing clear and concise <uri link="#bugs">bug reports</uri>.</li>
714 <li>Testing software that does not yet have the <c>~alpha</c> keyword.</li>
715 <li>
716 Answering questions on the <uri link="/main/en/lists.xml">mailing
717 lists</uri>, <uri link="http://forums.gentoo.org/viewforum-f-32.html">
718 forum</uri> and IRC channel.
719 </li>
720 <li>Sending patches</li>
721 <li>Becoming an <uri
722 link="http://www.gentoo.org/proj/en/base/alpha/AT/index.xml">AT</uri>
723 </li>
724 </ul>
725
726 </body>
727 </section>
728 <section id="archtest">
729 <title>Is there an Alpha Arch Testers Project?</title>
730 <body>
731
732 <p>
733 Yes, see the <uri link="http://www.gentoo.org/proj/en/base/alpha/AT/index.xml">
734 Gentoo Linux Alpha Arch Testers Project</uri> page for details.
735 </p>
736
737 </body>
738 </section>
739 </chapter>
740
741 <chapter>
742 <title>Other Resources</title>
743 <section id="noforum">
744 <title>Why is there no Gentoo on Alpha forum?</title>
745 <body>
746
747 <p>
748 On the <uri link="http://forums.gentoo.org">Gentoo Forums</uri> there are
749 several arch specific categories like <uri
750 link="http://forums.gentoo.org/viewforum-f-24.html">Gentoo on PPC</uri> and
751 <uri link="http://forums.gentoo.org/viewforum-f-24.html">Gentoo on
752 Sparc</uri>. There is no Gentoo on Alpha category because there simply isn't
753 enough Gentoo/Alpha activity on the forums to warrant one. All Alpha related
754 posts should go in the <uri
755 link="http://forums.gentoo.org/viewforum-f-32.html"> Gentoo on Alternative
756 Architectures</uri> category.
757 </p>
758
759 </body>
760 </section>
761 <section id="othergentoo">
762 <title>Where can I get more help or information about Gentoo/Alpha?</title>
763 <body>
764
765 <p>
766 If any of your questions weren't answered here, you can try other resources
767 like the <uri link="/doc/en/handbook/handbook-alpha.xml">Alpha Handbook</uri>
768 or <uri link="/proj/en/base/alpha/">our project homepage</uri>. You can also
769 ask us at <c>#gentoo-alpha</c> on <c>irc.freenode.net</c>, <uri
770 link="http://forums.gentoo.org/viewforum-f-32.html">Gentoo on Alternative
771 Architectures Forum</uri>, or on the <mail>gentoo-alpha@lists.gentoo.org</mail>
772 mailing list.
773 </p>
774
775 </body>
776 </section>
777 <section id="other">
778 <title>Where can I get more help or information about Alpha/Linux?</title>
779 <body>
780
781 <p>
782 <uri link="http://alphalinux.org/">AlphaLinux.org</uri> is a central repository
783 for all things Alpha/Linux.
784 </p>
785
786 </body>
787 </section>
788 </chapter>
789 </guide>

  ViewVC Help
Powered by ViewVC 1.1.20