Re: usb-keys
by Paul W. Frields
On Fri, 2004-08-13 at 03:54, Dave Pawson wrote:
> > <grin/> For 1 & 2, I guess I meant "better" in the sense that the
> > hotplug/updfstab method (1) is a way that both makes a more consistent
> > user interface (see comments above), (2) does not depend on the hardware
> > configuration remaining constant between insertions (i.e. what happens
> > if next time you have one or more other USB storage devices plugged in
> > already?), and (3) allows the user to contribute back to the community
> > by entering a bug against either hotplug or kudzu for their particular
> > USB device, so others can benefit.
>
> OK, I'm convinced!
> (And I'll expect those comments in the write-up Paul :-)
Hmm, that's a good point. I don't mention the "up side" in the document.
If someone's reviewing a bunch of different how-to docs, they would
probably be interested in knowing why I think my way is a good one. If
we can score points like that in official Fedora docs, then it keeps 'em
coming back. ;-)
> My notes were (sorry if too cryptic)
> <quote>
> mount /dev/sda1 /mnt/usbflash
>
> http://www.fedoraforum.org/forum/showthread.php?t=1291&highlight=mounted+usb
[...snip...]
Right. That's the way I used to do it before updfstab, too. And there's
no doubt that the venerable way works, it just doesn't give you all the
crunchy goodness of having your browser and permissions all fall into
line too, for whoever owns the console.
[...snip...]
> > Q.v. my BZ entry from 8/1:
> > http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=128952
>
> I note you broke off into Martian half way through that Paul.
> A conversation with ??? Nasrat went the same way on IRC this week.
> I'm beginning to suspect that using Linux for a while does things
> to the vocal chords.
> <quote> I'll also try and keep up with g-v-m and HAL so the
> document can be polished for FC3 </quote>
> What happended to English?
:-) Sorry, I was short on time and abbreviating gnome-volume-manager,
which Bill N. noted in his comment directly before. HAL is a
non-Linux-specific acronym, standing for "Hardware Abstraction Layer." I
suppose they talk about this a lot on the Linux kernel mailing list; I
don't have time to keep up with all of that traffic and actually *see*
my family! Hope that doesn't make me too much of a loser.
--
Paul W. Frields, RHCE
19 years, 8 months
Re: Self-Introduction: Tom Large
by Karsten Wade
Welcome, Tom!
On Thu, 2004-08-12 at 11:36, Tom Large wrote:
> Aside from all that, I'm mainly just interested in working with an Open
> Source project that I use regularly and can get some satisfaction out of
> helping.
We're just starting to gather ideas in a bucket in
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=129784. Do you
come with any specific ideas of where Fedora needs documenting?
> ~ - T H E L U G
> ~ - The Hectic Eclectic Linux User Group
> ~ - Linux without attitude, or directions, or goals...
> ~ - http://www.thelug.org
Ha! Careful, or someone might want to franchise that idea. :)
- Karsten
ps - sorry, had to break the message-id ;-)
--
Karsten Wade, RHCE, Tech Writer
a lemon is just a melon in disguise
http://people.redhat.com/kwade/
gpg fingerprint: 2680 DBFD D968 3141 0115 5F1B D992 0E06 AD0E 0C41
19 years, 8 months
Process suggestions vol. 1
by Paul W. Frields
The following is a core dump, because I have to get to a HOA meeting and
want to strike while the iron is hot. (Why yes, that *does* mean I have
a thick head, thanks for noticing.)
Ideas for improvied Docs Guide organization:
"Part 0."
Which part you should start reading. If you skip any parts (e.g. you
already have a tutorial written), what do you need to know to proceed?
Part 1. From idea to assignment.
Guidelines for scope, "pitch" (sorry if it's too Hollywood -- I mean
defining the syllabus or synopsis), and how to get the FDP's attention
(where to find us, come with a project in mind if possible, etc.). Why
this is a good idea rather than just throwing documents at us pell-mell.
Querying BZ for ideas.
Part 2. From assignment to production.
A slightly gentler how-to on getting the tools working, especially for
the Emacs/PSGML faint-of-heart. Pointers to other tool sets, and maybe
even instructions as well. Guidelines for the system you're documenting,
such as making sure that you're eliminating variables on your system to
which the "average" Fedora user isn't privy, trying to stick to best
methods for doing things (up2date vs. cli apt/yum, RPM vs tarballs,
etc.). Remember that we are not here to "fix" the system, we are here to
document how to use it as is. (See GNOME Docs Guide for similar
sentiments.)
We might want to include a style guide here.
Part 3. From production to posting.
How to submit the finished sources (BZ, eventual CVS,
fedora-docs-list...). What happens to your document after you submit it.
What the editor's responsibility is to you. What your responsibility is
to the editor. Approval process.
Part 4. From posting to...? (the grave?)
FDP/editors'/authors' responsibilities for keeping docs updated, and
how to change hands. Using BZ to report or query problems. Resolving
problems. Branching documents for different releases of FC.
Just some thoughts, more to come I fear.... :-)
--
Paul W. Frields, RHCE
19 years, 8 months
Re: fedora-docs-list Digest, Vol 6, Issue 3
by redwire＠therockmere.com
> My $0.02: CVS is still locked because we don't yet have a workable
> protocol for prioritizing, assigning, accepting, editing, QA/QC'ing, and
> automatically Web-fielding documents. I think (hope?) Red Hat people are
> working on the infrastructure part of that. We are here to talk about
> those protocols, and not to just grow a plethora of third-party
> repositories for docs.
>
Paul;
I understand that we maybe waiting on RH, but waiting on something that
'may' happen when 'someone' gets to it is like being the bridesmaid and
never the bride. [also, Sounds like Redmond, WA]
I'm not trying to be rude or insulting, but IF a working documentation
structure isn't able to be Resolved\Approved by those people that are
spending their own free time on it, then 'Houston, we have a problem'.
There is a difference between a releasing documents, especially those that
can be change so easily like XML, and making revisions and what seems to
be occurring; saying 'well, unless it is 100.01% perfect nobody gets to
see it'.
The advantage of OPEN SOURCE is the FREE EXCHANGE of information. This is
most importantly includes documentation. Red Hat gave the Fedora project
to the OS community because their focus shifted to Enterprise level sales
and service to make a profit. By extension that means that WE are able to
set standards. [aside: until recently monster.com had a job posting for a
DocBook person at RH. It is since been removed]
If FC is to progress to FC3, and gain traction, then it requires, and
demands, a large, free and accessible Document set.
While there are a number of 'document' sites. I will say that most of them
are a hodge-podge of minor tutorials and\or a document here or there on
FC. Not a dedicated single source for FC in an easy to read, DocBook
format.
Lastly, I understand that I am new to the group. I understand that I don't
post alot and am still trying to master DocBook syntax and d'l the
examples, but I will mention that I have 10+ yrs of computer programming &
training experience.
I know from experience that if you don't provide a basis for knowledge for
others to build on then the product, no matter how good, is destine to
fall by the wayside.
Brad
19 years, 8 months
Fedora install boot floppy doc
by David Nedrow
I've begun a document that details how to create a boot floppy for
Fedora installs on systems that don't have CD-ROM drives, etc.
Several people suggested I participate in the docs list to see about
adding it into the doc stream.
It's already in Docbook XML format, since that's what we do all of our
documentation in at work.
Several people have already contributed additions, including a script to
pretty much handle the gruntwork automatically.
I'm including a text transform of the first draft.
I haven't lloked at the Fedora doc guidelines yet, but if I remember
correctly they're pretty straightforward, so it should be relatively
easy for me to jimmy things around if necessary.
-David
Fedora Boot Floppy
David Nedrow
_________________________________________________________
Table of Contents
I. Motivation and Overview
Motivation
Overview
II. Detailed Boot Floppy Instructions
Build the kernel
Set up the work files
Create modules.cgz
Create new initrd
Create the boot floppy
Appendix A. Sample kernel config file
I. Motivation and Overview
Table of Contents
Motivation
Overview
_________________________________________________________
Motivation
Fedora does not currently provide boot floppies for installation.
The reason for this can be attributed to the fact that virtually no
computer ships these days without either a CD-ROM drive or a DVD-ROM
drive. Additionally, many computers now do not even ship with a
floppy drive. This can present a problem for systems that may have a
floppy, but no CD-ROM drive
A good example of the problem presented by the lack of a boot
install floppy comes when users are dealing with remote
installations on systems for which the user does not have physical
access. In the case of the original Compaq Remote Insight Lights Out
(RILO) boards, the user can only remote install the system using a
boot floppy. There is no support for virtuallized CD-ROM access on
the original RILO cards.
_________________________________________________________
Overview
Creating a boot floppy for Fedora is actually quite simple, though
it does require several manual steps.
Basically, you will use the diskboot.img file that is provided
Fedora. This image is normally used to create bootable devices using
USB memory pens, etc. This image provides all of the installation
bits to which you will add a custom kernel and modules.
II. Detailed Boot Floppy Instructions
Table of Contents
Build the kernel
Set up the work files
Create modules.cgz
Create new initrd
Create the boot floppy
_________________________________________________________
Build the kernel
You will need to build a new kernel using the kernel source files
provided with the Fedora installation you are attempting. For this
document, I will be using Fedora Core 2 (FC2) as the base system.
FC2 uses a kernel tree identified as linux-2.6.5-1.358. If you do
not have this source tree, simply download and install
kernel-source-2.6.5-1.358.i386.rpm.
The key to making a boot floppy for the Fedora installation is
creating a kernel and set of modules that include the absolute
minimum number of features you need to boot and install.
This means excluding items like parallel port support, ACPI and APM,
non-essential filesystem support, etc. You should also exclude
serial support, framebuffer support, etc. Basically, anything that
you don't need for the installation process should not be included
in the kernel or as modules. E.g., don't add CD-ROM drivers if
you're installing from the network.
It's important to remember that the installation itself will install
a fully functional kernel on the target system.
Included in Appendix A is a sample kernel configuration file.
_________________________________________________________
Set up the work files
You will need the diskboot.img file provided with the Fedora
installation under the images directory.
Warning You will need mount/umount access on the local filesystem
for the following steps.
Create a working directory (for this document, I'll be using
~/bootwork), and move diskboot.img to that directory. Within the
working directory, also create the following sub-directories:
* initrd-old
* initrd-new
* bootdisk-old
* floppy
You can use the following command to create all of the required
directories and files you will need:
cd ~
mkdir -p ~/bootwork/initrd-old; mkdir ~/bootwork/initrd-new
mkdir ~/bootwork/diskboot-old; mkdir ~/bootwork/floppy
mkdir ~/bootwork/linux-2.6.5-1.358
dd if=/dev/zero of=~/bootwork/initrd bs=512 count=2880
/sbin/mke2fs -F -m0 ~/bootwork/initrd
dd if=/dev/zero of=~/bootwork/floppy.img bs=512 count=2880
/sbin/mkfs.vfat ~/bootwork/floppy.img
syslinux ~/bootwork/floppy.img
Now, you need to mount diskboot.img so that we can get to the files
we need. Assuming that diskboot.img is in your home directory:
cd ~/bootwork
mount -o loop ~/diskboot.img diskboot-old
mount -o loop floppy.img floppy
cp diskboot-old/*.msg floppy/
cp diskboot-old/splash.lss floppy/
cp diskboot-old/syslinux.cfg floppy/
cp /usr/src/linux-2.6.5-1.358/arch/i386/boot/bzImage floppy/vmlinuz
gunzip -dc diskboot-old/initrd.img > initrd.old
mount -o loop initrd.old initrd-old
mount -o loop initrd initrd-new
_________________________________________________________
Create modules.cgz
The modules.cgz contains the modules (if any) that you built with
your custom kernel.
Use the following commands to create a new modules.cgz:
cd ~/bootwork
mkdir 2.6.5-1.358
find /usr/src/linux-2.6.5-1.358/drivers -name *.ko | xargs -n 1 -I {} c
p {} 2.6.5-1.358
find 2.6.5-1.358 | cpio -o -H crc | gzip -c9 > modules.cgz
_________________________________________________________
Create new initrd
Most of the new initrd image will be copied from the original initrd
that was extracted from the diskboot image.
cd ~/bootwork
cp -a initrd-old/bin initrd-new
cp -a initrd-old/dev initrd-new
cp -a initrd-old/etc initrd-new
cp -a initrd-old/linuxrc initrd-new
cp -a initrd-old/proc initrd-new
cp -a initrd-old/sbin initrd-new
cp -a initrd-old/selinux initrd-new
cp -a initrd-old/sys initrd-new
cp -a initrd-old/tmp initrd-new
cp -a initrd-old/var initrd-new
mkdir initrd-new/modules
cp -a initrd-old/modules/module-info initrd-new/modules
cp -a initrd-old/modules/modules.dep initrd-new/modules
cp -a initrd-old/modules/modules.pcimap initrd-new/modules
cp -a initrd-old/modules/pcitable initrd-new/modules
cp ~/anaconda-ks.cfg initrd-new/ks.cfg
cp -a modules.cgz initrd-new/modules
umount initrd-new
gzip -c9 initrd > initrd.img
cp initrd.img floppy
_________________________________________________________
Create the boot floppy
Now, all that has to be done is to unmount the new floppy image and
dump it to a floppy.
cd ~/bootwork
umount floppy
umount diskboot-old
umount initrd-old
dd if=floppy.img of=/dev/fd0
_________________________________________________________
Sample kernel config file
#
# Automatically generated make config: don't edit
#
CONFIG_X86=y
CONFIG_MMU=y
CONFIG_UID16=y
CONFIG_GENERIC_ISA_DMA=y
#
# Code maturity level options
#
CONFIG_EXPERIMENTAL=y
CONFIG_CLEAN_COMPILE=y
CONFIG_STANDALONE=y
CONFIG_BROKEN_ON_SMP=y
#
# General setup
#
CONFIG_SWAP=y
CONFIG_SYSVIPC=y
CONFIG_POSIX_MQUEUE=y
CONFIG_BSD_PROCESS_ACCT=y
CONFIG_SYSCTL=y
# CONFIG_AUDIT is not set
CONFIG_LOG_BUF_SHIFT=14
# CONFIG_HOTPLUG is not set
# CONFIG_IKCONFIG is not set
# CONFIG_EMBEDDED is not set
CONFIG_KALLSYMS=y
CONFIG_FUTEX=y
CONFIG_EPOLL=y
CONFIG_IOSCHED_NOOP=y
CONFIG_IOSCHED_AS=y
CONFIG_IOSCHED_DEADLINE=y
CONFIG_IOSCHED_CFQ=y
CONFIG_CC_OPTIMIZE_FOR_SIZE=y
#
# Loadable module support
#
CONFIG_MODULES=y
CONFIG_MODULE_UNLOAD=y
# CONFIG_MODULE_FORCE_UNLOAD is not set
CONFIG_OBSOLETE_MODPARM=y
# CONFIG_MODVERSIONS is not set
CONFIG_KMOD=y
#
# Processor type and features
#
CONFIG_X86_PC=y
# CONFIG_X86_ELAN is not set
# CONFIG_X86_VOYAGER is not set
# CONFIG_X86_NUMAQ is not set
# CONFIG_X86_SUMMIT is not set
# CONFIG_X86_BIGSMP is not set
# CONFIG_X86_VISWS is not set
# CONFIG_X86_GENERICARCH is not set
# CONFIG_X86_ES7000 is not set
# CONFIG_M386 is not set
# CONFIG_M486 is not set
CONFIG_M586=y
# CONFIG_M586TSC is not set
# CONFIG_M586MMX is not set
# CONFIG_M686 is not set
# CONFIG_MPENTIUMII is not set
# CONFIG_MPENTIUMIII is not set
# CONFIG_MPENTIUMM is not set
# CONFIG_MPENTIUM4 is not set
# CONFIG_MK6 is not set
# CONFIG_MK7 is not set
# CONFIG_MK8 is not set
# CONFIG_MCRUSOE is not set
# CONFIG_MWINCHIPC6 is not set
# CONFIG_MWINCHIP2 is not set
# CONFIG_MWINCHIP3D is not set
# CONFIG_MCYRIXIII is not set
# CONFIG_MVIAC3_2 is not set
# CONFIG_X86_GENERIC is not set
CONFIG_X86_CMPXCHG=y
CONFIG_X86_XADD=y
CONFIG_X86_L1_CACHE_SHIFT=5
CONFIG_RWSEM_XCHGADD_ALGORITHM=y
CONFIG_X86_PPRO_FENCE=y
CONFIG_X86_F00F_BUG=y
CONFIG_X86_WP_WORKS_OK=y
CONFIG_X86_INVLPG=y
CONFIG_X86_BSWAP=y
CONFIG_X86_POPAD_OK=y
CONFIG_X86_ALIGNMENT_16=y
# CONFIG_X86_4G is not set
# CONFIG_X86_SWITCH_PAGETABLES is not set
# CONFIG_X86_4G_VM_LAYOUT is not set
# CONFIG_X86_UACCESS_INDIRECT is not set
# CONFIG_X86_HIGH_ENTRY is not set
# CONFIG_HPET_TIMER is not set
# CONFIG_HPET_EMULATE_RTC is not set
# CONFIG_SMP is not set
# CONFIG_PREEMPT is not set
# CONFIG_X86_UP_APIC is not set
# CONFIG_X86_MCE is not set
# CONFIG_TOSHIBA is not set
# CONFIG_I8K is not set
# CONFIG_MICROCODE is not set
# CONFIG_X86_MSR is not set
# CONFIG_X86_CPUID is not set
#
# Firmware Drivers
#
# CONFIG_EDD is not set
CONFIG_NOHIGHMEM=y
# CONFIG_HIGHMEM4G is not set
# CONFIG_HIGHMEM64G is not set
# CONFIG_MATH_EMULATION is not set
# CONFIG_MTRR is not set
# CONFIG_REGPARM is not set
#
# Power management options (ACPI, APM)
#
# CONFIG_PM is not set
#
# ACPI (Advanced Configuration and Power Interface) Support
#
# CONFIG_ACPI is not set
CONFIG_ACPI_BOOT=y
#
# CPU Frequency scaling
#
# CONFIG_CPU_FREQ is not set
#
# Bus options (PCI, PCMCIA, EISA, MCA, ISA)
#
CONFIG_PCI=y
# CONFIG_PCI_GOBIOS is not set
# CONFIG_PCI_GOMMCONFIG is not set
# CONFIG_PCI_GODIRECT is not set
CONFIG_PCI_GOANY=y
CONFIG_PCI_BIOS=y
CONFIG_PCI_DIRECT=y
CONFIG_PCI_MMCONFIG=y
CONFIG_PCI_LEGACY_PROC=y
# CONFIG_PCI_NAMES is not set
# CONFIG_ISA is not set
# CONFIG_MCA is not set
# CONFIG_SCx200 is not set
#
# Executable file formats
#
CONFIG_BINFMT_ELF=y
# CONFIG_BINFMT_AOUT is not set
# CONFIG_BINFMT_MISC is not set
#
# Device Drivers
#
#
# Generic Driver Options
#
#
# Memory Technology Devices (MTD)
#
# CONFIG_MTD is not set
#
# Parallel port support
#
# CONFIG_PARPORT is not set
#
# Plug and Play support
#
#
# Block devices
#
CONFIG_BLK_DEV_FD=y
CONFIG_BLK_CPQ_DA=y
CONFIG_BLK_CPQ_CISS_DA=y
# CONFIG_BLK_DEV_DAC960 is not set
# CONFIG_BLK_DEV_UMEM is not set
CONFIG_BLK_DEV_LOOP=y
# CONFIG_BLK_DEV_CRYPTOLOOP is not set
# CONFIG_BLK_DEV_NBD is not set
# CONFIG_BLK_DEV_CARMEL is not set
CONFIG_BLK_DEV_RAM=y
CONFIG_BLK_DEV_RAM_SIZE=16384
CONFIG_BLK_DEV_INITRD=y
# CONFIG_LBD is not set
#
# ATA/ATAPI/MFM/RLL support
#
CONFIG_IDE=y
CONFIG_BLK_DEV_IDE=y
#
# Please see Documentation/ide.txt for help/info on IDE drives
#
# CONFIG_BLK_DEV_HD_IDE is not set
# CONFIG_BLK_DEV_IDEDISK is not set
# CONFIG_BLK_DEV_IDECD is not set
# CONFIG_BLK_DEV_IDETAPE is not set
# CONFIG_BLK_DEV_IDEFLOPPY is not set
# CONFIG_IDE_TASK_IOCTL is not set
# CONFIG_IDE_TASKFILE_IO is not set
#
# IDE chipset support/bugfixes
#
CONFIG_IDE_GENERIC=y
# CONFIG_BLK_DEV_CMD640 is not set
CONFIG_BLK_DEV_IDEPCI=y
CONFIG_IDEPCI_SHARE_IRQ=y
# CONFIG_BLK_DEV_OFFBOARD is not set
CONFIG_BLK_DEV_GENERIC=y
# CONFIG_BLK_DEV_OPTI621 is not set
# CONFIG_BLK_DEV_RZ1000 is not set
CONFIG_BLK_DEV_IDEDMA_PCI=y
# CONFIG_BLK_DEV_IDEDMA_FORCED is not set
CONFIG_IDEDMA_PCI_AUTO=y
CONFIG_IDEDMA_ONLYDISK=y
CONFIG_BLK_DEV_ADMA=y
# CONFIG_BLK_DEV_AEC62XX is not set
# CONFIG_BLK_DEV_ALI15X3 is not set
# CONFIG_BLK_DEV_AMD74XX is not set
# CONFIG_BLK_DEV_ATIIXP is not set
# CONFIG_BLK_DEV_CMD64X is not set
# CONFIG_BLK_DEV_TRIFLEX is not set
# CONFIG_BLK_DEV_CY82C693 is not set
# CONFIG_BLK_DEV_CS5520 is not set
# CONFIG_BLK_DEV_CS5530 is not set
# CONFIG_BLK_DEV_HPT34X is not set
# CONFIG_BLK_DEV_HPT366 is not set
# CONFIG_BLK_DEV_SC1200 is not set
# CONFIG_BLK_DEV_PIIX is not set
# CONFIG_BLK_DEV_NS87415 is not set
# CONFIG_BLK_DEV_PDC202XX_OLD is not set
# CONFIG_BLK_DEV_PDC202XX_NEW is not set
CONFIG_BLK_DEV_SVWKS=y
# CONFIG_BLK_DEV_SIIMAGE is not set
# CONFIG_BLK_DEV_SIS5513 is not set
# CONFIG_BLK_DEV_SLC90E66 is not set
# CONFIG_BLK_DEV_TRM290 is not set
# CONFIG_BLK_DEV_VIA82CXXX is not set
CONFIG_BLK_DEV_IDEDMA=y
# CONFIG_IDEDMA_IVB is not set
CONFIG_IDEDMA_AUTO=y
# CONFIG_BLK_DEV_HD is not set
#
# SCSI device support
#
# CONFIG_SCSI is not set
#
# Multi-device support (RAID and LVM)
#
# CONFIG_MD is not set
#
# Fusion MPT device support
#
# CONFIG_FUSION is not set
#
# IEEE 1394 (FireWire) support
#
# CONFIG_IEEE1394 is not set
#
# I2O device support
#
# CONFIG_I2O is not set
#
# Networking support
#
CONFIG_NET=y
#
# Networking options
#
CONFIG_PACKET=y
CONFIG_PACKET_MMAP=y
# CONFIG_NETLINK_DEV is not set
CONFIG_UNIX=y
# CONFIG_NET_KEY is not set
CONFIG_INET=y
# CONFIG_IP_MULTICAST is not set
# CONFIG_IP_ADVANCED_ROUTER is not set
# CONFIG_IP_PNP is not set
# CONFIG_NET_IPIP is not set
# CONFIG_NET_IPGRE is not set
# CONFIG_ARPD is not set
# CONFIG_SYN_COOKIES is not set
# CONFIG_INET_AH is not set
# CONFIG_INET_ESP is not set
# CONFIG_INET_IPCOMP is not set
# CONFIG_IPV6 is not set
# CONFIG_NETFILTER is not set
#
# SCTP Configuration (EXPERIMENTAL)
#
# CONFIG_IP_SCTP is not set
# CONFIG_ATM is not set
# CONFIG_BRIDGE is not set
# CONFIG_VLAN_8021Q is not set
# CONFIG_DECNET is not set
# CONFIG_LLC2 is not set
# CONFIG_IPX is not set
# CONFIG_ATALK is not set
# CONFIG_X25 is not set
# CONFIG_LAPB is not set
# CONFIG_NET_DIVERT is not set
# CONFIG_ECONET is not set
# CONFIG_WAN_ROUTER is not set
# CONFIG_NET_FASTROUTE is not set
# CONFIG_NET_HW_FLOWCONTROL is not set
#
# QoS and/or fair queueing
#
# CONFIG_NET_SCHED is not set
#
# Network testing
#
# CONFIG_NET_PKTGEN is not set
# CONFIG_NETPOLL is not set
# CONFIG_NET_POLL_CONTROLLER is not set
# CONFIG_HAMRADIO is not set
# CONFIG_IRDA is not set
# CONFIG_BT is not set
# CONFIG_TUX is not set
CONFIG_NETDEVICES=y
# CONFIG_DUMMY is not set
# CONFIG_BONDING is not set
# CONFIG_EQUALIZER is not set
# CONFIG_TUN is not set
#
# ARCnet devices
#
# CONFIG_ARCNET is not set
#
# Ethernet (10 or 100Mbit)
#
CONFIG_NET_ETHERNET=y
CONFIG_MII=y
# CONFIG_HAPPYMEAL is not set
# CONFIG_SUNGEM is not set
# CONFIG_NET_VENDOR_3COM is not set
#
# Tulip family network device support
#
# CONFIG_NET_TULIP is not set
# CONFIG_HP100 is not set
CONFIG_NET_PCI=y
# CONFIG_PCNET32 is not set
# CONFIG_AMD8111_ETH is not set
# CONFIG_ADAPTEC_STARFIRE is not set
# CONFIG_B44 is not set
# CONFIG_FORCEDETH is not set
# CONFIG_DGRS is not set
CONFIG_EEPRO100=m
# CONFIG_EEPRO100_PIO is not set
CONFIG_E100=m
# CONFIG_E100_NAPI is not set
# CONFIG_FEALNX is not set
# CONFIG_NATSEMI is not set
# CONFIG_NE2K_PCI is not set
# CONFIG_8139CP is not set
# CONFIG_8139TOO is not set
# CONFIG_SIS900 is not set
# CONFIG_EPIC100 is not set
# CONFIG_SUNDANCE is not set
# CONFIG_TLAN is not set
# CONFIG_VIA_RHINE is not set
#
# Ethernet (1000 Mbit)
#
# CONFIG_ACENIC is not set
# CONFIG_DL2K is not set
# CONFIG_E1000 is not set
# CONFIG_NS83820 is not set
# CONFIG_HAMACHI is not set
# CONFIG_YELLOWFIN is not set
# CONFIG_R8169 is not set
# CONFIG_SK98LIN is not set
# CONFIG_TIGON3 is not set
#
# Ethernet (10000 Mbit)
#
# CONFIG_IXGB is not set
# CONFIG_S2IO is not set
#
# Token Ring devices
#
# CONFIG_TR is not set
#
# Wireless LAN (non-hamradio)
#
# CONFIG_NET_RADIO is not set
#
# Wan interfaces
#
# CONFIG_WAN is not set
# CONFIG_FDDI is not set
# CONFIG_HIPPI is not set
# CONFIG_PPP is not set
# CONFIG_SLIP is not set
# CONFIG_RCPCI is not set
# CONFIG_SHAPER is not set
# CONFIG_NETCONSOLE is not set
#
# ISDN subsystem
#
# CONFIG_ISDN is not set
#
# Telephony Support
#
# CONFIG_PHONE is not set
#
# Input device support
#
CONFIG_INPUT=y
#
# Userland interfaces
#
CONFIG_INPUT_MOUSEDEV=y
# CONFIG_INPUT_MOUSEDEV_PSAUX is not set
CONFIG_INPUT_MOUSEDEV_SCREEN_X=1024
CONFIG_INPUT_MOUSEDEV_SCREEN_Y=768
# CONFIG_INPUT_JOYDEV is not set
# CONFIG_INPUT_TSDEV is not set
# CONFIG_INPUT_EVDEV is not set
# CONFIG_INPUT_EVBUG is not set
#
# Input I/O drivers
#
# CONFIG_GAMEPORT is not set
CONFIG_SOUND_GAMEPORT=y
CONFIG_SERIO=y
CONFIG_SERIO_I8042=y
# CONFIG_SERIO_SERPORT is not set
# CONFIG_SERIO_CT82C710 is not set
# CONFIG_SERIO_PCIPS2 is not set
#
# Input Device Drivers
#
CONFIG_INPUT_KEYBOARD=y
CONFIG_KEYBOARD_ATKBD=y
# CONFIG_KEYBOARD_SUNKBD is not set
# CONFIG_KEYBOARD_LKKBD is not set
# CONFIG_KEYBOARD_XTKBD is not set
# CONFIG_KEYBOARD_NEWTON is not set
CONFIG_INPUT_MOUSE=y
CONFIG_MOUSE_PS2=y
# CONFIG_MOUSE_SERIAL is not set
# CONFIG_MOUSE_VSXXXAA is not set
# CONFIG_INPUT_JOYSTICK is not set
# CONFIG_INPUT_TOUCHSCREEN is not set
# CONFIG_INPUT_MISC is not set
#
# Character devices
#
CONFIG_VT=y
CONFIG_VT_CONSOLE=y
CONFIG_HW_CONSOLE=y
# CONFIG_SERIAL_NONSTANDARD is not set
#
# Serial drivers
#
# CONFIG_SERIAL_8250 is not set
#
# Non-8250 serial port support
#
CONFIG_UNIX98_PTYS=y
# CONFIG_LEGACY_PTYS is not set
# CONFIG_CRASH is not set
# CONFIG_QIC02_TAPE is not set
#
# IPMI
#
# CONFIG_IPMI_HANDLER is not set
#
# Watchdog Cards
#
# CONFIG_WATCHDOG is not set
# CONFIG_HW_RANDOM is not set
# CONFIG_NVRAM is not set
# CONFIG_RTC is not set
# CONFIG_GEN_RTC is not set
# CONFIG_DTLK is not set
# CONFIG_R3964 is not set
# CONFIG_APPLICOM is not set
# CONFIG_SONYPI is not set
#
# Ftape, the floppy tape device driver
#
# CONFIG_FTAPE is not set
# CONFIG_AGP is not set
# CONFIG_DRM is not set
# CONFIG_MWAVE is not set
# CONFIG_RAW_DRIVER is not set
# CONFIG_HANGCHECK_TIMER is not set
#
# I2C support
#
# CONFIG_I2C is not set
#
# Misc devices
#
# CONFIG_IBM_ASM is not set
#
# Multimedia devices
#
# CONFIG_VIDEO_DEV is not set
#
# Digital Video Broadcasting Devices
#
# CONFIG_DVB is not set
#
# Graphics support
#
# CONFIG_FB is not set
# CONFIG_VIDEO_SELECT is not set
#
# Console display driver support
#
CONFIG_VGA_CONSOLE=y
# CONFIG_MDA_CONSOLE is not set
CONFIG_DUMMY_CONSOLE=y
#
# Sound
#
# CONFIG_SOUND is not set
#
# USB support
#
# CONFIG_USB is not set
#
# USB Gadget Support
#
# CONFIG_USB_GADGET is not set
#
# File systems
#
CONFIG_EXT2_FS=y
CONFIG_EXT2_FS_XATTR=y
CONFIG_EXT2_FS_POSIX_ACL=y
CONFIG_EXT2_FS_SECURITY=y
CONFIG_EXT3_FS=y
CONFIG_EXT3_FS_XATTR=y
CONFIG_EXT3_FS_POSIX_ACL=y
CONFIG_EXT3_FS_SECURITY=y
CONFIG_JBD=y
# CONFIG_JBD_DEBUG is not set
CONFIG_FS_MBCACHE=y
# CONFIG_REISERFS_FS is not set
# CONFIG_JFS_FS is not set
CONFIG_FS_POSIX_ACL=y
# CONFIG_XFS_FS is not set
# CONFIG_MINIX_FS is not set
CONFIG_ROMFS_FS=y
# CONFIG_QUOTA is not set
CONFIG_AUTOFS_FS=y
# CONFIG_AUTOFS4_FS is not set
#
# CD-ROM/DVD Filesystems
#
# CONFIG_ISO9660_FS is not set
# CONFIG_UDF_FS is not set
#
# DOS/FAT/NT Filesystems
#
CONFIG_FAT_FS=y
CONFIG_MSDOS_FS=y
CONFIG_VFAT_FS=y
# CONFIG_NTFS_FS is not set
#
# Pseudo filesystems
#
CONFIG_PROC_FS=y
CONFIG_PROC_KCORE=y
CONFIG_SYSFS=y
# CONFIG_DEVFS_FS is not set
# CONFIG_DEVPTS_FS_XATTR is not set
CONFIG_TMPFS=y
# CONFIG_HUGETLBFS is not set
# CONFIG_HUGETLB_PAGE is not set
CONFIG_RAMFS=y
#
# Miscellaneous filesystems
#
# CONFIG_ADFS_FS is not set
# CONFIG_AFFS_FS is not set
# CONFIG_HFS_FS is not set
# CONFIG_HFSPLUS_FS is not set
# CONFIG_BEFS_FS is not set
# CONFIG_BFS_FS is not set
# CONFIG_EFS_FS is not set
CONFIG_CRAMFS=y
# CONFIG_VXFS_FS is not set
# CONFIG_HPFS_FS is not set
# CONFIG_QNX4FS_FS is not set
# CONFIG_SYSV_FS is not set
# CONFIG_UFS_FS is not set
#
# Network File Systems
#
# CONFIG_NFS_FS is not set
# CONFIG_NFSD is not set
# CONFIG_EXPORTFS is not set
# CONFIG_SMB_FS is not set
# CONFIG_CIFS is not set
# CONFIG_NCP_FS is not set
# CONFIG_CODA_FS is not set
# CONFIG_INTERMEZZO_FS is not set
# CONFIG_AFS_FS is not set
#
# Partition Types
#
CONFIG_PARTITION_ADVANCED=y
# CONFIG_ACORN_PARTITION is not set
# CONFIG_OSF_PARTITION is not set
# CONFIG_AMIGA_PARTITION is not set
# CONFIG_ATARI_PARTITION is not set
# CONFIG_MAC_PARTITION is not set
CONFIG_MSDOS_PARTITION=y
# CONFIG_BSD_DISKLABEL is not set
# CONFIG_MINIX_SUBPARTITION is not set
# CONFIG_SOLARIS_X86_PARTITION is not set
# CONFIG_UNIXWARE_DISKLABEL is not set
# CONFIG_LDM_PARTITION is not set
# CONFIG_NEC98_PARTITION is not set
# CONFIG_SGI_PARTITION is not set
# CONFIG_ULTRIX_PARTITION is not set
# CONFIG_SUN_PARTITION is not set
# CONFIG_EFI_PARTITION is not set
#
# Native Language Support
#
CONFIG_NLS=y
CONFIG_NLS_DEFAULT="utf8"
# CONFIG_NLS_CODEPAGE_437 is not set
# CONFIG_NLS_CODEPAGE_737 is not set
# CONFIG_NLS_CODEPAGE_775 is not set
# CONFIG_NLS_CODEPAGE_850 is not set
# CONFIG_NLS_CODEPAGE_852 is not set
# CONFIG_NLS_CODEPAGE_855 is not set
# CONFIG_NLS_CODEPAGE_857 is not set
# CONFIG_NLS_CODEPAGE_860 is not set
# CONFIG_NLS_CODEPAGE_861 is not set
# CONFIG_NLS_CODEPAGE_862 is not set
# CONFIG_NLS_CODEPAGE_863 is not set
# CONFIG_NLS_CODEPAGE_864 is not set
# CONFIG_NLS_CODEPAGE_865 is not set
# CONFIG_NLS_CODEPAGE_866 is not set
# CONFIG_NLS_CODEPAGE_869 is not set
# CONFIG_NLS_CODEPAGE_936 is not set
# CONFIG_NLS_CODEPAGE_950 is not set
# CONFIG_NLS_CODEPAGE_932 is not set
# CONFIG_NLS_CODEPAGE_949 is not set
# CONFIG_NLS_CODEPAGE_874 is not set
# CONFIG_NLS_ISO8859_8 is not set
# CONFIG_NLS_CODEPAGE_1250 is not set
# CONFIG_NLS_CODEPAGE_1251 is not set
# CONFIG_NLS_ISO8859_1 is not set
# CONFIG_NLS_ISO8859_2 is not set
# CONFIG_NLS_ISO8859_3 is not set
# CONFIG_NLS_ISO8859_4 is not set
# CONFIG_NLS_ISO8859_5 is not set
# CONFIG_NLS_ISO8859_6 is not set
# CONFIG_NLS_ISO8859_7 is not set
# CONFIG_NLS_ISO8859_9 is not set
# CONFIG_NLS_ISO8859_13 is not set
# CONFIG_NLS_ISO8859_14 is not set
# CONFIG_NLS_ISO8859_15 is not set
# CONFIG_NLS_KOI8_R is not set
# CONFIG_NLS_KOI8_U is not set
CONFIG_NLS_UTF8=y
#
# Profiling support
#
# CONFIG_PROFILING is not set
#
# Kernel hacking
#
# CONFIG_DEBUG_KERNEL is not set
CONFIG_EARLY_PRINTK=y
# CONFIG_DEBUG_SPINLOCK_SLEEP is not set
# CONFIG_FRAME_POINTER is not set
#
# Security options
#
# CONFIG_SECURITY is not set
#
# Cryptographic options
#
# CONFIG_CRYPTO is not set
#
# Library routines
#
# CONFIG_CRC32 is not set
# CONFIG_LIBCRC32C is not set
CONFIG_ZLIB_INFLATE=y
CONFIG_X86_BIOS_REBOOT=y
CONFIG_X86_STD_RESOURCES=y
CONFIG_PC=y
19 years, 8 months
CVS Mirror
by redwire＠therockmere.com
The question was asked about 2 weeks ago about hosting the CVS. I got some
specs, but I wanted to follow up.
I am migrating to a static IP 1.5/286 with Speakeasy in the next month.
While I don't want to drag my connex down, I'd be interested in hosting a
CVS mirror. In real terms, how much drag will I see if I host a CVS or
mirror CVS?
I guess I don't quite understand why the CVS is LOCKED and why the Fedora
Main Page hasn't been updated to release\hyperlink to at least some
documentation.
FC1 and FC2 have been in production since APRIL, it seems important to ME
at least that there be some sort of documentation made avail. Also, I
think that releasing some documentation would help alleviate some of the
errant posting of questions to the fedora-docs mailing list.
The other alt. is to consider a FC docs based website, on my server, and
ask for any interested doc mailing list participants to send their docs to
me and I'll post them.
Thoughts and clarification of usage appreicated
Brad
19 years, 8 months
Using elvis?
by Colin Charles
Hi,
We've been talking about public CVS for far too long, and I think the
longer we wait, the longer Fedora Docs becomes less & less relevant
Keeping in mind that the barrier of entry is already relatively high
(you need to know DocBook, you need to use Emacs, etc...), this makes
folk move closer to creating docs on 3rd party sites
Why can't we use elvis.redhat.com ? Anaconda, translations and so on
happen at elvis, so why not fedora docs? This will mean external
contributors *can* commit to cvs as well
Kind regards
--
Colin Charles, byte(a)aeon.com.my
http://www.bytebot.net/
"First they ignore you, then they laugh at you, then they fight you,
then you win." -- Mohandas Gandhi
19 years, 8 months
Clarification
by redwire＠therockmere.com
I guess I kicked the hornets nest...so, Let me clarify a couple of points
that I raised in my last post
I am not suggesting that we Fork the doc project.
I used the offer of setting a CVS on my server only as repository for
completed documentation, to be made avail on a website.
I'm not openning my server to become a public FTP. Not going to happen.
But, I may have been a little OT with my terminology. In order to offer my
server for this I need it to be 90-95% automated. Like most of you, I
work, have kids and blah, blah, blah [ insert your busy sched. here ;-) ].
I am looking for controlled thruput. That is why I didn't suggest a WiKi.
I believe that the document integrity needs to be maintained. The DocBook
s/b published to a site with versioning.
I propose to give CVS or U'L access to ONLY the active members of this
list group for upload of Completed project(s). Then they are propagate to
the website. Docs are then avail for dissemination.
OK, here is what I have to ask\state;
1) Is this acceptable to the group?
2) Can CVS port to a live site? if so, where is the tutorial. Is there a
better tool for this idea?
( I can have a Nuke site up ASAP, but I dis-like some of the display
features for docs,but, can the RSS feeds pull the data?)
3) If RH opens their CVS ~ or starts posting docs ~ then they become prime
4) Proposed \ avail names?
5) I'm not asking you, singularly or as a group, to duplicate your
published work to 2 CVS's if there is a way to scrap the RH CVS. if so,
how?
Lastly, Karsten ~ TY for the shameless plug. I love tech writing and
trning, but I'd never get that job ~ I write like I talk ~ rambling
on-and-on-and... you get the idea!
> Since you opened the can, I don't mind a shameless plug as a reward for
> reading this far ... :) ... There is at least one position for a tech
> writer at Red Hat.
>
> http://redhat.hrdpt.com/cgi-bin/a/highlightjob.cgi?jobid=7
>
> This is the position that authors the System Administration Guide, so
> requires a fair amount of Linux and writing expertise.
>
> If you are a perfect fit for this position, feel free to contact me,
> I'll see your resume gets to the right person.
>
Thanks,
Brad
19 years, 8 months
