[gentoo-doc-cvs] cvs commit: gentoo-alpha-faq.xml - gentoo-doc-cvs

From:	Xavier Neys <neysx@×××××××××××.org>
To:	gentoo-doc-cvs@l.g.o
Subject:	[gentoo-doc-cvs] cvs commit: gentoo-alpha-faq.xml
Date:	Thu, 12 Jan 2006 21:32:25
Message-Id:	`200601122132.k0CLWGkA029712@robin.gentoo.org`

1

neysx       06/01/12 21:32:15

2

3

  Modified:    xml/htdocs/doc/en metadoc.xml

4

  Added:       xml/htdocs/doc/en gentoo-alpha-faq.xml

5

  Log:

6

  #116192 New Gentoo/Alpha FAQ

7

8

Revision  Changes    Path

9

1.134     +7 -2      xml/htdocs/doc/en/metadoc.xml

10

11

file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/metadoc.xml?rev=1.134&content-type=text/x-cvsweb-markup&cvsroot=gentoo

12

plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/metadoc.xml?rev=1.134&content-type=text/plain&cvsroot=gentoo

13

diff : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/metadoc.xml.diff?r1=1.133&r2=1.134&cvsroot=gentoo

14

15

Index: metadoc.xml

16

===================================================================

17

RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/metadoc.xml,v

18

retrieving revision 1.133

19

retrieving revision 1.134

20

diff -u -r1.133 -r1.134

21

--- metadoc.xml	9 Jan 2006 14:24:46 -0000	1.133

22

+++ metadoc.xml	12 Jan 2006 21:32:14 -0000	1.134

23

@@ -1,9 +1,9 @@

24

 <?xml version='1.0' encoding="UTF-8"?>

25

-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/metadoc.xml,v 1.133 2006/01/09 14:24:46 neysx Exp $ -->

26

+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/metadoc.xml,v 1.134 2006/01/12 21:32:14 neysx Exp $ -->

27

 <!DOCTYPE metadoc SYSTEM "/dtd/metadoc.dtd">

28

29

 <metadoc lang="en">

30

-<version>1.62</version>

31

+<version>1.63</version>

32

   <members>

33

     <lead>swift</lead>

34

     <lead>neysx</lead>

35

@@ -117,6 +117,7 @@

36

     <file id="2.6-migration">/doc/en/migration-to-2.6.xml</file>

37

     <file id="altinstall">/doc/en/altinstall.xml</file>

38

     <file id="faq">/doc/en/faq.xml</file>

39

+    <file id="gentoo-alpha-faq">/doc/en/gentoo-alpha-faq.xml</file>

40

     <file id="gentoo-amd64-faq">/doc/en/gentoo-amd64-faq.xml</file>

41

     <file id="handbook-alpha">/doc/en/handbook/handbook-alpha.xml</file>

42

     <file id="handbook-amd64">/doc/en/handbook/handbook-amd64.xml</file>

43

@@ -614,6 +615,10 @@

44

       <memberof>faq</memberof>

45

       <fileid>faq</fileid>

46

     </doc>

47

+    <doc id="gentoo-alpha-faq">

48

+      <memberof>faq</memberof>

49

+      <fileid>gentoo-alpha-faq</fileid>

50

+    </doc>

51

     <doc id="gentoo-amd64-faq">

52

       <memberof>faq</memberof>

53

       <fileid>gentoo-amd64-faq</fileid>

1.1                  xml/htdocs/doc/en/gentoo-alpha-faq.xml

58

59

file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/gentoo-alpha-faq.xml?rev=1.1&content-type=text/x-cvsweb-markup&cvsroot=gentoo

60

plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/gentoo-alpha-faq.xml?rev=1.1&content-type=text/plain&cvsroot=gentoo

61

62

Index: gentoo-alpha-faq.xml

63

===================================================================

64

<?xml version="1.0" encoding="UTF-8"?>

65

<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/gentoo-alpha-faq.xml,v 1.1 2006/01/12 21:32:14 neysx Exp $ -->

66

67

