sendmail install issue
by Charles Dillard
I am running Fedora 7 kernel 2.6.21-1.3194.fc7. I am trying to get sendmail 8.14.1-2.i386.rpm working. The Build of the sendmail.cf file
using this command
m4 /usr/share/sendmail-cf/m4/cf.m4 sendmail.mc > sendmail.cf
appears to be successful; it produces a sendmail.cf file. Running the command
make install-cf
produces the following error:
../../devtools/bin/install.sh -c -o root -g bin -m 0444 sendmail.cf /etc/mail/sendmail.cf
make: ../../devtools/bin/install.sh: Command not found
make: *** [install-sendmail-cf] Error 127
There is no "devtools" in my distribution (which includes the accompanying sendmail-cf 8.14.1-2.i386.rpm).
Any ideas on where this can be obtained? Also, the README mentions an INSTALL file that would be helpful that is also missing.
df -k tells me I have plenty of drive space.
Many thanks for anyone providing meaningful insight, and especially if someone can provide the missing INSTALL file.
BTW, I've uninstalled and installed the sendmail rpms several times, w/o luck.
CTD
---------------------------------
Moody friends. Drama queens. Your life? Nope! - their life, your story.
Play Sims Stories at Yahoo! Games.
16 years, 7 months
Re: shell security
by tony.chamberlain@lemko.com
I am making the bash program to be executed via "sudo"
>Why do you have the permissions on your root directory and its contents
>that an ordinary user can erase?
**********************************
16 years, 7 months
convert file.wmv to .wav ?
by Bob Goodwin
Can someone tell me how to convert audio .wmv to .wav, .mp3, or .ogg?
I tried ImageMagick 'convert' but I don't seem to be able to make it
work, perhaps because I don't have the command right? As usual I'm
having trouble with the man page ...
Or there may be a better way to do this. I have an audio file in .wmv
that I would like to compress, it's not very important but I hate to let
it go undone.
Bob Goodwin
16 years, 7 months
service-network-restart
by david walcroft
Every time I use this command in my shell I get disconnected from the net
and have to reboot if I'm to use the net.
Thanks david
16 years, 7 months
How to create initrd.img to boot LVM-on-RAID0?
by Dean S. Messing
I'm having the devil of a time trying to boot off
an "LVM-on-RAID0" device.
I've created a software RAID-0, defined a Volume Group on in with
(currently) a single logical volume, and copied my entire
installation onto it, modifying the copied fstab to reflect where
the new "/" is.
I created a new initrd with:
mkinitrd --preload raid0 --with=raid0 initrd_raid.img 2.6.22.5-76-fc7
Note: the LVM modules are getting included in the initrd "for free"
because I'm currently running on a non-raid LV-managed file system.
I added a stanza to grub.conf for the new initrd.img.
But the thing won't boot. From the boot messages it appears to not
be starting the array, so when it goes to scan for LVs it doesn't
find the one that's sitting on top of the array where root lives.
Are there instructions for how to make this work? I've googled for
a couple of hours, tried a bunch of stuff, but can't get it to
work. From what I've read I suspect I must hand-tweek the "init"
file in the initrd.
Surely there is "a right way" to do this.
Dean
16 years, 7 months
Error: kernel cannot suspend to ram.
by Paul Smith
Dear All,
When running on the console the command 'pm-suspend', I get the following:
$ pm-suspend
Error: kernel cannot suspend to ram.
$
Any ideas?
Thanks in advance,
Paul
16 years, 7 months
Re: fedora 7 - dmesg
by Antonio Olivares
----- Original Message ----
From: Antonio Olivares <olivares14031(a)yahoo.com>
To: For users of Fedora <fedora-list(a)redhat.com>
Sent: Wednesday, October 3, 2007 5:01:20 PM
Subject: Re: fedora 7 - dmesg
> ----- Original Message ----
> > From: ann kok <annkok2001(a)yahoo.com>
> > To: fedora-list(a)redhat.com
> > Sent: Wednesday, October 3, 2007 1:31:05 PM
> > Subject: fedora 7 - dmesg
> >
>
> > Hi all
> >
> > I got the following from dmesg in my fedora 7 desktop.
> > ls it normal?
> Yes it is if you are running the default kernel that came with Fedora 7 which is 2.6.21-1.3194.fc7
> Known bug cannot remember BZ#
Here it is:
https://bugzilla.redhat.com/show_bug.cgi?id=240982
>
> You need to get the latest kernel and update your system to avoid seeing this.
>
> >
> > Thank you
> >
> > BUG: warning at kernel/softirq.c:138/local_bh_enable()
> > (Not tainted)
> > [<c042b0cf>] local_bh_enable+0x45/0x92
> > [<c06002bd>] cond_resched_softirq+0x2c/0x42
> > [<c059adf3>] release_sock+0x4f/0x9d
> > [<c05c670d>] tcp_sendmsg+0x90b/0x9f9
> > [<c05dec95>] inet_sendmsg+0x3b/0x45
> > [<c0598731>] sock_aio_write+0xf6/0x102
> > [<c04754ee>] do_sync_write+0xc7/0x10a
> > [<c0436e71>] autoremove_wake_function+0x0/0x35
> > [<c0475d47>] vfs_write+0xbc/0x154
> > [<c0476342>] sys_write+0x41/0x67
> > [<c0404f70>] syscall_call+0x7/0xb
> > =======================
Update your system and you should not see this anymore.
Regards,
Antonio
____________________________________________________________________________________
Don't let your dream ride pass you by. Make it a reality with Yahoo! Autos.
http://autos.yahoo.com/index.html
16 years, 7 months
Re: fedora 7 - dmesg
by Antonio Olivares
----- Original Message ----
> From: ann kok <annkok2001(a)yahoo.com>
> To: fedora-list(a)redhat.com
> Sent: Wednesday, October 3, 2007 1:31:05 PM
> Subject: fedora 7 - dmesg
>
> Hi all
>
> I got the following from dmesg in my fedora 7 desktop.
> ls it normal?
Yes it is if you are running the default kernel that came with Fedora 7 which is 2.6.21-1.3194.fc7
Known bug cannot remember BZ#
You need to get the latest kernel and update your system to avoid seeing this.
>
> Thank you
>
> BUG: warning at kernel/softirq.c:138/local_bh_enable()
> (Not tainted)
> [<c042b0cf>] local_bh_enable+0x45/0x92
> [<c06002bd>] cond_resched_softirq+0x2c/0x42
> [<c059adf3>] release_sock+0x4f/0x9d
> [<c05c670d>] tcp_sendmsg+0x90b/0x9f9
> [<c05dec95>] inet_sendmsg+0x3b/0x45
> [<c0598731>] sock_aio_write+0xf6/0x102
> [<c04754ee>] do_sync_write+0xc7/0x10a
> [<c0436e71>] autoremove_wake_function+0x0/0x35
> [<c0475d47>] vfs_write+0xbc/0x154
> [<c0476342>] sys_write+0x41/0x67
> [<c0404f70>] syscall_call+0x7/0xb
> =======================
Regards,
Antonio
____________________________________________________________________________________
Be a better Heartthrob. Get better relationship answers from someone who knows. Yahoo! Answers - Check it out.
http://answers.yahoo.com/dir/?link=list&sid=396545433
16 years, 7 months
Subject: Re: How to force a (SATA) drive to be sda and the PATA one, sdb
by R. G. Newbury
Alfredo Ferrari wrote:
Thanks a lot for the answer. I tried to work with the initial ramdisk, I
managed to edit the init and, sigh, there is no ide module loaded,
apparently the libata + ata_piix do both PATA and SATA in recent kernels,
so apparently there is no obvious way to get the disks in the "right"
order. Googling a bit I found other people complaining that PATA's are
recognized before SATA's now... so I am still with my problem.
Labels are fine for ext3 partition and no automount, while I have Windows
partitions as well, and a lot of partition with automount (just because
the second disk is there sometimes yes sometimes no)
_________________________________________________________________________
Well, I'm glad to know that I',m not the only one hurting...although my
problem was the opposite way round. A PATA drive which I wanted to boot
from, and 2 SATA drives as data drives. This on Fedora 8 rc2.
I was eventually able to get the BIOS of the motherboard, an ASUS P5L-MX
to recognize things in the correct order, but (and this is why I have
commented) it ALSO took installing the SATA drives on sockets 2 and 4 of
the four SATA connectors..
Apparently the SATA connectors are paired: #1 is a MASTER, #2 a SLAVE,
#3 a MASTER and #4 a SLAVE. By mounting the PATA drive as the PATA IDE
MASTER (and the CDROM as Slave) the system saw ONLY the one master
driver....Which is a good thing, as the data drives are not bootable!.
But it did take more than a couple of reboots into the BIOS, and 2
'break-ins' to box, before I figured that out. Symptom was that one data
disk was visible, and one not. Swapping cables at the drives, swapped
the problem. Swapping cables at the mb, swapped the problem..so I
figured that the mb socket was bad..tried another socket. Success.
Then, of course, and only then, did I find the Manual!....
Geoff
16 years, 7 months