DOCSLIB.ORG

Freebsd 2.X、3.X、4.X についての

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Freebsd 2.X、3.X、4.X についての FreeBSD 2.X、3.X、4.X についての FAQ (よくある質問とその答え) FreeBSD 2.X、3.X、4.X についての FAQ (よくある質問とその答え) 改訂: 8def749c53 製作著作 © 1995, 1996, 1997, 1998, 1999, 2000, 2001 FreeBSD ドキュメンテーションプロジェクト 概要 この文書は FreeBSD システム・バージョン 2.X、3.X、4.X についての FAQ です。 特に断わりがない 限り、どの項目も FreeBSD 2.0.5 以降のものを想定しています。 <XXX> のついている項目はまだ作業 中のものです。 この FreeBSD ドキュメンテーションプロジェクトに協力したいと思われる方は、 FreeBSD documentation project メーリングリスト まで (英語で) 電子メールを送ってください。 この文書の最新 バージョンは、いつでも 日本国内版 FreeBSD World Wide Web サーバや FreeBSD World Wide Web サーバで 見ることができます。 また、ひとつの巨大な HTML ファイルとして HTTP でダウンロードすることも できます。 プレーンテキスト、PostScript、PDF、およびその他の形式のものは FreeBSD FTP サーバに置 かれています。 また、FAQ の検索も可能です。 注記 2005 年 6 月現在、HTML 版以外の日本語 FAQ は用意されていません。 日本語版の作成は FreeBSD 日本語ドキュメンテーションプロジェクトが オリジナルの英語版をもとにし て行なっています。 FreeBSD FAQ 日本語訳および、 FreeBSD FAQ 日本語版のみに関連すること は、 日本語ドキュメンテーションプロジェクト <[email protected] > において日本語で議論されてい ます。 必要に応じて日本語ドキュメンテーションプロジェクトから、 FreeBSD Documentation Project に対してフィードバックを行ないますので、 英語が得意でない方は 日本語ドキュメンテーションプロジェクト <[email protected] > まで日本語でコメントをお寄せください。 また、この FreeBSD FAQ とは別に、日本の FreeBSD ユーザ有志によって FreeBSD users-jp メーリン グリスト <[email protected] > やニュースグループ fj.os.bsd.freebsd などへの投稿をもと に作成された QandA が公開されています。 特に日本語環境など日本固有の話題が充実していますので、 こちらも合わせてご覧ください。 Copyright Redistribution and use in source (XML DocBook) and 'compiled' forms (XML, HTML, PDF, PostScript, RTF and so forth) with or without modification, are permitted provided that the following conditions are met: 1. Redistributions of source code (XML DocBook) must retain the above copyright notice, this list of conditions and the following disclaimer as the first lines of this file unmodified. 2. Redistributions in compiled form (transformed to other DTDs, converted to PDF, PostScript, RTF and other formats) must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. 重要 THIS DOCUMENTATION IS PROVIDED BY THE FREEBSD DOCUMENTATION PROJECT "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A ii PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE FREEBSD DOCUMENTATION PROJECT BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS DOCUMENTATION, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. iii 目次 まえがき ................................................................................................................................... xi 1. インストール .......................................................................................................................... 1 2. ハードウェアコンパチビリティ ................................................................................................... 13 3. トラブルシューティング .......................................................................................................... 23 4. 商用アプリケーション ............................................................................................................ 35 5. ユーザアプリケーション .......................................................................................................... 39 6. カーネルコンフィグレーション .................................................................................................. 43 7. システム管理 ....................................................................................................................... 45 8. X Window System と仮想コンソール ..................................................................................... 65 9. ネットワーキング ................................................................................................................... 75 10. PPP ................................................................................................................................ 83 11. シリアル接続 ..................................................................................................................... 95 12. その他の質問 .................................................................................................................. 101 13. まじめな FreeBSD ハッカーだけの話題 ................................................................................ 109 14. 謝辞 .............................................................................................................................. 117 15. FreeBSD FAQ 日本語化について ..................................................................................... 119 有用な書籍 ........................................................................................................................... 121 表の一覧 1.1. ネットワーク接続用のパラレルケーブルの結線 ............................................................................ 6 1.2. 最大ファイルサイズ .............................................................................................................. 9 1.3. 指定できるセキュリティプロファイル ....................................................................................... 11 例の一覧 8.1. moused による変換を利用してホイールマウスを 使用するための XFree86 3.3.x 系列の XF86Config の 「Pointer」 セクションの設定例 ............................................................................ 66 8.2. 自動的なプロトコル認識機能およびボタン配置変換機能を 利用し、ホイールマウスを使用するための XFree86 4.x 系列の XF86Config の 「InputDevice」 セクションの設定例 ....................................... 66 8.3. ホイールマウスで Emacs 上でのページスクロールを 行うための 「.emacs」 の設定例 ..................... 66 8.4. X サーバによる変換を利用してホイールマウスを使用するための XF86Config の 「Pointer」 セク ションの設定例 ........................................................................................................................ 67 8.5. Imwheel を利用するための Emacs の設定例 ....................................................................... 67 8.6. Imwheel を利用するための XEmacs の設定例 ..................................................................... 68 まえがき 訳: 栗山 淳 <[email protected] >、 花井 浩之 <[email protected] >、 中井 幸 博 <[email protected] >、 今野 元之 <[email protected] >、 杉村 貴士 <[email protected] >、 1997 年 11 月 5 日 FreeBSD 2.X-4.X FAQ へようこそ! Usenet の FAQ がそうであるように、 この文書も FreeBSD オペレーティングシステムに関して 頻繁に尋ねられ る質問を網羅することを目的としています (もちろんそれに対する答えも!)。 FAQ は本来バンド幅を減らし、 同じ質 問が何度も繰り返されるのを避けるために作られたものですが、 最近は有用な情報源と見なされるようになってき ました。 この FAQ をできる限り有用なものにしようと、 あらゆる努力がはらわれています。 もし何かしらの改善案が浮かん だら、ぜひ FAQ 保守担当者 <[email protected] > までメールを送ってください。 問： FreeBSD って何? 答： FreeBSD とは一言で言えば、カリフォルニア大学バークレイ校から リリースされた 「4.4BSD-Lite」 と 「4.4BSD-Lite2」 による 強化の一部に由来する、 i386 および Alpha/AXP 系のプラットフォーム向けの UN*X ライクなオペレーティングシステムです。 間接的には同じバークレイ校の 「Net/2」 を William Jolitz が i386 系に移植した 「386BSD」 も基にしていますが、 386BSD のコードはほとんど残っていません。 FreeBSD についての詳細と、何ができるかについては FreeBSD のホームページ を参照してください。 FreeBSD は企業やインターネットサービスプロバイダ、研究者、 コンピュータ専門家、学生、家庭のユーザ などにより、業務や教育、 娯楽に用いられています。これらに関しては FreeBSD ギャラリーをご覧ください。 FreeBSD に関するより詳しい情報は FreeBSD ハンドブックを参照してください。 問： FreeBSD が目指しているもの 答： FreeBSD プロジェクトの目的は、 いかなる用途にも使用でき、 何ら制限のないソフトウェアを供給するこ とです。 私たちの多くは、 コード (そしてプロジェクト) に対してかなりの投資をしてきており、 これからも多 少の代償はあっても投資を続けて行くつもりです。 ただ、他の人達にも同じような負担をするように主張して いるわけではありません。 FreeBSD に興味を持っている一人残らずすべての人々に、 目的を限定しないで コードを提供すること。 これが、 私たちの最初のそして最大の「任務」であると信じています。 そうすれば、 コードは可能な限り広く使われ、 最大の恩恵をもたらすことができるでしょう。 これが、私たちが熱烈に支持 しているフリーソフトウェアの最も基本的な目的であると、 私は信じています。 私たちのソースツリーに含まれるソースのうち、GNU 一般公有使用許諾 (GPL) または GNU ライブラ リ 一般公有使用許諾 (LGPL) に従っているものについては、 多少制限が科されています。ただし、 ソース コードへのアクセスの保証という、 一般の制限とはいわば逆の制限です。 ただし GPL ソフトウェアを商用 で利用する場合、 さらに複雑になるのは避けられません。 そのため、それらのソフトウェアを、より制限の少な い BSD 著作権に従ったソフトウェアで置き換える努力を、 可能な限り日々続けています。 訳注 GPL では、「ソースコードを実際に受け取るか、 あるいは希望しさえすればそれを入 手することが可能であること」を求めています。 問： どうして FreeBSD と呼ばれているのですか? 答： • 無料 (free) で使うことができる (商利用も含む)。 • オペレーティングシステムの完全なソースコードが自由 (freely) に手に入り、 商利用・非商利用にかかわ らず、最低限の制限で他の仕事への利用、配布、導入が可能。 • 改良やバグフィックスがある場合、 誰でも (free) そのコードを提出でき、 ソースツリーに加えることができ ます (いくつかの簡単な条件には従ってもらいます)。 母国語が英語でない読者のために、ここでは 「free」 という単語が二つの意味で用いられていることを指 摘しておくと分かりやすいかも知れません。 ひとつは「無料である」ということ、 もうひとつは「自分のやりた いようにできる」ということです。 FreeBSD のコードでできないいくつかのこと (自分が書いたものだと偽る など) を除けば、 あなたは自分のやりたいことをやることが可能なのです。 問： FreeBSD の最新バージョンは? 答： 4.3 が最新の STABLE バージョンで、 2001 年 4 月にリリースされました。 また、これは最新の RELEASE バージョンでもあります。 簡単に言ってしまうと、-STABLE は最新の -CURRENT のスナップショットのすばらしい新機能の数々より も、 安定性と変更回数の少なさを好む ISP や、 他の企業のユーザをターゲットにしています。 リリースは この二種類のブランチで行なわれますが、 (-STABLE と比較すると多少) 不安定な動作があるということを 許容できるなら、 必要となるのは -CURRENT の方だけでしょう。 各リリースは 数カ月毎にしか行なわれません。 多くの人々が FreeBSD のソースをそのリリースよりも 最新 の状態に維持している (FreeBSD-current と FreeBSD-stable に関する質問も参照してください) のです が、 ソースというのは常に改変され続けているため、 そうすることは一種の慣例になっています。 問： FreeBSD-CURRENTって何? 答： FreeBSD-CURRENT はオペレーティングシステムの開発バージョンで、 やがて 5.0-RELEASE となりま す。よってこれは、そこに携わっている開発者や、 どんな障害をも乗り越えていけるタフな愛好家たちにとっ てのみ興味の対象となるものです。 -CURRENT の使用に際しての詳細は FreeBSD ハンドブック の 関連 するセクション を参照してください。 オペレーティングシステムに馴染みがない場合や、 それが一時的に発生している問題なのか、 それと も本質的な問題かを見極める能力がない場合は、 FreeBSD-CURRENT を使うべきではありません。 このブランチは時々急激に拡張されたり、 システムが構築できない状態になることもしょっちゅうあります。 FreeBSD-CURRENT を使う人は問題を分析し、 「小さな欠陥」ではなく、 明らかに間違いであると思われ るものだけを報告できるものと想定されています。 「make world したら group 関係でエラーがでました」 のような質問は、 -CURRENT メーリングリストでは軽蔑の眼差しであしらわれることもあります。 毎日、その時点の -CURRENT と -STABLE のコードを元に snapshot が作成されています。 現在は、そ の snapshot の配布も利用可能です。 それぞれの snapshot には以下のような目的があります。 • インストールプログラムの最新版のテスト。 • 試してみたいけれど、 基礎的な所から毎日変わるようなものを追いかける時間もバンド幅も無い、 という 人にも -CURRENT や -STABLE を使えるようにする。 また、そのような人たちのシステム移行のための 手っ取り早い方法を提供する。 • あとでとんでもないことをしてしまった時のために、 問題となるコードの特定の参照基準点を保存してお く。 (通常は CVS がこういうハプニングのような恐ろしい事態を防止して いるんですけどね :) • テストが必要な新しい機能を、 できる限り多くの隠れテスターに試してもらう。 どんな目的であれ、-CURRENT snapshot が 「製品レベルの品質」 であるとの考えに基づく要求は行わな
Load more

