A welcoming email
by Stefano L. Sordini
Hello, my name is Stefano Sordini and am new to this mailing list. I
want to ask if this mailing list is safe from viruses etc.. Hope admins
have installed a quite strong firewall and filters :)
Thanks,
--
Stefano L. Sordini
University Of Athens
Computer Science Dept
http://www.netshop-isp.com
19 years, 6 months
Recent Fedora Core kernels (plus my SPEC file for 2.6.8-1.541 with Athlon support)
by Bryan Smith
Is there a document or page that details all of the changes in how
recent Fedora Core kernels are built? I've noticed several changes, and
I want to verify I understand them all. I apologize as I've seen some
traffic, but I can't seem to find a definite answer (I'm sure I just
passed over it).
Specifically:
1. The "sourcecode" package, which is now ARCH="noarch"
Assumption:
I assume the package name change was because the ARCH has changed.
Additional Q:
Why is the "sourcecode" package not built by default when
"--target=noarch" is passed? I.e.,
%ifarch noarch
%define builddoc 1
%define buildsource 0
^^^
2. There is another variable in EXTRAVERSIONS, defaults to "root"
Assumption:
I assume this is to differentiate between UML (User Mode Linux)
kernels (so the same build system can be used)?
Additional Q:
Is this a stock kernel change? Or Red Hat only?
3. Athlon no longer a build option at all in the SPEC file
Assumption:
Are there support issues with this? Or was it another reasoning?**
Additional Q:
Is there any reason why we can't "patch back in" just the few changes
into the SPEC so one can build Athlon kernels easily with
"--target=athlon"?
[ **BTW, I'm fully aware that the i686 kernel runs fairly optimized on
Athlon. But turning off the generic support, and optimizing for K7
makes a significant difference for me in engineering applications. ]
Also, to add in Athlon support, you don't have to make it part of the
"all_x86" set. In fact, I made Athlon a separate build conditional on
its own in my own spec file (for 2.6.8-1.541) here (along with a few
other changes):
http://www.vaporwarelabs.com/files/temp/kernel-2.6.8-1.541BS.spec
And for those that want to build Athlon optimized kernels, the .config
files are here:
http://www.vaporwarelabs.com/files/temp/kernel-2.6.8-athlon.config
http://www.vaporwarelabs.com/files/temp/kernel-2.6.8-athlon-smp.config
--
Bryan J. Smith b.j.smith(a)ieee.org
------------------------------------------------------------------
"Communities don't have rights. Only individuals in the community
have rights. ... That idea of community rights is firmly rooted
in the 'Communist Manifesto.'" -- Michael Badnarik
19 years, 6 months
FC2 won't boot on battery!!
by Dave Oxley
I have FC2 (with all updates) installed on an Inspiron 8600. The machine
works fine when plugged into the mains but will not boot when running on
betteries. It gets to 'Setting up local disks' and hangs. Does anyone
know how I can solve this?
Cheers.
Dave.
19 years, 7 months
[Fwd: Mailman hostname]
by Rodolfo J. Paiz
Hello, all:
Resending this message since I haven't seen it show up on the list since
Friday. Thanks for any pointers anyone can offer!
-----Forwarded Message-----
> From: Rodolfo J. Paiz <rodolfo(a)merkdeo.com>
> To: fedora-list(a)redhat.com
> Subject: Mailman hostname
> Date: Fri, 27 Aug 2004 08:50:31 -0600
>
> Hi!
>
> Does anyone know where I can change mailman's hostname for internal
> URL's in its pages? I changed the hostname of my server, but the links
> on mailman admin pages are still constructed with the old hostname so
> they're broken.
>
> No, keeping the old hostname around is not an option.
>
> In this case, I would appreciate replies both on-list and CC'd to my
> address. I'm having some trouble checking all my mail.
>
> Thanks in advance!
--
Rodolfo J. Paiz <rpaiz(a)simpaticus.com>
Simpaticus.com
19 years, 7 months
About Trash bin
by Christian Loza
Hi,
Anyone knows how to correct the icon of the trash bin in KDE? It appears
to be always full.
Thanks,
Christian
--
Christian Loza <christianl(a)unete.com.bo>
UNETE Telecomunicaciones Ltda.
19 years, 7 months
hack attempt on my server...What do you do about this?
by Jonathan T. Steadman
Sorry this is yet another lame question, but I am new to hosting web
server ect. just kinda experimenting actually and in my logs i came
across some garbage (its at the bottom of this email) what do you do
about this? Just let it be? inform ISP? wait and see if it is more
continuous? dont know the proper thing to do i guess just making sure
with you guys.
Jul 17 14:42:24 localhost sshd[6746]: Illegal user test from
130.120.81.14
Jul 17 14:42:26 localhost sshd[6746]: Failed password for illegal user
test from 130.120.81.14 port 48692 ssh2
Jul 17 14:42:27 localhost sshd[6748]: Illegal user guest from
130.120.81.14
Jul 17 14:42:30 localhost sshd[6748]: Failed password for illegal user
guest from 130.120.81.14 port 48753 ssh2
Jul 17 14:42:31 localhost sshd[6750]: Illegal user admin from
130.120.81.14
Jul 17 14:42:33 localhost sshd[6750]: Failed password for illegal user
admin from 130.120.81.14 port 48807 ssh2
Jul 17 14:42:34 localhost sshd[6752]: Illegal user admin from
130.120.81.14
Jul 17 14:42:37 localhost sshd[6752]: Failed password for illegal user
admin from 130.120.81.14 port 48849 ssh2
Jul 17 14:42:38 localhost sshd[6754]: Illegal user user from
130.120.81.14
Jul 17 14:42:40 localhost sshd[6754]: Failed password for illegal user
user from 130.120.81.14 port 48879 ssh2
Jul 17 14:42:43 localhost sshd[6756]: Failed password for root from
130.120.81.14 port 48900 ssh2
Jul 17 14:42:47 localhost sshd[6758]: Failed password for root from
130.120.81.14 port 48913 ssh2
Jul 17 14:42:50 localhost sshd[6760]: Failed password for root from
130.120.81.14 port 48924 ssh2
Jul 17 14:42:51 localhost sshd[6762]: Illegal user test from
130.120.81.14
Jul 17 14:42:54 localhost sshd[6762]: Failed password for illegal user
test from 130.120.81.14 port 48931 ssh2
19 years, 7 months
Squid Performance - Default Options Tweak?
by fedora.kh@undp.org
Dear all:
I am installing Squid on RedHat 9 out of the Distro CDs on a Dell PowerEdge
1300 Server, Pentium III RAM 256MB. I've been trying it out for 1 week now
with the default options. It seems very slow.
Could someone guide me with some useful tips to tweak the default options of
the /etc/squid/squid.conf file for better performance?
Also, I installed BIND to act as the DNS server; but i configured it to
forward queries to my ISP DNS. Could this be the major traffic block to my
connection to ISP?
Since I started to use Squid and BIND, my ISP notified me that, my 1Mbps
leased-line connection has always been saturated.
Could it be because of Squid or DNS forwarding or a virus?
Regards,
Vidol
19 years, 7 months
Postfix smtpd killed by signal 11: bad command startup
by Jonas De Vuyst
Hi,
I was hoping someone could help me out with a Postfix-problem that I
ran into after upgrading from FC1 to FC2. I did Google around first
but found nothing that really got me closer to a fix. Below are some
of my findings.
rpm -q postfix: postfix-2.0.18-4
What works:
- echo Message | mail someone@otherserver
- echo Message | mail someone@myserver
What broke:
- incoming e-mail
- outgoing e-mail when using smtpd
The /var/log/maillog error:
Oct 31 00:28:24 foobar postfix/smtpd[25296]: running:
PATH=/bin:/usr/bin:/usr/local/bin; export PATH; (echo cont;
echo where) | gdb /usr/libexec/postfix/smtpd 25296 2>&1
>/etc/postfix/smtpd.25296.log & sleep 5
Oct 31 00:28:29 foobar postfix/master[25291]: warning: process
/usr/libexec/postfix/smtpd pid 25296 killed by signal 11
Oct 31 00:28:29 foobar postfix/master[25291]: warning:
/usr/libexec/postfix/smtpd: bad command startup -- throttling
All this tells me that smtpd is the one failing component.
So I Googled around and stumbled on some mailing list conversations
wherein similar smtpd segfaults were discussed. I found two cruelpits
were mentioned in particular:
1. db4, in combination with nsswitch and openldap. However, I don't
use OpenLDAP and I don't have nss_db(-compat) installed.
/etc/nsswitch.conf also doesn't contain any 'db' lines.
2. sasl. In the past there seem to have been problems with a
Postfix/Sasl1 combination but FC2 uses sasl2. Some Google results laid
blame on sasl version mismatches between different e-mail components,
but they seem not to be applicable to my system.
That's not to say they're no longer suspect though.
With db4, for example, I ran into problems earlier with respect to my
Subversion repositories (in addition to the change in db schemas). A
dump/load cycle fixed this though. Because of this I rebuilt the alias
and virtual map databases but this didn't help.
That nss could be to blame shows from the gdb results that I'll paste
below. The exact command, which I took from a Postfix debug help file,
was:
debugger_command =
PATH=/bin:/usr/bin:/usr/local/bin; export PATH;
(echo cont; echo where) | gdb $daemon_directory/$process_name
$process_id 2>&1 >$config_directory/$process_name.$process_id.log &
sleep 5
Notice though, that the 'cont' and 'where' commands didn't seem to be
executed. I don't know why that is. I found one e-mail online from
someone with a similar problem where the result of cont and where gave
a hint at sasl. I don't know if this can be generalised to my case,
-----
GNU gdb Red Hat Linux (6.0post-0.20040223.19rh)
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "i386-redhat-linux-gnu"...(no debugging
symbols found)...Using host libthread_db library
"/lib/tls/libthread_db.so.1".
Attaching to program: /usr/libexec/postfix/smtpd, process 25296
Reading symbols from /usr/lib/libldap.so.2...(no debugging symbols
found)...done.
Loaded symbols for /usr/lib/libldap.so.2
Reading symbols from /usr/lib/liblber.so.2...(no debugging symbols
found)...done.
Loaded symbols for /usr/lib/liblber.so.2
Reading symbols from /lib/libpcre.so.0...(no debugging symbols found)...done.
Loaded symbols for /lib/libpcre.so.0
Reading symbols from /usr/lib/libsasl2.so.2...(no debugging symbols
found)...done.
Loaded symbols for /usr/lib/libsasl2.so.2
Reading symbols from /lib/libssl.so.4...(no debugging symbols found)...done.
Loaded symbols for /lib/libssl.so.4
Reading symbols from /lib/libcrypto.so.4...(no debugging symbols found)...done.
Loaded symbols for /lib/libcrypto.so.4
Reading symbols from /usr/lib/libgssapi_krb5.so.2...(no debugging
symbols found)...done.
Loaded symbols for /usr/lib/libgssapi_krb5.so.2
Reading symbols from /usr/lib/libkrb5.so.3...(no debugging symbols
found)...done.
Loaded symbols for /usr/lib/libkrb5.so.3
Reading symbols from /lib/libcom_err.so.2...(no debugging symbols found)...done.
Loaded symbols for /lib/libcom_err.so.2
Reading symbols from /usr/lib/libk5crypto.so.3...(no debugging symbols
found)...done.
Loaded symbols for /usr/lib/libk5crypto.so.3
Reading symbols from /lib/libresolv.so.2...(no debugging symbols found)...done.
Loaded symbols for /lib/libresolv.so.2
Reading symbols from /lib/libdl.so.2...(no debugging symbols found)...done.
Loaded symbols for /lib/libdl.so.2
Reading symbols from /usr/lib/libz.so.1...(no debugging symbols found)...done.
Loaded symbols for /usr/lib/libz.so.1
Reading symbols from /lib/tls/libdb-4.2.so...(no debugging symbols
found)...done.
Loaded symbols for /lib/tls/libdb-4.2.so
Reading symbols from /lib/libnsl.so.1...(no debugging symbols found)...done.
Loaded symbols for /lib/libnsl.so.1
Reading symbols from /lib/tls/libc.so.6...(no debugging symbols found)...done.
Loaded symbols for /lib/tls/libc.so.6
Reading symbols from /lib/libcrypt.so.1...(no debugging symbols found)...done.
Loaded symbols for /lib/libcrypt.so.1
Reading symbols from /lib/ld-linux.so.2...(no debugging symbols found)...done.
Loaded symbols for /lib/ld-linux.so.2
Reading symbols from /lib/tls/libpthread.so.0...(no debugging symbols
found)...done.
[Thread debugging using libthread_db enabled]
[New Thread -151037152 (LWP 25296)]
Loaded symbols for /lib/tls/libpthread.so.0
Reading symbols from /lib/libnss_files.so.2...(no debugging symbols
found)...done.
Loaded symbols for /lib/libnss_files.so.2
Loaded symbols for /lib/libnss_files.so.2
Loaded symbols for /lib/libnss_files.so.2
0x008e27a2 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2
(gdb) Hangup detected on fd 0
error detected on stdin
Detaching from program: /usr/libexec/postfix/smtpd, process 25296
-----
So if anyone could help, I'd appreciate it much.
Thanks,
Jonas
19 years, 7 months
Can't get sensors to work...
by Thiago Guzella
Hi there guys...
I have FC2 x86_64 running on Athlon64 Box, with an Asus A8V Deluxe Rev
A2 (VIA K8T800Pro + VT8237)...
I have been trying to install the mobo monitoring sensors, in order to
check the system's temperature...
I am using the default 2.6.5 kernel (uname -a returns:
"Linux Guzella 2.6.5-1.358 #1 Sat May 8 09:01:26 EDT 2004 x86_64
x86_64 x86_64 GNU/Linux").
When executing /usr/sbin/sensors-detect (as root), I get the following error:
---
$ sudo ./sensors-detect
This program will help you determine which I2C/SMBus modules you need to
load to use lm_sensors most effectively. You need to have i2c and
lm_sensors installed before running this program.
Also, you need to be `root', or at least have access to the /dev/i2c-*
files, for most things.
If you have patched your kernel and have some drivers built in, you can
safely answer NO if asked to load some modules. In this case, things may
seem a bit confusing, but they will still work.
It is generally safe and recommended to accept the default answers to all
questions, unless you know what you're doing.
We can start with probing for (PCI) I2C or SMBus adapters.
You do not need any special privileges for this.
Do you want to probe now? (YES/no): yes
Probing for PCI bus adapters...
Use driver `i2c-viapro' for device 00:11.0: VIA Technologies VT8237
South BridgeProbe succesfully concluded.
We will now try to load each adapter module in turn.
Load `i2c-viapro' (say NO if built into your kernel)? (YES/no): yes
Module loaded succesfully.
If you have undetectable or unsupported adapters, you can have them
scanned by manually loading the modules before running this script.
To continue, we need module `i2c-dev' to be loaded.
If it is built-in into your kernel, you can safely skip this.
i2c-dev is not loaded. Do you want to load it now? (YES/no): yes
Module loaded succesfully.
We are now going to do the adapter probings. Some adapters may hang halfway
through; we can't really help that. Also, some chips will be double detected;
we choose the one with the highest confidence value in that case.
If you found that the adapter hung after probing a certain address, you can
specify that address to remain unprobed. That often
includes address 0x69 (clock chip).
Can't exec "i2cdetect": No such file or directory at ./sensors-detect
line 4366, <STDIN> line 3.
Couldn't find i2cdetect program!! at ./sensors-detect line 4366, <STDIN> line 3.
--
The weird thing is that the "i2cdetect" program is located in the same
directory (/usr/sbin):
-rwxr-xr-x 1 root root 13744 Apr 13 2004 /usr/sbin/i2cdetect
By running i2cdetect (again as root), I get the following info:
$ sudo ./i2cdetect
Error: No i2c-bus specified!
Syntax: i2cdetect [-f] I2CBUS
I2CBUS is an integer
With -f, scans all addresses (NOT RECOMMENDED)
i2cdetect -l lists installed busses only
Installed I2C busses:
i2c-0 unknown SMBus Via Pro adapter at 0400
Algorithm unavailable
Any clues on how to solve this??
Also, has anyone successfully installed it on this mobo??
Thanks
Thiago Guzella
19 years, 7 months