LinuxQuestions.org
Visit Jeremy's Blog.
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Non-*NIX Forums > General
User Name
Password
General This forum is for non-technical general discussion which can include both Linux and non-Linux topics. Have fun!

Notices


Reply
  Search this Thread
Old 03-07-2001, 05:35 AM   #1
devnull
Member
 
Registered: Feb 2001
Posts: 84

Rep: Reputation: 15

4.11. Where Can I Get Information about NFS Compatibility?

This information is partly taken from Nicolai Langfeldt's excellent
NFS HOWTO, and is current as of 10/1/1999.

Most version 2.2.x kernels need a set of patches to install the knfsd
subsystem, maintained by H.J. Lu, to communicate efficiently (if at
all) with Sparc, IBM RS, and Alpha machines, and probably others. This
package is actually a collection of patches to the kernel sources.

There is also a user-space server. Although it lacks remote file
locking, it is easier to install. It may be equally efficient.

In the Documentation/Changes of recent kernel distributions, there is
a list of URL's for both the knfsd server and the user-space server.

There is a CVS server available for the kernel-space NFS subsystem, as
well as a NFS WWW page at http://www.linuxnfs.sourceforge.org/,
although the URL requires a password for access. The relevant URL's
are listed in the README.nfs file at ftp://ftp.us.kernel.org/, and
other kernel archive sites, along with login information. Patches are
at ftp://ftp.varesearch.com/pub/kernel/latest/patches/.

The source archives of the user-space server and utilities currently
reside on
ftp://linux.mathematik.tu-darmstadt..../people/okir/.

In the case of older Solaris releases, the lack of statd or lockd on a
client or server machine may cause incompatibility. On some versions
of Solaris, statd can be used to exploit features of the automounter.
Sun released a patch to correct this, but statd still needs to be
started by root on such systems. On recent Solaris systems, refer to
the information in /etc/dfs/dfstab and the share(1M) manual page to
enable volume sharing. In addition, the rpcinfo program can tell you
if statd or lockd are available on the local or remote machines.

The linux-kernel mailing list has on-and-off discussions of the status
of the NFS subsystem, which appears to be changing rapidly.

[Nicolai Langfeldt, Robert Kiesling, Anders Hammarquist]

4.12. Can I Use True Type Fonts with Linux?

Yes. There are a number of True Type font servers for the X Window
System. One of them is xfsft. Its home page is
http://www.dcs.ed.ac.uk/home/jec/programs/xfsft/. There are also
instructions for configuration.

People have reported success with other True Type font servers. There
are links from the xfsft Home Page to them as well.

You can also compile True Type Font support into your X server
directly. Again, refer to the xfsft Home Page for details.

4.13. How Can I Boot Linux from MS-DOS?

If LILO doesn't work, and if the machine has MS-DOS or Microsoft
Windows, you may be left with a computer that won't boot. This can
also happen on an upgrade to your Linux distribution. Re-installing
LILO is the last thing that the installation does. So it is vitally
important when installing or upgrading Linux on a dual boot machine,
to have a MS-DOS or Windows rescue disk nearby so you can FDISK -MBR.
Then you can go about using LOADLIN.EXE instead of LILO.

This config.sys file is one possible way to invoke LOADLIN.EXE and
boot MS-DOS or Linux.

[menu]
menuitem=DOS, Dos Boot
menuitem=LINUX, Linux Boot

[LINUX]
shell=c:\redhat\loadlin.exe c:\redhat\autoboot\vmlinuz vga=5 root=/dev

[DOS]
STACKS = 0,0
rem all the other DOS drivers get loaded here.

This creates a menu where you can directly jump to LOADLIN.EXE before
all of the MS-DOS drivers get loaded.

The paths and options are peculiar to one machine and should be
intuitively obvious to the most casual observer. See the LOADLIN.EXE
docs for options. They are the same as LILO, and options are just
passed to the kernel, anyhow.

[Jim Harvey]

4.14. How Can I Boot Linux from OS/2's Boot Manager?