Recommended publications
  • Advanced Integration
    ZFS: Advanced Integration Allan Jude -- [email protected] @allanjude Introduction: Allan Jude • 16 Years as FreeBSD Server Admin • FreeBSD src/doc committer (ZFS, installer, boot loader, GELI, bhyve, libucl, libxo) • FreeBSD Core Team (July 2016 - 2018) • Co-Author of “FreeBSD Mastery: ZFS” and “FreeBSD Mastery: Advanced ZFS” with Michael W. Lucas • Architect of the ScaleEngine CDN (HTTP and Video) • Host of weekly BSDNow.tv Podcast • Personally Responsible for 1000 TB of ZFS Storage ZFS: What Is It? • ZFS is a filesystem with a built in volume manager (combine multiple disks into a pool) • Space from the pool is thin-provisioned to multiple filesystems or block volumes (zvols) • All data and metadata is checksummed • Optional transparent compression • Copy-on-Write with snapshots and clones • Each filesystem is tunable with properties Snapshots and Clones • Copy-on-Write means snapshots are instant • Blocks referenced by a snapshot kept when they are removed from the live filesystem • Snapshots allows you to access the file- system as it was when snapshot was taken • No performance impact on reads/writes • Take no additional space until blocks change • Clones allow you to “fork” a filesystem Boot Environments • If the root filesystem is on ZFS, you can snapshot before an upgrade, then clone it • You now have 2 filesystems, one before the upgrade, and one after. Only takes the space of blocks that changed • FreeBSD boot loader allows you to select which one to use from a menu • Upgrade without fear, can always rollback Boot Environment Tooling • Existing tool: sysadmin/beadm • GSoC 2017: be(8) and libbe(3) • New tool supports better management of filesystem properties for boot integration • New tool will support “deep” boot environments.
    [Show full text]
  • The Release Engineering of Freebsd 4.4
    The Release Engineering of FreeBSD 4.4 Murray Stokely [email protected] Wind River Systems Abstract different pace, and with the general assumption that they This paper describes the approach used by the FreeBSD re- have first gone into FreeBSD-CURRENT and have been lease engineering team to make production-quality releases thoroughly tested by our user community. of the FreeBSD operating system. It details the methodol- In the interim period between releases, nightly snap- ogy used for the release of FreeBSD 4.4 and describes the shots are built automatically by the FreeBSD Project build tools available for those interested in producing customized machines and made available for download from ftp: FreeBSD releases for corporate rollouts or commercial pro- //stable.FreeBSD.org. The widespread availabil- ductization. ity of binary release snapshots, and the tendency of our user community to keep up with -STABLE development with CVSup and “make world”[8] helps to keep FreeBSD- 1 Introduction STABLE in a very reliable condition even before the qual- ity assurance activities ramp up pending a major release. The development of FreeBSD is a very open process. Bug reports and feature requests are continuously sub- FreeBSD is comprised of contributions from thousands of mitted by users throughout the release cycle. Problem people around the world. The FreeBSD Project provides reports are entered into our GNATS[9] database through anonymous CVS[1] access to the general public so that email, the send-pr(1) application, or via a web-based form. others can have access to log messages, diffs between de- In addition to the multitude of different technical mailing velopment branches, and other productivity enhancements lists about FreeBSD, the FreeBSD quality-assurance mail- that formal source code management provides.
    [Show full text]
  • Sun Storagetek 5320 NAS Appliance and Gateway Administration Guide
    Sun StorageTek™ 5320 NAS Appliance and Gateway Administration Guide NAS Software Version 4.12 Sun Microsystems, Inc. www.sun.com Part No. 819-6388-10 May 2006, Revision A Submit comments about this document at: http://www.sun.com/hwdocs/feedback Copyright 2006 Sun Microsystems, Inc., 4150 Network Circle, Santa Clara, California 95054, U.S.A. All rights reserved. Sun Microsystems, Inc. has intellectual property rights relating to technology that is described in this document. In particular, and without limitation, these intellectual property rights may include one or more of the U.S. patents listed at http://www.sun.com/patents and one or more additional patents or pending patent applications in the U.S. and in other countries. This document and the product to which it pertains are distributed under licenses restricting their use, copying, distribution, and decompilation. No part of the product or of this document may be reproduced in any form by any means without prior written authorization of Sun and its licensors, if any. Third-party software, including font technology, is copyrighted and licensed from Sun suppliers. Parts of the product may be derived from Berkeley BSD systems, licensed from the University of California. UNIX is a registered trademark in the U.S. and in other countries, exclusively licensed through X/Open Company, Ltd. Sun, Sun Microsystems, the Sun logo, Java, AnswerBook2, docs.sun.com, Sun StorEdge, Sun StorageTek, Java, and Solaris are trademarks or registered trademarks of Sun Microsystems, Inc. in the U.S. and in other countries. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc.
    [Show full text]
  • Freebsd Handbook
    FreeBSD Handbook http://www.freebsd.org/doc/en_US.ISO8859-1/books/han... FreeBSD Handbook The FreeBSD Documentation Project Copyright © 1995, 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010, 2011, 2012, 2013 The FreeBSD Documentation Project Welcome to FreeBSD! This handbook covers the installation and day to day use of FreeBSD 8.3-RELEASE and FreeBSD 9.1-RELEASE. This manual is a work in progress and is the work of many individuals. As such, some sections may become dated and require updating. If you are interested in helping out with this project, send email to the FreeBSD documentation project mailing list. The latest version of this document is always available from the FreeBSD web site (previous versions of this handbook can be obtained from http://docs.FreeBSD.org/doc/). It may also be downloaded in a variety of formats and compression options from the FreeBSD FTP server or one of the numerous mirror sites. If you would prefer to have a hard copy of the handbook, you can purchase one at the FreeBSD Mall. You may also want to search the handbook. REDISTRIBUTION AND USE IN SOURCE (XML DOCBOOK) AND 'COMPILED' FORMS (XML, HTML, PDF, POSTSCRIPT, RTF AND SO FORTH) WITH OR WITHOUT MODIFICATION, ARE PERMITTED PROVIDED THAT THE FOLLOWING CONDITIONS ARE MET: 1. REDISTRIBUTIONS OF SOURCE CODE (XML DOCBOOK) MUST RETAIN THE ABOVE COPYRIGHT NOTICE, THIS LIST OF CONDITIONS AND THE FOLLOWING DISCLAIMER AS THE FIRST LINES OF THIS FILE UNMODIFIED. 2. REDISTRIBUTIONS IN COMPILED FORM (TRANSFORMED TO OTHER DTDS, CONVERTED TO PDF, POSTSCRIPT, RTF AND OTHER FORMATS) MUST REPRODUCE THE ABOVE COPYRIGHT NOTICE, THIS LIST OF CONDITIONS AND THE FOLLOWING DISCLAIMER IN THE DOCUMENTATION AND/OR OTHER MATERIALS PROVIDED WITH THE DISTRIBUTION.
    [Show full text]
  • Tuesday October 20: a Guide to Event-Driven SRE-Inspired Devops 16:55 GMT-3 / 15:55 GMT -4 / 14:55 GMT -5 / 12:55 GMT -7
    Buenos Aires, Arg.: GMT -3, ART New York, USA., Toronto and Montreal, Ca.: EDT, GMT -4 Texas, USA., Winnipeg, Ca.: CDT, GMT -5 California, USA., Vancouver, Ca: PDT, GMT -7 Twitter: @nerdearla Website: https://nerdear.la/en/ ​ Schedule (in spanish with Argentine GMT -3 timezone): https://nerdear.la/agenda/ ​ How to register? See at the end of this document for a step by step guide. Tuesday October 20: A Guide to Event-driven SRE-inspired DevOps 16:55 GMT-3 / 15:55 GMT -4 / 14:55 GMT -5 / 12:55 GMT -7 We have broken our monoliths into event-driven microservice architectures! Yet, many of us are still using old monolithic pipeline approaches to delivery & operations. Let me show you a modern open source event-driven approach to delivery & operations with the safety net of SRE! By Andreas Grabner — DevOps Activist FreeBSD: Code, Community and Collaboration 17:55 GMT-3 / 16:55 GMT -4 / 15:55 GMT -5 / 13:55 GMT -7 The FreeBSD Open Source Operating System is one of the oldest, largest, and most successful open source projects, with a long history of innovation. FreeBSD descended from Berkeley Unix back in the early ’90s, with its lineage dating back 50 years to the original UNIX. It’s known for its reliability, stability, and advanced networking and performance. Deb will take you through its long history and highlight some of the features that set FreeBSD apart from other operating systems. She’ll describe how the FreeBSD Project works and how you can contribute to the Project. She will point out some of the differences between FreeBSD and Linux, and share why individuals and companies use FreeBSD.
    [Show full text]
  • Personal Homepages at ETH
    Personal Homepages at ETH ETH students and employees own a space for a personal homepage. This homepage is available at http://n.ethz.ch/~<loginname>/ (The same homepage is also available via https.) 1.1 Access The files of this personal homepage are stored on the general home directory provided by ETH, which might be different from the home directory provided by your institute. 1.1.1 Access for Linux and Mac OS X To access the homepage, you can connect to your ETH home directory using the smb protocol. The server location and path to your home directory are: smb://d.ethz.ch/users/all/<username> Please provide your login credentials to connect to the server. 1.1.2 Access for Windows Windows users can connect using the following address: \\d.ethz.ch\users\all\<username>\ The home directory can be mapped to a drive letter. This process is richly documented od 3rd party websites (https://www.google.com/search?client=firefox-b-d&q=win- dows+map+network+drive). 1.2 Access via ssh / putty If you prefer to work with a command-line tool, you can access your homepage files by ssh-ing to slab1.ethz.ch providing your username and password. Then, navigate to the subfolder homepage to edit the existing files (read on below). 1.3 Files in your homepage folder When connected to the ETH home directory via smb or as network drive, there is a folder called “homepage”. All the usual web-files placed in this folder will be world-wide available via the URL mentioned before http://n.ethz.ch/~<loginname> Please do not change the name of the file index.html.
    [Show full text]
  • DN Print Magazine BSD News BSD Mall BSD Support Source Wars Join Us
    Mirrors Primary (US) Issues August 2001 August 2001 Get BSD Contact Us Search BSD FAQ New to BSD? DN Print Magazine BSD News BSD Mall BSD Support Source Wars Join Us T H I S M O N T H ' S F E A T U R E S From the Editor The Effects of Tuning a FreeBSD Box for High Open Packages Reaches Performance Milestone 2 by Gilbert Gong by Chris Coleman Each BSD project has its A stock FreeBSD installation delivers a system which is own 3rd party software designed to meet the needs of most users, and strives to packaging system. They are provide the best balance of safety, reliablity, and all based on the same code, performance in a multi-user environment. It is therefore not yet, each of them have optimized for use as a high performance dedicated network features that make one server. This article investigates the effect of tuning a better than the other. Open FreeBSD for use as a dedicated network server. Read More Packages is a volunteer project to unify that code base and incorporate the best features of each. The NetBSD rc.d system by Will Andrews Get BSD Stuff There's been a lot of hubbub the last few months about NetBSD's new rc.d system being the successor of 4.4BSD's. At the USENIX Annual Technical Conference 2001 in Boston, MA, I had the pleasure of sitting down to listen to Luke Mewburn of Wasabi Systems discuss the new rc system NetBSD introduced in their operating system in the 1.5 release earlier this year.
    [Show full text]
  • Freebsd Release Engineering
    FreeBSD Release Engineering Murray Stokely <[email protected]> FreeBSD is a registered trademark of the FreeBSD Foundation. Intel, Celeron, Centrino, Core, EtherExpress, i386, i486, Itanium, Pentium, and Xeon are trade- marks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries. Many of the designations used by manufacturers and sellers to distinguish their products are claimed as trademarks. Where those designations appear in this document, and the FreeBSD Project was aware of the trademark claim, the designations have been followed by the “™” or the “®” symbol. 2018-06-12 18:54:46 +0000 by Benedict Reuschling. Abstract Note This document is outdated and does not accurately describe the current release procedures of the FreeBSD Release Engineering team. It is re- tained for historical purposes. The current procedures used by the Free- BSD Release Engineering team are available in the FreeBSD Release Engi- neering article. This paper describes the approach used by the FreeBSD release engineering team to make pro- duction quality releases of the FreeBSD Operating System. It details the methodology used for the official FreeBSD releases and describes the tools available for those interested in produc- ing customized FreeBSD releases for corporate rollouts or commercial productization. Table of Contents 1. Introduction ........................................................................................................................... 1 2. Release Process ......................................................................................................................
    [Show full text]
  • The Complete Solutions Guide for Every Linux/Windows System Administrator!
    Integrating Linux and Windows Integrating Linux and Windows By Mike McCune Publisher : Prentice Hall PTR Pub Date : December 19, 2000 ISBN : 0-13-030670-3 • Pages : 416 The complete solutions guide for every Linux/Windows system administrator! This complete Linux/Windows integration guide offers detailed coverage of dual- boot issues, data compatibility, and networking. It also handles topics such as implementing Samba file/print services for Windows workstations and providing cross-platform database access. Running Linux and Windows in the same environment? Here's the comprehensive, up-to-the-minute solutions guide you've been searching for! In Integrating Linux and Windows, top consultant Mike McCune brings together hundreds of solutions for the problems that Linux/Windows system administrators encounter most often. McCune focuses on the critical interoperability issues real businesses face: networking, program/data compatibility, dual-boot systems, and more. You'll discover exactly how to: Use Samba and Linux to deliver high-performance, low-cost file and print services to Windows workstations Compare and implement the best Linux/Windows connectivity techniques: NFS, FTP, remote commands, secure shell, telnet, and more Provide reliable data exchange between Microsoft Office and StarOffice for Linux Provide high-performance cross-platform database access via ODBC Make the most of platform-independent, browser-based applications Manage Linux and Windows on the same workstation: boot managers, partitioning, compressed drives, file systems, and more. For anyone running both Linux and Windows, McCune delivers honest and objective explanations of all your integration options, plus realistic, proven solutions you won't find anywhere else. Integrating Linux and Windows will help you keep your users happy, your costs under control, and your sanity intact! 1 Integrating Linux and Windows 2 Integrating Linux and Windows Library of Congress Cataloging-in-Publication Data McCune, Mike.
    [Show full text]
  • IRIX® 6.5.17 Update Guide
    IRIX® 6.5.17 Update Guide 1600 Amphitheatre Pkwy. Mountain View, CA 94043-1351 Telephone (650) 960-1980 FAX (650) 961-0595 August 2002 Dear Valued Customer, SGI® is pleased to present the new IRIX® 6.5.17 maintenance and feature release. Starting with IRIX® 6.5, SGI created a new software upgrade strategy, which delivers both the maintenance (6.5.17m) and feature (6.5.17f) streams. This upgrade is part of a family of releases that periodically enhances IRIX 6.5. There are several benefits to this release strategy: it provides periodic fixes to IRIX, it assists in managing upgrades, and it supports all platforms. Additional information on this strategy and how it affects you is included in the updated Installation Instructions manual contained in this package. If you need assistance, please visit the Supportfolio™ online website at http://support.sgi.com or contact your local support provider. In conjunction with the release of IRIX® 6.5.15, SGI added to the existing life cycle management categories the Limited Support Mode that customizes services we deliver to our users. This new support mode is targeted for open source products. We now offer eight modes of service 2 for software supported by SGI: Active, Maintenance, Limited, Legacy, Courtesy, Divested, Retired, and Expired. Active Mode is our highest level of service. It applies to products that are being actively developed and maintained and are orderable through general distribution. Software fixes for all levels of problems can be expected. Maintenance Mode software is maintained and is still an important part of our product mix.
    [Show full text]
  • Freebsd VS. Linux: ZFS by ALLAN JUDE
    SEE TEXT ONLY FreeBSD VS. Linux: ZFS BY ALLAN JUDE Why Use ZFS? It is not that other filesystems are bad; they just make the mistake of trusting your storage hardware to return your data when you ask for it. As it turns out, hard drives are pretty good at that, but pretty good is often not good enough. ZFS is the only open-source, OpenZFS is available on many plat- production-quality filesystem that can not only forms, including FreeBSD and Solaris detect but correct the errors when a disk derivatives like IllumOS, as well as Mac returns incorrect data. By combining the roles of filesystem and volume manager, ZFS is also OS X and Linux. However, not all of the able to ensure your data is safe, even in the functionality is available on the latter absence of one or more disks, depending on platforms. The FreeBSD Project has fully your configuration. ZFS doesn’t trust your adopted ZFS, putting significant effort hardware; it verifies that the correct data was into integrating it with the system and returned from each read from the disk. The primary design consideration for ZFS is management tools to make ZFS a seam- the safety of the data. Every block that is writ- less part of the OS, rather than a bolt- ten to the filesystem is accompanied by a ed-on extra. OpenZFS is better inte- checksum of the data, stored with the other grated, instrumented, and documented metadata. That metadata block also has a on FreeBSD than on any of the various checksum, as does its parent, all the way up to the top-level block, called the uber block.
    [Show full text]
  • Security Scanning a Jail by BENEDICT REUSCHLING
    1 of 3 PRACTICAL Security Scanning a Jail BY BENEDICT REUSCHLING This column covers ports and packages for FreeBSD that are useful in some way, peculiar, or otherwise good to know about. Ports extend the base OS functionality and make sure you get something done or, simply, put a smile on your face. Come along for the ride, maybe you’ll find something new. n this installment, I stray a bit from presenting a bouquet of ports and just focus on a single one: security/lynis. Lynis is a tool for security auditing, hardening, and compliance testing. What lynis does dif- ferently from other security scanners is that it tries to detect available components on a sys- Item such as a webserver or database. Once it finds them, it checks them further for vulnerabil- ities, missing patches, etc. This way, the scans are different on each system based on the configured software and purpose. For example, your firewall Available as open host may receive different examinations than your backup server. Plugins extend lynis’s functionality to source as well as a cover specific software. A comprehensive security commercial enterprise report is generated at the end, eliciting either a pat on the back from your security-minded superiors or tool, lynis scans a range your next security sensitivity training. Available as open source as well as a commer- of operating systems for cial enterprise tool, it scans a range of operating systems for security anomalies. Sysadmins as well security anomalies. as penetration testers, developers, and auditors can use it to assess if there are any vulnerabilities, not only in installed software but also in their configurations.
    [Show full text]