<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">

68

<guide link="/doc/en/gentoo-alpha-faq.xml">

69

70

<title>Gentoo Linux/Alpha Frequently Asked Questions</title>

71

<author title="Author">

72

  <mail link="tcort@×××××××××××.ca">Thomas Cort</mail>

73

</author>

74

75

<abstract>

76

This FAQ is intended to answer some of the most frequently asked questions

77

relating to Gentoo/Alpha and Linux/Alpha in general.

78

</abstract>

79

80

<!-- The content of this document is licensed under the CC-BY-SA license -->

81

<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->

82

<license/>

83

84

<version>1.0</version>

85

<date>2006-01-12</date>

86

87

<chapter>

88

<title>About this Document</title>

89

90

<section>

91

<title>Introduction</title>

92

<body>

93

94

<p>

95

This document contains answers to the most commonly asked questions about

96

Gentoo/Alpha and Alpha/Linux. It's aimed at both new users and experienced

97

users alike.

98

</p>

99

100

101

</body>

102

</section>

103

104

<section>

105

<title>Content</title>

106

<body>

107

108

<p>

109

<b>About the Gentoo/Alpha Project</b>

110

</p>

111

112

<ul>

113

  <li><uri link="#what">What is Gentoo/Alpha?</uri></li>

114

  <li>

115

    <uri link="#status">

116

      What is the current status of the Gentoo/Alpha Project?

117

    </uri>

118

  </li>

119

</ul>

120

121

<p>

122

<b>The Alpha Architecture</b>

123

</p>

124

125

<ul>

126

  <li><uri link="#dead">Isn't the Alpha architecture dead?</uri></li>

127

  <li><uri link="#32bit">Can I run 32-bit applications?</uri></li>

128

  <li><uri link="#endian">Is Alpha big endian or little endian?</uri></li>

129

  <li><uri link="#i386">Can I run Linux/x86 applications on Alpha?</uri></li>

130

  <li><uri link="#why">Why install Gentoo on Alpha?</uri></li>

131

  <li><uri link="#where">Where can I buy Alpha hardware?</uri></li>

132

</ul>

133

134

<p>

135

<b>Alpha Specific Compiler Flags</b>

136

</p>

137

138

<ul>

139

  <li>

140

    <uri link="#CFLAGS">

141

      Is the use of Alpha specific compiler flags recommended?

142

    </uri>

143

  </li>

144

  <li>

145

    <uri link="#MCPU">

146

      How do I optimize for a specific instruction set and scheduling model?

147

    </uri>

148

  </li>

149

  <li>

150

    <uri link="#MTUNE">

151

      How do I specify the scheduling model without changing the instruction set?

152

    </uri>

153

  </li>

154

  <li>

155

    <uri link="#mieee">

156

      How do I enable software assisted floating point numbers?

157

    </uri>

158

  </li>

159

  <li>

160

    <uri link="#MEMLAT">How do I specify the memory latency of my system?</uri>

161

  </li>

162

  <li>

163

    <uri link="#SMALLDATA">

164

      How do I specify that static data should be placed in the small data area?

165

    </uri>

166

  </li>

167

  <li>

168

    <uri link="#SMALLTEXT">

169

      How do I specify that object code should be placed in the small text area?

170

    </uri>

171

  </li>

172

  <li>

173

    <uri link="#CFLAGSERR">

174

      What do I do if any of these compiler flags cause a compile, linker, or

175

      runtime error?

176

    </uri>

177

  </li>

178

</ul>

179

180

<p>

181

<b>Alpha Booting and Bootloaders</b>

182

</p>

183

184

<ul>

185

  <li><uri link="#SRM">What is SRM?</uri></li>

186

  <li><uri link="#ARC">What is ARC?</uri></li>

187

  <li>

188

    <uri link="#ARCvsSRM">

189

      How can I tell if which firmware my Alpha has, ARC or SRM?

190

    </uri>

191

  </li>

192

  <li><uri link="#whichbootloader">Which bootloader do I use?</uri></li>

193

</ul>

194

