'linux/temp'에 해당되는 글 9건

  1. 2007.04.30 getting start docbook
  2. 2007.03.16 /etc/yum.conf
  3. 2007.03.16 /etc/yum.repos.d/CentOS-Base.repo
  4. 2007.03.16 kernel 2.6.18.4 compile error
  5. 2007.03.16 Geexbox Manual Installation

getting start docbook

linux/temp 2007. 4. 30. 17:45
닥북 홈 http://docbook.org
닥북위키  http://wiki.docbook.org/topic/DocBookTutorials#head-9fa4b6025a5fbd3d559cf3345ed08ca874b0ac14
닥북으로 글쓰기  http://kldp.org/KoreanDoc/html/Using_Docbook-KLDP/preparingtransform.html
닥북 미니하우투 http://kldp.org/KoreanDoc/html/DocBook_Install-KLDP/
xml - naver 블로거 http://blog.naver.com/kimsok845?Redirect=Log&logNo=150016222315

################## docbook.dtd #####################
<!-- ...................................................................... -->
<!-- DocBook XML DTD V4.1.2 ................................................. -->
<!-- File docbookx.dtd .................................................... -->

<!-- Copyright 1992-2000 HaL Computer Systems, Inc.,
     O'Reilly & Associates, Inc., ArborText, Inc., Fujitsu Software
     Corporation, Norman Walsh, and the Organization for the Advancement
     of Structured Information Standards (OASIS).

     $Id: docbookx.dtd,v 1.12 2000/08/27 15:15:26 nwalsh Exp $

     Permission to use, copy, modify and distribute the DocBook XML DTD
     and its accompanying documentation for any purpose and without fee
     is hereby granted in perpetuity, provided that the above copyright
     notice and this paragraph appear in all copies.  The copyright
     holders make no representation about the suitability of the DTD for
     any purpose.  It is provided "as is" without expressed or implied
     warranty.

     If you modify the DocBook DTD in any way, except for declaring and
     referencing additional sets of general entities and declaring
     additional notations, label your DTD as a variant of DocBook.  See
     the maintenance documentation for more information.

     Please direct all questions, bug reports, or suggestions for 
     changes to the docbook@lists.oasis-open.org mailing list. For more
     information, see http://www.oasis-open.org/docbook/.
-->

<!-- ...................................................................... -->

<!-- This is the driver file for V4.1.2 of the DocBook DTD.
     Please use the following formal public identifier to identify it:

     "-//OASIS//DTD DocBook XML V4.1.2//EN"

     For example, if your document's top-level element is Book, and
     you are using DocBook directly, use the FPI in the DOCTYPE
     declaration:

     <!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.1.2//EN"
                    "http://www.oasis-open.org/docbook/xml/4.0/docbookx.dtd"
                    [...]>

     Or, if you have a higher-level driver file that customizes DocBook,
     use the FPI in the parameter entity declaration:

     <!ENTITY % DocBookDTD PUBLIC "-//OASIS//DTD DocBook XML V4.1.2//EN"
                "http://www.oasis-open.org/docbook/xml/4.0/docbookx.dtd">
     %DocBookDTD;

     See the documentation for detailed information on the parameter
     entity and module scheme used in DocBook, customizing DocBook and
     planning for interchange, and changes made since the last release
     of DocBook.
-->

<!-- ...................................................................... -->
<!-- Notation declarations ................................................ -->

<!ENTITY % dbnotn.module "INCLUDE">
<![%dbnotn.module;[
<!ENTITY % dbnotn PUBLIC 
"-//OASIS//ENTITIES DocBook XML Notations V4.1.2//EN"
"dbnotnx.mod">
%dbnotn;
]]>

<!-- ...................................................................... -->
<!-- ISO character entity sets ............................................ -->

<!ENTITY % dbcent.module "INCLUDE">
<![%dbcent.module;[
<!ENTITY euro "&#x20AC;"><!-- euro sign, U+20AC NEW -->
<!ENTITY % dbcent PUBLIC 
"-//OASIS//ENTITIES DocBook XML Character Entities V4.1.2//EN"
"dbcentx.mod">
%dbcent;
]]>

<!-- ...................................................................... -->
<!-- DTD modules .......................................................... -->

<!-- Information pool .............. -->