1. Create a partition using OS/2's FDISK.EXE (Not Linux's fdisk).
2. Format the partition under OS/2, either with FAT or HPFS. This is
so that OS/2 knows about the partition being formatted. (This step
is not necessary with OS/2 `warp' 3.0.)
3. Add the partition to the Boot Manager.
4. Boot Linux, and create a file system on the partition using mkfs
-t ext2 or mke2fs. At this point you may, if you like, use Linux's
fdisk to change the code of the new partition to type 83 (Linux
Native)--this may help some automated installation scripts find
the right partition to use.
5. Install Linux on the partition.
6. Install LILO on the Linux partition--NOT on the master boot record
of the hard drive. This installs LILO as a second-stage boot
loader on the Linux partition itself, to start up the kernel
specified in the LILO configuration file. To do this, you should
put

boot = /dev/hda2

(where /dev/hda2 is the partition you want to boot from) in your
/etc/lilo/config or /etc/lilo.config file.
7. Make sure that it is the Boot Manager partition that is marked
active, so that you can use Boot Manager to choose what to boot.

There is a set of HOWTO's on the subject of multi-boot systems at the
LDP Home Page, http://www.linuxdoc.org/.

5. File Systems, Disks, and Drives

5.1. How Can I Get Linux to Work with My Disk?

If your disk is an IDE or EIDE drive, you should read the file
/usr/src/linux/drivers/block/README.ide (part of the Linux kernel
source code). This README contains many helpful hints about IDE
drives. Many modern IDE controllers do translation between `physical'
cylinders/heads/sectors, and `logical' ones.

SCSI disks are accessed by linear block numbers. The BIOS invents some
`logical' cylinder/head/sector fiction to support DOS.

An IBM PC-compatible BIOS will usually not be able to access
partitions which extend beyond 1024 logical cylinders, and will make
booting a Linux kernel from such partitions using LILO problematic at
best.

You can still use such partitions for Linux or other operating systems
that access the controller directly.

It's recommend that you create at least one Linux partition entirely
under the 1024 logical cylinder limit, and boot from that. The other
partitions will then be okay.

Also there seems to be a bit of trouble with the newer Ultra-DMA
drives. I haven't gotten the straight scoop on them--but they are
becoming a very common problem at the SVLUG installfests. When you can
get 8 to 12 Gig drives for $200 to $300 it's no wonder.

[Jim Dennis]

5.2. How Can I Undelete Files?

In general, this is very hard to do on unices because of their
multitasking nature. Undelete functionality for the ext2fs file system
is being worked on, but don't hold your breath.

There are a number of packages available which instead provide new
commands for deleting and copying which move deleted files into a
`wastebasket' directory. The files can be recovered until cleaned out
automatically by background processing.

Alternatively, you can search the raw disk device which holds the file
system in question. This is hard work, and you will need to be logged
in as root to do this. But it can be done. Run grep on the raw device;
e.g.:

grep -b 'bookmarks' /dev/hda

If the data has not been overwritten, you should be able to recover it
with a text editor.

[Dave Cinege]

5.3. How Do I Make Backups?

You can back up a directory hierarchy or complete file system to any
media using GNU tar or cpio, the standard *nix tools for this purpose.
tar seems to be the more commonly used program currently, and includes
command line options to make compressed, incremental, and multi-volume
backups. Complete information is contained in the documentation, which
is in GNU Texinfo format.

The free program, Amanda, receives a lot of mentions on Usenet. Its
home page is http://www.amanda.org/.

Several commercial backup utilities also exist. They are often
included in commercial distributions.

5.4. How Do I Resize a Partition (Non-Destructively)?

Use the FIPS.EXE program, included with most Linux distributions,under
MS-DOS.

Parted, the free GNU partition editor, seems to be approaching
usability for normal, non-systems programmer users. The latest version
is at ftp://ftp.gnu.org/pub/gnu/parted/.

Also, some commercial distributions come with their own partitioning
software, like Partition Magic.

5.5. Is There a Defragmenter for Ext2fs, Etc.?

Yes. There is defrag, a Linux file system defragmenter for ext2,
Minix, and old-style ext file systems. It is available at
ftp://metalab.unc.edu/pub/Linux/syst...ag-0.70.tar.gz
.

Users of the ext2 file system can probably do without defrag, because
ext2 contains extra code to keep fragmentation reduced even in very
full file systems.

5.6. How Do I Format and Create a File System on a Floppy?

To format a 3.5-inch, high density floppy:

$ fdformat /dev/fd0H1440
$ mkfs -t ext2 -m 0 /dev/fd0H1440 1440

For a 5.25 inch floppy, use fd0h1200 and 1200 as appropriate. For the
B: drive use fd1 instead of fd0.

The -m 0 option tells mkfs.ext2 not to reserve any space on the disk
for the superuser--usually the last 10% is reserved for root.

The first command performs a low-level format. The second creates an
empty file system. You can mount the floppy like a hard disk partition
and simply cp and mv files, etc.

Device naming conventions generally are the same as for other unices.
They can be found in Matt Welsh's Installation and Getting Started
guide. Refer to ("Where Can I Get the HOWTO's and Other
Documentation?") A more detailed and technical description is Linux
Allocated Devices by H. Peter Anvin, hpa@zytor.com, which is included
in LaTeX and ASCII form in the kernel source distribution (probably in
/usr/src/kernel/Documentation/), as devices.tex and devices.txt.

5.7. Does Linux Support Virtualized File Systems Like RAID?

The most recent Linux kernels support software RAID, and they will
work with RAID disk controllers.

An automounter for NFS partitions is part of most Linux distributions.

In addition, several virtual file system projects exist. One of them,
the Linux Logical Volume Manager, is located at
http://linux.msede.com/lvm/.

5.8. Does Linux Support File System Encryption?

Yes. One file system, ppdd, is archived at
http://pweb.de.uu.net/flexsys.mtk/.

5.9. I Get Nasty Messages about Inodes, Blocks, and the Like.

You may have a corrupted file system, probably caused by not shutting
Linux down properly before turning off the power or resetting. You
need to use a recent shutdown program to do this--for example, the one
included in the util-linux package, available on sunsite and tsx-11.

If you're lucky, the program fsck (or e2fsck or xfsck as appropriate
if you don't have the automatic fsck front-end) will be able to repair
your file system. If you're unlucky, the file system is trashed, and
you'll have to re-initialize it with mkfs (or mke2fs, mkxfs, etc.),
and restore from a backup.

NB: don't try to check a file system that's mounted read/write--this
includes the root partition, if you don't see

VFS: mounted root ... read-only

at boot time.

5.10. My Swap Area Isn't Working.

When you boot (or enable swapping manually) you should see

Adding Swap: NNNNk swap-space

If you don't see any messages at all you are probably missing

swapon -av

(the command to enable swapping) in your /etc/rc.local or /etc/rc.d/*
(the system startup scripts), or have forgotten to make the right
entry in /etc/fstab:

/dev/hda2 none swap sw

for example.

If you see:

Unable to find swap-space signature

you have forgotten to run mkswap. See the manual page for details; it
works much like mkfs.

Running, free in addition to showing free memory, should display:

total used free
Swap: 10188 2960 7228

[Andy Jefferson]

5.11. How Do I Add Temporary Swap Space?

In addition to a swap partition, Linux can also use a swap file. Some
programs, like g++, can use huge amounts of virtual memory, requiring
the temporary creation of extra space. To install an extra 64 MB of
swap space, for example, use the following shell commands:

# dd if=/dev/zero of=/swap bs=1024 count=65535
# mkswap /swap
# swapon /swap

The count= argument to dd determines how big the swap file will be. In
this example the swap file's name is /swap, but the name and location
are, generally, arbitrary, depending only on the file system's
available space and your having write permissions in the directory.

When you don't need the swap space any more, remove it with the
following statements:

# swapoff /swap
# rm /swap

Take a look also at the Installation HOWTO and Installation & Getting
Started for detailed instructions.

If that still doesn't provide enough swap space, refer to ("How Can I
Have More Than 128Mb of Swap?")

5.12. How Do I Remove LILO So My System Boots DOS Again?

The lilo program (not the complete LILO package), uses the command
line option -u to uninstall the LILO boot loader. You have to supply
the device name of the device you installed LILO on, for example:

lilo -u /dev/hda

This rewrites the original, pre-LILO master boot record back to the
first hard drive, from the boot record saved in /boot/boot.0300. If
you installed LILO to a partition as a secondary boot loader, for
example, /dev/hda1, lilo re-installs the original boot sector from the
save file /boot/boot.0301. Refer to the lilo manual page for details.
Thanks to Villy Kruse for reminding me to update this answer.

If you have an earlier version of LILO, you will have to use the DOS
(MS-DOS 5.0 or later, or OS/2) FDISK /MBR (which is not documented).
This will restore a standard MS-DOS Master Boot Record. If you have
DR-DOS 6.0, go into FDISK.EXE in the normal way and then select the
Re-write Master Boot Record option.

If you don't have MS-DOS or DR-DOS, you need to have the boot sector
that LILO saved when you first installed it. You did keep that file,
didn't you? It's probably called boot.0301 or some such. Type:

dd if=boot.0301 of=/dev/hda bs=445 count=1

(or /dev/sda if you're using a SCSI disk). This may also wipe out your
partition table, so beware! If you're desperate, you could use

dd if=/dev/zero of=/dev/hda bs=512 count=1

This will erase your partition table and boot sector completely: you
can then reformat the disk using your favorite software. But this will
render the contents of your disk inaccessible--you'll lose it all
unless you're an expert.

Note that the DOS MBR boots whichever (single!) partition is flagged
as "active." You may need to use fdisk to set and clear the active
flags on partitions appropriately.

5.13. Why Can't I Use fdformat Except as Root?

The system call to format a floppy can only be done as root,
regardless of the permissions of /dev/fd0*. If you want any user to be
able to format a floppy, try getting the fdformat2 program. This works
around the problems by being setuid to root.

5.14. My Ext2fs Partitions Are Checked Each Time I Reboot.

Refer to ("EXT2-fs: warning: mounting unchecked file system.)

5.15. My Root File System Is Read-Only!

Remount it. If /etc/fstab is correct, you can simply type:

mount -n -o remount /

If /etc/fstab is wrong, you must give the device name and possibly the
type, too: e.g.

mount -n -o remount -t ext2 /dev/hda2 /

To understand how you got into this state, see, ("EXT2-fs: warning:
mounting unchecked file system.")

5.16. I Have a Huge /proc/kcore! Can I Delete It?

None of the files in /proc are really there--they're all, "pretend,"
files made up by the kernel, to give you information about the system
and don't take up any hard disk space.

/proc/kcore is like an "alias" for the memory in your computer. Its
size is the same as the amount of RAM you have, and if you read it as
a file, the kernel does memory reads.

5.17. The AHA1542C Doesn't Work with Linux.

The option to allow disks with more than 1024 cylinders is only
required as a workaround for a PC-compatible BIOS misfeature and
should be turned `off' under Linux. For older Linux kernels you need
to turn off most of the `advanced BIOS' options--all but the one about
scanning the bus for bootable devices.

5.18. Where Do I Find the Journalling File System?

The journalling file system, named Reiserfs has just been released
from testing. It is said to make Linux even faster than Linux with the
Ext2 file system installed. Complete information is available at
http://devlinux.org/namesys/.

6. Porting, Compiling and Obtaining Programs

6.1. How Do I Compile Programs?

Most Linux software is written in C and compiled with the GNU C
compiler. GCC is a part of every Linux distribution. The latest
compiler version, documentation, and patches are on
ftp://ftp.gnu.org/pub/gnu/.

Programs that are written in C++ must be compiled with the GNU G++
compiler, which is also included in Linux distributions and available
from the same place as GCC.

To build version 2.0.x and later kernels, you will need GCC version
2.7.2.x. Trying to build a Linux kernel with a different compiler,
like GCC 2.8.x, EGCS, or PGCC, may cause problems until the kernel
developers changed change the code so it will compile correctly with
compilers other than GCC 2.7.2.x.

Information on the EGCS compiler is at
http://www.gnu.org/software/gcc/gcc.html.

Note that at this time, the kernel developers are not answering bug
requests for earlier kernels, but instead are concentrating on
developing 2.3.x version kernels and maintaining 2.2.x version
kernels.

[J.H.M. Dassen, Axel Boldt]

6.2. How Do I Install GNU Software?

On a correctly configured system, installing a GNU software package
requires four steps:

* With the source.tar.gz archive in the /usr/src/ directory, or
wherever you maintain your source files, untar and decompress the
package with the command:

tar zxvf package-name.tar.gz

* Run the ./configure script in the untarred source archive's
top-level directory with whatever command line arguments you need.
The options that configure recognizes are usually contained in a
file called INSTALL or README.
* Run make. This will build the source code into an executable
program (or programs) and may take a few minutes or a few hours,
depending on the speed of the computer and the size of the
package.
* Run make install. This will install the compiled binaries,
configuration files, and any libraries in the appropriate
directories.

6.3. Where Do I Get Java?

The Sun Microsystems Java Developer's Kit (JDK) Version 1.2, is at
http://java.sun.com/products/jdk/1.2...ad-linux.html.

You can also get the source code, which is licensed by Sun
Microsystems.

Kaffee, an Open-Source version of Java, is at
http://www.transvirtual.com/products/.

The home page of IBM's Jikes Java compiler is
http://www10.software.ibm.com/develo...nsource/jikes.

There is a version of Sun's HotJava browser for Linux at
http://www.java.sun.com/products/hotjava/.

Netscape Communicator comes with its own version of the Java Runtime
Environment, so if you need Java only to view Web graphics, you may
already have the runtime version of the Java Virtual Machine and
libraries that you need installed on your system. You can download
Communicator from http://www.netscape.com/.

6.4. How Do I Port XXX to Linux?

In general, *nix programs need very little porting. Simply follow the
installation instructions. If you don't know--and don't know how to
find out--the answers to some of the questions asked during the
installation procedure, you can guess, but this tends to produce buggy
programs. In this case, you're probably better off asking someone else
to do the port. If you have a BSD-ish program, you should try using
-I/usr/include/bsd and -lbsd on the appropriate parts of the
compilation lines.

6.5. What Is ld.so and Where Do I Get It?

ld.so is the dynamic library loader. Each binary using shared
libraries used to have about 3K of start-up code to find and load the
shared libraries. Now that code has been put in a special shared
library, /lib/ld.so, where all binaries can look for it, so that it
wastes less disk space, and can be upgraded more easily. ld.so can be
obtained from http://tsx-11.mit.edu/pub/linux/packages/GCC/ and mirror
sites. The latest version at the time of writing is
ld.so.1.9.5.tar.gz. /lib/ld-linux.so.1 is the same thing for ELF
("What's all this about ELF? ") and comes in the same package as the
a.out loader.

6.6. How Do I Upgrade the Libraries without Trashing My System?

Warning

Note: You should always have a rescue disk set ready when you perform
this procedure, in the likely event that something goes wrong!

This procedure is especially difficult if you're upgrading very old
libraries like libc4. But you should be able to keep libc4 on the same
system with libc5 libraries for the programs that still need them. The
same holds true for upgrading from libc5 to the newer-yet glibc2
libraries.

The problem with upgrading dynamic libraries is that, the moment you
remove the old libraries, the utilities that you need to upgrade to
the new version of the libraries don't work. There are ways around
around this. One is to temporarily place a spare copy of the run time
libraries, which are in /lib/, in /usr/lib/, or /usr/local/lib/, or
another directory that is listed in the /etc/ld.so.conf file.

For example, when upgrading libc5 libraries, the files in /lib/ might
look something like:

libc.so.5
libc.so.5.4.33
libm.so.5
libm.so.5.0.9

These are the C libraries and the math libraries. Copy them to another
directory that is listed in /etc/ld.so.conf, like /usr/lib/:

$ cp -df /lib/libc.so.5* /usr/lib/
$ cp -df /lib/libm.so.5* /usr/lib/
$ ldconfig

Be sure to run ldconfig to upgrade the library configuration.

The files libc.so.5 and libm.so.5 are symbolic links to the actual
library files. When you upgrade, the new links will not be created if
the old links are still there, unless you use the -f flag with cp. The
-d flag to cp will copy the symbolic link itself, and not the file it
points to.

If you need to overwrite the link to the library directly, use the -f
flag with ln.

For example, to copy new libraries over the old ones, try this. Make a
symbolic link to the new libraries first, then copy both the libraries
and the links to /lib/, with the following commands.

$ ln -sf ./libm.so.5.0.48 libm.so.5
$ ln -sf ./libc.so.5.0.48 libc.so.5
$ cp -df libm.so.5* /lib
$ cp -df libc.so.5* /lib

Again, remember to run ldconfig after you copy the libraries.

If you are satisfied that everything is working correctly, you can
remove the temporary copies of the old libraries from /usr/lib/ or
wherever you copied them.

6.7. Has Anyone Ported/Compiled/Written XXX for Linux?

First, look in the Linux Software Map--it's at
ftp://metalab.unc.edu/pub/Linux/docs...-software-map/, and on the
other FTP sites. A search engine is available on the World Wide Web at
http://www.boutell.com/lsm/.

Check the FTP sites ("Where can I get Linux material by FTP?")
first--search the ls-lR or INDEX files for appropriate strings. Also
look at the Linux Projects Map,
ftp://ftp.ix.de/pub/ix/Linux/docs/Projects-Map.gz. There's a search
engine for Linux FTP archives at http://lfw.linuxhq.com/. Also check
out the Freshmeat Web site http://www.freshmeat.net, which is really
cool, even if the logo does look like cat food. (" What online/free
periodicals exist for Linux? " Freshmeat is basically a site index
that continuously updates the notices of new or upgraded software for
Linux. If you don't find anything, you could download the sources to
the program yourself and compile them. See ("How Do I Port XXX to
Linux?") If it's a large package that may require some porting, post a
message to comp.os.linux.development.apps. If you compile a large-ish
program, please upload it to one or more of the FTP sites, and post a
message to comp.os.linux.announce (submit your posting to
linux-announce@news.ornl.gov). If you're looking for an application
program, the chances are that someone has already written a free
version. The comp.sources.wanted FAQ has instructions for finding the
source code.

6.8. Can I Use Code or a Compiler Compiled for a 486 on My 386?

Yes, unless it's the kernel.

The -m486 option to GCC, which is used to compile binaries for x486
machines, merely changes certain optimizations. This makes for
slightly larger binaries that run somewhat faster on a 486. They still
work fine on a 386, though, with a small performance hit.

However, from version 1.3.35 the kernel uses 486 or Pentium-specific
instructions if configured for a 486 or Pentium, thus making it
unusable on a 386.

GCC can be configured for a 386 or 486; the only difference is that
configuring it for a 386 makes -m386 the default and configuring for a
486 makes -m486 the default. In either case, these can be overridden
on a per-compilation basis or by editing /usr/lib/gcc-lib/i*-linux/
n.n.n/specs.

There is an alpha version of GCC that knows how to do optimization
well for the 586, but it is quite unreliable, especially at high
optimization settings. The Pentium GCC can be found on
ftp://tsx-11.mit.edu/pub/linux/ALPHA/pentium-gcc/. The ordinary 486
GCC supposedly produces better code for the Pentium using the -m386,
or at least slightly smaller.

6.9. What Does "gcc -O6" Do?

Currently, the same as -O2 (GCC 2.5) or -O3 (GCC 2.6, 2.7). Any number
greater than that does the same thing. The Makefiles of newer kernels
use -O2, and you should probably do the same.

6.10. Where Are linux/*.h and asm/*.h?

The files /usr/include/linux/ and /usr/include/asm/ are often soft
links to the directories where the kernel headers are. They are
usually under /usr/src/kernel*/.

If you don't have the kernel sources, download them--see, ("How Do I
Upgrade/Recompile My Kernel?")

Then, use rm to remove any garbage, and ln to create the links:

$ rm -rf /usr/include/linux /usr/include/asm
$ ln -sf /usr/src/linux/include/linux /usr/include/linux
$ ln -sf /usr/src/linux/include/asm /usr/include/asm

/usr/src/linux/include/asm/ is a symbolic link to an
architecture-specific asm directory--if you have a freshly unpacked
kernel source tree, you must make symlinks. You'll also find that you
may need to do `make config' in a newly-unpacked kernel source tree,
to create linux/autoconf.h.

6.11. I Get Errors when I Try to Compile the Kernel.

See the previous question regarding the header files.

Remember that when you apply a patch to the kernel, you must use the
"-p0" or "-p1" option: otherwise, the patch may be misapplied. See the
patch manual page for details.

"ld: unrecognized option `-qmagic'" means that you should get a newer
linker, from ftp://tsx-11.mit.edu/pub/linux/packages/GCC/, in the file
binutils-2.8.1.0.1.bin.tar.gz.

 
Old 06-10-2002, 05:43 AM   #2
Bert
Senior Member
 
Registered: Jul 2001
Location: 406292E 290755N
Distribution: GNU/Linux Slackware 8.1, Redhat 8.0, LFS 4.0
Posts: 1,004

Rep: Reputation: 46
On defragmenting ext2fs ...

You might want to mention that defragmenting ext2fs is not recommended (in fact I wouldn't recommend it on any filesystem). The second extended filesystem does not cluster information on disks in the same way as FAT so the disk should not become fragmented at all.

I think of it like books in boxes. If you always choose the right size box, you'll never end up with empty space. Defragmenting is like squashing boxes and moving them (which usually damages the contents).

Bert
 
Old 06-10-2002, 06:08 AM   #3
acid_kewpie
Moderator
 
Registered: Jun 2001
Location: UK
Distribution: Gentoo, RHEL, Fedora, Centos
Posts: 43,417

Rep: Reputation: 1985Reputation: 1985Reputation: 1985Reputation: 1985Reputation: 1985Reputation: 1985Reputation: 1985Reputation: 1985Reputation: 1985Reputation: 1985Reputation: 1985
well i doubt HE will want to mentino anything, as HE has not posted here since last august. Even though this is a potentially useful thread, dragging up old ones is not generally appreciated
 
Old 06-10-2002, 06:20 AM   #4
Bert
Senior Member
 
Registered: Jul 2001
Location: 406292E 290755N
Distribution: GNU/Linux Slackware 8.1, Redhat 8.0, LFS 4.0
Posts: 1,004

Rep: Reputation: 46
Oh. sorry. On the other hand though ...

The title FAQ3 was misleading - it infers that this post was forming part of an LQ FAQ.

I posted with this in mind. If it's not part of the LQ FAQ it should't be labelled so and should be deleted or it's title changed.

Which only a moderator can do.

Apologies.

Bert
 
Old 06-10-2002, 06:24 AM   #5
acid_kewpie
Moderator
 
Registered: Jun 2001
Location: UK
Distribution: Gentoo, RHEL, Fedora, Centos
Posts: 43,417

Rep: Reputation: 1985Reputation: 1985Reputation: 1985Reputation: 1985Reputation: 1985Reputation: 1985Reputation: 1985Reputation: 1985Reputation: 1985Reputation: 1985Reputation: 1985
well no one seemed to pay any attention till now... this guy just copied an entire doc for no real reason other than it might be handy, but it sunk without trace. certainly in the wrong forum, and certainly nothing offical as far as LQ stands. at some point something more formal will probably be set up tho. nice to see someone actually found it tho!
 
Old 06-17-2002, 09:43 AM   #6
tundra
Member
 
Registered: Jun 2002
Location: Koom Valley
Distribution: rh8
Posts: 528

Rep: Reputation: 31
yea... but it's so long i passed it over and looked down to see if anyone bothered to read it.

all i can say is... uhhhhhhhh, someone's got plenty of time to spare...
 
  


Reply



Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Debian FAQ Artik Debian 13 06-30-2005 11:28 AM
BootP faq? basemodel Linux - Software 2 12-07-2003 02:06 PM
FAQ for Slackware? Danielallan Slackware 7 11-27-2003 11:09 PM
security faq??? crickett Linux - Security 1 06-23-2003 11:38 AM
FAQ part 4 devnull LQ Suggestions & Feedback 0 03-07-2001 05:37 AM

LinuxQuestions.org > Forums > Non-*NIX Forums > General

All times are GMT -5. The time now is 05:34 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration