The last time I got a new scanner I spent about a week
correlating the lists of scanners actually available for
purchase with the list of supported devices on the sane
web pages (99.999% of which are models that are out of
Has anyone recently purchased a flatbed scanner with good
linux support? (I mostly want it for documents and such,
not photo or negative scanning).
The Canoscan LIDE 60 I wound up with at the end of the first
painful search has apparently died the real death. It doesn't
show up as a USB device at all. If it had a fuse, I'd say
it had blown it :-). Naturally they are up to LIDE 90 now
(60 no longer made), and the 90 isn't supported in sane.
I want to move /home to another internal disk.
I know how to make the partition and to copy files to it.
What I'm not sure of is how to change things so that
the new partition automatically mounts as /home .
If I edit fstab and reboot will it stick?
Is fstab the point of truth or
will some program "fix" it for me?
I've read that editing fstab is the way to go,
but I've also read that fstab is edited by programs.
"Those parts of the system that you can hit with a hammer (not advised)
are called Hardware; those program instructions that you can only
curse at are called Software."
Why has pirut been dumped?
According to the wiki, it was supposed to remain as an alternative to
Package-kit but it has been obsoleted and removed from rawhide and the
preview release completely.
Someone in a position to know needs to explain the vendetta that has
left us with the POS that is gnome-packagekit.
I'm having a strange problem with Fedora 9 Preview. At first I couldn't
get my network port to be configured by Network Manager. There are no
details of it in the NetworkManager configuration screens and I can't
"Add" it as all the buttons are greyed out.
Frustrated by the inability to do anything with NM, I decided instead to
use system-config-network. The NIC is listed there so I configured it,
made sure to check the "start interface on boot" button. Unticked the
box which lets NetworkManager control the interface.
Now when I activate the interface in system-config-network, it works
fine, but every time I reboot it's disabled again.
I've tried unchecking the "Enable Networking" button in NetworkManager
but that makes no difference - and annoyingly is always checked again
after a reboot.
System-wise, I started with the F9 Preview and have done a couple of yum
updates so I'm up-to-date. The onboard NIC is an Intel 82562EZ 10/100
Any ideas why this might be happening? Is Network Manager likely to be
the culprit, and if so, is it fairly safe to uninstall?
Thanks in advance,
I just installed nagios on my Fedora 8 trough Yum. (standard repo's)
Now it seems that the rpm installs in different dir's than what you're
expected to do while installing from source.
Now it's quite hard to follow the official nagios manual, and i can't seem
to find modified ones.
What should I do?
Is anyone successfully using openldap to maintain an address book?
As far as I can see, if you save kaddressbook data in LDIF format,
the resulting file has to be extensively modified
before it becomes acceptable to openldap.
Eg the DN of a typical entry in the LDIF file reads
dn: cn=Andrew Ryan,mail=aryan27(a)tcd.ie
which openldap certainly will not like.
What puzzles me about this is that the issue must be one
which occurs to many people.
How is one meant to keep a "global" address book under Fedora?
Incidentally, the KMail handbook claims that there is some way
of using MySQL with the address book,
but I have never seen any explanation of how to do this.
Since nobody has whined about this yet I suppose somebody must. So
consider this an official whine.
For the last week or so I've been getting log messages about updating
to clamav 0.93 from 0.92.1. I just searched the updates and updates/testing
for both 7, which I am running, and 8. There is nary a sign of clamav 0.93.
Tsk tsk, gentlemen. Please do get on it.
And to those of you who've been ignoring your logs - shame on you.
Jari Marikainen wrote:
> I would like to forward incoming traffic from internet to
> "<195.198.111.x> port 80" to "<some other ip on the internet> port 80"
> in FC3 on the same interface.
I would try the DNAT/SNAT iptables targets, along the lines of:
iptables -t nat -A PREROUTING -p tcp --dport 80 -d 195.198.111.x \
-j DNAT --to-destination 188.8.131.52
iptables -t nat -A POSTROUTING -p tcp --dport 80 -d 184.108.40.206 \
-j SNAT --to-source <your external IP address on this machine>
The second line makes the real server send it's replies through the same
path (otherwise it will reply directly to the client)
You have to enable/allow forwarding for everything to work.
I realize this question may not be fedora specific but here it is.
I am trying to determine how soon after a
/sbin/ifconfig eth2 up 192.168.0.2
can I actually successfully send UDP packets out that interface. (UDP
since i wanted to keep things simple, not TCP flow/congestion control
entanglements.) I have a loop such as:
$utime = $ARGV;
system "usleep $utime";
system "/sbin/ifconfig eth2 down";
print "after eth2 down\n";
system "usleep $utime";
system "/sbin/ifconfig eth2 up 192.168.0.2";
print "after eth2 up\n";
From my tests it appears that it takes between 4 to 6 seconds after the
"up" command before my UDP packets actually start going out. The tests
are between two machines with addresses 192.168.0.2 <---> 192.168.0.3.
Any hints welcome. The "/sbin/ifconfig eth2 up 192.168.0.2" command
returns right away, but the interface is not ready to go for a few
seconds. What can this be due to?