<!ENTITY % dbpool.module "INCLUDE">
<![ %dbpool.module; [
<!ENTITY % dbpool PUBLIC 
"-//OASIS//ELEMENTS DocBook XML Information Pool V4.1.2//EN"
"dbpoolx.mod">
%dbpool;
]]>

<!-- Redeclaration placeholder ..... -->

<!ENTITY % intermod.redecl.module "IGNORE">
<![%intermod.redecl.module;[
<!-- Defining rdbmods here makes some buggy XML parsers happy. -->
<!ENTITY % rdbmods "">
%rdbmods;
<!--end of intermod.redecl.module-->]]>

<!-- Document hierarchy ............ -->

<!ENTITY % dbhier.module "INCLUDE">
<![ %dbhier.module; [
<!ENTITY % dbhier PUBLIC 
"-//OASIS//ELEMENTS DocBook XML Document Hierarchy V4.1.2//EN"
"dbhierx.mod">
%dbhier;
]]>

<!-- ...................................................................... -->
<!-- Other general entities ............................................... -->

<!ENTITY % dbgenent.module "INCLUDE">
<![ %dbgenent.module; [
<!ENTITY % dbgenent PUBLIC
"-//OASIS//ENTITIES DocBook XML Additional General Entities V4.1.2//EN"
"dbgenent.mod">
%dbgenent;
]]>

<!-- End of DocBook XML DTD V4.1.2 .......................................... -->
<!-- ...................................................................... -->

'linux > temp' 카테고리의 다른 글

/etc/yum.conf  (0) 2007.03.16
/etc/yum.repos.d/CentOS-Base.repo  (0) 2007.03.16
kernel 2.6.18.4 compile error  (0) 2007.03.16
Geexbox Manual Installation  (0) 2007.03.16
web terminal connection error - mind term  (0) 2007.03.15
Posted by efrit
,

/etc/yum.conf

linux/temp 2007. 3. 16. 14:51
[main]
cachedir=/var/cache/yum
debuglevel=2
logfile=/var/log/yum.log
pkgpolicy=newest
distroverpkg=centos-release
tolerant=1
exactarch=1
retries=20
obsoletes=1
gpgcheck=1

# PUT YOUR REPOS HERE OR IN separate files named file.repo
# in /etc/yum.repos.d

'linux > temp' 카테고리의 다른 글

getting start docbook  (0) 2007.04.30
/etc/yum.repos.d/CentOS-Base.repo  (0) 2007.03.16
kernel 2.6.18.4 compile error  (0) 2007.03.16
Geexbox Manual Installation  (0) 2007.03.16
web terminal connection error - mind term  (0) 2007.03.15
Posted by efrit
,
[base]
name=CentOS-$releasever - Base
baseurl=http://mirror.centos.org/centos/$releasever/os/$basearch/
gpgcheck=1
gpgkey=http://mirror.centos.org/centos/RPM-GPG-KEY-centos4

#released updates
[update]
name=CentOS-$releasever - Updates
baseurl=http://mirror.centos.org/centos/$releasever/updates/$basearch/
gpgcheck=1
gpgkey=http://mirror.centos.org/centos/RPM-GPG-KEY-centos4

#packages used/produced in the build but not released
[addons]
name=CentOS-$releasever - Addons
baseurl=http://mirror.centos.org/centos/$releasever/addons/$basearch/
gpgcheck=1
gpgkey=http://mirror.centos.org/centos/RPM-GPG-KEY-centos4

#additional packages that may be useful
[extras]
name=CentOS-$releasever - Extras
baseurl=http://mirror.centos.org/centos/$releasever/extras/$basearch/
gpgcheck=1
gpgkey=http://mirror.centos.org/centos/RPM-GPG-KEY-centos4

#additional packages that extend functionality of existing packages
[centosplus]
name=CentOS-$releasever - Plus
baseurl=http://mirror.centos.org/centos/$releasever/centosplus/$basearch/
gpgcheck=1
enabled=0
gpgkey=http://mirror.centos.org/centos/RPM-GPG-KEY-centos4

#contrib - packages by Centos Users
[contrib]
name=CentOS-$releasever - Contrib
baseurl=http://mirror.centos.org/centos/$releasever/contrib/$basearch/
gpgcheck=1
enabled=0
gpgkey=http://mirror.centos.org/centos/RPM-GPG-KEY-centos4

#packages in testing
[testing]
name=CentOS-$releasever - Testing
baseurl=http://mirror.centos.org/centos/$releasever/testing/$basearch/
gpgcheck=1
enabled=0
gpgkey=http://mirror.centos.org/centos/RPM-GPG-KEY-centos4

