HELP - Need a DNS Guru

2003-10-18 Thread Keith Goettert

Ns1.helpfulhome.com is the DNS server for a variety of email and
websites.  I have been having trouble lately with email arriving late
(several days) or not at all.  As far as I can tell, this is a new
issue.  I am concerned because locally the DNS server appears to be
working fine.  But when I issue commands like:

   dig ns1.helpfulhome.com @ns1.covad.net

I don't get an answer section.  I have double checked my forward and
reverse entries and all appears correct.  Can somebody give me a clue??



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Lvm - converting EXT2 block to LV extent

2003-08-11 Thread Keith Goettert
Title: Message



Need a reality check here.  Based on what I see here I am assuming 
that the bad logical extent would be:
 
14712839/(4096*1024/512)   which breaks down to 
BadBlock/BlocksPerExtent
 
here is some system 
information.

Aug 10 06:30:04 sevenfountains kernel: hdd: 
dma_intr: status=0x51 { DriveReady Seek Complete Error }Aug 10 06:30:04 
sevenfountains kernel: hdd: dma_intr: error=0x40 { Uncorrectable Error }, 
LBAsect=78411097, sector=58859928Aug 10 06:30:04 sevenfountains kernel: 
end_request: I/O error, dev 16:48 (hdd), sector 58859928Aug 10 06:30:04 
sevenfountains kernel: EXT2-fs error (device lvm(58,0)): ext2_read_inode: unable 
to read inode block - inode=7356422, block=14712839--- 
Physical volume ---PV 
Name   
/dev/hdd8VG 
Name   
vg_stripedPV 
Size   
28.84 GB [60484662 secs] / NOT usable 4.19 MB [LVM: 156 
KB]PV#   
2PV 
Status 
NOT 
availableAllocatable   
yes (but full)Cur 
LV    
1PE Size (KByte)   
4096Total 
PE  
7382Free 
PE   
0Allocated PE  
7382PV 
UUID   
7Z4tXn-G3WY-ZR1w-3ILF-2U4v-Hm8N-sPdDHg 


Hard Drive Going - Need a good backup utility

2003-08-14 Thread Keith Goettert
Title: Message



The 
boot drive of one of my systems is going.  I would like to make a copy to 
CD or a Disk to Disk copy.  It has many partitions and I would like to 
preserve them seperately or at least be able to recreate them 
painlessly.


RE: I want separate MUA/MTA/MDA

2003-08-14 Thread Keith Goettert
I would definitely go with the latest exim.  I have been having a
wonderful time with it and I really like the responsiveness of the user
community.  I would like to hear what you think of postfix and procmail.
I need to include server side rules for mail sorting, and exim user
filters will work, but I would prefer a gui over the top of it.  Any
suggestions.

