I know the proccess has been covered to death in this list, but has anyone
taken the time to write a tutorial explaining how to install the ATI
drivers (the ones for Radeon and up) from the ATI website?
http://www.webpageworkshop.co.uk - FREE Web tutorials and references
I've a network problem on my Fedora Core 1.
on my switch the 100 led is ok.
But if I make an mii-tool command I've this result :
eth0: 10 Mbit, full duplex, link ok
And it's bad. Why the led on my switch ok in 100 Mbit but mii-tool see
it with 10 Mbit ?
I've try this : mii-tool -v -A 100baseTx-FD
But no changes..
Thanks for help ;D
When it was more difficult, it worked: months ago, i compiled and
installed Cyrus-IMAPd on FC1 and had no issues with it.
Now, when it's simple, it does not work. On FC2, i can't convince Cyrus
to work. I can create the accounts, but Evo does not read the email
Anyone using Cyrus on FC2? What were the steps you took to make it work,
after installing the RPM?
My users like to keep 500 to 1000 messages in their mailboxes and
average about 500K per message (we are a talent management company, so
there is lots of multimedia being exchanged).
So far I have been running whatever came stock with FC1, so I have
Postfix with WU IMAP running in that standard UNIX mailbox mode.
Can I keep Postifix and just change it to Cyrus IMAP style mailboxes and
install Cyrus IMAP? Or do I have to start from scratch?
Fortunately I have only 10 users, so I will have to deal with about 10K
in messages and about 150 sub folders.
as seen there is not the old imapd in FC2, and it did install the cyrus-imap.
Ok, but, when I login I can not see any directory formerly created, INBOX is
And in documentation of cyrus I didn't find anything about that, I thought it
should run out of the box.
So: can someone give a hint, how I convert all /home/<user>/mail to cyrus,
which way I must go, that cyrus will display the INBOX for that user, and
them don't get a "permission denied" when try to create a folder?
Meanwhile I use dovecot, but there are some other problems, too. (filter via
procmail, in cyrus I would make it via sieve and so on)
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).
1. The "sourcecode" package, which is now ARCH="noarch"
I assume the package name change was because the ARCH has changed.
Why is the "sourcecode" package not built by default when
"--target=noarch" is passed? I.e.,
%define builddoc 1
%define buildsource 0
2. There is another variable in EXTRAVERSIONS, defaults to "root"
I assume this is to differentiate between UML (User Mode Linux)
kernels (so the same build system can be used)?
Is this a stock kernel change? Or Red Hat only?
3. Athlon no longer a build option at all in the SPEC file
Are there support issues with this? Or was it another reasoning?**
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
[ **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
And for those that want to build Athlon optimized kernels, the .config
files are here:
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
Resending this message since I haven't seen it show up on the list since
Friday. Thanks for any pointers anyone can offer!
> 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
> 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>
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: Illegal user test from
Jul 17 14:42:26 localhost sshd: Failed password for illegal user
test from 188.8.131.52 port 48692 ssh2
Jul 17 14:42:27 localhost sshd: Illegal user guest from
Jul 17 14:42:30 localhost sshd: Failed password for illegal user
guest from 184.108.40.206 port 48753 ssh2
Jul 17 14:42:31 localhost sshd: Illegal user admin from
Jul 17 14:42:33 localhost sshd: Failed password for illegal user
admin from 220.127.116.11 port 48807 ssh2
Jul 17 14:42:34 localhost sshd: Illegal user admin from
Jul 17 14:42:37 localhost sshd: Failed password for illegal user
admin from 18.104.22.168 port 48849 ssh2
Jul 17 14:42:38 localhost sshd: Illegal user user from
Jul 17 14:42:40 localhost sshd: Failed password for illegal user
user from 22.214.171.124 port 48879 ssh2
Jul 17 14:42:43 localhost sshd: Failed password for root from
126.96.36.199 port 48900 ssh2
Jul 17 14:42:47 localhost sshd: Failed password for root from
188.8.131.52 port 48913 ssh2
Jul 17 14:42:50 localhost sshd: Failed password for root from
184.108.40.206 port 48924 ssh2
Jul 17 14:42:51 localhost sshd: Illegal user test from
Jul 17 14:42:54 localhost sshd: Failed password for illegal user
test from 220.127.116.11 port 48931 ssh2