'linux > temp' 카테고리의 다른 글

getting start docbook  (0) 2007.04.30
/etc/yum.conf  (0) 2007.03.16
kernel 2.6.18.4 compile error  (0) 2007.03.16
Geexbox Manual Installation  (0) 2007.03.16
web terminal connection error - mind term  (0) 2007.03.15
Posted by efrit
,
intel_rng: FWH not detected
Enforcing mode requested but no policy loaded. Halting now.
kernel panic not syncing : Attemped to kill init


1. intel_rng : FWH not deteced
http://www.linuxquestions.org/questions/showthread.php?t=525184

when I reboot I get the message:
Uncompressing Linux... Ok, booting the kernel.
[ 7.495464] PCI: BIOS Bug: MCFG area at f80000000 is not E820-reserved
[ 7.495521] PCI: Not using MMCONFIG.
[ 7.495912] PCI: intel_rng: FWH not detected
Loading, pleases wait...
[ 11.255779] usb 1-1: device not accepting address 2, error -71
[ 13.239787] ACPI: Getting cpuindex for acpiid 0x2
ALERT! /dev/sda2 does not exist. Dropping to a shell!

Hi treebug,
Looks like the entire debug message had not been printed. If you are using grub, then delete the "silent" (or "quiet", don't remember exactly) parameter before booting and paste the entire output here. --LM


2. Enforcing mode requested but no policy loaded. Halting now
http://forums.fedoraforum.org/showthread.php?t=1325

I am running Fedora Core 2 test 2 and decided to upgrade to the lastest kernel. I have downbloaded the source and gone through the process of making and installing the kernel and modules. However whenever I try and boot from the new kernel I am getting

"Enforcing mode requested but no policy loaded. Halting now."
Kernel panic: Attempted to kill init!


Try adding enforcing=0 to your grub.conf.
kernel /boot/bzImage-2.6.5 ro root=/dev/hda5 enforcing=0

'linux > temp' 카테고리의 다른 글

/etc/yum.conf  (0) 2007.03.16
/etc/yum.repos.d/CentOS-Base.repo  (0) 2007.03.16
Geexbox Manual Installation  (0) 2007.03.16
web terminal connection error - mind term  (0) 2007.03.15
Linux Desktop Web mineterm(java)  (0) 2007.03.15
Posted by efrit
,
Manual Installation

http://www.geexbox.org/wiki/index.php/Installation


--------------------------------------------------------------------------------
This part explains how to manually install GeeXboX. Under normal circumstances, the Installator is the ideal solution for installing GeeXboX and should be used instead of this method. However, on occasion one needs to manually install, perhaps for a device the Installator does not recognize, perhaps because you wish to test certain changes or use your own bootloader, or even maybe you just wish to learn how because, once you know how to do it, it's actually quite easy to install GeeXboX and upgrades involve copying only a few things. I strongly recommend that, unless you know what you are doing, you stick to using the Installator for installation to your harddrive or other devices.
--------------------------------------------------------------------------------

Here are the steps to follow to accomplish this:

The first step, obviously enough, is to download GeeXboX's files. The ISO image is preferable as you can make the same changes the Generator makes yourself. The Generator includes all necessary files, however, a few are renamed or modified during compilation, so you will need to either generate an ISO using the tool or figure out which files it renames and modifies to manually do this yourself (if you can do this, you will be able to simply copy the files, skipping mkzftree.) You do not have to actually burn this image unless you want to.
You will need access to the partition you wish to install to. If you are in Windows, you will be unable to do a full installation from Windows alone to a non-Microsoft partition. For this reason, FAT16 or FAT32 partitions are preferable if using Windows. Don't worry, the files which require specific linux filesystem related settings (eg permissions) are kept in an archive with these settings to be extracted during bootup into the ramdrive, so even if stored on a FATxx partition, GeeXboX will function correctly. Linux users should have no issues with the proper filesystems. GeeXboX recommends installing to a FATxx or EXTx partition. Either one should be fine, so use what is best for you.
Gain access to the downloaded files. The reason I call this a seperate step is because you may not necessarily wish to burn the image to a disc to access them. If you do not wish to do this, in Windows you will need to use a tool designed to access CD images, and in linux you can simply mount the image as a loopback filesystem. Linux users simply type something along the lines of "mount -t iso9660 -o loop ~/downloads/geexbox.iso /mnt/cdrom" appropriately changing paths and the filename as necessary. Windows users will probably most benefit from using a "virtual drive" software. There are many which can do this, some of which are integrated into burning software. Probably the best of the free utilities to do this is Daemon-Tools What you use is up to you, just as long as you can access the image as if it were a CD-ROM. I have not yet found a tool which will extract the image correctly due to the usage of compression.
Copy the GeeXboX files from the image you've downloaded. Normally you could simply copy the entire /GEEXBOX folder into the root of the partition on which you wish to install GeeXboX, however GeeXboX currently uses mkzftree to compress part of the filesystem. Windows does not understand this, so you will need to properly extract the files. Most linux distros have support seamlessly integrated, so linux users will be able to simply copy the files without worrying about the compression. Windows users will need to be famililar with the console or find some GUI frontend to mkzftree. For Windows users:
Copy mkzftree to where you can get to it (either in your path or directly where you plan to install GeeXboX to make it easier in the future.)
Open a command prompt and change to the partition you wish to install to.
If you are a linux user, simply copy the /GEEXBOX folder from the CD image to the root of the partition you wish to install to. If you are a Windows user, run mkzftree with the -u (or --uncompress) command, citing the appropriate path to the CD image. Ex: "mkzftree -u Z:/GEEXBOX ./GEEXBOX" (note that the target folder must not exist for this command to work for some reason.) Some versions of mkzftree may have troubles, if so, the safest bet is to use the copy included in the Generator in the Win32 folder (you may also need to put the two DLL files with it. Be careful with these as there are sometimes conflicts when you use a different version of the Cygwin DLLs with programs, so it's probably best if you copy all three files to the place you intend to install GeeXboX rather than placing them into the path.)
Set it up for your favorite bootloader. You will probably need to copy the vmlinuz and initrd.gz files from /GEEXBOX/boot to wherever your bootloader needs them unless it is ok with such a path. Any bootloader capable of loading a linux kernel should be alright here. (I personally use Syslinux which is the harddrive incarnation of the tool used to boot the CD-ROM, and find it easiest to configure when using multiple operating systems.) It may be necessary to rename these files appropriately, such as "geexbox" for the kernel and "geexinit.gz" for the ramdrive image. The actual filenames only matter insofar as what the bootloader needs and whether or not you can remember what they are.
Configure and install the bootloader (I can't be too specific since different bootloaders operate differently. If you aren't sure about this, read the bootloader's documentation very carefully to prevent making your system unbootable.) /GEEXBOX/boot/isolinux.cfg shows the configuration used on the CD-ROM. Look at the second line under the "geexbox" label for the current append statement being used by the version of GeeXboX you are installing. Most of it you will leave as-is, but, you'll want to change the boot=cdrom statement to the place you are installing. For example, hda1 if installing to the first partition of the first IDE harddrive. Similarly, sda1 for the first partition of the first SCSI drive (and USB drives typically get treated like SCSI, so this setting usually works when installing to a USB flash drive.) So, in the first example, you would change it into "boot=hda1" and in the second "boot=sda1"
Reboot and test your new setup.
Hopefully this method will help a few people. I personally use this method because I wish to use my own bootloader, but, I have seen at least one person who said that the Installator did not properly work with their flashdrive, so this sort of method might help there as well. Once you've gotten the idea down, it's rather easy to repeat. Normally one has only to copy over the GeeXboX folder and replace the kernel and ramdrive images to manually update. Rarely a change is made to the syntax of the appended statements and these need to be adjusted in the bootloader.

Note: Installator will fail in case you are using old BIOS that does not support booting from USB as RMD-HDD. Manual installation is helpful there. Just do not create any partition table on targe USB drive. (I had to set the BIOS setting as USB-RMD-FDD to make sure it boots.)

Retrieved from "http://www.geexbox.org/wiki/index.php/Installation"

'linux > temp' 카테고리의 다른 글

/etc/yum.repos.d/CentOS-Base.repo  (0) 2007.03.16
kernel 2.6.18.4 compile error  (0) 2007.03.16
web terminal connection error - mind term  (0) 2007.03.15
Linux Desktop Web mineterm(java)  (0) 2007.03.15
대표적인 ISP의 DNS 서버 주소  (0) 2007.03.15
Posted by efrit
,