solving(?) the updatedb problem w/ the kernel cache
I've been following lkml for a little while (not understanding it all, but following nonetheless ) and I've noticed that in a lot of the talks about schedulers, elevators, and performance, the issue of running updatedb and its effects on the kernel's fs cache seems to recur. I've also yet to see anyone present a solution that others think is worth pursuing. I'm curious why we're trying to solve the problem, when we can simply avoid the problem to begin with by making use of inotify and introducing a new user-space daemon, 'located'. This daemon would be started by the init scripts, register one or more inotify listeners based on /etc/updatedb.conf and then go to sleep. Whenever the fs is modified, an inotify event is triggered and 'located' wakes up, adjusts 'locate.db', and then goes back to sleep. It's about as simple as a daemon can get and still be of use, I think. Add a little 'configure' foo to detect if the system has inotify support and if it does, build/install the new daemon. If it doesn't, then don't build it and use the old behavior. With the daemon up and running, you can rm the updatedb entry in cron.daily and the negative impact it causes on the kernel's fs simply goes away. You wouldn't need to modify 'locate' itself, as it would still read from 'locate.db' like it does now. As an added bonus, you'd now have real-time results from 'locate'. If your Sys Admin just installed /usr/bin/foo, then 'locate foo' would find it "immediately". No more waiting until the next run of 'updatedb' for accurate results. All the major distros support inotify at this point, I believe. If I could code, I'd have attached the daemon here myself :) I must admit, though, I'm a little perplexed why greater minds than mine haven't already implemented this. I must be missing some technical issue. Can anyone enlighten me on the same? -- Douglas J Hunley (doug at hunley.homeip.net) - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
solving(?) the updatedb problem w/ the kernel cache
I've been following lkml for a little while (not understanding it all, but following nonetheless g) and I've noticed that in a lot of the talks about schedulers, elevators, and performance, the issue of running updatedb and its effects on the kernel's fs cache seems to recur. I've also yet to see anyone present a solution that others think is worth pursuing. I'm curious why we're trying to solve the problem, when we can simply avoid the problem to begin with by making use of inotify and introducing a new user-space daemon, 'located'. This daemon would be started by the init scripts, register one or more inotify listeners based on /etc/updatedb.conf and then go to sleep. Whenever the fs is modified, an inotify event is triggered and 'located' wakes up, adjusts 'locate.db', and then goes back to sleep. It's about as simple as a daemon can get and still be of use, I think. Add a little 'configure' foo to detect if the system has inotify support and if it does, build/install the new daemon. If it doesn't, then don't build it and use the old behavior. With the daemon up and running, you can rm the updatedb entry in cron.daily and the negative impact it causes on the kernel's fs simply goes away. You wouldn't need to modify 'locate' itself, as it would still read from 'locate.db' like it does now. As an added bonus, you'd now have real-time results from 'locate'. If your Sys Admin just installed /usr/bin/foo, then 'locate foo' would find it immediately. No more waiting until the next run of 'updatedb' for accurate results. All the major distros support inotify at this point, I believe. If I could code, I'd have attached the daemon here myself :) I must admit, though, I'm a little perplexed why greater minds than mine haven't already implemented this. I must be missing some technical issue. Can anyone enlighten me on the same? -- Douglas J Hunley (doug at hunley.homeip.net) - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.4.5pre2aa1
On Wednesday 16 May 2001 09:52, Andrea Arcangeli babbled: > > These descriptions are very helpful. Are they available somewhere > personally, I wish all kernel announcements were as nice as this. Kudos to Andrea. -- Douglas J. Hunley (Linux User #174778) http://hunley.homeip.net/ http://linux.nf/http://www.kicq.org/ And on the 8th day God said, "OK Murphy, you take over." - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.4.5pre2aa1
On Wednesday 16 May 2001 09:52, Andrea Arcangeli babbled: These descriptions are very helpful. Are they available somewhere personally, I wish all kernel announcements were as nice as this. Kudos to Andrea. -- Douglas J. Hunley (Linux User #174778) http://hunley.homeip.net/ http://linux.nf/http://www.kicq.org/ And on the 8th day God said, OK Murphy, you take over. - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.2.19 and ide.2.2.19.04092001.patch error
On Friday 27 April 2001 20:21, Mark Hahn babbled: > > Kernel config is attached. So is a description of my computer. Anyone got > > any ideas? > > your disk has bad errors. why do you think software changes will help? I know the disk has errors. Hence I run fsck. This is a brand new drive. I thought the kernel messages were indicative of an issue w/ the IDE patch. -- Douglas J. Hunley (Linux User #174778) http://hunley.homeip.net/ "Where do you want to go today?" Outside - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
2.2.19 and ide.2.2.19.04092001.patch error
While trying to use this patch to access /dev/hde1 on my Promise controller,
I get the following errors:
dma_intr: status=0x51 { DriveReady SeekComplete Error }
dma_intr: error=0x40 { UncorrectableError }, LBAsect=21233782, sector=21233712
This fs has errors on it, and trying to run fsck on it I get:
Error reading block 2654557 (Attempt to read block from filesystem resuleted
in short read) while doing inode scan. Ignore error?
I use the following in my /etc/lilo.conf:
ide[0-2]=autotune
This is 2.2.19 with the IDE patch, and the EXT3 patch (though this drive is
still ext2).
Kernel config is attached. So is a description of my computer. Anyone got any
ideas?
--
Douglas J. Hunley (Linux User #174778)
http://hunley.homeip.net/
Ambivalent? Well, yes and no.
#
# Automatically generated by make menuconfig: don't edit
#
#
# Code maturity level options
#
CONFIG_EXPERIMENTAL=y
#
# Processor type and features
#
# CONFIG_M386 is not set
# CONFIG_M486 is not set
CONFIG_M586=y
# CONFIG_M586TSC is not set
# CONFIG_M686 is not set
CONFIG_X86_WP_WORKS_OK=y
CONFIG_X86_INVLPG=y
CONFIG_X86_BSWAP=y
CONFIG_X86_POPAD_OK=y
# CONFIG_MICROCODE is not set
# CONFIG_X86_MSR is not set
# CONFIG_X86_CPUID is not set
CONFIG_1GB=y
# CONFIG_2GB is not set
# CONFIG_MATH_EMULATION is not set
CONFIG_MTRR=y
# CONFIG_SMP is not set
#
# Loadable module support
#
CONFIG_MODULES=y
# CONFIG_MODVERSIONS is not set
# CONFIG_KMOD is not set
#
# General setup
#
CONFIG_NET=y
CONFIG_PCI=y
# CONFIG_PCI_GOBIOS is not set
# CONFIG_PCI_GODIRECT is not set
CONFIG_PCI_GOANY=y
CONFIG_PCI_BIOS=y
CONFIG_PCI_DIRECT=y
CONFIG_PCI_QUIRKS=y
CONFIG_PCI_OPTIMIZE=y
CONFIG_PCI_OLD_PROC=y
# CONFIG_MCA is not set
# CONFIG_VISWS is not set
CONFIG_SYSVIPC=y
# CONFIG_BSD_PROCESS_ACCT is not set
CONFIG_SYSCTL=y
CONFIG_BINFMT_AOUT=y
CONFIG_BINFMT_ELF=y
# CONFIG_BINFMT_MISC is not set
# CONFIG_BINFMT_JAVA is not set
CONFIG_PARPORT=y
CONFIG_PARPORT_PC=y
# CONFIG_PARPORT_OTHER is not set
# CONFIG_APM is not set
# CONFIG_TOSHIBA is not set
#
# Plug and Play support
#
CONFIG_PNP=y
CONFIG_PNP_PARPORT=y
#
# Block devices
#
CONFIG_BLK_DEV_FD=y
CONFIG_BLK_DEV_IDE=y
# CONFIG_BLK_DEV_HD_IDE is not set
CONFIG_BLK_DEV_IDEDISK=y
CONFIG_IDEDISK_MULTI_MODE=y
CONFIG_IDEDISK_STROKE=y
CONFIG_BLK_DEV_IDECD=y
# CONFIG_BLK_DEV_IDETAPE is not set
# CONFIG_BLK_DEV_IDEFLOPPY is not set
CONFIG_BLK_DEV_IDESCSI=y
# CONFIG_IDE_TASK_IOCTL is not set
# CONFIG_PKT_TASK_IOCTL is not set
# CONFIG_IDE_TASK_IOCTL_DEBUG is not set
# CONFIG_BLK_DEV_CMD640 is not set
# CONFIG_BLK_DEV_RZ1000 is not set
CONFIG_BLK_DEV_IDEPCI=y
CONFIG_IDEPCI_SHARE_IRQ=y
CONFIG_BLK_DEV_IDEDMA=y
CONFIG_IDEDMA_AUTO=y
CONFIG_IDEDMA_NEW_DRIVE_LISTINGS=y
CONFIG_IDEDMA_PCI_EXPERIMENTAL=y
# CONFIG_IDEDMA_PCI_WIP is not set
# CONFIG_BLK_DEV_OFFBOARD is not set
# CONFIG_BLK_DEV_AEC62XX is not set
# CONFIG_BLK_DEV_ALI15X3 is not set
# CONFIG_BLK_DEV_AMD74XX is not set
# CONFIG_BLK_DEV_CMD64X is not set
# CONFIG_BLK_DEV_CY82C693 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_PIIX is not set
# CONFIG_BLK_DEV_OPTI621 is not set
CONFIG_BLK_DEV_PDC202XX=y
CONFIG_PDC202XX_BURST=y
# CONFIG_BLK_DEV_SIS5513 is not set
# CONFIG_BLK_DEV_SLC90E66 is not set
# CONFIG_BLK_DEV_OSB4 is not set
# CONFIG_BLK_DEV_TRM290 is not set
CONFIG_BLK_DEV_VIA82CXXX=y
# CONFIG_IDE_CHIPSETS is not set
CONFIG_IDEDMA_IVB=y
CONFIG_BLK_DEV_LOOP=y
# CONFIG_BLK_DEV_NBD is not set
# CONFIG_BLK_DEV_MD is not set
# CONFIG_BLK_DEV_RAM is not set
# CONFIG_BLK_DEV_XD is not set
# CONFIG_BLK_DEV_DAC960 is not set
CONFIG_PARIDE_PARPORT=y
# CONFIG_PARIDE is not set
CONFIG_BLK_DEV_IDE_MODES=y
# CONFIG_BLK_CPQ_DA is not set
# CONFIG_BLK_CPQ_CISS_DA is not set
# CONFIG_BLK_DEV_HD is not set
#
# Networking options
#
CONFIG_PACKET=y
CONFIG_NETLINK=y
CONFIG_RTNETLINK=y
CONFIG_NETLINK_DEV=y
CONFIG_FIREWALL=y
CONFIG_FILTER=y
CONFIG_UNIX=y
CONFIG_INET=y
CONFIG_IP_MULTICAST=y
CONFIG_IP_ADVANCED_ROUTER=y
CONFIG_RTNETLINK=y
CONFIG_NETLINK=y
CONFIG_IP_MULTIPLE_TABLES=y
CONFIG_IP_ROUTE_MULTIPATH=y
CONFIG_IP_ROUTE_TOS=y
CONFIG_IP_ROUTE_VERBOSE=y
# CONFIG_IP_ROUTE_LARGE_TABLES is not set
CONFIG_IP_ROUTE_NAT=y
CONFIG_IP_PNP=y
CONFIG_IP_PNP_DHCP=y
# CONFIG_IP_PNP_BOOTP is not set
# CONFIG_IP_PNP_RARP is not set
CONFIG_IP_FIREWALL=y
CONFIG_IP_FIREWALL_NETLINK=y
CONFIG_NETLINK_DEV=y
CONFIG_IP_ROUTE_FWMARK=y
CONFIG_IP_TRANSPARENT_PROXY=y
CONFIG_IP_MASQUERADE=y
CONFIG_IP_MASQUERADE_ICMP=y
CONFIG_IP_MASQUERADE_MOD=y
CONFIG_IP_MASQUERADE_IPAUTOFW=y
CONFIG_IP_MASQUERADE_IPPORTFW=y
CONFIG_IP_MASQUERADE_MFW=y
CONFIG_IP_ROUTER=y
# CONFIG_NET_IPIP is not set
# CONFIG_NET_IPGRE is not set
# CONFIG_IP_MROUTE is not set
CONFIG_IP_ALIAS=y
# CONFIG_ARPD is not set
CONFIG_SYN_COOKIES=y
CONFIG_INET_RARP=y
CONFIG_SKB_LARGE=y
# CONFIG_IPV6 is not set
# CONFIG_IPX is not set
# CONFIG_ATALK is not set
# CONFIG_X25 is not set
# CONFIG_LAPB is not set
# CONFIG_BRIDGE is not set
# CONFIG_NET_DIVERT is not set
# CONFIG_LLC
2.2.19 and ide.2.2.19.04092001.patch error
While trying to use this patch to access /dev/hde1 on my Promise controller,
I get the following errors:
dma_intr: status=0x51 { DriveReady SeekComplete Error }
dma_intr: error=0x40 { UncorrectableError }, LBAsect=21233782, sector=21233712
This fs has errors on it, and trying to run fsck on it I get:
Error reading block 2654557 (Attempt to read block from filesystem resuleted
in short read) while doing inode scan. Ignore errory?
I use the following in my /etc/lilo.conf:
ide[0-2]=autotune
This is 2.2.19 with the IDE patch, and the EXT3 patch (though this drive is
still ext2).
Kernel config is attached. So is a description of my computer. Anyone got any
ideas?
--
Douglas J. Hunley (Linux User #174778)
http://hunley.homeip.net/
Ambivalent? Well, yes and no.
#
# Automatically generated by make menuconfig: don't edit
#
#
# Code maturity level options
#
CONFIG_EXPERIMENTAL=y
#
# Processor type and features
#
# CONFIG_M386 is not set
# CONFIG_M486 is not set
CONFIG_M586=y
# CONFIG_M586TSC is not set
# CONFIG_M686 is not set
CONFIG_X86_WP_WORKS_OK=y
CONFIG_X86_INVLPG=y
CONFIG_X86_BSWAP=y
CONFIG_X86_POPAD_OK=y
# CONFIG_MICROCODE is not set
# CONFIG_X86_MSR is not set
# CONFIG_X86_CPUID is not set
CONFIG_1GB=y
# CONFIG_2GB is not set
# CONFIG_MATH_EMULATION is not set
CONFIG_MTRR=y
# CONFIG_SMP is not set
#
# Loadable module support
#
CONFIG_MODULES=y
# CONFIG_MODVERSIONS is not set
# CONFIG_KMOD is not set
#
# General setup
#
CONFIG_NET=y
CONFIG_PCI=y
# CONFIG_PCI_GOBIOS is not set
# CONFIG_PCI_GODIRECT is not set
CONFIG_PCI_GOANY=y
CONFIG_PCI_BIOS=y
CONFIG_PCI_DIRECT=y
CONFIG_PCI_QUIRKS=y
CONFIG_PCI_OPTIMIZE=y
CONFIG_PCI_OLD_PROC=y
# CONFIG_MCA is not set
# CONFIG_VISWS is not set
CONFIG_SYSVIPC=y
# CONFIG_BSD_PROCESS_ACCT is not set
CONFIG_SYSCTL=y
CONFIG_BINFMT_AOUT=y
CONFIG_BINFMT_ELF=y
# CONFIG_BINFMT_MISC is not set
# CONFIG_BINFMT_JAVA is not set
CONFIG_PARPORT=y
CONFIG_PARPORT_PC=y
# CONFIG_PARPORT_OTHER is not set
# CONFIG_APM is not set
# CONFIG_TOSHIBA is not set
#
# Plug and Play support
#
CONFIG_PNP=y
CONFIG_PNP_PARPORT=y
#
# Block devices
#
CONFIG_BLK_DEV_FD=y
CONFIG_BLK_DEV_IDE=y
# CONFIG_BLK_DEV_HD_IDE is not set
CONFIG_BLK_DEV_IDEDISK=y
CONFIG_IDEDISK_MULTI_MODE=y
CONFIG_IDEDISK_STROKE=y
CONFIG_BLK_DEV_IDECD=y
# CONFIG_BLK_DEV_IDETAPE is not set
# CONFIG_BLK_DEV_IDEFLOPPY is not set
CONFIG_BLK_DEV_IDESCSI=y
# CONFIG_IDE_TASK_IOCTL is not set
# CONFIG_PKT_TASK_IOCTL is not set
# CONFIG_IDE_TASK_IOCTL_DEBUG is not set
# CONFIG_BLK_DEV_CMD640 is not set
# CONFIG_BLK_DEV_RZ1000 is not set
CONFIG_BLK_DEV_IDEPCI=y
CONFIG_IDEPCI_SHARE_IRQ=y
CONFIG_BLK_DEV_IDEDMA=y
CONFIG_IDEDMA_AUTO=y
CONFIG_IDEDMA_NEW_DRIVE_LISTINGS=y
CONFIG_IDEDMA_PCI_EXPERIMENTAL=y
# CONFIG_IDEDMA_PCI_WIP is not set
# CONFIG_BLK_DEV_OFFBOARD is not set
# CONFIG_BLK_DEV_AEC62XX is not set
# CONFIG_BLK_DEV_ALI15X3 is not set
# CONFIG_BLK_DEV_AMD74XX is not set
# CONFIG_BLK_DEV_CMD64X is not set
# CONFIG_BLK_DEV_CY82C693 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_PIIX is not set
# CONFIG_BLK_DEV_OPTI621 is not set
CONFIG_BLK_DEV_PDC202XX=y
CONFIG_PDC202XX_BURST=y
# CONFIG_BLK_DEV_SIS5513 is not set
# CONFIG_BLK_DEV_SLC90E66 is not set
# CONFIG_BLK_DEV_OSB4 is not set
# CONFIG_BLK_DEV_TRM290 is not set
CONFIG_BLK_DEV_VIA82CXXX=y
# CONFIG_IDE_CHIPSETS is not set
CONFIG_IDEDMA_IVB=y
CONFIG_BLK_DEV_LOOP=y
# CONFIG_BLK_DEV_NBD is not set
# CONFIG_BLK_DEV_MD is not set
# CONFIG_BLK_DEV_RAM is not set
# CONFIG_BLK_DEV_XD is not set
# CONFIG_BLK_DEV_DAC960 is not set
CONFIG_PARIDE_PARPORT=y
# CONFIG_PARIDE is not set
CONFIG_BLK_DEV_IDE_MODES=y
# CONFIG_BLK_CPQ_DA is not set
# CONFIG_BLK_CPQ_CISS_DA is not set
# CONFIG_BLK_DEV_HD is not set
#
# Networking options
#
CONFIG_PACKET=y
CONFIG_NETLINK=y
CONFIG_RTNETLINK=y
CONFIG_NETLINK_DEV=y
CONFIG_FIREWALL=y
CONFIG_FILTER=y
CONFIG_UNIX=y
CONFIG_INET=y
CONFIG_IP_MULTICAST=y
CONFIG_IP_ADVANCED_ROUTER=y
CONFIG_RTNETLINK=y
CONFIG_NETLINK=y
CONFIG_IP_MULTIPLE_TABLES=y
CONFIG_IP_ROUTE_MULTIPATH=y
CONFIG_IP_ROUTE_TOS=y
CONFIG_IP_ROUTE_VERBOSE=y
# CONFIG_IP_ROUTE_LARGE_TABLES is not set
CONFIG_IP_ROUTE_NAT=y
CONFIG_IP_PNP=y
CONFIG_IP_PNP_DHCP=y
# CONFIG_IP_PNP_BOOTP is not set
# CONFIG_IP_PNP_RARP is not set
CONFIG_IP_FIREWALL=y
CONFIG_IP_FIREWALL_NETLINK=y
CONFIG_NETLINK_DEV=y
CONFIG_IP_ROUTE_FWMARK=y
CONFIG_IP_TRANSPARENT_PROXY=y
CONFIG_IP_MASQUERADE=y
CONFIG_IP_MASQUERADE_ICMP=y
CONFIG_IP_MASQUERADE_MOD=y
CONFIG_IP_MASQUERADE_IPAUTOFW=y
CONFIG_IP_MASQUERADE_IPPORTFW=y
CONFIG_IP_MASQUERADE_MFW=y
CONFIG_IP_ROUTER=y
# CONFIG_NET_IPIP is not set
# CONFIG_NET_IPGRE is not set
# CONFIG_IP_MROUTE is not set
CONFIG_IP_ALIAS=y
# CONFIG_ARPD is not set
CONFIG_SYN_COOKIES=y
CONFIG_INET_RARP=y
CONFIG_SKB_LARGE=y
# CONFIG_IPV6 is not set
# CONFIG_IPX is not set
# CONFIG_ATALK is not set
# CONFIG_X25 is not set
# CONFIG_LAPB is not set
# CONFIG_BRIDGE is not set
# CONFIG_NET_DIVERT is not set
# CONFIG_LLC
Re: 2.2.19 and ide.2.2.19.04092001.patch error
On Friday 27 April 2001 20:21, Mark Hahn babbled: Kernel config is attached. So is a description of my computer. Anyone got any ideas? your disk has bad errors. why do you think software changes will help? I know the disk has errors. Hence I run fsck. This is a brand new drive. I thought the kernel messages were indicative of an issue w/ the IDE patch. -- Douglas J. Hunley (Linux User #174778) http://hunley.homeip.net/ Where do you want to go today? Outside - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: ext3-0.0.5d questions
David Weinehall wrote: > > On Fri, Dec 15, 2000 at 10:15:05AM -0500, Douglas J. Hunley wrote: > > I just took the plunge and converted all my drives to EXT3. I've now got > > a _lot_ of questions. Is there a FAQ? Web documentation? Mailing list? > > A tip for next time you decide to do something akin to this: > > Read FAQ's, documentation etc. FIRST, then convert your > filesystems/install new software etc... > > /David Weinehall I normally do. However, I couldn't find any. And after rebuildin a lost 30G drive, I decided to bite the bullet. (sorry for the dupe David) -- Douglas J. Hunley (Linux User #174778) http://hunley.homeip.net/ Linux, the way to get rid of boot viruses - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
ext3-0.0.5d questions
I just took the plunge and converted all my drives to EXT3. I've now got a _lot_ of questions. Is there a FAQ? Web documentation? Mailing list? Thanks! -- Douglas J. Hunley (Linux User #174778) http://hunley.homeip.net/ Ambivalent? Well, yes and no. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
ext3-0.0.5d questions
I just took the plunge and converted all my drives to EXT3. I've now got a _lot_ of questions. Is there a FAQ? Web documentation? Mailing list? Thanks! -- Douglas J. Hunley (Linux User #174778) http://hunley.homeip.net/ Ambivalent? Well, yes and no. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: ext3-0.0.5d questions
David Weinehall wrote: On Fri, Dec 15, 2000 at 10:15:05AM -0500, Douglas J. Hunley wrote: I just took the plunge and converted all my drives to EXT3. I've now got a _lot_ of questions. Is there a FAQ? Web documentation? Mailing list? A tip for next time you decide to do something akin to this: Read FAQ's, documentation etc. FIRST, then convert your filesystems/install new software etc... /David Weinehall I normally do. However, I couldn't find any. And after rebuildin a lost 30G drive, I decided to bite the bullet. (sorry for the dupe David) -- Douglas J. Hunley (Linux User #174778) http://hunley.homeip.net/ Linux, the way to get rid of boot viruses - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