195

<p>

196

<b>Java on Gentoo/Alpha</b>

197

</p>

198

199

<ul>

200

  <li><uri link="#javasupport">How is Java support in Gentoo/Alpha?</uri></li>

201

  <li><uri link="#compaqjava">What's wrong with compaq-jdk?</uri></li>

202

  <li><uri link="#currentjava">Will there ever be working Java support?</uri></li>

203

</ul>

204

205

<p>

206

<b>Alpha Linux Kernel</b>

207

</p>

208

209

<ul>

210

  <li><uri link="#whichkernel">Which kernel sources should I use?</uri></li>

211

  <li><uri link="#selinux">Are hardened-sources supported?</uri></li>

212

  <li><uri link="#smpkernel">Does the 2.6 kernel support Alpha SMP?</uri></li>

213

</ul>

214

215

<p>

216

<b>Helping out the Gentoo/Alpha Project</b>

217

</p>

218

219

<ul>

220

  <li><uri link="#bugs">How do I report bugs?</uri></li>

221

  <li><uri link="#project">How can I help the Gentoo/Alpha Project?</uri></li>

222

  <li><uri link="#archtest">Is there an Alpha Arch Testers Project?</uri></li>

223

</ul>

224

225

<p>

226

<b>Other Resources</b>

227

</p>

228

229

<ul>

230

  <li><uri link="#noforum">Why is there no Gentoo on Alpha forum?</uri></li>

231

  <li>

232

    <uri link="#othergentoo">

233

      Where can I get more help or information about Gentoo/Alpha?

234

    </uri>

235

  </li>

236

  <li>

237

    <uri link="#other">

238

      Where can I get more help or information about Alpha/Linux?

239

    </uri>

240

  </li>

241

</ul>

242

243

</body>

244

</section>

245

</chapter>

246

247

<chapter>

248

<title>About the Gentoo/Alpha Project</title>

249

<section id="what">

250

<title>What is Gentoo/Alpha?</title>

251

<body>

252

253

<p>

254

The Gentoo/Alpha project is responsible for keeping the Gentoo distribution

255

updated and current for the Alpha platform. This primarily includes keywording

256

and new releases. The Gentoo/Alpha project aims to provide a usable environment

257

for both desktop and server usage.

258

</p>

259

260

</body>

261

</section>

262

<section id="status">

263

<title>What is the current status of the Gentoo/Alpha Project?</title>

264

<body>

265

266

<p>

267

You can find out about the current status of the Gentoo/Alpha project in our

268

status reports. Jose Luis Rivero (<mail

269

link="yoswink@g.o">yoswink</mail>) plans on releasing a Gentoo/Alpha

270

status report about once every 6 months. The current status report can be found

271

<uri link="/proj/en/base/alpha/status/status-20051207.xml"> here</uri>.

272

</p>

273

274

</body>

275

</section>

276

</chapter>

277

278

<chapter>

279

<title>The Alpha Architecture</title>

280

<section id="dead">

281

<title>Isn't the Alpha architecture dead?</title>

282

<body>

283

284

<p>

285

Not yet! HP will be taking orders for new Alpha systems until October 27, 2006

286

and Alpha options and upgrades until November 2, 2007. See their <uri

287

link="http://h18002.www1.hp.com/alphaserver/planning2005.html">planning

288

page</uri> for more details.

289

</p>

290

291

</body>

292

</section>

293

<section id="32bit">

294

<title>Can I run 32-bit applications?</title>

295

<body>

296

297

<p>

298

No, all Alpha systems use a pure 64 bit kernel and a pure 64 bit userland. You

299

cannot even force gcc to output 32 bit code using the <c>-m32</c> compiler

300

flag.

301

</p>

302

303

</body>

304

</section>

305

<section id="endian">

306

<title>Is Alpha big endian or little endian?</title>

307

<body>

308

309

<p>

310

All Alpha systems support both little and big endian. However, Linux only uses

311

little endian.

312

</p>

313

314

</body>

315

</section>

316

<section id="i386">

317

<title>Can I run Linux/x86 applications on Alpha?</title>

318

<body>

319

320

<p>

321

No, not without a full x86 system emulator like <uri

322

link="http://bochs.sourceforge.net/">bochs</uri>. In the past DEC/Compaq/HP

323

maintained a program called <c>em86</c> which allowed Linux/x86 applications to

324

be run on Linux/Alpha systems. However, the program is closed source and no

325

longer maintained upstream. There are no <c>em86</c> binaries available that

326

are compatible with gcc3's ABI.

327

</p>

328

329

</body>

330

</section>

331

<section id="why">

332

<title>Why install Gentoo on Alpha?</title>

333

<body>

334

335

<p>

336

Admittedly, you can find faster 64-bit systems out there, like amd64. However,

337

that doesn't mean that Alpha systems are useless. The following are a few good

338

reasons why you'd want to install Linux on this sort of hardware:

339

</p>

340

341

<ul>

342

  <li>

343

    You can turn an old computer into something useful. Older Alphas make great

344

    routers and servers. Their desktop performance isn't that bad either.

345

  </li>

346

  <li>You will learn about unusual computer hardware.</li>

347

  <li>

348

    It's cool. How many people can say they've got Linux running on an Alpha?

349

  </li>

350

</ul>

351

352

</body>

353

</section>

354

<section id="where">

355

<title>Where can I buy Alpha hardware?</title>

356

<body>

357

358

<p>

359

Alpha hardware generally isn't available at your local computer store.  If you

360

want a new Alpha you're going to have to contact <uri

361

link="http://h18002.www1.hp.com/alphaserver/">HP</uri>. If you want a used

362

Alpha (more economical), <uri link="http://ebay.com">eBay</uri> is usually a

363

good option, assuming that the shipping doesn't cost you too much.  There are

364

several used equipment dealers that can be found via google, however most of

365

them charge too much.

366

</p>

367

368

</body>

369

</section>

370

</chapter>

371

372

<chapter>

373

<title>Alpha Specific Compiler Flags</title>

374

<section id="CFLAGS">

375

<title>Is the use of Alpha specific compiler flags recommended?</title>

376

<body>

377

378

<p>

379

As with all compiler optimizations, don't over do it. Use these flags with care

380

and they will give you a stable, speedy system; use them too aggressively and

381

you could seriously break your system. When in doubt, leave it out. If you need

382

further clarification, check the <c>gcc</c> man page.

383

</p>

384

385

</body>

386

</section>

387

<section id="MCPU">

388

<title>

389

  How do I optimize for a specific instruction set and scheduling model?

390

</title>

391

<body>

392

393

<p>

394

You can optimize for a specific instruction set and scheduling model with

395

<c>-mcpu=XXX</c>, where XXX is your cpu type. Valid cpu types are <c>ev4</c>,

396

<c>ev45</c>, <c>ev5</c>, <c>ev56</c>, <c>pca56</c>, <c>ev6</c> and <c>ev67</c>.

397

If you do not use the <c>-mcpu=XXX</c> flag, then <c>gcc</c> will  default to

398

the cpu type of the machine it was compiled on. <c>-mcpu=</c> is equivalent to

399

the <c>-march=</c> flag on x86.

400

</p>

401

402

</body>

403

</section>

404

<section id="MTUNE">

405

<title>

406

  How do I specify the scheduling model without changing the instruction set?

407

</title>

408

<body>

409

410

<p>

411

You can specify the scheduling model without changing the instruction set with

412

<c>-mtune=XXX</c>, where XXX is your cpu type. Valid cpu types are <c>ev4</c>,

413

<c>ev45</c>, <c>ev5</c>, <c>ev56</c>, <c>pca56</c>, <c>ev6</c> and <c>ev67</c>.

414

<c>-mtune=</c> is implied by <c>-mcpu=</c>, so you don't need to specify this

415

with if you set <c>-mcpu=</c>. <c>-mtune=</c> is equivalent to the

416

<c>-mcpu=</c> flag on x86.

417

</p>

418

419

