Hello All:
I am having a problem trying to get my new kernel image to boot. I have
recompiled the kernel for IPTables/NAT support and after I do a make dep
clean bzImage, make modules, make bzlilo and make modules_install..I copy
the old kernel over to vmlinuz.old and make the new bzImage the vmlinuz and
adjust the lilo.conf file accordingly. I then restarted lilo and
rebooted...it will get only a little ways before it comes up with "could not
mount root", please specify differnt area for root=
I have gone over this several times and keep getting the same problem. What
step am I missing here? Anyone's help is greatly appreciated.
Thanks
Traci
Hi List!
On my SuSE 6.2 Box (all relevant security patches installed) I tried to
change the password for a user.
server:~ # passwd bruni
passwd: Module is unknown
server:~ # cd /var/log
server:/var/log # tail warn
Oct 30 20:36:32 server passwd[21887]: PAM unable to
dlopen(/lib/security/pam_pwcheck.so)
Oct 30 20:36:32 server passwd[21887]: PAM [dlerror:
/lib/security/pam_pwcheck.so: cannot open shared object file: No such file
or directory]
Oct 30 20:36:32 server passwd[21887]: PAM adding faulty module:
/lib/security/pam_pwcheck.so
After re-installing the pam.rpm the same error occured while changing
password.
Any ideas how solve this problem?
Cheers,
Boris.
Hi all,
There's been a request to have attachments in postings stripped
before being sent off in the interest of keeping ISPs from blocking
posts because of "dangerous content". In this case, it was post a
during the recent discussion on (ironically enough) regexes in
postfix's body_checks that contained an empty file named
AUTOEXEC.BAT, that was sent in order to test a postfix configuration.
Personally, I'm all for stripping removing attachments and rejecting
posts that consist only of a MIME attachment because they annoy me,
but I think I'm in the minority. Of course, we don't have to block
all attachments but just the "dangerous" ones.
I'd appreciate any thoughts you may have on this but, in the
interest of subscribers that aren't interested or don't care, please
send them directly to ml-admin(a)suse.com and not the list.
Thanks,
--
-ckm
Hi List..
As I do not want to have default kernel and I also have not so much
compiled inside, I have installed lx_sus22-2.2.19-SuSE-103.i386.rpm
So I start to compile it with my previous configuration (before I use also
2.2.19) and during making bzImage I have got following error list:
kernel/kernel.o: In function `context_thread':
kernel/kernel.o(.text+0xc4): undefined reference to `memset'
kernel/kernel.o: In function `flush_scheduled_tasks':
kernel/kernel.o(.text+0x308): undefined reference to `memset'
kernel/kernel.o: In function `__down':
kernel/kernel.o(.text+0x21b4): undefined reference to `memset'
kernel/kernel.o: In function `__down_interruptible':
kernel/kernel.o(.text+0x2258): undefined reference to `memset'
kernel/kernel.o: In function `sys_wait4':
kernel/kernel.o(.text+0x8a29): undefined reference to `memset'
fs/fs.o(.text+0x3695): more undefined references to `memset' follow
make: *** [vmlinux] Error 1
Does anybody have any idea??
I can send the whole kernel config of course, but the same config is OK for
previous release of kernel 2.2.19 (without this bug fixed). And I also
tried to recompile the previous one (after I got this error on new one) -
and it is still OK.. So this looks like some general problem in this kernel
source distribution...
Regards
Marcin Gryszczuk
Hello,
We've been getting strange reboots which were formerly attributed to a
a possible bad UPS. This is a brand new install (I know anything is
possible, but..) Does this look strange?
Oct 23 15:22:14 callisto in.ftpd[722]: connect from 212.56.149.116 (212.56.149.116)
Oct 23 15:28:40 callisto init: Switching to runlevel: 6
Oct 23 15:28:44 callisto sshd[234]: Received signal 15; terminating.
Oct 23 15:28:44 callisto kernel: Kernel logging (proc) stopped.
Oct 23 15:28:44 callisto kernel: Kernel log daemon terminating.
Oct 23 15:28:45 callisto exiting on signal 15
Oct 23 15:29:55 callisto syslogd 1.3-3: restart.
.....
Oct 30 00:15:18 callisto su: (to nobody) root on none
Oct 30 00:15:18 callisto PAM-unix2[6375]: session started for user nobody, service su
Oct 30 00:15:24 callisto PAM-unix2[6375]: session finished for user nobody, service su
Oct 30 00:36:11 callisto init: Switching to runlevel: 6
Oct 30 00:36:12 callisto PAM-unix2[4230]: session finished for user root, service su
Oct 30 00:36:15 callisto sshd[233]: Received signal 15; terminating.
Oct 30 00:36:15 callisto kernel: Kernel logging (proc) stopped.
Oct 30 00:36:15 callisto kernel: Kernel log daemon terminating.
Oct 30 00:36:16 callisto exiting on signal 15
Oct 30 00:37:30 callisto syslogd 1.3-3: restart.
.....
-Brian
Hi all
i got the following messages in the message file and was wondering what it
really means?
nobrain kernel:martian source 0100007f for ffffffff, dev eth0
nobrain kernel:ll header ff ff ff ff ff ff 00 d0 59 2e 3b 65 08 00
Thanks
Marios
_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp
One more off-topic comment:
Adaptec AHA-2400 IDE Raid supports 4 IDE ATA 100 drives with Raid5 and runs
under Linux (SuSE 7.2 and 7.3). I have one 120 GB Raid5 with 4 x 40 GB IDE
and 1 cold standby running 3 partitions /boot (ext3), / (reiser) and /data
(reiser) and it runs smothly since more than 2 months.
Greets,
Remo Pini
> -----Original Message-----
> From: Keith Hopkins [mailto:hne@inetnow.net]
> Sent: Tuesday, October 30, 2001 2:09 PM
> To: John Andersen
> Cc: gt(a)src-gmbh.de; Simon Oliver; suse-security(a)suse.com
> Subject: Re: AW: [suse-security] raid on what
>
>
> Guido Tschakert wrote:
>
> > Am Dienstag, 30. Oktober 2001 12:00 schrieb Simon Oliver:
> >
> >>If you need to buy an additional controller why not get a simple IDE
> >>RAID controller, offering RAID 0 + 1? You would need to
> but an extra
> >>disk too for RAID 0 + 1. This allows you to stripe and
> mirror accross
> >>the channels providing better performance and protection.
> >>
> >>
> > Hi,
> > correct me if I'm wrong:
> > As far as I know, no IDE-RAID-Controller is supported by linux.
> > And btw: is this question really security-related in terms
> of these list?
> >
>
> I've had excellent luck with IWill's SIDE-RAID100 card, and
> very little luck with the Promise 20265R chip found on many
> motherboards.
>
> http://www.iwillusa.com/products/spec.asp?ModelName=SIDE-RAID1
> 00&SupportID=
> http://support.iwill.net/download.asp?path=drivers&file=r100_drv.exe
>
> There is even a handy utility you can monitor your array with
> (like AMI' Megaraid Manager)
> http://support.iwill.net/download.asp?path=drivers&file=r100_lnx.exe
>
> Don't ask me why these are .exe files, but you can unzip them
> in Linux. :-)
>
> But, since you want RAID5, the HW RAID features of the IWill
> card will not help you, but it makes for a nice (inexpensive)
> Ultra100 controller, especially with the monitoring utility.
>
> I assume your are wanting MD Software RAID, correct?
>
> The biggest advantage of LVM for me, is the ability to
> increase the size of a (logical) partition on the disk! Of
> course, if your partition is the same size as whole RAID
> volume, this doesn't help any. Another benefit, if you
> actually make backups of production systems, is the Snapshot feature.
>
> More about LVM on Linux from the source:
> http://www.sistina.com/lvm_howtos/lvm_howto/
> http://www.sistina.com/lvm_howtos/lvm_howto/Why_would_I_want_it.html
> http://tech.sistina.com/cgi-bin/lvm-faqprocessor.cgi?q=Where%2
0can%20I%20find%20more%20information%20about%20the%20Logical%20Volume%20Mana
ger%20for%20Linux%3F
As for LVM, if you are using your
Lost in Tokyo,
Keith
(No, it's not really security related.)
--
"hne(a)inetnow.net" Copyright 1996-2001. Not for distribution without express
permission.
--
To unsubscribe, e-mail: suse-security-unsubscribe(a)suse.com
For additional commands, e-mail: suse-security-help(a)suse.com
-----Ursprüngliche Nachricht-----
>Von: John Andersen [mailto:jsa@pen.homeip.net]
>Gesendet am: Dienstag, 30. Oktober 2001 09:23
>An: suse-security(a)suse.com
>Betreff: [suse-security] raid on what
>Using Suse 7.3, I'm planning a raid (5) server instalation
>and was planing to use reiserfs partitions on three drives
>connected each to a different ide controller.
>Any problems with this?
No if all of them are master without a slave device on the same cable.
>Is reiserfs a suitable partition for raid?
>any other suggestions?
Reiserfs is fine, but you have first to partition the disks, then you define
the raid-array and don´t format it, if you plan to use LVM! At this point
you leave it as ext2. With LVM you can partition the raid-array. Use yast2
for installation. Yast1 can´t configure raid.
>--
>__________________________________________
>J.Andersen
--
To unsubscribe, e-mail: suse-security-unsubscribe(a)suse.com
For additional commands, e-mail: suse-security-help(a)suse.com