-Original Message-
From: MJM [mailto:[EMAIL PROTECTED] 
Sent: Monday, August 11, 2003 11:50 AM
To: [EMAIL PROTECTED]
Subject: Re: I want separate MUA/MTA/MDA


On Monday 11 August 2003 13:22, Mark Ferlatte wrote:
> Derrick 'dman' Hudson said on Mon, Aug 11, 2003 at 12:58:52PM -0400:
> > I heard (about a year ago) that RedHat now ships postfix instead of 
> > sendmail.  I haven't checked it out for myself, though.
>
> It's an option, but I don't know if it's the default.
>
> > | ( Never learned the syntax of sendmail configuration files 
> > | myself... )
> >
> > Me neither.
>
> It's not nearly as bad as people make it out to be anymore.  The 
> sendmail.mc is pretty straightforward to use, and you don't really 
> have to know anything about sendmail.cf anymore.
>
> I still prefer postfix, but not for the ease of configuration.
>
> I would say that if you want to be a Unix admin, you'd better know 
> sendmail, if only so that you can make a coherent argument for 
> replacing it with something that you like better.

Thanks for all the help.  Based on the advice given, I am reading the 
material available linked by the procmail, postfix, exim, etc. websites.
I 
will take a closer look at sendmail as well.  I want to understand email
at 
all levels and from all povs.  I would like to eventually understand the

nuances of the various tools as well.

My first practical, baby-step concern is if I will be able to maintain
my 
working KMail configuration while I try out combinations of uni-purpose
mail 
tools.  
-- 
Mike Mueller


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact
[EMAIL PROTECTED]




-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



iostat does not show all drives

2003-08-22 Thread Keith Goettert

I am running a 2.4.20 kernel but using the latest stable distribution.
Is there a reason that my iostat command only shows one of the three
hard drives?  Do I need a switch somewhere?


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



RE: Hard Drive Crash Recovery

2003-08-22 Thread Keith Goettert
Not sure I understand the question.  But...

If all your doing is creating a new /home directory, then simply do a
"mkdir /home" from the root as root on your other drive.  Or, if the
space is not on your root drive, then make a home directory on another
drive and ln -s  / 

As for swap, you need a partition formatted for swap.  That means your
going to have to carve out some space from one of your drives.   You can
use filesystem swap, but I have not used it and can't tell you how to
set it up.

-Original Message-
From: Curtis Spencer [mailto:[EMAIL PROTECTED] 
Sent: Thursday, August 21, 2003 11:29 AM
To: [EMAIL PROTECTED]
Subject: Hard Drive Crash Recovery


I had a hard drive crash last night on one of my systems.  Fortunately 
only a near empty /home and the swap partition were on that drive so I 
did not lose too much data. 
However, I don't know how to go about remounting the /home directory and

the swap partition.  Is there any way to mount the /home directory on 
another drive that already has data on it, but is not full?  I would 
prefer not to buy a new drive if I don't have to.  If I have to use 
another drive what are the commands I must do to prepare it for mounting

/home and a new swap partition on it?

Thanks for all the help,
Curtis


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact
[EMAIL PROTECTED]




-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



libperl-dev -- question to debian user

2003-08-28 Thread Keith Goettert
Title: Message



I have also noticed 
that libperl.a seems misplaced.  Did you ever get an answer out of the 
community?
 
==
 From: Bill 
Moseley 
 Why does it seem like libperl.a is in the wrong place?

I'm running testing.

ii  perl   5.8.0-18   Larry Wall's Practical Extraction and Report
ii  perl-base  5.8.0-18   The Pathologically Eclectic Rubbish Lister.
ii  perl-doc   5.8.0-17   Perl documentation.
ii  perl-modules   5.8.0-18   Core Perl modules.
ii  libperl-dev5.8.0-18   Perl library: development files.
ii  libperl5.6 5.6.1-8.2  Shared Perl library.
ii  libperl5.8 5.8.0-18   Shared Perl library.

Trying to build a perl binary linked with a module (for debugging 
reasons):

$ make perl
make[1]: *** No rule to make target `/usr/lib/perl/5.8.0/CORE/libperl.a', needed by `perl'.  Stop.

$ dpkg -S libperl.a
libperl-dev: /usr/lib/libperl.a






 
Keith Goettert, CIO, Lightwave Access, 
LLC.   818 501 8872  [EMAIL PROTECTED]
===
CONFIDENTIALITY NOTICE: E-mail may contain 
confidential information that is legally privileged. Do not read this e-mail 
if you are not the intended recipient. 
This e-mail transmission, and any documents, files 
or previous e-mail messages attached to it may contain confidential information 
that is legally privileged. If you are not the intended recipient, or a person 
responsible for delivering it to the intended recipient, you are hereby notified 
that any disclosure, copying, distribution or use of any of the information 
contained in or attached to this transmission is STRICTLY PROHIBITED. If you 
have received this transmission in error, please immediately notify us by reply 
e-mail, by forwarding this to postmaster@LightwaveAccess.com or 
by telephone at (818) 501-8872 
and destroy the original transmission and its attachments without reading or 
saving in any manner. Thank you. 
===
 


Webmagick and Imagemagick on Debian Woody - A Tutorial

2003-09-01 Thread Keith Goettert
  no
ZLIB  --with-zlib=yes   no

X11 Configuration:

  Not using X11.

Options used to compile and link:
  CC   = gcc
  CFLAGS   = -g -O2 -Wall
  CPPFLAGS = -I/usr/include/freetype2 -D_FILE_OFFSET_BITS=64
-D_REENTRANT
  CXX  = g++
  CXXFLAGS = -g -O2
  LDFLAGS  = -L/usr/lib
  LIBS = -lfreetype -ljpeg -lpthread -lm


---
The "Configured value" column is the important one.  Make sure that all
the yes' and values are in the right place for what your trying to do.
As you can see, I did not want PNG support, but you may...

make and make install work as advertised.  So just run them.

Once they are completed, cd to the PerlMagick directory under the
ImageMagick directory and run the following commands:

  perl Makefile.PL
  make
  make install
  make test

I have no idea why this is necessary, but without doing this various
necessary library files seem to be missing in the installation.  The
last line is not really necessary, but you should get a descent number
of the test to run.  I got around 60% of the main test and about 90% of
the subtests.  Failures are caused by packages not being enabled (like
X11 support which webmagick does not need).

  Testing the installation  ===

Ok, if all this worked (and it should) you should be able to do the
following (This is directly from the Imagemagick developers email to
me):

Before concerning yourself with PerlMagick and WebMagick make sure
ImageMagick can read jpegs.  Type

 convert -list format

Is JPEG listed:

 JPEG* JPEG  rw-   Joint Photographic Experts Group JFIF format
(62)
  JPG* JPEG  rw-   Joint Photographic Experts Group JFIF format

If not, go back to config.log to determine why the configure program
failed to accept your JPEG installation.

If JPEG is listed, type

  convert logo: logo.jpg
  identify logo.jpg

If all this works, PerlMagick should be able to read JPEG images.  To
test, run this script:

  use Image::Magick;
  $image=Image::Magick->new():
  $x = $image->Read('logo.jpg');
  warn "$x" if $x;
  $x = $image->Write('image.jpg');
  warn "$x" if $x;

If the above script works, WebMagick should be able to read JPEG images.

For Perl newbie's like myself, take the little perl script above and put
it into an executable file.  Then run it by typing:

   #perl [NameOfFile]

You should get no output, that is, it should run clean without warnings
or errors.

  Building Webmagick  ===

The top part of the INSTALL instructions in the Webmagick source
directory talk about configuring ImageMagick.  You can skip these steps
because you have already carefully performed them above.  About half way
down the document, you will come to the configure step for Webmagick.
My command looked like:

./configure --prefix= /usr/share/apache/webmagick

Because I wanted the pictures placed in the area that apache uses for
shared components.  You will also want to add the following lines to
your apache/httpd.conf file:

#
# Aliases: Add here as many aliases as you need (with no limit). The
format is 
# Alias fakename realname
#
# Note that if you include a trailing / on fakename then the server will
# require it to be present in the URL.  So "/icons" isn't aliased in
this
# example, only "/icons/"..
#

Alias /webmagick/ /usr/share/apache/webmagick/


Options Indexes MultiViews
AllowOverride None
Order allow,deny
Allow from all


Now any virtual servers can get to the webmagick images with
http://[yourvirtualdomain]/webmagick/

I forget how I answered all the other questions it asked, but rerunning
it works just fine so feel free to experiment.

  Some final fixes  ===

The current version of Webmagick and Imagemagick (more specifically
Perlmagick) are out of sync with each other.  It may happen that
webmagick ends up using GraphicsMagick's PerlMagick
(http://www.graphicsmagick.org/) instead.  However, today you would have
to do some searching and replacing to make that happen.  To get
Webmagick working the way we are going, make the following edits to the
/bin/webmagick file:

Change:
$opt_thumbcompose   = 'Replace';   # Thumbnail image composition
operation
To:
$opt_thumbcompose   = 'Copy';   # Thumbnail image composition
operation

Comment out:
#$montageArguments .= "foreground=>\'$opt_thumbforeground\',\n "
#   if $opt_thumbforeground ne 'false';

  Runing Webmagick  ===

That's all folks!  You should be able to run a nice quiet montage now
with a command like:

webmagick --iconbase ../../../../webmagick

Have Fun!!!

Keith Goettert, CIO, Lightwave Access, LLC.   [EMAIL PROTECTED]


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



RAID card shows SCSI and unwanted IDE devices

2003-12-05 Thread Keith Goettert




I am using a Hipoint IDE RAID card.  The driver that Hipoint has
created makes the card appear to be a scsi device.  This all works fine
and I can access the array as though it was a single SCSI drive. 
Unfortunately, the kernel also detects the hpt370 ide controller chips
and attempts to configure an hd"x" device for each drive in the array. 
This fails during boot with "interrupt lost" errors and greatly
lengthens the boot cycle.  The system runs fine except for disk
utilities like Mondo that attempt to catalog the phantom drives and end
up locking up the system.

How can I tell the kernel not to detect these ide devices but still
detect the other valid ide devices (like the CDROM and some non-RAID
drives)?

Boot messages follow...
.
.
.
Uniform Multi-Platform E-IDE driver Revision: 6.31
ide: Assuming 33MHz system bus speed for PIO modes; override with
idebus=xx
ICH4: IDE controller on PCI bus 00 dev f9
PCI: Device 00:1f.1 not available because of resource collisions
ICH4: BIOS setup was incomplete.
ICH4: chipset revision 1
ICH4: not 100% native mode: will probe irqs later
    ide0: BM-DMA at 0xfc00-0xfc07, BIOS settings: hda:DMA, hdb:DMA
    ide1: BM-DMA at 0xfc08-0xfc0f, BIOS settings: hdc:pio, hdd:DMA
HPT370A: IDE controller on PCI bus 03 dev 00
HPT370A: detected chipset, but driver not compiled in!
PCI: Enabling device 03:00.0 (0005 -> 0007)
HPT370A: chipset revision 4
HPT370A: not 100% native mode: will probe irqs later
    ide2: BM-DMA at 0xbc00-0xbc07, BIOS settings: hde:pio, hdf:pio
    ide3: BM-DMA at 0xbc08-0xbc0f, BIOS settings: hdg:pio, hdh:pio
hda: MAXTOR 6L080J4, ATA DISK drive
hdb: MAXTOR 6L080J4, ATA DISK drive
hdd: LITE-ON LTR-40125S, ATAPI CD/DVD-ROM drive
hde: WDC WD2000JB-00EVA0, ATA DISK drive
hdg: WDC WD2000JB-00EVA0, ATA DISK drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
ide1 at 0x170-0x177,0x376 on irq 15
ide2 at 0xcc00-0xcc07,0xc802 on irq 16
ide3 at 0xc400-0xc407,0xc002 on irq 16
blk: queue c035b4a4, I/O limit 4095Mb (mask 0x)
hda: 156355584 sectors (80054 MB) w/1819KiB Cache, CHS=9732/255/63,
UDMA(100)
blk: queue c035b5f0, I/O limit 4095Mb (mask 0x)
hdb: 156355584 sectors (80054 MB) w/1819KiB Cache, CHS=9732/255/63,
UDMA(100)
hde: lost interrupt
hde: lost interrupt
hde: lost interrupt
hde: lost interrupt
hde: 390721968 sectors (200050 MB) w/8192KiB Cache, CHS=24321/255/63
hde: lost interrupt
hde: lost interrupt
hdg: lost interrupt
hdg: lost interrupt
hdg: lost interrupt
hdg: lost interrupt
hdg: 390721968 sectors (200050 MB) w/8192KiB Cache, CHS=24321/255/63
hdg: lost interrupt
hdg: lost interrupt
Partition check:
 hda: hda1 hda2 hda3 hda4 < hda5 hda6 hda7 hda8 >
 hdb: unknown partition table
 hde:hde: lost interrupt

 hdg:hdg: lost interrupt

.  and later in the boot  ...


scsi0 : SCSI host adapter emulation for IDE ATAPI devices
  Vendor: LITE-ON   Model: LTR-40125S    Rev: ZS0K
  Type:   CD-ROM ANSI SCSI revision: 02
Attached scsi CD-ROM sr0 at scsi0, channel 0, id 0, lun 0
sr0: scsi3-mmc drive: 48x/48x writer cd/rw xa/form2 cdda tray
Uniform CD-ROM driver Revision: 3.12
Device Driver for HPT37x2 ATA RAID Controller
Version 1.31, Compiled Nov 24 2003 08:58:36
Found Controller: HPT370 UDMA/ATA100 RAID Controller
scsi1 : hpt37x2
  Vendor: HPT Inc.  Model: HPT37x2   RAID 1  Rev: 1.05
  Type:   Direct-Access  ANSI SCSI revision: 02
Attached scsi disk sda at scsi1, channel 0, id 0, lun 0
SCSI device sda: 390721968 512-byte hdwr sectors (200050 MB)
 sda:






RAID card shows SCSI and unwanted IDE devices

2003-12-05 Thread Keith Goettert




Sorry about the resend.  Original message got lost in a thread...



I am using a Hipoint IDE RAID card.  The driver that Hipoint has
created makes the card appear to be a scsi device.  This all works fine
and I can access the array as though it was a single SCSI drive. 
Unfortunately, the kernel also detects the hpt370 ide controller chips
and attempts to configure an hd"x" device for each drive in the array. 
This fails during boot with "interrupt lost" errors and greatly
lengthens the boot cycle.  The system runs fine except for disk
utilities like Mondo that attempt to catalog the phantom drives and end
up locking up the system.

How can I tell the kernel not to detect these ide devices but still
detect the other valid ide devices (like the CDROM and some non-RAID
drives)?

Boot messages follow...
.
.
.
Uniform Multi-Platform E-IDE driver Revision: 6.31
ide: Assuming 33MHz system bus speed for PIO modes; override with
idebus=xx
ICH4: IDE controller on PCI bus 00 dev f9
PCI: Device 00:1f.1 not available because of resource collisions
ICH4: BIOS setup was incomplete.
ICH4: chipset revision 1
ICH4: not 100% native mode: will probe irqs later
    ide0: BM-DMA at 0xfc00-0xfc07, BIOS settings: hda:DMA, hdb:DMA
    ide1: BM-DMA at 0xfc08-0xfc0f, BIOS settings: hdc:pio, hdd:DMA
HPT370A: IDE controller on PCI bus 03 dev 00
HPT370A: detected chipset, but driver not compiled in!
PCI: Enabling device 03:00.0 (0005 -> 0007)
HPT370A: chipset revision 4
HPT370A: not 100% native mode: will probe irqs later
    ide2: BM-DMA at 0xbc00-0xbc07, BIOS settings: hde:pio, hdf:pio
    ide3: BM-DMA at 0xbc08-0xbc0f, BIOS settings: hdg:pio, hdh:pio
hda: MAXTOR 6L080J4, ATA DISK drive
hdb: MAXTOR 6L080J4, ATA DISK drive
hdd: LITE-ON LTR-40125S, ATAPI CD/DVD-ROM drive
hde: WDC WD2000JB-00EVA0, ATA DISK drive
hdg: WDC WD2000JB-00EVA0, ATA DISK drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
ide1 at 0x170-0x177,0x376 on irq 15
ide2 at 0xcc00-0xcc07,0xc802 on irq 16
ide3 at 0xc400-0xc407,0xc002 on irq 16
blk: queue c035b4a4, I/O limit 4095Mb (mask 0x)
hda: 156355584 sectors (80054 MB) w/1819KiB Cache, CHS=9732/255/63,
UDMA(100)
blk: queue c035b5f0, I/O limit 4095Mb (mask 0x)
hdb: 156355584 sectors (80054 MB) w/1819KiB Cache, CHS=9732/255/63,
UDMA(100)
hde: lost interrupt
hde: lost interrupt
hde: lost interrupt
hde: lost interrupt
hde: 390721968 sectors (200050 MB) w/8192KiB Cache, CHS=24321/255/63
hde: lost interrupt
hde: lost interrupt
hdg: lost interrupt
hdg: lost interrupt
hdg: lost interrupt
hdg: lost interrupt
hdg: 390721968 sectors (200050 MB) w/8192KiB Cache, CHS=24321/255/63
hdg: lost interrupt
hdg: lost interrupt
Partition check:
 hda: hda1 hda2 hda3 hda4 < hda5 hda6 hda7 hda8 >
 hdb: unknown partition table
 hde:hde: lost interrupt

 hdg:hdg: lost interrupt

.  and later in the boot  ...


scsi0 : SCSI host adapter emulation for IDE ATAPI devices
  Vendor: LITE-ON   Model: LTR-40125S    Rev: ZS0K
  Type:   CD-ROM ANSI SCSI revision: 02
Attached scsi CD-ROM sr0 at scsi0, channel 0, id 0, lun 0
sr0: scsi3-mmc drive: 48x/48x writer cd/rw xa/form2 cdda tray
Uniform CD-ROM driver Revision: 3.12
Device Driver for HPT37x2 ATA RAID Controller
Version 1.31, Compiled Nov 24 2003 08:58:36
Found Controller: HPT370 UDMA/ATA100 RAID Controller
scsi1 : hpt37x2
  Vendor: HPT Inc.  Model: HPT37x2   RAID 1  Rev: 1.05
  Type:   Direct-Access  ANSI SCSI revision: 02
Attached scsi disk sda at scsi1, channel 0, id 0, lun 0
SCSI device sda: 390721968 512-byte hdwr sectors (200050 MB)
 sda:





RocketRAID 100 and Linux Booting - HELP!

2003-12-05 Thread Keith Goettert




I don't see anywhere information on setting up the booting of Linux
with the RocketRAID.  I tried to write the MBR of the designated BOOT
drive and even though lilo said that it had done it, I get a never
ending flow of 01's on the screen instead of a lilo boot screen.

More information:

The operating system is a Linux2.4.20 Kernel compiled from kernel.org
source.  The distribution is Debian 3.0 (but like I said, I built my
own kernel) and I am using the standard lilo distribution that came
with it.

The RR100 is in a P4 2.4GHz and supports two 200G WesternDigital Drives
(each on its own Cable as the master.)

Additionally, there are two 80G Maxtors on the MSI motherboards IDE
controllers (one is shared with the CD/RW)

The RR100 is a new addition and intended to replace the two 80G's

The system currently boots to the first 80G and I built a kernel with
the Open Source RR100 RAID driver and it works great.  I can see the
two 200G drives as a SINGLE (RAID1) 200G SCSI drive.  I was able to
partition, format and copy the full system from the 80G drives to the
200G drive.

Now I am attempting to write a boot record to the RAID array so that I
can remove the two 80G drives.  

As part of making the boot process work, I also compiled IDE HPT370
support into the kernel.   Without it, the native IDE driver would see
the HPT370 chips and try to enable the drives.  This would result in
multiple "interrupt lost" errors.  Now with the support compiled in,
the errors are gone and the SCSI device still works great.

My first attempt at making the system boot was to tell lilo to write
the MBR to the /dev/sda device (RR100).
 didn't work (and I figure its because the SCSI driver
does not load till after the boot)
My second attempt was to have lilo write the MBR to /dev/hde (RR100
first IDE drive)
 didn't work
My final attempt was to have lilo write the MBR to /dev/hdg (RR100
second IDE drive)
  didn't work

Before each attempt at booting, I disabled the two 80G drives (they are
in carriers so I just unjack them) and this leaves the RR100 as the
only harddrive in the system (I confirmed this in the bios).  I have
also gone into the RR100 bios and set the first drive of  the set to be
the Boot Drive.

So now I have had lilo on all occasions tell me that the MBR was
updated successfully only to have the system boot and display a never
ending stream of  01 01 01's to the console.

Any ideas would be greatly appreciated...   Here is some output from a
lilo run

[EMAIL PROTECTED]:/home/keith# dpkg-reconfigure lilo
Running /usr/sbin/liloconfig

LILO, the LInux LOader, sets up your system to boot Linux directly
from your hard disk, without the need for a boot floppy.

You already have a LILO configuration in the file /etc/lilo.conf

Checking your /etc/lilo.conf for incompatible options...

Install a boot block using your current LILO configuration? [Yes] 

  
==
WARNING: Even if lilo runs successfully, see
/usr/share/doc/lilo/INCOMPAT.gz
 for changes in the usage of the /etc/lilo.conf file.
 If needed: edit /etc/lilo.conf and rerun '/sbin/lilo -v'

Running lilo...
LILO version 22.2, Copyright (C) 1992-1998 Werner Almesberger
Development beyond version 21 Copyright (C) 1999-2001 John Coffman
Released 05-Feb-2002 and compiled at 20:57:26 on Apr 13 2002.
MAX_IMAGES = 27

Reading boot sector from /dev/hde
Warning: /dev/hde is not on the first disk
Merging with /boot/boot-menu.b
Boot image: /vmlinuz -> /boot/vmlinuz-2.4.20-idepci
Added Linux_2.4.20

Boot image: /vmlinuz.raid -> /boot/vmlinuz-2.4.20-raid
Added RAID.2.4.20 *

Boot image: /vmlinuz.old -> /boot/vmlinuz-2.2.20-idepci
Added Linux_2.2.20

/boot/boot.2100 exists - no backup copy made.
Writing boot sector.


And the top of the lilo.conf file that produced it.
# Support LBA for large hard disks.
#
lba32

# Overrides the default mapping between harddisk names and the BIOS'
# harddisk order. Use with caution.
#disk=/dev/hde
#    bios=0x81

#disk=/dev/sda
#    bios=0x80

# Specifies the boot device.  This is where Lilo installs its boot
# block.  It can be either a partition, or the raw device, in which
# case it installs in the MBR, and will overwrite the current MBR.
#
boot=/dev/hde

# Specifies the device that should be mounted as root. (`/')
#
root=/dev/sda1

And the IDE and SCSI section of the boot screen (when booting off the
80G drive)

Uniform Multi-Platform E-IDE driver Revision: 6.31
ide: Assuming 33MHz system bus speed for PIO modes; override with
idebus=xx
ICH4: IDE controller on PCI bus 00 dev f9
PCI: Device 00:1f.1 not available because of resource collisions
ICH4: BIOS setup was incomplete.
ICH4: chipset revision 1
ICH4: not 100% native mode: will probe irqs later
    ide0: BM-DMA at 0xfc00-0xfc07, BIOS settings: hda:DMA, hdb:DMA
    ide1: BM-DMA at 0xfc08-0xfc0f, BIOS settings: hdc:pio, hdd:DMA
HPT370A: IDE controller on 

Initrd - cramfs image is not being recognized by 2.4.20 kernel

2003-12-17 Thread Keith Goettert



I have a kernel 
built from kernel.org source.  I have included support for ramdisk, initial 
ramdisk, and cramfs.
 
I built a ram disk 
image using mkinitrd
 
I can mount the 
image and list directories and files in it by using mount -o loop rdimage 
mntpnt
 
So, it looks like it 
is functional.  Additionally, when I look at the mount I 
see:
 
/boot/raidrd.img on 
/initrd type cramfs (rw,loop=/dev/loop0)
 
Again, this looks 
fine.
 
In my lilo.conf I 
have placed:
 
image=/vmlinuz.raid    
label=RAID.2.4.20    
read-only    append="hde=noprobe 
hdf=noprobe hdg=noprobe 
hdh=noprobe"    
initrd=/boot/raidrd.img
 
And when I run lilo 
-v 3 I get:
 
 
Boot image: 
/vmlinuz.raid -> /boot/vmlinuz-2.4.20-raidDevice 0x0301: BIOS drive 0x80, 
255 heads, 9732 
cylinders,   
63 sectors. Partition offset: 63 sectors.Using Volume ID 17E81084 on bios 
80Setup length is 5 sectors.Mapped 2001 sectors.Mapping RAM disk 
/boot/raidrd.imgDevice 0x0301: BIOS drive 0x80, 255 heads, 9732 
cylinders,   
63 sectors. Partition offset: 63 sectors.Using Volume ID 17E81084 on bios 
80RAM disk: 1832 sectors.Added RAID.2.4.20 *    
    "ro root=301 
hde=noprobe hdf=noprobe hdg=noprobe hdh=noprobe"
 
 
 
All indications are 
that Lilo is mapping the rdimage to the proper place.
 
BUT, when I boot, I 
get:
 
 
 ... (lotza 
stuff)...
RAMDISK driver 
initialized: 16 RAM disks of 4096K size 1024 blocksizeloop: loaded (max 8 
devices) ...(lotza stuff) ...
RAMDISK: Couldn't 
find valid RAM disk image starting at 0.Freeing initrd memory: 916k 
freed
 
I have run out of 
ideas.  Everything appears to be according to the initrd, mkinitrd, and 
lilo man pages.   Could my problem be with versions?  I am using 
the latest lilo (24), a 2.4.20 kernel and whatever mkinitrd and mkcramfs came 
with debian 3.  Is there a flag I can set in my lilo.conf file that will 
cause the kernel to be more chatty about why there is no 
love?
 
 
 


Kernel build problems 2.2.17 - No modversion.h

2000-08-11 Thread Keith Goettert

After completing successfully a full install of the Debian 2.2.17 product
with optional kernel packages I am unable to locate the modversions.h header
file.  Could somebody please tell me what package this little gem is tucked
away in.



Re: Initrd - cramfs image is not being recognized by 2.4.20 kernel

2003-12-18 Thread Keith Goettert




My support of cramfs was complied into the kernel, but it still would
not work.  A very telling sign that it was compiled in was its
complaint that it couldn't find a valid filesystem in the boot messages
(which according to my readings is also a disputed and unresolved
bug/feature.)  Now I have redone the initrd image as an uncompressed
ext2 fs.  I am still not home free (many many errors that need to be
checked) but it does appear to be mounting it.  STAY TUNED this is
going to be a HOWTO when I'm done.  I can't believe the number of hours
this has taken!

Thomas Krennwallner wrote:

  Hi!

On Wed Dec 17, 2003 at 07:07:14PM -0800, Keith Goettert wrote:
  
  
I have a kernel built from kernel.org source.  I have included support
for ramdisk, initial ramdisk, and cramfs.
 
I built a ram disk image using mkinitrd

  
  
The vanilla linux kernels don't support cramfs. See mkinitrd(8):

By  default  mkinitrd  will  generate a CRAMFS image.  This is not cur-
rently supported by Linux.  However,  the  Debian  prepackaged  kernels
have been patched to support it.  You can also generate an initrd image
of another type by changing the MKIMAGE setting in mkinitrd.conf.

So long
Thomas

  





Re: Suggestions on choosing an IMAP server

2003-07-16 Thread Keith Goettert




If you go with courier, make sure you increase the number of
connections.  Several email readers have real heartburn if this is set
to low.  I have set mine to 10.

Jamin W. Collins wrote:

  On Wed, Jul 16, 2003 at 04:07:57PM -0700, Mike Fedyk wrote:

  
  
I'm going to switch from pop3 to imap, and I'd like to know what you
guys think is the best debian packaged IMAP server, and why.

I'd really like to use MailDir mailboxes.

  
  
Don't know if it's the "best", but I use courier-imap and
courier-imap-ssl.  Why? They supported what I wanted (Maildirs) and they
worked immediately after install.

  





ldap_default_servers - anybody got an example?

2003-07-17 Thread Keith Goettert
I would like to use the ldap_default_servers configuration setting with 
my ldap querry.  So far I have been unable to discern how the variable 
replaces itself into a search.

Here is my settings

ldap_default_servers = localhost::389:www.anotherhost.com::389

and latter in a router...

condition = ${lookup ldap {/ou=AList,dc=alistmail,dc=net? .

This doesn't work.  I get the error...

LDAP query error: unknown parameter "/ou=" precedes LDAP URL



--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]