</body>

420

</section>

421

<section id="mieee">

422

<title>How do I enable software assisted floating point numbers?</title>

423

<body>

424

425

<p>

426

You can enable software assisted floating point numbers with <c>-mieee</c>.

427

This will enable software assistance to correctly support denormalized numbers

428

and exceptional IEEE values such as not-a-number and plus/minus infinity.

429

</p>

430

431

<p>

432

This should be in your global <c>CFLAGS</c> unless you really know what you are

433

doing.

434

</p>

435

436

</body>

437

</section>

438

<section id="MEMLAT">

439

<title>How do I specify the memory latency of my system?</title>

440

<body>

441

442

<p>

443

You can specify the memory latency of your system with

444

<c>-mmemory-latency=XXX</c>, where XXX is the number of clock cycles. This sets

445

the latency time that the scheduler should assume for memory references.

446

<c>gcc</c> has some predefined "typical" values that are also accepted by

447

<c>-mmemory-latency=XXX</c>. Those values are <c>L1</c> for Dcache, <c>L2</c>

448

for Scache, <c>L3</c> for Bcache, and <c>main</c> for main memory.

449

</p>

450

451

<p>

452

This flag should probably not be use in your global <c>CFLAGS</c> as the value

453

you choose is highly dependent on the memory access pattern of the application

454

you are compiling.

455

</p>

456

457

</body>

458

</section>

459

<section id="SMALLDATA">

460

<title>

461

  How do I specify that static data should be placed in the small data area?

462

</title>

463

<body>

464

465

<p>

466

You can specify that static data should be placed in the small data area with

467

<c>-msmall-data</c>. This will cause <c>gcc</c> to take advantage of some

468

features of the Alpha architecture by storing heavily used pieces of data in

469

specific sections called the small memory sections. The sections are limited to

470

64kb which means accessing anything stored in them will only take one

471

instruction.

472

</p>

473

474

<p>

475

<c>-fPIC</c> will override <c>-msmall-data</c>, so you should use the

476

<c>-fpic</c> flag instead if you do not want <c>-msmall-data</c> to be

477

overridden.

478

</p>

479

480

<p>

481

This flag should probably not be used in your global <c>CFLAGS</c> as some

482

objects require more than 64kb to be stored, and this will cause a gp_overflow

483

ld error.

484

</p>

485

486

</body>

487

</section>

488

<section id="SMALLTEXT">

489

<title>

490

  How do I specify that object code should be placed in the small text area?

491

</title>

492

<body>

493

494

<p>

495

You can specify that object code should be placed in the small text area with

496

<c>-msmall-text</c>. This will cause <c>gcc</c> to assume that the entire

497

program (or library) fits in 4MB, and is thus reachable with a branch

498

instruction.  This reduces the number of instructions required for a function

499

call from 4 to 1.

500

</p>

501

502

<p>

503

This flag should probably not be used in your global <c>CFLAGS</c> as some

504

programs (or libraries) are larger than 4MB, and this will cause an ld error.

505

</p>

506

507

</body>

508

</section>

509

<section id="CFLAGSERR">

510

<title>

511

  What do I do if any of these compiler flags cause a compile, linker, or

512

  runtime error?

513

</title>

514

<body>

515

516

<p>

517

As <uri link="#CFLAGS">already mentioned</uri>, please use these <c>CFLAGS</c>

518

cautiously. They may break your system. If you experience problems, try using

519

less aggressive <c>CFLAGS</c> before <uri link="#bugs">filing a bug

520

report</uri>.

521

</p>

522

523

</body>

524

</section>

525

</chapter>

526

527

<chapter>

528

<title>Alpha Booting and Bootloaders</title>

529

<section id="SRM">

530

<title>What is SRM?</title>

531

<body>

532

533

<p>

534

SRM is based on the Alpha Console Subsystem specification, which provides an

535

operating environment for OpenVMS, Tru64 UNIX, and Linux operating systems. See

536

the <uri link="http://www.alphalinux.org/faq/SRM-HOWTO/"> SRM Howto</uri> for

537

more information about SRM.

538

</p>

539

540

</body>

541

</section>

542

<section id="ARC">

543

<title>What is ARC?</title>

544

<body>

545

546

<p>

547

ARC is based on the Advanced RISC Computing (ARC) specification, which provides

548

an operating environment for Windows NT.

549

</p>

550

551

</body>

552

</section>

553

<section id="ARCvsSRM">

554

<title>How can I tell if which firmware my Alpha has, ARC or SRM?</title>

555

<body>

556

557

<p>

558

When you power your system on you will see a screen with a blue background and

559

white text if it is using SRM. You will see a graphical boot system if it is

560

using ARC.

561

</p>

562

563

</body>

564

</section>

565

<section id="whichbootloader">

566

<title>Which bootloader do I use?</title>

567

<body>

568

569

<p>

570

If your Alpha system supports SRM, then you should use aboot. If your system

571

supports both SRM and ARCs (ARC, AlphaBIOS, ARCSBIOS), then you should follow

572

<uri link="http://www.alphalinux.org/faq/x31.html">the SRM Firmware Howto</uri>

573

for switching to SRM and use aboot. If your system can only use ARCs (Ruffian,

574

nautilus, xl, etc.) then you will need to choose milo.

575

</p>

576

577

</body>

578

</section>

579

</chapter>

580

<chapter>

581

<title>Java on Gentoo/Alpha</title>

582

583

<section id="javasupport">

584

<title>How is Java support in Gentoo/Alpha?</title>

585

<body>

586

587

<p>

588

Currently, there is only one option for Java VM and Java SDK on Gentoo/Alpha.

589

The packages are called <c>compaq-jre</c> and <c>compaq-jdk</c>.

590

</p>

591

592

</body>

593

</section>

594

<section id="compaqjava">

595

<title>What's wrong with compaq-jdk?</title>

596

<body>

597

598

<p>

599

<c>compaq-jre</c> and <c>compaq-jdk</c> are not very desirable because they are

600

unsupported upstream and obsolete. They only provide Java 1.3.1 and are binary

601

only. The binaries are compiled against an older glibc which causes some

602

unexpected results when you are using a recent glibc. See <uri

603

link="https://bugs.gentoo.org/84306">bug #84306</uri> for our attempts at

604

workarounds.

605

</p>

606

607

</body>

608

</section>

609

<section id="currentjava">

610

<title>Will there ever be working Java support?</title>

611

<body>

612

613

<p>

614

We really hope so. We are following the development of the jdk from <uri

615

link="http://sablevm.org">SableVM</uri>. It isn't ready yet, but we hope with

616

time that it will be a full drop in replacement jdk.

617

</p>

618

619

</body>

620

</section>

621

</chapter>

622

623

<chapter>

624

<title>Alpha Linux Kernel</title>

625

<section id="whichkernel">

626

<title>Which kernel sources should I use?</title>

627

<body>

628

629

<p>

630

<c>gentoo-sources</c> and <c>vanilla-sources</c> are both supported.  You

631

should read the <uri link="/doc/en/gentoo-kernel.xml">Gentoo Kernel Guide</uri>

632

to determine which one is right for your needs.

633

</p>

634

635

</body>

636

</section>

637

<section id="selinux">

638

<title>Are hardened-sources supported?</title>

639

<body>

640

641

<p>

642

<c>hardened-sources</c> and SELinux support is being worked on by Stephen

643

Bennett (<mail link="spb@g.o">spb</mail>). We hope to see an SELinux

644

profile for Alpha in the tree as soon as we feel confident about it.

645

</p>

646

647

</body>

648

</section>

649

<section id="smpkernel">

650

<title>Does the 2.6 kernel support Alpha SMP?</title>

651

<body>

652

653

<p>

654

Working SMP for Alpha with the 2.6 Linux kernel varies from version to version.

655

If you find that it is broken and want SMP support you will need to use a 2.4

656

kernel. If you really need to run a 2.6 kernel on an SMP box and you don't care

657

that only one of your processors is getting used, then you could configure the

658

2.6 kernel without SMP support.

659

</p>

660

661

<p>

662

The 2.6 Linux kernel runs fine on uniprocessor Alpha systems.

663

</p>

664

665

</body>

666

</section>

667

</chapter>

668

669

<chapter>

670

<title>Helping out the Gentoo/Alpha Project</title>

671

<section id="bugs">

672

<title>How do I report bugs?</title>

673

<body>

674

675

<p>

676

If you find a bug or you want to send us patches, then you need to file a bug

677

report. It only takes you a little while, and your help is really appreciated.

678

Please follow the <uri link="/doc/en/bugzilla-howto.xml">Gentoo Bug Reporting

679

Guide</uri>.

680

</p>

681

682

</body>

683

</section>

684

<section id="project">

685

<title>How can I help the Gentoo/Alpha Project?</title>

686

<body>

687

688

<p>

689

Users can help us by:

690

</p>

691

692

<ul>

693

  <li>Filing clear and concise <uri link="#bugs">bug reports</uri>.</li>

694

  <li>Testing software that does not yet have the <c>~alpha</c> keyword.</li>

695

  <li>

696

    Answering questions on the <uri link="/main/en/lists.xml">mailing

697

    lists</uri>, <uri link="http://forums.gentoo.org/viewforum-f-32.html">

698

    forum</uri> and IRC channel.

699

  </li>

700

  <li>Sending patches</li>

701

</ul>

702

703

</body>

704

</section>

705

<section id="archtest">

706

<title>Is there an Alpha Arch Testers Project?</title>

707

<body>

708

709

<p>

710

At the moment there is no arch testers project for Gentoo/Alpha. However, there

711

will be one in the future. Fernando J. Pereda (<mail

712

link="ferdy@g.o">ferdy</mail>) has been working on getting the project

713

off the ground.

714

</p>

715

716

</body>

717

</section>

718

</chapter>

719

720

<chapter>

721

<title>Other Resources</title>

722

<section id="noforum">

723

<title>Why is there no Gentoo on Alpha forum?</title>

724

<body>

725

726

<p>

727

On the <uri link="http://forums.gentoo.org">Gentoo Forums</uri> there are

728

several arch specific categories like <uri

729

link="http://forums.gentoo.org/viewforum-f-24.html">Gentoo on PPC</uri> and

730

<uri link="http://forums.gentoo.org/viewforum-f-24.html">Gentoo on Sparc</uri>.

731

There is no Gentoo on Alpha category because there simply isn't enough

732

Gentoo/Alpha activity on the forums to warrant one. All Alpha related posts

733

should go in the <uri link="http://forums.gentoo.org/viewforum-f-32.html">

734

Gentoo on Alternative Architectures</uri> category.

735

</p>

736

737

</body>

738

</section>

739

<section id="othergentoo">

740

<title>Where can I get more help or information about Gentoo/Alpha?</title>

741

<body>

742

743

<p>

744

If any of your questions weren't answered here, you can try other resources

745

like the <uri link="/doc/en/handbook/handbook-alpha.xml">Alpha Handbook</uri>

746

or <uri link="/proj/en/base/alpha/">our project homepage</uri>. You can also

747

ask us at <c>#gentoo-alpha</c> on <c>irc.freenode.net</c>, <uri

748

link="http://forums.gentoo.org/viewforum-f-32.html">Gentoo on Alternative

749

Architectures Forum</uri>, or on the <mail>gentoo-alpha@l.g.o</mail>

750

mailing list.

751

</p>

752

753

</body>

754

</section>

755

<section id="other">

756

<title>Where can I get more help or information about Alpha/Linux?</title>

757

<body>

758

759

<p>

760

<uri link="http://alphalinux.org/">AlphaLinux.org</uri> is a central repository

761

for all things Alpha/Linux.

762

</p>

763

764

</body>

765

</section>

766

</chapter>

767

</guide>

--

772

gentoo-doc-cvs@g.o mailing list

Gentoo Archives: gentoo-doc-cvs