What's up with the selinux list?

[Mike Cloaked]

For the past few days it seems that the Fedora SELinux List is not accepting
or processing posts.
Does anyone know if there is a server problem or how long it might be before
the list is working again?
-- 
View this message in context: 
http://www.nabble.com/What%27s-up-with-the-selinux-list--tp20616565p20616565.html
Sent from the Fedora List mailing list archive at Nabble.com.

-- 
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

Re: HOW the "H" do you get the Mic working in FC8

[Simon Slater]

On Wed, 2008-11-19 at 15:35 -0500, Jim wrote:
> FC8/KDE
> I have gone into Alsamixer selected MIC, enabled, Mic 1 is selected,  
> what else must I do to get MIC working.
> In Kmix all settings are enabled for MIC .
> The Mic is the most Frustrating thing to get working in the sound system.
> How do you run Pulse to check Mic Settings.
> The MIC is also a problem FC10,  submitted  messages to  Fedora-test 
> and  filed bug report, no body can  help.
> Anyhow  back to FC 8 Mic problems.
> 
Good question.  After reading this post I realized that since
installing F8 I hadn't used the mic either.  I used Kmix and set the
level & clicked the green dot to turn it on.  Works fine.

-- 
Regards,
Simon Slater
Registered Linux User #463789. Be counted at: http://counter.li.org/


-- 
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

RE: Moving Fedora 9 Hard Disk To Another System

[Joseph L. Casale]

>When the kernel is updated, the Fedora 9 framework will rebuild a new
>initrd and it will  NOT have the special modules in it.

On the CentOS list, a similar discussion revealed a procedure to facilitate 
this:

http://lists.centos.org/pipermail/centos/2008-November/067688.html

jlc

-- 
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

Re: set up NAT (network address translation) on local server

[Marko Vojinovic]

On Thursday 20 November 2008 13:52, Christopher K. Johnson wrote:
> Does /etc/sysconfig/iptables actually contain the lines
>
> *nat
>
> :PREROUTING ACCEPT [1:233]
> :POSTROUTING ACCEPT [0:0]
> :OUTPUT ACCEPT [0:0]
>
> -A POSTROUTING -s 192.168.1.0/24 -o eth0 -j SNAT --to-source 10.154.19.210
> COMMIT
>
> It seems unlikely that it was written correctly since the restart did
> not implement your SNAT rule, and this file is what a restart reads.
> Perhaps there is  a bug in iptables-save?  I edit
> /etc/sysconfig/iptables directly, and recommend that if you are not
> using some firewall front-end or tool to do this, that you do the same.

:-)

I am not that much pro for iptables as for dhcp --- in fact, I gave up on 
learning iptables syntax a long time ago and rely on guis for configuration 
--- but wouldn't it be much much easier for the OP to set up nat using, say, 
firestarter?

First "yum install firestarter". Then run it and answer the questions that 
wizard asks. Activate NAT options, do not touch dhcp options (this is already 
configured). The eth1 device is the local network, while eth0 is the uplink 
to outside. I don't have two network cards here now so I cannot repeat exact 
steps, but it should be trivial in a sense.

HTH, :-)
Marko





-- 
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

Re: More strange F9 dependencies

[john wendel]

Beartooth wrote:
	I have no PDA, nor expect ever to, much less hardware to connect 
it to a PC.


	When I was working, and literally running my life on rails, its 
ancestors, then called organizers, were fine things; I had a whole series 
of them. 

	Those who want or need them are welcome to them; strength to 
their arms. Theirs, not mine.  To an old retired fart without a schedule, 
a PDA or even a fancy phone is a dispensable expense, and thus cruft at 
best, if not a security liability. So I tried to cut.


[EMAIL PROTECTED] ~]# yum remove bluez-*
[]
Dependencies Resolved


 Package   Arch  Version Repository   
Size 


Removing:
 bluez-libsi386  3.36-1.fc9  installed
126 k
 bluez-utils-cups  i386  3.36-1.fc9  
installed 40 k

Removing for dependencies:
 gnome-user-share  i386  0.31-1.fc9  installed
219 k
 gvfs  i386  0.2.5-1.fc9 installed
3.5 M
 gvfs-fuse i386  0.2.5-1.fc9 
installed 25 k
 libwiimotei386  0.4-6.fc9   
installed 46 k
 nautilus  i386  2.22.5.1-1.fc9  
installed 15 M
 obex-data-server  i386  1:0.3.4-1.fc9   installed
145 k
 xorg-x11-drivers  i386  7.3-4.fc9   
installed 0.0 
 xorg-x11-drv-wiimote  i386  0.0.1-1.fc9 
installed 12 k


Transaction Summary

Install  0 Package(s) 
Update   0 Package(s) 
Remove  10 Package(s) 


Is this ok [y/N]: n
Exiting on user Command

	Some of those dependencies certainly make sense, and others look 
likely to. Some of them. I grant that.


	Some make mud seem clear. I don't understand, despite googling, 
what gvfs is or does. I know only that it too threatened to take a long 
list of indispensable apps with it if removed -- and that the gnome 
system monitor always shows some half dozen of its creatures, sleeping.


	But what of nautilus? It would be fine for bluez to depend on it; 
but why should it depend on bluez?? Is someone going to tell me that 
pango uses bluez, with or without hardware? And then sneer down his nose 
that I'm welcome to write new code??


What ever became of linux being tailorable??



There's no need to be at the mercy of a package maintainer. Ever hear of 
"rpm -e --nodeps ". Works most of the time for me. 
And if it breaks, just reinstall the worthless-package.


Regards,

John

--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

Re: How to test cups printer system

[Steven W. Orr]

On Thursday, Nov 20th 2008 at 19:21 -, quoth Dave Feustel:

=>On Thu, Nov 20, 2008 at 04:58:06PM -0700, Phil Meyer wrote:
=>> Dave Feustel wrote:
=>>> I just added my hp2100 laserjet printer to f9.  I then tried to print a
=>>> small test file. I get no output (the job is queued tho) plus a warning
=>>> message that the printer may not be connected.
=>>>
=>>> Do I need to do something else to get the cups system enabled?
=>>>
=>>> Thanks.
=>>>
=>>>   
=>>
=>> Most HP printers want hplip.  Check your /var/log/messages for an error  
=>> message about a 'back-end'.
=>>
=>> # yum install hplip hplip-gui hplip-libs
=>
=>hplip - already installed
=>hplip-gui - installed by yum
=>hplip-libs - not found by yum
=>
=>> Afterward, your print job should just happen.
=>
=>Unfortunately, with 3 jobs queued, printer remains quiescent.
=>printer is connected to parallel port and was recognised by
=>printer config.
=>
=>> Modern USB printers  
=>> usually need no config at all for CPUS to see it and work.  Just plug it  
=>> in and it should show up in printing dialogs.
=>>
=>> Good Luck!

Same here. There is no hplip-libs package.

Also, if I run hp-check -r, it complains that I don't have cups-ddk but I 
do have cupsddk. 

Should this be reported?

-- 
Time flies like the wind. Fruit flies like a banana. Stranger things have  .0.
happened but none stranger than this. Does your driver's license say Organ ..0
Donor?Black holes are where God divided by zero. Listen to me! We are all- 000
individuals! What if this weren't a hypothetical question?
steveo at syslang.net

-- 
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

Re: how to configure xdg-open applications?

[Rex Dieter]

Paul Johnson wrote:

> On Thu, Nov 20, 2008 at 1:21 PM, Rex Dieter <[EMAIL PROTECTED]> wrote:
>> Paul Johnson wrote:
>>
>>> I want to change the programs that xdg-open points to for things like
>>> pdf or dvi.  There are no configure tools I can find on the
>>> freedesktop site and the xdg-open man page gives no help at all. In
>>> /etc/xdg I don't see settings for evince or such.  "grep -r pdf *" in
>>> the /etc/xdg directory returns nothing.
>>>
>>> Throw me some help, please.
>>
>> xdg-open uses the default apps as defined by the desktop you're using
>> (gnome, kde, etc...).  So, the question becomes, which desktop are you
>> using?  Do you need help setting the default .pdf app on desktop foo?
>>
>> -- Rex
>>
> 
> Well, I use several different desktops, if you must know.  On all of
> them LyX runs and uses xdg-open to grab pdf files, and I had thought
> that the freedesktop framework was aiming at having a
> desktop-brand-free method of specifying what applications are used.
> That is the long term goal, I think.  Googling tells me that many
> people have the same desire, but it is not implemented YET because the
> freedesktop people are coming along with general standards after the
> desktop systems evolved.
> 
> But I have something of an answer.  The previous poster points me to
> the xdg-mime program. It is used to set the default applications. I've
> been testing it and reading its source code.  It is not a general
> application chooser.  Rather, it "adjusts most desktops" to use a
> program program. If you run it  in your current environment, it tells
> you what is specified if it understands what desktop you are previous
> running (AFAIK, it is OK for Gnome,KDE, and XFCE, but not for a less
> desktopish desktop like an old fashioned window-manager-only setup
> like  WindowMaker.  If you use xdg-mime to set a value, it tries to
> set values for Gnome, KDE, and XFCE if it finds them in your system.
> It can set them either for the whole system or the user account.
> 
> Another answer I've found is that Gnome users can hand edit this file:
> 
> /usr/share/applications/defaults.list
> 
> That is the "gnome" way of doing it system wide, and xdg-mime just
> edits that file for you.
> 
> If an individual user already has this file,
> 
> ~/.local/share/applications/defaults.list
> 
> then system-wide changes will have no effect, and users have to either
> edit their own defaults.list or delete it and let it be re-created by
> the desktop environment.  That will copy the system-wide set into the
> user's account.
> 
> But, then again, this is all stuff I've pieced together in the last 2
> hours, so hopefully the program maintainers will step up and tell us
> if I have it wrong.

Excellent detective work! :)

Good news for all that latter stuff about defaults.list... Most desktops 
(including kde4) use that same spec/standard too.

-- Rex


-- 
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

Re: More strange F9 dependencies

[Michael Schwendt]

On Fri, 21 Nov 2008 08:43:38 +1030, Tim wrote:

> > Run: repoquery --whatrequires libbluetooth.so.2
> > 
> > That shows all packages with a _direct_ dependency on that library.
> > Nautilus depends on something that depends on bluez-libs.
> 
> It strikes me that with things like this, and others (e.g. requiring
> CUPs on a single, headless, remote web server), that we should be
> developing some strategies to remove *USELESS* dependencies.  Even if
> that means an extra "hack" repo with various dummy RPMs to satisfy RPM
> demands for files that will never be used, or to supply the bare minimum
> files it wants for a dependency, without the rest of the package.

RPM dependencies are no silly game.

Especially not the automatically determined dependencies on shared library
names. They are not hand-crafted by a packager.

If a program or library is built and linked with some other library, in
the majority of cases this leads to a strict dependency: you must
install the _required_ (!) library, or else the program fails and
doesn't start since the system's linker stumbles upon a missing library.

You cannot simply insert a dummy package, which provides a virtual
"libfoo.so.1" but which does not include the needed shared library
and its interface.

This is different only with optional plugins, which can be added or
removed freely, and which are stored in optional packages to make
dependencies optional. Or with libraries that can be loaded by an
application itself (at run-time) and need not be present. It requires
extra efforts at the implementation-level to decouple a library
interface, so it can become optional at run-time. In many cases
the extra effort is not worthwhile.

-- 
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

Re: Evolution and the Global Catalog Server Debacle

[Da Rock]

On Thu, 2008-11-20 at 08:57 -0700, Christopher A. Williams wrote:
> On Thu, 2008-11-20 at 07:04 -0700, Christopher A. Williams wrote:
> > I could really use a hand on this one:
> > 
> > I'm running Evolution (on F10 PR/Rawhide) with the Exchange Connector,
> > and have always had incredible problems browsing my employer's Exchange
> > Global Address List. I picked up what I believe is the Global Catalog
> > Server by using Outlook 2007 and going through all of the motions to
> > find it there.
> 
> ...Meant to post this to Fedora Test List. Sorry 'bout that! Please move
> this thread to there.

Try searching google for ldap addressbooks and evolution. I don't think
this is just a test issue - its a bug in evolution.

-- 
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

Re: Mount usb devices

[Dave Feustel]

On Thu, Nov 20, 2008 at 04:23:11PM -0800, Rick Stevens wrote:
> Dave Feustel wrote:
>> On Thu, Nov 20, 2008 at 02:26:28PM -0800, Rick Stevens wrote:
>>> FFS is the BSD "fast file system" (yes, the Amiga also had an FFS, but
>>> since the OP said "BSD", I'm going to discount the Amiga).  I think
>>> Linux' UFS filesystem can mount it but I'm not sure.  If it can, it
>>> should automount, but UFS may not recognize FFS markers even if it can
>>> mount it.  You can try forcing UFS to see if it'll work.
>>>
>>> First, make a directory somewhere where you want to mount it.  A good
>>> place would be in either /media or /mnt.  I'd do it in /mnt to leave
>>> /media pristine for automounts:
>>>
>>> mkdir /mnt/test
>>>
>>> Do a "dmesg" just before you plug in the drive, plug it in, wait a few
>>> seconds and do "dmesg" again.  The additional lines from dmesg should
>>> refer to the device you plugged in.  You'll probably see something like
>>> this:
>>>
>>> sd 6:0:0:0: [sdb] Assuming drive cache: write through
>>>  sdb: sdb1
>>>
>>> (that's from plugging in a FLASH drive).  In this case, the drive
>>> itself is sdb (/dev/sdb) and it contains one partition, sdb1 (or
>>> /dev/sdb1).  Then:
>>>
>>> mount -t ufs /dev/sdXY /path/to/your/mount/point
>>>
>>> In this case, "mount -t ufs /dev/sdb1 /mnt/test
>>>
>>> If it mounts up, voila!  If not, either you didn't specify the right
>>> partition or UFS doesn't mount FFS stuff.  I don't have any FFS drives
>>> handy or I'd test it for you.
>>
>> Thanks for this. I recognise the stuff from dmesg. I was trying to
>> mount the ffs disk because it is handy. I have another flash device
>> that I would like to partition as a 2 or 3 partition drive, mkfs
>> and then copy data to it from (hd0,0). Then I want to recreate
>> hd0 as a multi-partition drive, install 64-bit f9, and then copy
>> the data back from the flash drive.
>>
>> The stumbling block for me was that I didn't understand how the usb
>> devices are named and accessed in Fedora before they are mounted. I 
>> think I understand naming now.
>
> Ah!  Yes, virtually all disk-like devices are treated as if they were
> SCSI.  "/dev/sd" is the prefix for all such devices, "sd" meaning "SCSI
> disk".  Then there's a drive designator which will be the letter "a"  
> through "zz" (yes, I've seen such two-letter things...typically on big
> FC disk farms), then a decimal number, 1 through 15 for the partition
> number.  So, the fifth partition on the third drive found would be
> /dev/sdc5 (and that would actually be INSIDE /dev/sdc4, see below).
>
> Additional note: Partition numbers 1 through 4 are reserved for
> "primary" partitions.  One primary partition can also be an "extended"  
> partition and partition 4 is always used for such a beast.  Partitions 5
> through 15 will always refer to partitions INSIDE that extended
> partition (partition 4), so don't freak out when you see the sector list
> for partition 4 overlap those for partitions 5 through 15 in the output  
> of "fdisk" or "sfdisk".
>
> Probably more data than you need, but I'm nothing if not thorough (some
> would say "bombastic" or "long winded").

Thanks again for the info above. This is the kind of info that I
understand but which seems to be missing from my f9 bible. Linux
device names are quite different from device names in OpenBSD which
I had been using for several years before I started using Linux
(Fedora 9 and Suse 11).

-- 
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

Re: Help with email issues

[Ed Greshko]

Kevin Kempter wrote:
> Hi All;
>
> I'm hoping someone can help me with some strange email issues.
>
>
> I can send emails to most anyone except for the postgresql email lists. I've 
> pinged 'em several times - even the list admins but I dont think my mails are 
> getting through.
>
> At one point I tried to send an email to the list and I got this message back:
>
>
> =
> Hi. This is the qmail-send program at outboundproxy6.
> I'm afraid I wasn't able to deliver your message to the following addresses.
> This is a permanent error; I've given up. Sorry it didn't work out.
>
> <[EMAIL PROTECTED]>:
> 200.46.204.86 does not like recipient.
> Remote host said: 504 5.5.2 : Helo command rejected: need 
> fully-qualified hostname
> Giving up on 200.46.204.86.
>
> --- Enclosed are the original headers of the message.
>   
In this particular case it seems that mail.postgresql.org
(200.46.204.86) is unhappy with the SMTP helo issued by
outboundproxy6.bluehost.com (74.220.195.74).  If I read the message
correctly outboundproxy6 is sending "helo outboundproxy6" and not "helo
outboundproxy6.bluehost.com".  And mail.postgresql.org is configured to
reject.

Look at this

[EMAIL PROTECTED] ~]$ telnet 200.46.204.86 25
Trying 200.46.204.86...
Connected to mail.postgresql.org (200.46.204.86).
Escape character is '^]'.
220 mail.postgresql.org ESMTP Postfix
helo misty
250 mail.postgresql.org
mail from:<[EMAIL PROTECTED]>
250 2.1.0 Ok
rcpt to:<[EMAIL PROTECTED]>
504 5.5.2 : Helo command rejected: need fully-qualified hostname
rset
250 2.0.0 Ok
helo misty.greshko.com
250 mail.postgresql.org
mail from:<[EMAIL PROTECTED]>
250 2.1.0 Ok
rcpt to:<[EMAIL PROTECTED]>
450 4.7.1 <[EMAIL PROTECTED]>: Recipient address rejected:
Greylisted for 5 minutes
rset
250 2.0.0 Ok
quit
221 2.0.0 Bye
Connection closed by foreign host.

So, the problem would be with the configuration on
outboundproxy6.bluehost.com.

> =
>
>
> I did some google  searches and found lots of messages like this (they all 
> seem to be related to this 200.46.204.86 IP):
>
>
> Can you perhaps track it down through the logfiles on the MX machine,
> using the ESMTP id of the last hop out of postgresql.org/hub.org?
>
> Since it appears to be a mail hosting company who *also* happens to use
> postini/google for their antispam, it can be pretty much any domainname
> at all, I think... And we can't very well null-route any address who
> uses postini as their relayers, becuase loads of legit users do that...
>
> //Magnus
>
> Marc G. Fournier wrote:
>   
>> I just checked the lists, and find nothing for mi8/postini or obsmtp.com ... 
>> even checked globally (all lists), and nothing ...
>>
>> And its all keyed on the From, which is Magnus ... I could ban him from the 
>> list? :)
>>
>> This is where the duplicate checksum'ng is meant to come into play, but we 
>> 
> have 
>   
>> it disabled, for obvious reasons (key one: automated scripts that use the 
>> 
> same 
>   
>> commit message each time would then ben conssitently rejected) ...
>>
>>
>> --On Friday, June 27, 2008 23:56:58 -0400 Tom Lane 
>> 
>  wrote:
>   
>>> Is there a way to not only purge the lists of these bozos, but prevent
>>> future signups?  I've not only had enough of seeing them duplicating
>>> posts onto the lists, I've had much more than enough of mail bounces
>>> originating in their forging my address as envelope sender for such
>>> regurgitations.  I suppose everyone else who posts to the lists gets
>>> the same.  It's past time for a zero tolerance policy.
>>>   
>>> regards, tom lane
>>>   
>
>
> I did a ping on my mail server :
>
> $ ping mail.kevinkempterllc.com
> PING kevinkempterllc.com (69.89.20.54) 56(84) bytes of data.
> 64 bytes from box54.bluehost.com (69.89.20.54): icmp_seq=1 ttl=128 time=84.5 
> ms
>
>
> and I checked the main IP my firewall is getting from comcast 
>
> neither of them is anything like the  200.46.204.86 IP
>
> I'm pretty good with Linux but I'm more of a DBA - the email/network areas 
> are 
> far far from my skill set
>
> Thoughts?
>
> Thanks in advance...
>
>   


-- 
First law of debate: Never argue with a fool. People might not know the
difference.

-- 
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

Re: Moving Fedora 9 Hard Disk To Another System

[Mikkel L. Ellertson]

Paul Johnson wrote:
> On Thu, Nov 20, 2008 at 2:42 PM, Mikkel L. Ellertson
>> What I have done in the past is to boot off the install media,
>> select the rescue mode, and then chroot to where the root file
>> system is mounted. I thin build the new initrd, making sure it
>> matches the kernel I plan to boot from. In the future, installing a
>> new kernel will build the initrd, using the information from the
>> running kernel. At least it has worked correctly for the last 5
>> updates on this machine sense I moved the drive here, and rebuilt
>> the initrd for this motherboard.
>>
>> Mikkel
>>
> Unless you understand the mechanism through which the new initrd is
> built, you cannot be confident in your statement that the new kernel
> will be "using the information from the running kernel," as you put
> it.  As far as I know, that is just wrong.  The initrd is built by the
> new-kernel script, and it has no way of "talking to" the existing
> kernel and getting the correct modules.
> Instead, it is reading some configuration files under /etc, and
> apparently you are lucky to have those files set correctly, but you
> don't have any good reason to expect OP has same lucky configuration.
> 
> I'm not on a Fedora 9 system now, but I can tell you about Centos 52,
> and it matches my memory of Fedora 8.  Fedora uses a script
> 
> /sbin/new-kernel-pkg
> 
> to handle the building of the initrd.  In that file, it calls
> mkinitrd.  That file does not specify any options or modules to
> pre-load.  When I want to be absolutely sure a module is loaded, I
> have sometimes written them into that file.  But you see it just uses
> mkinitrd without options.  So you go read mkinitrd man page, and it is
> not entirely too clear about how the required modules are to be
> specified, but it does say it reads "/etc/modprobe.conf" and
> "/etc/modules.conf".   Note the preload option in mkinitrd is probably
> where you need to focus.  Look in /etc/modprobe.conf on this Centos
> system, and it has components like this:
> 
> alias scsi_hostadapter ata_piix
> 
> I am pretty sure that mkinitrd is taking note of that and using the
> modules for ata_piix to get motherboard connectivity.
> 
> In the past, when I have wanted to know FOR SURE what modules are
> needed, I make a small custom install on the machine in question.
> Don't bother about configuring it.  Then I copy the modprobe.conf file
> and the stuff in modules.conf if it exists.  Then you can go ahead and
> install your standard disk image.  THen boot off a rescue disk, use it
> to go into the new system and fix the modules so they are proper and
> rebuild initrd.  Because you have fixed modprobe.conf, then new
> kernels installs will get the right settings.
> 
> Sorry if this appears pedantic. I'm a teacher :)
> 
> PJ
> 
You may want to take a closer look at the /sbin/mkinitrd script, and
all the hardware probing it does by default. Among other things, it
makes sure you have the modules for the root file system, and the
device it is mounted on by default. (PROBE="yes" is one of the
defaults.)

About the only time I could see having problems is if your
modprobe.conf is not valid for the running system. I have not
tracked down witch has priority - the information found by probing,
or found in modprobe.conf. Not that it matters much to me - I always
clean up /etc/modprobe.conf as well as the udev persistent rules as
part of moving the drive to a new system. (Delete the persistent
rules, and run kudzu on the new system.)

Mikkel
-- 

  Do not meddle in the affairs of dragons,
for thou art crunchy and taste good with Ketchup!



signature.asc
Description: OpenPGP digital signature
-- 
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

Re: Mount usb devices

[Rick Stevens]

Dave Feustel wrote:

On Thu, Nov 20, 2008 at 02:26:28PM -0800, Rick Stevens wrote:

FFS is the BSD "fast file system" (yes, the Amiga also had an FFS, but
since the OP said "BSD", I'm going to discount the Amiga).  I think
Linux' UFS filesystem can mount it but I'm not sure.  If it can, it
should automount, but UFS may not recognize FFS markers even if it can
mount it.  You can try forcing UFS to see if it'll work.

First, make a directory somewhere where you want to mount it.  A good
place would be in either /media or /mnt.  I'd do it in /mnt to leave
/media pristine for automounts:

mkdir /mnt/test

Do a "dmesg" just before you plug in the drive, plug it in, wait a few
seconds and do "dmesg" again.  The additional lines from dmesg should
refer to the device you plugged in.  You'll probably see something like
this:

sd 6:0:0:0: [sdb] Assuming drive cache: write through
 sdb: sdb1

(that's from plugging in a FLASH drive).  In this case, the drive
itself is sdb (/dev/sdb) and it contains one partition, sdb1 (or
/dev/sdb1).  Then:

mount -t ufs /dev/sdXY /path/to/your/mount/point

In this case, "mount -t ufs /dev/sdb1 /mnt/test

If it mounts up, voila!  If not, either you didn't specify the right
partition or UFS doesn't mount FFS stuff.  I don't have any FFS drives
handy or I'd test it for you.


Thanks for this. I recognise the stuff from dmesg. I was trying to
mount the ffs disk because it is handy. I have another flash device
that I would like to partition as a 2 or 3 partition drive, mkfs
and then copy data to it from (hd0,0). Then I want to recreate
hd0 as a multi-partition drive, install 64-bit f9, and then copy
the data back from the flash drive.

The stumbling block for me was that I didn't understand how the usb
devices are named and accessed in Fedora before they are mounted. 
I think I understand naming now.


Ah!  Yes, virtually all disk-like devices are treated as if they were
SCSI.  "/dev/sd" is the prefix for all such devices, "sd" meaning "SCSI
disk".  Then there's a drive designator which will be the letter "a" 
through "zz" (yes, I've seen such two-letter things...typically on big

FC disk farms), then a decimal number, 1 through 15 for the partition
number.  So, the fifth partition on the third drive found would be
/dev/sdc5 (and that would actually be INSIDE /dev/sdc4, see below).

Additional note: Partition numbers 1 through 4 are reserved for
"primary" partitions.  One primary partition can also be an "extended" 
partition and partition 4 is always used for such a beast.  Partitions 5

through 15 will always refer to partitions INSIDE that extended
partition (partition 4), so don't freak out when you see the sector list
for partition 4 overlap those for partitions 5 through 15 in the output 
of "fdisk" or "sfdisk".


Probably more data than you need, but I'm nothing if not thorough (some
would say "bombastic" or "long winded").
--
- Rick Stevens, Systems Engineer  [EMAIL PROTECTED] -
- AIM/Skype: therps2ICQ: 22643734Yahoo: origrps2 -
--
-   Duct Tape + Magic Marker = Label Maker!  -
--

--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

Re: How to test cups printer system

[Dave Feustel]

On Thu, Nov 20, 2008 at 04:58:06PM -0700, Phil Meyer wrote:
> Dave Feustel wrote:
>> I just added my hp2100 laserjet printer to f9.  I then tried to print a
>> small test file. I get no output (the job is queued tho) plus a warning
>> message that the printer may not be connected.
>>
>> Do I need to do something else to get the cups system enabled?
>>
>> Thanks.
>>
>>   
>
> Most HP printers want hplip.  Check your /var/log/messages for an error  
> message about a 'back-end'.
>
> # yum install hplip hplip-gui hplip-libs

hplip - already installed
hplip-gui - installed by yum
hplip-libs - not found by yum

> Afterward, your print job should just happen.

Unfortunately, with 3 jobs queued, printer remains quiescent.
printer is connected to parallel port and was recognised by
printer config.

> Modern USB printers  
> usually need no config at all for CPUS to see it and work.  Just plug it  
> in and it should show up in printing dialogs.
>
> Good Luck!
>
> -- 
> fedora-list mailing list
> fedora-list@redhat.com
> To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
> Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

-- 
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

Help with email issues

[Kevin Kempter]

Hi All;

I'm hoping someone can help me with some strange email issues.


I can send emails to most anyone except for the postgresql email lists. I've 
pinged 'em several times - even the list admins but I dont think my mails are 
getting through.

At one point I tried to send an email to the list and I got this message back:


=
Hi. This is the qmail-send program at outboundproxy6.
I'm afraid I wasn't able to deliver your message to the following addresses.
This is a permanent error; I've given up. Sorry it didn't work out.

<[EMAIL PROTECTED]>:
200.46.204.86 does not like recipient.
Remote host said: 504 5.5.2 : Helo command rejected: need 
fully-qualified hostname
Giving up on 200.46.204.86.

--- Enclosed are the original headers of the message.

=


I did some google  searches and found lots of messages like this (they all 
seem to be related to this 200.46.204.86 IP):


Can you perhaps track it down through the logfiles on the MX machine,
using the ESMTP id of the last hop out of postgresql.org/hub.org?

Since it appears to be a mail hosting company who *also* happens to use
postini/google for their antispam, it can be pretty much any domainname
at all, I think... And we can't very well null-route any address who
uses postini as their relayers, becuase loads of legit users do that...

//Magnus

Marc G. Fournier wrote:
> 
> I just checked the lists, and find nothing for mi8/postini or obsmtp.com ... 
> even checked globally (all lists), and nothing ...
> 
> And its all keyed on the From, which is Magnus ... I could ban him from the 
> list? :)
> 
> This is where the duplicate checksum'ng is meant to come into play, but we 
have 
> it disabled, for obvious reasons (key one: automated scripts that use the 
same 
> commit message each time would then ben conssitently rejected) ...
> 
> 
> --On Friday, June 27, 2008 23:56:58 -0400 Tom Lane 
 wrote:
> 
>> Is there a way to not only purge the lists of these bozos, but prevent
>> future signups?  I've not only had enough of seeing them duplicating
>> posts onto the lists, I've had much more than enough of mail bounces
>> originating in their forging my address as envelope sender for such
>> regurgitations.  I suppose everyone else who posts to the lists gets
>> the same.  It's past time for a zero tolerance policy.
> 
>>  regards, tom lane
> 


I did a ping on my mail server :

$ ping mail.kevinkempterllc.com
PING kevinkempterllc.com (69.89.20.54) 56(84) bytes of data.
64 bytes from box54.bluehost.com (69.89.20.54): icmp_seq=1 ttl=128 time=84.5 
ms


and I checked the main IP my firewall is getting from comcast 

neither of them is anything like the  200.46.204.86 IP

I'm pretty good with Linux but I'm more of a DBA - the email/network areas are 
far far from my skill set

Thoughts?

Thanks in advance...

-- 
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

Re: Moving Fedora 9 Hard Disk To Another System

[Phil Meyer]

Paul Johnson wrote:

On Thu, Nov 20, 2008 at 2:42 PM, Mikkel L. Ellertson
<[EMAIL PROTECTED]> wrote:
  

Paul Johnson wrote:


When the kernel is updated, the Fedora 9 framework will rebuild a new
initrd and it will  NOT have the special modules in it.  On fedora
systems, I found no simpler solution than to edit the new-kernel
script and change the modules that were assumed.   Otherwise, the boot
up will fail just like you have been seeing.  On Ubuntu linux, I've
learned that the required modules can be configured in
/etc/modprobe.conf or someplace similar, and the initrd builder takes
notice of it.


  

...

Sorry if this appears pedantic. I'm a teacher :)

  


Well, my solution is even more so ...

I got tired of fighting it.  My requirements are to build a bootable 
disk in a VM and have it run on any i686 based platform.  Exceptions are 
SAN based ...


In my post install I do this:
# make sure drivers are in the initrd image
kernel=`ls /boot/vmli* | tail -1 | awk -F\- '{printf("%s-%s\n", $2,$3)}'`
initrd="/boot/initrd-${kernel}.img"
rm $initrd
/sbin/mkinitrd --preload=ehci-hcd --preload=ahci --preload=libata 
--preload=jbd --preload=ohci-hcd --preload=uhci-hcd 
--preload=scsi_wait_scan --preload=usb-storage --preload=scsi_mod 
--preload=sd_mod --preload=pata_amd --preload=ata_generic 
--preload=pata_cs5536 --preload=pata_acpi $initrd $kernel


THAT will boot. :)

Good Luck!

--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

Re: How to test cups printer system

[Phil Meyer]

Dave Feustel wrote:

I just added my hp2100 laserjet printer to f9.  I then tried to print a
small test file. I get no output (the job is queued tho) plus a warning
message that the printer may not be connected.

Do I need to do something else to get the cups system enabled?

Thanks.

  


Most HP printers want hplip.  Check your /var/log/messages for an error 
message about a 'back-end'.


# yum install hplip hplip-gui hplip-libs

Afterward, your print job should just happen.  Modern USB printers 
usually need no config at all for CPUS to see it and work.  Just plug it 
in and it should show up in printing dialogs.


Good Luck!

--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

Re: how to configure xdg-open applications?

[Paul Johnson]

On Thu, Nov 20, 2008 at 1:21 PM, Rex Dieter <[EMAIL PROTECTED]> wrote:
> Paul Johnson wrote:
>
>> I want to change the programs that xdg-open points to for things like
>> pdf or dvi.  There are no configure tools I can find on the
>> freedesktop site and the xdg-open man page gives no help at all. In
>> /etc/xdg I don't see settings for evince or such.  "grep -r pdf *" in
>> the /etc/xdg directory returns nothing.
>>
>> Throw me some help, please.
>
> xdg-open uses the default apps as defined by the desktop you're using
> (gnome, kde, etc...).  So, the question becomes, which desktop are you
> using?  Do you need help setting the default .pdf app on desktop foo?
>
> -- Rex
>

Well, I use several different desktops, if you must know.  On all of
them LyX runs and uses xdg-open to grab pdf files, and I had thought
that the freedesktop framework was aiming at having a
desktop-brand-free method of specifying what applications are used.
That is the long term goal, I think.  Googling tells me that many
people have the same desire, but it is not implemented YET because the
freedesktop people are coming along with general standards after the
desktop systems evolved.

But I have something of an answer.  The previous poster points me to
the xdg-mime program. It is used to set the default applications. I've
been testing it and reading its source code.  It is not a general
application chooser.  Rather, it "adjusts most desktops" to use a
program program. If you run it  in your current environment, it tells
you what is specified if it understands what desktop you are previous
running (AFAIK, it is OK for Gnome,KDE, and XFCE, but not for a less
desktopish desktop like an old fashioned window-manager-only setup
like  WindowMaker.  If you use xdg-mime to set a value, it tries to
set values for Gnome, KDE, and XFCE if it finds them in your system.
It can set them either for the whole system or the user account.

Another answer I've found is that Gnome users can hand edit this file:

/usr/share/applications/defaults.list

That is the "gnome" way of doing it system wide, and xdg-mime just
edits that file for you.

If an individual user already has this file,

~/.local/share/applications/defaults.list

then system-wide changes will have no effect, and users have to either
edit their own defaults.list or delete it and let it be re-created by
the desktop environment.  That will copy the system-wide set into the
user's account.

But, then again, this is all stuff I've pieced together in the last 2
hours, so hopefully the program maintainers will step up and tell us
if I have it wrong.


pj



-- 
Paul E. Johnson
Professor, Political Science
1541 Lilac Lane, Room 504
University of Kansas

-- 
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

How to test cups printer system

[Dave Feustel]

I just added my hp2100 laserjet printer to f9.  I then tried to print a
small test file. I get no output (the job is queued tho) plus a warning
message that the printer may not be connected.

Do I need to do something else to get the cups system enabled?

Thanks.

-- 
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

Re: Moving Fedora 9 Hard Disk To Another System

[Paul Johnson]

On Thu, Nov 20, 2008 at 2:42 PM, Mikkel L. Ellertson
<[EMAIL PROTECTED]> wrote:
> Paul Johnson wrote:
>>
>> When the kernel is updated, the Fedora 9 framework will rebuild a new
>> initrd and it will  NOT have the special modules in it.  On fedora
>> systems, I found no simpler solution than to edit the new-kernel
>> script and change the modules that were assumed.   Otherwise, the boot
>> up will fail just like you have been seeing.  On Ubuntu linux, I've
>> learned that the required modules can be configured in
>> /etc/modprobe.conf or someplace similar, and the initrd builder takes
>> notice of it.
>>
> What I have done in the past is to boot off the install media,
> select the rescue mode, and then chroot to where the root file
> system is mounted. I thin build the new initrd, making sure it
> matches the kernel I plan to boot from. In the future, installing a
> new kernel will build the initrd, using the information from the
> running kernel. At least it has worked correctly for the last 5
> updates on this machine sense I moved the drive here, and rebuilt
> the initrd for this motherboard.
>
> Mikkel
>
Unless you understand the mechanism through which the new initrd is
built, you cannot be confident in your statement that the new kernel
will be "using the information from the running kernel," as you put
it.  As far as I know, that is just wrong.  The initrd is built by the
new-kernel script, and it has no way of "talking to" the existing
kernel and getting the correct modules.
Instead, it is reading some configuration files under /etc, and
apparently you are lucky to have those files set correctly, but you
don't have any good reason to expect OP has same lucky configuration.

I'm not on a Fedora 9 system now, but I can tell you about Centos 52,
and it matches my memory of Fedora 8.  Fedora uses a script

/sbin/new-kernel-pkg

to handle the building of the initrd.  In that file, it calls
mkinitrd.  That file does not specify any options or modules to
pre-load.  When I want to be absolutely sure a module is loaded, I
have sometimes written them into that file.  But you see it just uses
mkinitrd without options.  So you go read mkinitrd man page, and it is
not entirely too clear about how the required modules are to be
specified, but it does say it reads "/etc/modprobe.conf" and
"/etc/modules.conf".   Note the preload option in mkinitrd is probably
where you need to focus.  Look in /etc/modprobe.conf on this Centos
system, and it has components like this:

alias scsi_hostadapter ata_piix

I am pretty sure that mkinitrd is taking note of that and using the
modules for ata_piix to get motherboard connectivity.

In the past, when I have wanted to know FOR SURE what modules are
needed, I make a small custom install on the machine in question.
Don't bother about configuring it.  Then I copy the modprobe.conf file
and the stuff in modules.conf if it exists.  Then you can go ahead and
install your standard disk image.  THen boot off a rescue disk, use it
to go into the new system and fix the modules so they are proper and
rebuild initrd.  Because you have fixed modprobe.conf, then new
kernels installs will get the right settings.

Sorry if this appears pedantic. I'm a teacher :)

PJ



-- 
Paul E. Johnson
Professor, Political Science
1541 Lilac Lane, Room 504
University of Kansas

-- 
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

Re: middle mouse - how to configure ?

[Kevin Kempter]

On Thursday 20 November 2008 03:44:04 pm kevin kempter wrote:
> Hi All;
>
> I have a Logitech Nano VX wireless mouse - I'm running Fedora 9 & KDE4
> in a VM
> (Vmware Fusion on a mac)
>
> Anyone kow how I can setup the middle mouse button ? my xorg.conf has
> no mouse
> section (see listing below)
>
> Thanks in advance
>
>
>
>
>
> # cat /etc/X11/xorg.conf
> # Xorg configuration created by system-config-display
>
> Section "ServerLayout"
>  Identifier "single head configuration"
>  Screen  0  "Screen0" 0 0
>  InputDevice"Keyboard0" "CoreKeyboard"
> EndSection
>
> Section "ServerFlags"
>  Option  "NoAutoAddDevices"
> EndSection
>
> Section "InputDevice"
>
> # keyboard added by rhpxl
>  Identifier  "Keyboard0"
>  Driver  "kbd"
>  Option  "XkbModel" "pc105"
>  Option  "XkbLayout" "us"
> EndSection
>
> Section "Monitor"
>  Identifier   "vmware"
>  VendorName   "VMware, Inc"
>  HorizSync1.0 - 1.0
>  VertRefresh  1.0 - 1.0
> EndSection
>
> Section "Device"
>  Identifier  "VMware SVGA"
>  Driver  "vmware"
> EndSection
>
> Section "Screen"
>
>  # Don't specify DefaultColorDepth unless you know what you're
>  # doing. It will override the driver's preferences which can
>  # cause the X server not to run if the host doesn't support the
>  # depth.
>  Identifier "Screen0"
>  Device "VMware SVGA"
>  Monitor"vmware"
>  DefaultDepth 24
>  SubSection "Display"
>
>  # VGA mode: better left untouched
>  Viewport   0 0
>  Depth 4
>  Modes"640x480"
>  EndSubSection
>  SubSection "Display"
>  Viewport   0 0
>  Depth 8
>  Modes"1280x1024"
>  EndSubSection
>  SubSection "Display"
>  Viewport   0 0
>  Depth 15
>  Modes"1280x1024"
>  EndSubSection
>  SubSection "Display"
>  Viewport   0 0
>  Depth 16
>  Modes"1280x1024"
>  EndSubSection
>  SubSection "Display"
>  Viewport   0 0
>  Depth 24
>
> Modes"1920x1440" "1856x1392" "1792x1344" "1600x1200" "1400x1050"
> "1280x1024" "1280x960" "1152x864" "1024x768" "832x624" "800x600"
> "720x400" "640x480" "640x400" "640x350"
>  EndSubSection
> EndSection


Hi List

Sorry about the duplicate email - It seemed I was having email issues however 
it turned out that the issue is isolated to the postgres email lists

-- 
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

middle mouse - how to configure ?

[kevin kempter]

Hi All;

I have a Logitech Nano VX wireless mouse - I'm running Fedora 9 & KDE4  
in a VM

(Vmware Fusion on a mac)

Anyone kow how I can setup the middle mouse button ? my xorg.conf has  
no mouse

section (see listing below)

Thanks in advance





# cat /etc/X11/xorg.conf
# Xorg configuration created by system-config-display

Section "ServerLayout"
Identifier "single head configuration"
Screen  0  "Screen0" 0 0
InputDevice"Keyboard0" "CoreKeyboard"
EndSection

Section "ServerFlags"
Option  "NoAutoAddDevices"
EndSection

Section "InputDevice"

# keyboard added by rhpxl
Identifier  "Keyboard0"
Driver  "kbd"
Option  "XkbModel" "pc105"
Option  "XkbLayout" "us"
EndSection

Section "Monitor"
Identifier   "vmware"
VendorName   "VMware, Inc"
HorizSync1.0 - 1.0
VertRefresh  1.0 - 1.0
EndSection

Section "Device"
Identifier  "VMware SVGA"
Driver  "vmware"
EndSection

Section "Screen"

# Don't specify DefaultColorDepth unless you know what you're
# doing. It will override the driver's preferences which can
# cause the X server not to run if the host doesn't support the
# depth.
Identifier "Screen0"
Device "VMware SVGA"
Monitor"vmware"
DefaultDepth 24
SubSection "Display"

# VGA mode: better left untouched
Viewport   0 0
Depth 4
Modes"640x480"
EndSubSection
SubSection "Display"
Viewport   0 0
Depth 8
Modes"1280x1024"
EndSubSection
SubSection "Display"
Viewport   0 0
Depth 15
Modes"1280x1024"
EndSubSection
SubSection "Display"
Viewport   0 0
Depth 16
Modes"1280x1024"
EndSubSection
SubSection "Display"
Viewport   0 0
Depth 24

Modes"1920x1440" "1856x1392" "1792x1344" "1600x1200" "1400x1050"  
"1280x1024" "1280x960" "1152x864" "1024x768" "832x624" "800x600"  
"720x400" "640x480" "640x400" "640x350"

EndSubSection
EndSection

--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

Setup middle button for a Logitech VX Nano wireless mouse ?

[Kevin Kempter]

Hi All;

I have a Logitech Nano VX wireless mouse - I'm running Fedora 9 & KDE4 in a VM 
(Vmware Fusion on a mac)

Anyone kow how I can setup the middle mouse button ? my xorg.conf has no mouse 
section (see listing below)

Thanks in advance





# cat /etc/X11/xorg.conf

# Xorg configuration created by system-config-display   
   

Section "ServerLayout"
Identifier "single head configuration"
Screen  0  "Screen0" 0 0  
InputDevice"Keyboard0" "CoreKeyboard" 
EndSection

Section "ServerFlags"
Option  "NoAutoAddDevices"
EndSection

Section "InputDevice"

# keyboard added by rhpxl
Identifier  "Keyboard0"
Driver  "kbd"  
Option  "XkbModel" "pc105"
Option  "XkbLayout" "us"  
EndSection

   
Section "Monitor"   
   
Identifier   "vmware"   
   
VendorName   "VMware, Inc"  
   
HorizSync1.0 - 1.0  
   
VertRefresh  1.0 - 1.0  
   
EndSection  
   

   
Section "Device"
   
Identifier  "VMware SVGA"   
   
Driver  "vmware"
   
EndSection  
   

   
Section "Screen"
   

   
# Don't specify DefaultColorDepth unless you know what you're   
   
# doing. It will override the driver's preferences which can
   
# cause the X server not to run if the host doesn't support the 
   
# depth.
   
Identifier "Screen0"
   
Device "VMware SVGA"
   
Monitor"vmware" 
   
DefaultDepth 24 
   
SubSection "Display"
   

   
# VGA mode: better left untouched   
   
Viewport   0 0
Depth 4
Modes"640x480"
EndSubSection
SubSection "Display"
Viewport   0 0
Depth 8
Modes"1280x1024"
EndSubSection
SubSection "Display"
Viewport   0 0
Depth 15
Modes"1280x1024"
EndSubSection
SubSection "Display"
Viewport   0 0
Depth 16
Modes"1280x1024"
EndSubSection
SubSection "Display"
Viewport   0 0
Depth 24

Modes"1920x1440" "1856x1392" "1792x1344" "1600x1200" "1400x1050" 
"1280x1024" "1280x960" "1152x864" "1024x768" "832x624" "800x600" "720x400" 
"640x480" "640x400" "640x350"
EndSubSection
EndSection

-- 
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

Re: set up NAT (network address translation) on local server

[Christopher K. Johnson]

Tim wrote:

On Thu, 2008-11-20 at 07:46 -0800, Antonio Olivares wrote:
  
[EMAIL PROTECTED] ~]# cat /etc/sysconfig/iptables 
*nat
:PREROUTING ACCEPT [1:233]  
:POSTROUTING ACCEPT [0:0]   
:OUTPUT ACCEPT [0:0]
-A POSTROUTING -s 192.168.1.0/24 -o eth0 -j SNAT --to-source 10.154.19.210  
COMMIT  
-A FORWARD -i eth1 -o eth0 -j ACCEPT  -A FORWARD -i eth0 -o eth1 -m state --state RELATED,ESTABLISHED -j ACCEPT
# manually added the changes 2008/11/20 
# Firewall configuration written by system-config-securitylevel 
# Manual customization of this file is not recommended.

*filter
:INPUT ACCEPT [0:0]
:FORWARD ACCEPT [0:0]
:OUTPUT ACCEPT [0:0]
:RH-Firewall-1-INPUT - [0:0]
-A INPUT -j RH-Firewall-1-INPUT
-A RH-Firewall-1-INPUT -i lo -j ACCEPT
-A RH-Firewall-1-INPUT -p icmp --icmp-type any -j ACCEPT
-A RH-Firewall-1-INPUT -p 50 -j ACCEPT
-A RH-Firewall-1-INPUT -p 51 -j ACCEPT
-A RH-Firewall-1-INPUT -p udp --dport 5353 -d 224.0.0.251 -j ACCEPT
-A RH-Firewall-1-INPUT -p udp -m udp --dport 631 -j ACCEPT
-A RH-Firewall-1-INPUT -p tcp -m tcp --dport 631 -j ACCEPT
-A RH-Firewall-1-INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT
-A RH-Firewall-1-INPUT -m state --state NEW -m tcp -p tcp --dport 22 -j ACCEPT
-A RH-Firewall-1-INPUT -j REJECT --reject-with icmp-host-prohibited
-A FORWARD -j REJECT --reject-with icmp-host-prohibited
COMMIT



Shouldn't there be ONLY one "COMMIT" command at the end of the file?
You've got two.

  
No, there should be one COMMIT for each table, and he has *nat and 
*filter tables.


--
  "A society grows great when old men plant trees whose shade they know
  they shall never sit in" - Greek Proverb

--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

Re: Mount usb devices

[Dave Feustel]

On Thu, Nov 20, 2008 at 02:26:28PM -0800, Rick Stevens wrote:
>
> FFS is the BSD "fast file system" (yes, the Amiga also had an FFS, but
> since the OP said "BSD", I'm going to discount the Amiga).  I think
> Linux' UFS filesystem can mount it but I'm not sure.  If it can, it
> should automount, but UFS may not recognize FFS markers even if it can
> mount it.  You can try forcing UFS to see if it'll work.
>
> First, make a directory somewhere where you want to mount it.  A good
> place would be in either /media or /mnt.  I'd do it in /mnt to leave
> /media pristine for automounts:
>
>   mkdir /mnt/test
>
> Do a "dmesg" just before you plug in the drive, plug it in, wait a few
> seconds and do "dmesg" again.  The additional lines from dmesg should
> refer to the device you plugged in.  You'll probably see something like
> this:
>
>   sd 6:0:0:0: [sdb] Assuming drive cache: write through
>sdb: sdb1
>
> (that's from plugging in a FLASH drive).  In this case, the drive
> itself is sdb (/dev/sdb) and it contains one partition, sdb1 (or
> /dev/sdb1).  Then:
>
>   mount -t ufs /dev/sdXY /path/to/your/mount/point
>
> In this case, "mount -t ufs /dev/sdb1 /mnt/test
>
> If it mounts up, voila!  If not, either you didn't specify the right
> partition or UFS doesn't mount FFS stuff.  I don't have any FFS drives
> handy or I'd test it for you.

Thanks for this. I recognise the stuff from dmesg. I was trying to
mount the ffs disk because it is handy. I have another flash device
that I would like to partition as a 2 or 3 partition drive, mkfs
and then copy data to it from (hd0,0). Then I want to recreate
hd0 as a multi-partition drive, install 64-bit f9, and then copy
the data back from the flash drive.

The stumbling block for me was that I didn't understand how the usb
devices are named and accessed in Fedora before they are mounted. 
I think I understand naming now.

-- 
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

Re: Jackd Problems -- alsa_pcm: xrun of at least 1227061150613.504 msecs

[Jonathan Ryshpan]

On Thu, 2008-11-20 at 11:16 +0100, Jeremy wrote: 
> Hello Jonathan,
> 
> To get jack running properly you need:
> - Planet CCRMA packages 
> (http://ccrma.stanford.edu/planetccrma/software/) which are not 
> available for F9
> - low latency kernel, Planet CCRMA also provides these, unfortunately 
> not for F9
> - zero latency soundcard, an onboard card probably never works without 
> an xrun every now and then
> 
> An xrun is indeed a buffer under/overrun and could be caused by numerous 
> things, always hard to put a finger on it. Could be software, hardware. 
> Best is to run jack with a light weight WM like fluxbox or IceWM and to 
> use as little other programs as possible. And to switch to another 
> version of Fedora (like 7 or 8) for which there are Planet CCRMA 
> packages available, otherwise it's no use I think.

Thanks for the info.  The fancy kernels, etc. are probably not necessary
to avoid xruns in a properly configured Fedora system with a strong
enough CPU, etc.  My own CPU is AMD x86_64 running at about 1 GHz.  In
the past I have had typically 1 xrun per hour, which hasn't affected the
sound quality of recordings perceptibly.

However your message doesn't answer the question: what does the time
interval associated with an xrun mean?  Do you (or anyone else) know?  A
reply to this question posted on the Jack-devel list indicates that the
very long time interval here is the result of a bug in this version of
jackd:
MarcO'Chapeau <[EMAIL PROTECTED]> writes: 
That's a bug fixed after 0.109.2 I'd say (is that still only in SVN ?). 
It
was due to a comparison of 2 timestamps not coming from the same clock
source afair
I have only one clock afaik on my system but who knows...

An attempt to build jackd on my system has failed due to problems in
portaudio as released in the F9 distro.  More on this in my next message
to the list.

Thanks - jon


-- 
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

Portaudio-devel missing definitions in Fedora-9

[Jonathan Ryshpan]

Portaudio-devel as released in the F9 distro is missing some entries in
its header files: in particular the definitions for the declarators (is
this the right word) PaTimestamp and PortAudioStream are missing.
Possibly a whole header file is missing.  These problems are in the
source rpm as well as in the binary.  As a result the test case
patest_two_rates.c doesn't compile (and probably other test cases
besides.)

Any help would be appreciated.  I'm posting here before reporting a bug
to Fedora in hope of being able to report a possible patch along with
the bug.  Any help would be much appreciated.

Thanks - jon




-- 
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

Re: set up NAT (network address translation) on local server

[Tim]

On Thu, 2008-11-20 at 07:46 -0800, Antonio Olivares wrote:
> [EMAIL PROTECTED] ~]# cat /etc/sysconfig/iptables 
> *nat
> :PREROUTING ACCEPT [1:233]  
> :POSTROUTING ACCEPT [0:0]   
> :OUTPUT ACCEPT [0:0]
> -A POSTROUTING -s 192.168.1.0/24 -o eth0 -j SNAT --to-source 10.154.19.210  
> COMMIT  
> -A FORWARD -i eth1 -o eth0 -j ACCEPT  -A FORWARD -i eth0 -o eth1 -m state 
> --state RELATED,ESTABLISHED -j ACCEPT
> # manually added the changes 2008/11/20   
>   
> # Firewall configuration written by system-config-securitylevel   
>   
> # Manual customization of this file is not recommended.
> *filter
> :INPUT ACCEPT [0:0]
> :FORWARD ACCEPT [0:0]
> :OUTPUT ACCEPT [0:0]
> :RH-Firewall-1-INPUT - [0:0]
> -A INPUT -j RH-Firewall-1-INPUT
> -A RH-Firewall-1-INPUT -i lo -j ACCEPT
> -A RH-Firewall-1-INPUT -p icmp --icmp-type any -j ACCEPT
> -A RH-Firewall-1-INPUT -p 50 -j ACCEPT
> -A RH-Firewall-1-INPUT -p 51 -j ACCEPT
> -A RH-Firewall-1-INPUT -p udp --dport 5353 -d 224.0.0.251 -j ACCEPT
> -A RH-Firewall-1-INPUT -p udp -m udp --dport 631 -j ACCEPT
> -A RH-Firewall-1-INPUT -p tcp -m tcp --dport 631 -j ACCEPT
> -A RH-Firewall-1-INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT
> -A RH-Firewall-1-INPUT -m state --state NEW -m tcp -p tcp --dport 22 -j ACCEPT
> -A RH-Firewall-1-INPUT -j REJECT --reject-with icmp-host-prohibited
> -A FORWARD -j REJECT --reject-with icmp-host-prohibited
> COMMIT

Shouldn't there be ONLY one "COMMIT" command at the end of the file?
You've got two.

-- 
[EMAIL PROTECTED] ~]$ uname -r
2.6.27.5-41.fc9.i686

Don't send private replies to my address, the mailbox is ignored.  I
read messages from the public lists.



-- 
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

Re: Replace 32-bit F9 with 64-bit F9

[Tim]

On Thu, 2008-11-20 at 14:24 -0500, Chris Snook wrote:
> The long answer is that anaconda and yum have no logic to handle this,
> so the only way to do it is to tell the installer not to format the
> filesystems you're installing on.  This means your installation will
> have a whole lot of random crap, which expects other random crap
> you've overwritten to be there, and anything on the system which scans
> directories for configuration files and scripts will try to use that
> random crap.

The work around for that is, prior to the new install, you boot off
something else (e.g. a rescue disc, or the new install disc, but
interrupt the installing routine), and remove the files and directories
other than home.

e.g. rm -rfd /bin
 rm -rfd /etc
 rm -rfd /usr

And so on...

This does give you a clean slate, however, it also means that you have
to choose what to install.  You don't get to do a install 64 bit with
the same list of 32 bit packages that you used to have, unless you
prepare a list of packages, too.

The other aspect to this sort of thing is user configuration files may
not be compatible between different installations.  If anything includes
a path to a 64 bit thing that's now going to be done by a 32 bit thing
in a different location, that configuration will be broken.

When I've updated a computer, in the above fashion, I renamed the home
directories.  e.g. "/home/tim" became "/home/tim-old".  I booted up,
logged in, let configurations be built for Gnome and applications, then
moved back in the things from my old directory that I wanted.  Which
might be a bookmarks file from a web browser, and some personal data
sub-directories.

-- 
[EMAIL PROTECTED] ~]$ uname -r
2.6.27.5-41.fc9.i686

Don't send private replies to my address, the mailbox is ignored.  I
read messages from the public lists.



-- 
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

Re: Mount usb devices

[Rick Stevens]

Dave Feustel wrote:

On Thu, Nov 20, 2008 at 02:55:28PM -0600, Mikkel L. Ellertson wrote:

Dave Feustel wrote:

On Thu, Nov 20, 2008 at 03:24:25PM -0500, Mark Haney wrote:

Dave Feustel wrote:

I have found no info on how to mount usb disk drives on Fedora.

How is it done?

Can F9 mount *BSD file systems?

Thanks.

Uh, you should bve able to just plug it in and fedora will automount it  
if it recognizes the file system.

I see no messages from f9 when I plug the drive in.


In the logs, or as a popup message? It should be quietly mounted on
/media/. You can control what  will be if you label the
partition(s).


When I plug in the usb disk, I now get a popup saying the volume
(OpenBSD ffs file system) cannot be mounted. Where do I find info on how
to partition the drive appropriately for fedora?


FFS is the BSD "fast file system" (yes, the Amiga also had an FFS, but
since the OP said "BSD", I'm going to discount the Amiga).  I think
Linux' UFS filesystem can mount it but I'm not sure.  If it can, it
should automount, but UFS may not recognize FFS markers even if it can
mount it.  You can try forcing UFS to see if it'll work.

First, make a directory somewhere where you want to mount it.  A good
place would be in either /media or /mnt.  I'd do it in /mnt to leave
/media pristine for automounts:

mkdir /mnt/test

Do a "dmesg" just before you plug in the drive, plug it in, wait a few
seconds and do "dmesg" again.  The additional lines from dmesg should
refer to the device you plugged in.  You'll probably see something like
this:

sd 6:0:0:0: [sdb] Assuming drive cache: write through
 sdb: sdb1

(that's from plugging in a FLASH drive).  In this case, the drive
itself is sdb (/dev/sdb) and it contains one partition, sdb1 (or
/dev/sdb1).  Then:

mount -t ufs /dev/sdXY /path/to/your/mount/point

In this case, "mount -t ufs /dev/sdb1 /mnt/test

If it mounts up, voila!  If not, either you didn't specify the right
partition or UFS doesn't mount FFS stuff.  I don't have any FFS drives
handy or I'd test it for you.
--
- Rick Stevens, Systems Engineer  [EMAIL PROTECTED] -
- AIM/Skype: therps2ICQ: 22643734Yahoo: origrps2 -
--
- "I was contemplating the immortal words of Socrates when he said,  -
- 'I drank what?'"   -- Val Kilmer in "Real Genius"  -
--

--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

Re: More strange F9 dependencies

[Tim]

Beartooth:
>>  But what of nautilus? It would be fine for bluez to depend on it; 
>> but why should it depend on bluez?? Is someone going to tell me that 
>> pango uses bluez, with or without hardware? And then sneer down his nose 
>> that I'm welcome to write new code??

Michael Schwendt:
> Run: repoquery --whatrequires libbluetooth.so.2
> 
> That shows all packages with a _direct_ dependency on that library.
> Nautilus depends on something that depends on bluez-libs.

It strikes me that with things like this, and others (e.g. requiring
CUPs on a single, headless, remote web server), that we should be
developing some strategies to remove *USELESS* dependencies.  Even if
that means an extra "hack" repo with various dummy RPMs to satisfy RPM
demands for files that will never be used, or to supply the bare minimum
files it wants for a dependency, without the rest of the package.

-- 
[EMAIL PROTECTED] ~]$ uname -r
2.6.27.5-41.fc9.i686

Don't send private replies to my address, the mailbox is ignored.  I
read messages from the public lists.



-- 
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

Re: set up NAT (network address translation) on local server

[Christopher K. Johnson]

If you send me off-list the iptables file you want as an attachment, I 
will send you back notes and a corrected file.


Clearly there is some simple mis-communication or editing going on 
because this is a basic iptables configuration.


Chris

--
  "A society grows great when old men plant trees whose shade they know
  they shall never sit in" - Greek Proverb

--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

Re: No Shutdown Service in Init 1

[Mikkel L. Ellertson]

Aaron Konstam wrote:
> On Wed, 2008-11-19 at 19:09 -0600, Mikkel L. Ellertson wrote:
>>> I agreee with the above but this raises the question what would running
>>> halt do?
>>>
>> Running halt or shutdown works the same as it does in any other run
>> level. There is just less for shutdown to actually shut down.
>>
> I was being to subtle. halt is a coomand that will halt a system in rl
> 1.
Sorry - I am kind of dense today - my head is all plugged up. :(

Mikkel
-- 

  Do not meddle in the affairs of dragons,
for thou art crunchy and taste good with Ketchup!



signature.asc
Description: OpenPGP digital signature
-- 
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

Re: what is .local directory?

[Brian Millett]

On Thu, 2008-11-20 at 15:16 -0600, Rex Dieter wrote:
> Brian Millett wrote:
> 
> > In my home folder, I have a .local folder.  What is it?  Should I care?
> 
> Used by freedesktop-related specs, namely,
> http://standards.freedesktop.org/basedir-spec/
> 

Thanks.  That is something I didn't know.

-- 
Brian Millett - [ G'Kar (to Delenn), "The Gathering"]
"On Narn, we heard the decision to surrender came from your holy men. A
 secret group called the Gray Council. Weak, frightened old fools with
 no vision or the will to fight."



signature.asc
Description: This is a digitally signed message part
-- 
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

Re: getting /lib/ld-linux.so.2 on a 64-bit f10 preview install?

[James Wilkinson]

Robert P. J. Day wrote:
>   long story short:  x86-64 f10 preview install on AMD64 laptop.
> install coldfire cross-compile toolchain, which immediately fails
> looking for /lib/ld-linux.so.2, which it obviously won't find since
> the system has /lib64/ld-2.9.so (along with various symlinks).
> 
>   solution?

Well, on F9,
$ yum whatprovides /lib/ld-linux.so.2
reports

glibc-2.8-8.i386 : The GNU libc libraries
Matched from:
Filename: /lib/ld-linux.so.2



glibc-2.8-8.i686 : The GNU libc libraries
Matched from:
Filename: /lib/ld-linux.so.2



glibc-2.8-3.i386 : The GNU libc libraries
Matched from:
Filename: /lib/ld-linux.so.2



glibc-2.8-3.i686 : The GNU libc libraries
Matched from:
Filename: /lib/ld-linux.so.2



glibc-2.8-8.i386 : The GNU libc libraries
Matched from:
Other   : Provides-match: /lib/ld-linux.so.2

I suspect that both the i686 and the i386 will work, and there will be
little difference between them. The i686 version may be *slightly*
faster (especially if you have multiple cores).

Hope this helps,

James.

-- 
E-mail: james@ | "This was, apparently, beyond her ken.
aprilcottage.co.uk | So far beyond her ken that she was well into barbie
   | territory."
   | -- J. D.  Baldwin

-- 
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

Re: Mount usb devices

[Dave Feustel]

On Thu, Nov 20, 2008 at 02:55:28PM -0600, Mikkel L. Ellertson wrote:
> Dave Feustel wrote:
> > On Thu, Nov 20, 2008 at 03:24:25PM -0500, Mark Haney wrote:
> >> Dave Feustel wrote:
> >>> I have found no info on how to mount usb disk drives on Fedora.
> >>>
> >>> How is it done?
> >>>
> >>> Can F9 mount *BSD file systems?
> >>>
> >>> Thanks.
> >>>
> >> Uh, you should bve able to just plug it in and fedora will automount it  
> >> if it recognizes the file system.
> > 
> > I see no messages from f9 when I plug the drive in.
> > 
> In the logs, or as a popup message? It should be quietly mounted on
> /media/. You can control what  will be if you label the
> partition(s).

When I plug in the usb disk, I now get a popup saying the volume
(OpenBSD ffs file system) cannot be mounted. Where do I find info on how
to partition the drive appropriately for fedora?

Thanks.

-- 
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

Re: what is .local directory?

[Rex Dieter]

Brian Millett wrote:

> In my home folder, I have a .local folder.  What is it?  Should I care?

Used by freedesktop-related specs, namely,
http://standards.freedesktop.org/basedir-spec/

-- Rex

-- 
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

Re: No Shutdown Service in Init 1

[Aaron Konstam]

On Wed, 2008-11-19 at 19:09 -0600, Mikkel L. Ellertson wrote:
> Aaron Konstam wrote:
> >> Yes, you need acpid running for the power switch to work. It does
> >> not run during run level 1 by default. Run level 1 is normally
> >> reserved for fixing problems on the system, as it outs it in the
> >> single user mode, with root as the user. Only the minimum services
> >> necessary are started.
> >>
> > I agreee with the above but this raises the question what would running
> > halt do?
> > 
> Running halt or shutdown works the same as it does in any other run
> level. There is just less for shutdown to actually shut down.
> 
I was being to subtle. halt is a coomand that will halt a system in rl
1.
-- 
Aaron Konstam <[EMAIL PROTECTED]>

-- 
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

Re: Network Card Naming Issue

[Phil Meyer]

Manish Kathuria wrote:

Hi,

I have experienced a strange issue in Fedora 9 while replacing
ethernet cards. Whenever a network card is replaced in Fedora 9, many
times the new NIC takes a new logical interface name instead of taking
the original interface name. For example, if a network card eth0 is
removed from a Fedora 9 system and is replaced by another network
card, the new card appears as eth1 or eth2 instead of eth0. This
happens even if the cards are having the same chipset (and therefore
the driver). What could be the reason for this behaviour ?  It leads
to a number of problems like modification in scripts, etc. I have
never observed this in the earlier distributions.

Thanks,
  


Other posters have given good answers as to how the newer 
kudzu/anaconda/udev/hal combo works, but perhaps a bit of reasoning is 
in order.


Consider for a moment, if you will, Solaris 2.3 on large hardware, 
capable of housing up to 64 disk controllers. 
Assume that cards are in slots 1, 5, and 9.
Assume that all drives on all controllers are part of software based 
RAID volumes.
Assume a new card is inserted into slot 2 while the machine is down, and 
new hard drives are attached to the new controller.


On next boot, all hard drives were reordered based upon controller card 
number.  All RAID volumes are now corrupt and will not mount, and are 
not recoverable.


This was a disaster for SUN, who quickly came up with a remedy.  All 
hardware would be cataloged and the catalog would be preserved upon 
rebooting.  Any new devices, would be given a new device number, 
regardless of whether a matching device is still present in the system.


By doing this, any new controller detected would not affect existing 
controllers or disc ordering.


At first, it was annoying, because failed controllers could not be 
replaced without hardship.


Eventually, the solution became reasonable, and was certainly better 
that the alternative, especially when considering software based RAID.


Now jump forward to modern days and the Linux kernel, and kernel 
supported hardware device drivers.


The same issues were in effect for Linux, as what was happening to early 
Solaris 2.X releases.  A method MUST exist to remember old hardware.


Right now, the key hardware components are remembered by udev.  As this 
new method matures, it will become easier to maintain/remove hardware.  
But think of the alternative!  The old way might be ok for single drive, 
single interface systems, but not otherwise.


There are many of us who remember the 'bad old days' when this issue was 
capable of destroying months of work!


Good Luck!

--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

Re: Mount usb devices

[Mikkel L. Ellertson]

Dave Feustel wrote:
> On Thu, Nov 20, 2008 at 03:24:25PM -0500, Mark Haney wrote:
>> Dave Feustel wrote:
>>> I have found no info on how to mount usb disk drives on Fedora.
>>>
>>> How is it done?
>>>
>>> Can F9 mount *BSD file systems?
>>>
>>> Thanks.
>>>
>> Uh, you should bve able to just plug it in and fedora will automount it  
>> if it recognizes the file system.
> 
> I see no messages from f9 when I plug the drive in.
> 
In the logs, or as a popup message? It should be quietly mounted on
/media/. You can control what  will be if you label the
partition(s).

>> Or, you can look at dmesg when you plug the drive in, find the device  
>> assignment and manually mount it.
> 
> This works, but I do not recognize the device name in the dmesg output.
> Also, dmesg reports that it cannout mount the device because ufs is
> compiled read-only, not read-write.
> 
The device will be a SCSI drive. Something like /dev/sdf and then
device entries for each partition. But it sounds like the system is
not identifying the file system type correctly. You may have to
search out the correct module name for the file system, and load
that manually before plugging in the drive.

Mikkel
-- 

  Do not meddle in the affairs of dragons,
for thou art crunchy and taste good with Ketchup!



signature.asc
Description: OpenPGP digital signature
-- 
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

Re: FIXED IP on FC 8

[Mikkel L. Ellertson]

Jim wrote:
> FC8 / KDE
> 
> I have a box that has DHCP setup, I have to communicate with 700 miles
> away, through a Linksys WRT54G, I have Port Forwarding setup in router
> to 192.16.1.100 to this box.
> But When rebooting this box 700 miles away computer, the IP is changed
> to 192.16.1.101 and I no longer can connect to it , because router is
> set to
> Port Forwarding to 192.168.1.100.
> 
> If I do a Static IP setup on that box FC8, 700 miles away, how will
> NetworkManager come in to play ??
> Will it have problem with a setup Static IP ??
> 
> And does someone have have a Static IP example of
> /etc/sysconfig/network.scripts/ifcfg-eth0 that I can use to do setup
> correctly, I don't completely trust system-config-network to do it
> right, let just say, I have had a bad experience in the past. I like to
> go into ifcfg-eth0 and edit what I want.
> 
One way to handle this is to give the MAC address of the NIC a fixed
IP address in the router. What I think happened in this case is that
the computer did not release the lease on 192.168.1.100 when it
rebooted, and did not ask to renew that lease when it booted. So it
was given the next free IP address.

I do not think you want to use NetworkManager is this case anyway.
Under the normal configuration, the network is not going to come up
until someone logs in. If you are going to be doing remote access,
you are better off using the network service instead. That makes
setting a static IP address easier. But you will want to make sure
the static address you use in not in the range the router gives out
using DHCP.

Mikkel
-- 

  Do not meddle in the affairs of dragons,
for thou art crunchy and taste good with Ketchup!



signature.asc
Description: OpenPGP digital signature
-- 
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

Re: Moving Fedora 9 Hard Disk To Another System

[Mikkel L. Ellertson]

Paul Johnson wrote:
> 
> When the kernel is updated, the Fedora 9 framework will rebuild a new
> initrd and it will  NOT have the special modules in it.  On fedora
> systems, I found no simpler solution than to edit the new-kernel
> script and change the modules that were assumed.   Otherwise, the boot
> up will fail just like you have been seeing.  On Ubuntu linux, I've
> learned that the required modules can be configured in
> /etc/modprobe.conf or someplace similar, and the initrd builder takes
> notice of it.
> 
What I have done in the past is to boot off the install media,
select the rescue mode, and then chroot to where the root file
system is mounted. I thin build the new initrd, making sure it
matches the kernel I plan to boot from. In the future, installing a
new kernel will build the initrd, using the information from the
running kernel. At least it has worked correctly for the last 5
updates on this machine sense I moved the drive here, and rebuilt
the initrd for this motherboard.

Mikkel
-- 

  Do not meddle in the affairs of dragons,
for thou art crunchy and taste good with Ketchup!



signature.asc
Description: OpenPGP digital signature
-- 
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

Re: Mount usb devices

[Dave Feustel]

On Thu, Nov 20, 2008 at 03:24:25PM -0500, Mark Haney wrote:
> Dave Feustel wrote:
>> I have found no info on how to mount usb disk drives on Fedora.
>>
>> How is it done?
>>
>> Can F9 mount *BSD file systems?
>>
>> Thanks.
>>
>
> Uh, you should bve able to just plug it in and fedora will automount it  
> if it recognizes the file system.

I see no messages from f9 when I plug the drive in.

> Or, you can look at dmesg when you plug the drive in, find the device  
> assignment and manually mount it.

This works, but I do not recognize the device name in the dmesg output.
Also, dmesg reports that it cannout mount the device because ufs is
compiled read-only, not read-write.

> What filesystem does your BSD system use on that drive?  There are few  
> filesystems that linux can't mount, although some might require more  
> setup than others.

ffs2 is close to the name used by openbsd.

> In this case, google is your friend, I'm sure you can google mounting  
> USB drives and Fedora and get a good howto.

Actually, I found nothing at all useful regarding mounting usb devices.
Also, I found nothing at all useful using either man or apropos on
fedora. I found no useful info in the fedora f9 bible on mounting usb or
what usb device names look like. In this regard, OpenBSD has much better
documentation on USB. Maybe there is a hook for usb in fedora I just
don't know about yet. I also tried a google search for usb info on
the fedora site. I'm just having no luck with this today.
>
>
>
> -- 
> Frustra laborant quotquot se calculationibus fatigant pro inventione  
> quadraturae circuli
>
> Mark Haney
> Sr. Systems Administrator
> ERC Broadband
> (828) 350-2415
>
> Call (866) ERC-7110 for after hours support
>
> -- 
> fedora-list mailing list
> fedora-list@redhat.com
> To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
> Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

-- 
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

what is .local directory?

[Brian Millett]

In my home folder, I have a .local folder.  What is it?  Should I care?

Thanks.
-- 
Brian Millett - [ Mariah, "The Long Dark"]
"Don't make promises life won't let you keep."



signature.asc
Description: This is a digitally signed message part
-- 
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

Re: Mount usb devices

[Mark Haney]

Dave Feustel wrote:

I have found no info on how to mount usb disk drives on Fedora.

How is it done?

Can F9 mount *BSD file systems?

Thanks.



Uh, you should bve able to just plug it in and fedora will automount it 
if it recognizes the file system.


Or, you can look at dmesg when you plug the drive in, find the device 
assignment and manually mount it.


What filesystem does your BSD system use on that drive?  There are few 
filesystems that linux can't mount, although some might require more 
setup than others.


In this case, google is your friend, I'm sure you can google mounting 
USB drives and Fedora and get a good howto.




--
Frustra laborant quotquot se calculationibus fatigant pro inventione 
quadraturae circuli


Mark Haney
Sr. Systems Administrator
ERC Broadband
(828) 350-2415

Call (866) ERC-7110 for after hours support

--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

Mount usb devices

[Dave Feustel]

I have found no info on how to mount usb disk drives on Fedora.

How is it done?

Can F9 mount *BSD file systems?

Thanks.

-- 
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

Re: set up NAT (network address translation) on local server

[Antonio Olivares]

--- On Thu, 11/20/08, Christopher K. Johnson <[EMAIL PROTECTED]> wrote:

> From: Christopher K. Johnson <[EMAIL PROTECTED]>
> Subject: Re: set up NAT (network address translation) on local server
> To: "Community assistance, encouragement, and advice for using Fedora." 
> 
> Date: Thursday, November 20, 2008, 10:27 AM
> It appears from your email that there was an editing error
> at the COMMIT or line after.
> Perhaps instead of a line-end on those lines it has spaces
> and wrapped them into one long line?
> Could happen from copy and paste depending on
> circumstances.
> Check that each rule is on its own line.
> 

I reset the iptables back to the original condition and added them, but still 
no joy :(


[EMAIL PROTECTED] ~]# gedit /etc/sysconfig/iptables &
[1] 8516   
[EMAIL PROTECTED] ~]# service iptables stop
iptables: Flushing firewall rules: [  OK  ]
iptables: Setting chains to policy ACCEPT: filter  [  OK  ]
iptables: Unloading modules:   [  OK  ]
[EMAIL PROTECTED] ~]# service iptables restart
iptables: Flushing firewall rules: [  OK  ]
iptables: Setting chains to policy ACCEPT: filter  [  OK  ]
iptables: Unloading modules:   [  OK  ]
iptables: Applying firewall rules: Bad argument `iptables' 
Error occurred at line: 2  
Try `iptables-restore -h' or 'iptables-restore --help' for more information.
   [FAILED] 
[EMAIL PROTECTED] ~]# service iptables stop
iptables: Flushing firewall rules: [  OK  ]
iptables: Setting chains to policy ACCEPT: nat filter  [  OK  ]
iptables: Unloading modules:   [  OK  ]
[EMAIL PROTECTED] ~]# iptables -A FORWARD -i eth1 -o eth0 -j ACCEPT [1]+  Done  
  gedit /etc/sysconfig/iptables   
[EMAIL PROTECTED] ~]# iptables -A FORWARD -i eth0 -o eth1 -m state --state 
ESTABLISHED,RELATED -j ACCEPT   
   
[EMAIL PROTECTED] ~]# iptables -A POSTROUTING -t nat -s 192.168.1.0/24 -o eth0 
-j SNAT --to-source 10.154.19.210  
[EMAIL PROTECTED] ~]# iptables-save
# Generated by iptables-save v1.4.1.1 on Thu Nov 20 13:14:50 2008
*nat 
:PREROUTING ACCEPT [5:692]   
:POSTROUTING ACCEPT [0:0]
:OUTPUT ACCEPT [0:0] 
-A POSTROUTING -s 192.168.1.0/24 -o eth0 -j SNAT --to-source 10.154.19.210 
COMMIT 
# Completed on Thu Nov 20 13:14:50 2008
# Generated by iptables-save v1.4.1.1 on Thu Nov 20 13:14:50 2008  
*filter
:INPUT ACCEPT [2483:1813687]   
:FORWARD ACCEPT [0:0]  
:OUTPUT ACCEPT [2598:1049836]  
-A FORWARD -i eth1 -o eth0 -j ACCEPT   
-A FORWARD -i eth0 -o eth1 -m state --state RELATED,ESTABLISHED -j ACCEPT  
COMMIT 
# Completed on Thu Nov 20 13:14:50 2008
[EMAIL PROTECTED] ~]# service iptables restart
iptables: Flushing firewall rules: [  OK  ]
iptables: Setting chains to policy ACCEPT: nat filter  [  OK  ]
iptables: Unloading modules:   [  OK  ]
iptables: Applying firewall rules: [  OK  ]
iptables: Loading additional modules: ip_conntrack_netbios_[  OK  ]
[EMAIL PROTECTED] ~]# service dhcpd start
Starting dhcpd:[  OK  ]
[EMAIL PROTECTED] ~]#

The iptables get back to original state.  error in iptables-save ?/bug 

[EMAIL PROTECTED] ~]# cat /etc/sysconfig/iptables
# Firewall configuration written by system-config-securitylevel
# Manual customization of this file is not recommended.
*filter
:INPUT ACCEPT [0:0]
:FORWARD ACCEPT [0:0]
:OUTPUT ACCEPT [0:0]
:RH-Firewall-1-INPUT - [0:0]
-A INPUT -j RH-Firewall-1-INPUT
-A RH-Firewall-1-INPUT -i lo -j ACCEPT
-A RH-Firewall-1-INPUT -p icmp --icmp-type any -j ACCEPT
-A RH-Firewall-1-INPUT -p 50 -j ACCEPT
-A RH-Firewall-1-INPUT -p 51 -j ACCEPT
-A RH-Firewall-1-INPUT -p udp --dport 5353 -d 224.0.0.251 -j ACCEPT
-A RH-Firewall-1-INPUT -p udp -m udp --dport 631 -j ACCEPT
-A RH-Firewall-1-INPUT -p tcp -m tcp --dport 631 -j ACCEPT
-A RH-Firewall-1-INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT
-A RH-Firewall-1-INPUT -m sta

Re: More strange F9 dependencies

[Michael Schwendt]

On Thu, 20 Nov 2008 18:43:17 + (UTC), Beartooth wrote:

> 
>   I have no PDA, nor expect ever to, much less hardware to connect 
> it to a PC.
> 
>   When I was working, and literally running my life on rails, its 
> ancestors, then called organizers, were fine things; I had a whole series 
> of them. 
> 
>   Those who want or need them are welcome to them; strength to 
> their arms. Theirs, not mine.  To an old retired fart without a schedule, 
> a PDA or even a fancy phone is a dispensable expense, and thus cruft at 
> best, if not a security liability. So I tried to cut.
> 
> [EMAIL PROTECTED] ~]# yum remove bluez-*
>   []
> Dependencies Resolved
> 
> 
>  Package   Arch  Version Repository   
> Size 
> 
> Removing:
>  bluez-libsi386  3.36-1.fc9  installed
> 126 k
>  bluez-utils-cups  i386  3.36-1.fc9  
> installed 40 k
> Removing for dependencies:
>  gnome-user-share  i386  0.31-1.fc9  installed
> 219 k
>  gvfs  i386  0.2.5-1.fc9 installed
> 3.5 M
>  gvfs-fuse i386  0.2.5-1.fc9 
> installed 25 k
>  libwiimotei386  0.4-6.fc9   
> installed 46 k
>  nautilus  i386  2.22.5.1-1.fc9  
> installed 15 M
>  obex-data-server  i386  1:0.3.4-1.fc9   installed
> 145 k
>  xorg-x11-drivers  i386  7.3-4.fc9   
> installed 0.0 
>  xorg-x11-drv-wiimote  i386  0.0.1-1.fc9 
> installed 12 k
> 
> Transaction Summary
> 
> Install  0 Package(s) 
> Update   0 Package(s) 
> Remove  10 Package(s) 
> 
> Is this ok [y/N]: n
> Exiting on user Command
> 
>   Some of those dependencies certainly make sense, and others look 
> likely to. Some of them. I grant that.
> 
>   Some make mud seem clear. I don't understand, despite googling, 
> what gvfs is or does. I know only that it too threatened to take a long 
> list of indispensable apps with it if removed -- and that the gnome 
> system monitor always shows some half dozen of its creatures, sleeping.
> 
>   But what of nautilus? It would be fine for bluez to depend on it; 
> but why should it depend on bluez?? Is someone going to tell me that 
> pango uses bluez, with or without hardware? And then sneer down his nose 
> that I'm welcome to write new code??

Run: repoquery --whatrequires libbluetooth.so.2

That shows all packages with a _direct_ dependency on that library.
Nautilus depends on something that depends on bluez-libs.

>   What ever became of linux being tailorable??

A Linux base distribution is tailored already.
Not each and every feature can be toggled on/off at run-time or
install-time. Some features build the core of the distribution.

-- 
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

Re: Replace 32-bit F9 with 64-bit F9

[Chris Snook]

Dave Feustel wrote:

I think I know the answer to this, but I am asking anyway just in case I
get a surprise.

I'm running 32-bit F9. I just got a 64-bit F9 install disk from
Cheapbytes and I'm wondering if there is a way to install the 64-bit
system over the 32-bit system without wiping out the current data.

It may be that I should just wait for the 64-bit F10 before doing
anything, since it is so close to release.

Thanks.


The short answer is no.

The long answer is that anaconda and yum have no logic to handle this, so the 
only way to do it is to tell the installer not to format the filesystems you're 
installing on.  This means your installation will have a whole lot of random 
crap, which expects other random crap you've overwritten to be there, and 
anything on the system which scans directories for configuration files and 
scripts will try to use that random crap.  If the packages you install are a 
strict superset of the packages in the original system, and provide the same 
files (which is the case if both are F9 and you haven't installed external 
packages) it will most likely be able to boot, but you'll still probably 
experience see things breaking in bizarre ways.  I've done this to get data off 
a system I could PXE-boot into an installer but couldn't boot into rescue mode, 
but it's very ugly and not something you want to actually use.


The lesson is that you should always put /home on a separate logical volume, and 
the same goes for anything else you want to preserve, like /srv.


-- Chris

--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

Re: how to configure xdg-open applications?

[Rex Dieter]

Paul Johnson wrote:

> I want to change the programs that xdg-open points to for things like
> pdf or dvi.  There are no configure tools I can find on the
> freedesktop site and the xdg-open man page gives no help at all. In
> /etc/xdg I don't see settings for evince or such.  "grep -r pdf *" in
> the /etc/xdg directory returns nothing.
> 
> Throw me some help, please.

xdg-open uses the default apps as defined by the desktop you're using
(gnome, kde, etc...).  So, the question becomes, which desktop are you
using?  Do you need help setting the default .pdf app on desktop foo?

-- Rex

-- 
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

Re: how to configure xdg-open applications?

[Mark Knoop]

At 13:01 on 20 Nov 2008, Paul Johnson wrote:
> I want to change the programs that xdg-open points to for things like
> pdf or dvi.  There are no configure tools I can find on the
> freedesktop site and the xdg-open man page gives no help at all. In
> /etc/xdg I don't see settings for evince or such.  "grep -r pdf *" in
> the /etc/xdg directory returns nothing.
> 
> Throw me some help, please.

apropos xdg
...
xdg-mime (1)  - command line tool for querying information
about file type handling and adding descriptions for new file types
...

man xdg-mime

should tell you all you need to know.

-- 
Mark Knoop

-- 
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

Re: Moving Fedora 9 Hard Disk To Another System

[Paul Johnson]

On Wed, Nov 19, 2008 at 7:23 PM, Manish Kathuria
<[EMAIL PROTECTED]> wrote:
> For a large installation of Fedora 9 we are cloning an updated system
> on identical hard disks and then using that hard disk on other
> systems. Most of the systems are either Pentium 4 or Core Duo
> processor based and are capable of running the same kernel (i686) The
> minor problems being faced include difference in network card drivers
> requiring reconfiguration . However in certain cases, though we are
> able to successfully boot Fedora 9 on a system using a cloned hard
> disk but if the same hard disk is moved to another system having a
> different motherboard, the system boot process comes to a halt after a
> few steps as it is not able to locate the file systems on the hard
> disk. The GRUB screen is displayed indicating that the MBR is being
> read properly. Can there be a likelihood of the disk geometry being
> interpreted in different manner leading to non recognition of
> filesystems ? I would appreciate any tips or suggestions.
>

I have done this and seen this same problem.  The previous poster's
suggestion about the modules is probably right.  If you google for
"installing Fedora 5 on an external usb hard disk", you will probably
learn about this the same way I did.  The install on a PC selects some
hardware devices and compiles the into the initrd file, and if you
take the disk to another system (assuming you do not use UUID in the
grub.conf file) , then it will often work, but not always.   The hard
part is to figure which module is missing.

So, with the CURRENT KERNEL on the working disk, you can put the
modules for usb and scsi in the initrd like so:

mkinitrd --with-usb --preload=ehci-hcd --preload=usb-storage
--preload=scsi_mod --preload=sd_mod ./usbinitrd-`uname -r` `uname -r`


Then you reconfigure grub.conf to use that initrd.

Here's the bad news for you.

When the kernel is updated, the Fedora 9 framework will rebuild a new
initrd and it will  NOT have the special modules in it.  On fedora
systems, I found no simpler solution than to edit the new-kernel
script and change the modules that were assumed.   Otherwise, the boot
up will fail just like you have been seeing.  On Ubuntu linux, I've
learned that the required modules can be configured in
/etc/modprobe.conf or someplace similar, and the initrd builder takes
notice of it.




> Thanks,
> --
> Manish Kathuria
>
> --
> fedora-list mailing list
> fedora-list@redhat.com
> To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
> Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
>



-- 
Paul E. Johnson
Professor, Political Science
1541 Lilac Lane, Room 504
University of Kansas

-- 
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

how to configure xdg-open applications?

[Paul Johnson]

I want to change the programs that xdg-open points to for things like
pdf or dvi.  There are no configure tools I can find on the
freedesktop site and the xdg-open man page gives no help at all. In
/etc/xdg I don't see settings for evince or such.  "grep -r pdf *" in
the /etc/xdg directory returns nothing.

Throw me some help, please.

-- 
Paul E. Johnson
Professor, Political Science
1541 Lilac Lane, Room 504
University of Kansas

-- 
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

More strange F9 dependencies

[Beartooth]

I have no PDA, nor expect ever to, much less hardware to connect 
it to a PC.

When I was working, and literally running my life on rails, its 
ancestors, then called organizers, were fine things; I had a whole series 
of them. 

Those who want or need them are welcome to them; strength to 
their arms. Theirs, not mine.  To an old retired fart without a schedule, 
a PDA or even a fancy phone is a dispensable expense, and thus cruft at 
best, if not a security liability. So I tried to cut.

[EMAIL PROTECTED] ~]# yum remove bluez-*
[]
Dependencies Resolved


 Package   Arch  Version Repository   
Size 

Removing:
 bluez-libsi386  3.36-1.fc9  installed
126 k
 bluez-utils-cups  i386  3.36-1.fc9  
installed 40 k
Removing for dependencies:
 gnome-user-share  i386  0.31-1.fc9  installed
219 k
 gvfs  i386  0.2.5-1.fc9 installed
3.5 M
 gvfs-fuse i386  0.2.5-1.fc9 
installed 25 k
 libwiimotei386  0.4-6.fc9   
installed 46 k
 nautilus  i386  2.22.5.1-1.fc9  
installed 15 M
 obex-data-server  i386  1:0.3.4-1.fc9   installed
145 k
 xorg-x11-drivers  i386  7.3-4.fc9   
installed 0.0 
 xorg-x11-drv-wiimote  i386  0.0.1-1.fc9 
installed 12 k

Transaction Summary

Install  0 Package(s) 
Update   0 Package(s) 
Remove  10 Package(s) 

Is this ok [y/N]: n
Exiting on user Command

Some of those dependencies certainly make sense, and others look 
likely to. Some of them. I grant that.

Some make mud seem clear. I don't understand, despite googling, 
what gvfs is or does. I know only that it too threatened to take a long 
list of indispensable apps with it if removed -- and that the gnome 
system monitor always shows some half dozen of its creatures, sleeping.

But what of nautilus? It would be fine for bluez to depend on it; 
but why should it depend on bluez?? Is someone going to tell me that 
pango uses bluez, with or without hardware? And then sneer down his nose 
that I'm welcome to write new code??

What ever became of linux being tailorable??

-- 
Beartooth Staffwright, PhD, Neo-Redneck Linux Convert
Remember I know precious little of what I am talking about.

-- 
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

Re: set up NAT (network address translation) on local server

[Christopher K. Johnson]

It appears from your email that there was an editing error at the COMMIT 
or line after.
Perhaps instead of a line-end on those lines it has spaces and wrapped 
them into one long line?

Could happen from copy and paste depending on circumstances.
Check that each rule is on its own line.

Antonio Olivares wrote:

How can I fix this?
I manually edited the file and I stopped service and now I get :

[EMAIL PROTECTED] ~]# gedit /etc/sysconfig/iptables &
[1] 7697   
[EMAIL PROTECTED] ~]# service iptables stop

iptables: Flushing firewall rules: [  OK  ]
iptables: Setting chains to policy ACCEPT: nat filter  [  OK  ]
iptables: Unloading modules:   [  OK  ]
[1]+  Donegedit /etc/sysconfig/iptables
[EMAIL PROTECTED] ~]# service iptables restart

iptables: Flushing firewall rules: [  OK  ]
iptables: Setting chains to policy ACCEPT: filter  [  OK  ]
iptables: Unloading modules:   [  OK  ]
iptables: Applying firewall rules: Bad argument `COMMIT'   
Error occurred at line: 6  
Try `iptables-restore -h' or 'iptables-restore --help' for more information.
   [FAILED] 
[EMAIL PROTECTED] ~]# cat /etc/sysconfig/iptables 
*nat
:PREROUTING ACCEPT [1:233]  
:POSTROUTING ACCEPT [0:0]   
:OUTPUT ACCEPT [0:0]
-A POSTROUTING -s 192.168.1.0/24 -o eth0 -j SNAT --to-source 10.154.19.210  
COMMIT  
-A FORWARD -i eth1 -o eth0 -j ACCEPT   -A FORWARD -i eth0 -o eth1 -m state --state RELATED,ESTABLISHED -j ACCEPT
# manually added the changes 2008/11/20 
# Firewall configuration written by system-config-securitylevel 
# Manual customization of this file is not recommended.

*filter
:INPUT ACCEPT [0:0]
:FORWARD ACCEPT [0:0]
:OUTPUT ACCEPT [0:0]
:RH-Firewall-1-INPUT - [0:0]
-A INPUT -j RH-Firewall-1-INPUT
-A RH-Firewall-1-INPUT -i lo -j ACCEPT
-A RH-Firewall-1-INPUT -p icmp --icmp-type any -j ACCEPT
-A RH-Firewall-1-INPUT -p 50 -j ACCEPT
-A RH-Firewall-1-INPUT -p 51 -j ACCEPT
-A RH-Firewall-1-INPUT -p udp --dport 5353 -d 224.0.0.251 -j ACCEPT
-A RH-Firewall-1-INPUT -p udp -m udp --dport 631 -j ACCEPT
-A RH-Firewall-1-INPUT -p tcp -m tcp --dport 631 -j ACCEPT
-A RH-Firewall-1-INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT
-A RH-Firewall-1-INPUT -m state --state NEW -m tcp -p tcp --dport 22 -j ACCEPT
-A RH-Firewall-1-INPUT -j REJECT --reject-with icmp-host-prohibited
-A FORWARD -j REJECT --reject-with icmp-host-prohibited
COMMIT
[EMAIL PROTECTED] ~]#

Thanks,

Antonio 



  

  



--
  "A society grows great when old men plant trees whose shade they know
  they shall never sit in" - Greek Proverb

--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

Replace 32-bit F9 with 64-bit F9

[Dave Feustel]

I think I know the answer to this, but I am asking anyway just in case I
get a surprise.

I'm running 32-bit F9. I just got a 64-bit F9 install disk from
Cheapbytes and I'm wondering if there is a way to install the 64-bit
system over the 32-bit system without wiping out the current data.

It may be that I should just wait for the 64-bit F10 before doing
anything, since it is so close to release.

Thanks.

-- 
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

FIXED IP on FC 8

[Jim]

FC8 / KDE

I have a box that has DHCP setup, I have to communicate with 700 miles 
away, through a Linksys WRT54G, I have Port Forwarding setup in router 
to 192.16.1.100 to this box.
But When rebooting this box 700 miles away computer, the IP is changed 
to 192.16.1.101 and I no longer can connect to it , because router is set to

Port Forwarding to 192.168.1.100.

If I do a Static IP setup on that box FC8, 700 miles away, how will 
NetworkManager come in to play ??

Will it have problem with a setup Static IP ??

And does someone have have a Static IP example of
/etc/sysconfig/network.scripts/ifcfg-eth0 that I can use to do setup
correctly, I don't completely trust system-config-network to do it 
right, let just say, I have had a bad experience in the past. I like to 
go into ifcfg-eth0 and edit what I want.


--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

Re: Network Card Naming Issue

[Rick Stevens]

Mikkel L. Ellertson wrote:

Tom Horsley wrote:

On Wed, 19 Nov 2008 19:05:54 -0600
"Mikkel L. Ellertson" <[EMAIL PROTECTED]> wrote:


Take a look at /etc/udev/rules.d/70-persistent-net.rules

Yep. It happens to other hardware as well. I replaced a dead
DVD drive and spent quite a while tracking down why it came
up as /dev/sr1 instead of /dev/sr0 (similar persistent .rules
file with different name).


Yup - to see the list, you can run:

ls /etc/udev/rules.d/??-persistent-*.rules

Maybe we need to update the program to check if the old hardware has
been removed when adding entries to the persistent rules...


An updated version of kudzu?  Who woulda thought?  :-)
--
- Rick Stevens, Systems Engineer  [EMAIL PROTECTED] -
- AIM/Skype: therps2ICQ: 22643734Yahoo: origrps2 -
--
-   Never try to outstubborn a cat.  -
--

--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

Re: Moving Fedora 9 Hard Disk To Another System

[Mikkel L. Ellertson]

Michael Cronenworth wrote:
>  Original Message 
> Subject: Re: Moving Fedora 9 Hard Disk To Another System
> From: Mikkel L. Ellertson <[EMAIL PROTECTED]>
> To: Community assistance, encouragement, and advice for using Fedora.
> 
> Date: 11/19/2008 08:08 PM
> 
>> What is more likely is that the motherboard is using a different
>> hard drive controller. The new controller requires a different
>> module from the original one. So you have to build a new initrd for
>> that system. This was covered in detail on the list a while back.
>>
>> Depending on the other hardware, you may have to run kudzu, or you
>> may have to delete some or all of the
>> /etc/udev/rules.d/??-persistent*.rules files.
>>
>> Mikkel
>>
> 
> 
> He won't need to build a new initrd. The UUID specified in his grub.conf
> is wrong. Correct me if I'm wrong, but the UUID is specific to a hard
> drive, so even if he cloned the image, the UUID would be for the
> original hard drive and wouldn't work on the cloned image.
> 
> Try setting root to "root=LABEL=/" or "root=/dev/sda2" or generate a new
> UUID.
> 
I would agree with you, except that the cloned drives worked on some
machines, and not others. It depended on the hardware. If it did not
work on any of the machines, that would support a UUID problem.

Mikkel
-- 

  Do not meddle in the affairs of dragons,
for thou art crunchy and taste good with Ketchup!



signature.asc
Description: OpenPGP digital signature
-- 
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

Re: Moving Fedora 9 Hard Disk To Another System

[Paul W. Frields]

On Thu, Nov 20, 2008 at 10:30:26AM -0600, Michael Cronenworth wrote:
>  Original Message 
> Subject: Re: Moving Fedora 9 Hard Disk To Another System
> From: Mikkel L. Ellertson <[EMAIL PROTECTED]>
> To: Community assistance, encouragement, and advice for using Fedora.  
> 
> Date: 11/19/2008 08:08 PM
>
>> What is more likely is that the motherboard is using a different
>> hard drive controller. The new controller requires a different
>> module from the original one. So you have to build a new initrd for
>> that system. This was covered in detail on the list a while back.
>>
>> Depending on the other hardware, you may have to run kudzu, or you
>> may have to delete some or all of the
>> /etc/udev/rules.d/??-persistent*.rules files.
>>
>> Mikkel
>>
>
>
> He won't need to build a new initrd. The UUID specified in his grub.conf  
> is wrong. Correct me if I'm wrong, but the UUID is specific to a hard  
> drive, so even if he cloned the image, the UUID would be for the  
> original hard drive and wouldn't work on the cloned image.
>
> Try setting root to "root=LABEL=/" or "root=/dev/sda2" or generate a new  
> UUID.

The UUID is part of the file system superblock, not tied to the
physical hard disk, IIRC.

-- 
Paul W. Frieldshttp://paul.frields.org/
  gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233  5906 ACDB C937 BD11 3717
  http://redhat.com/   -  -  -  -   http://pfrields.fedorapeople.org/
  irc.freenode.net: stickster @ #fedora-docs, #fedora-devel, #fredlug


pgpqCWKMz8uIv.pgp
Description: PGP signature
-- 
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

Re: Moving Fedora 9 Hard Disk To Another System

[Michael Cronenworth]

 Original Message 
Subject: Re: Moving Fedora 9 Hard Disk To Another System
From: Mikkel L. Ellertson <[EMAIL PROTECTED]>
To: Community assistance, encouragement, and advice for using Fedora. 


Date: 11/19/2008 08:08 PM


What is more likely is that the motherboard is using a different
hard drive controller. The new controller requires a different
module from the original one. So you have to build a new initrd for
that system. This was covered in detail on the list a while back.

Depending on the other hardware, you may have to run kudzu, or you
may have to delete some or all of the
/etc/udev/rules.d/??-persistent*.rules files.

Mikkel




He won't need to build a new initrd. The UUID specified in his grub.conf 
is wrong. Correct me if I'm wrong, but the UUID is specific to a hard 
drive, so even if he cloned the image, the UUID would be for the 
original hard drive and wouldn't work on the cloned image.


Try setting root to "root=LABEL=/" or "root=/dev/sda2" or generate a new 
UUID.


--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

Re: Network Card Naming Issue

[Mikkel L. Ellertson]

Tom Horsley wrote:
> On Wed, 19 Nov 2008 19:05:54 -0600
> "Mikkel L. Ellertson" <[EMAIL PROTECTED]> wrote:
> 
>> Take a look at /etc/udev/rules.d/70-persistent-net.rules
> 
> Yep. It happens to other hardware as well. I replaced a dead
> DVD drive and spent quite a while tracking down why it came
> up as /dev/sr1 instead of /dev/sr0 (similar persistent .rules
> file with different name).
> 
Yup - to see the list, you can run:

ls /etc/udev/rules.d/??-persistent-*.rules

Maybe we need to update the program to check if the old hardware has
been removed when adding entries to the persistent rules...

Mikkel
-- 

  Do not meddle in the affairs of dragons,
for thou art crunchy and taste good with Ketchup!



signature.asc
Description: OpenPGP digital signature
-- 
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

Re: Evolution and the Global Catalog Server Debacle

[Christopher A. Williams]

On Thu, 2008-11-20 at 07:04 -0700, Christopher A. Williams wrote:
> I could really use a hand on this one:
> 
> I'm running Evolution (on F10 PR/Rawhide) with the Exchange Connector,
> and have always had incredible problems browsing my employer's Exchange
> Global Address List. I picked up what I believe is the Global Catalog
> Server by using Outlook 2007 and going through all of the motions to
> find it there.

...Meant to post this to Fedora Test List. Sorry 'bout that! Please move
this thread to there.

--
==
By all means marry;
If you get a good wife, you'll be happy.
If you get a bad one, you'll become a philosopher.

--Socrates

-- 
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

Re: Moving Fedora 9 Hard Disk To Another System

[Mikkel L. Ellertson]

Aldo Foot wrote:
> On Wed, Nov 19, 2008 at 6:08 PM, Mikkel L. Ellertson
> <[EMAIL PROTECTED]> wrote:
>> What is more likely is that the motherboard is using a different
>> hard drive controller. The new controller requires a different
>> module from the original one. So you have to build a new initrd for
>> that system. This was covered in detail on the list a while back.
> 
> Do you have a date reference? I'd like to take a look at the thread.
> 
> thanks
> ~af
> 
About mid October - Two threads come to mind:
Trying to reconfigure F9 to new computer hardware... firstboot?
fedora 9 and swapping motherboards

Mikkel
-- 

  Do not meddle in the affairs of dragons,
for thou art crunchy and taste good with Ketchup!



signature.asc
Description: OpenPGP digital signature
-- 
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

Re: set up NAT (network address translation) on local server

[Antonio Olivares]

--- On Thu, 11/20/08, Christopher K. Johnson <[EMAIL PROTECTED]> wrote:

> From: Christopher K. Johnson <[EMAIL PROTECTED]>
> Subject: Re: set up NAT (network address translation) on local server
> To: [EMAIL PROTECTED], "Community assistance, encouragement, and advice for 
> using Fedora." 
> Date: Thursday, November 20, 2008, 7:28 AM
> I would add the *nat through COMMIT before the existing
> *filter line.
> 
> I don't believe it matters as long as you do not mix
> them together.  But usually the *nat is much briefer than
> *filter, thus a good convention to put it first to find
> easily later.
> 
> Antonio Olivares wrote:
> > It seems that it does not contain those lines :(
> > 
> >   I will need to edit the file manually and save it. 
> Then try it again.
> > 
> > Regards,
> > 
> > Antonio   
> 
> 
> --   "A society grows great when old men plant trees
> whose shade they know
>   they shall never sit in" - Greek Proverb

How can I fix this?
I manually edited the file and I stopped service and now I get :

[EMAIL PROTECTED] ~]# gedit /etc/sysconfig/iptables &
[1] 7697   
[EMAIL PROTECTED] ~]# service iptables stop
iptables: Flushing firewall rules: [  OK  ]
iptables: Setting chains to policy ACCEPT: nat filter  [  OK  ]
iptables: Unloading modules:   [  OK  ]
[1]+  Donegedit /etc/sysconfig/iptables
[EMAIL PROTECTED] ~]# service iptables restart
iptables: Flushing firewall rules: [  OK  ]
iptables: Setting chains to policy ACCEPT: filter  [  OK  ]
iptables: Unloading modules:   [  OK  ]
iptables: Applying firewall rules: Bad argument `COMMIT'   
Error occurred at line: 6  
Try `iptables-restore -h' or 'iptables-restore --help' for more information.
   [FAILED] 
[EMAIL PROTECTED] ~]# cat /etc/sysconfig/iptables 
*nat
:PREROUTING ACCEPT [1:233]  
:POSTROUTING ACCEPT [0:0]   
:OUTPUT ACCEPT [0:0]
-A POSTROUTING -s 192.168.1.0/24 -o eth0 -j SNAT --to-source 10.154.19.210  
COMMIT  
-A FORWARD -i eth1 -o eth0 -j ACCEPT   -A 
FORWARD -i eth0 -o eth1 -m state --state RELATED,ESTABLISHED -j ACCEPT  
  
# manually added the changes 2008/11/20 
# Firewall configuration written by system-config-securitylevel 
# Manual customization of this file is not recommended.
*filter
:INPUT ACCEPT [0:0]
:FORWARD ACCEPT [0:0]
:OUTPUT ACCEPT [0:0]
:RH-Firewall-1-INPUT - [0:0]
-A INPUT -j RH-Firewall-1-INPUT
-A RH-Firewall-1-INPUT -i lo -j ACCEPT
-A RH-Firewall-1-INPUT -p icmp --icmp-type any -j ACCEPT
-A RH-Firewall-1-INPUT -p 50 -j ACCEPT
-A RH-Firewall-1-INPUT -p 51 -j ACCEPT
-A RH-Firewall-1-INPUT -p udp --dport 5353 -d 224.0.0.251 -j ACCEPT
-A RH-Firewall-1-INPUT -p udp -m udp --dport 631 -j ACCEPT
-A RH-Firewall-1-INPUT -p tcp -m tcp --dport 631 -j ACCEPT
-A RH-Firewall-1-INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT
-A RH-Firewall-1-INPUT -m state --state NEW -m tcp -p tcp --dport 22 -j ACCEPT
-A RH-Firewall-1-INPUT -j REJECT --reject-with icmp-host-prohibited
-A FORWARD -j REJECT --reject-with icmp-host-prohibited
COMMIT
[EMAIL PROTECTED] ~]#

Thanks,

Antonio 


  

-- 
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

Re: set up NAT (network address translation) on local server

[Christopher K. Johnson]

I would add the *nat through COMMIT before the existing *filter line.

I don't believe it matters as long as you do not mix them together.  But 
usually the *nat is much briefer than *filter, thus a good convention to 
put it first to find easily later.


Antonio Olivares wrote:

It seems that it does not contain those lines :(

  
I will need to edit the file manually and save it.  Then try it again.


Regards,

Antonio 
  



--
  "A society grows great when old men plant trees whose shade they know
  they shall never sit in" - Greek Proverb

--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

Re: set up NAT (network address translation) on local server

[Antonio Olivares]

--- On Thu, 11/20/08, Christopher K. Johnson <[EMAIL PROTECTED]> wrote:

> From: Christopher K. Johnson <[EMAIL PROTECTED]>
> Subject: Re: set up NAT (network address translation) on local server
> To: "Community assistance, encouragement, and advice for using Fedora." 
> 
> Date: Thursday, November 20, 2008, 5:52 AM
> Does /etc/sysconfig/iptables actually contain the lines
> 
> *nat   
>  :PREROUTING ACCEPT [1:233] 
>  :POSTROUTING ACCEPT [0:0]  
>  :OUTPUT ACCEPT [0:0]   
>  -A POSTROUTING -s 192.168.1.0/24 -o eth0 -j
> SNAT --to-source 10.154.19.210 COMMIT   
>   
It seems that it does not contain those lines :(

[EMAIL PROTECTED] ~]# cat /etc/sysconfig/iptables
# Firewall configuration written by system-config-securitylevel
# Manual customization of this file is not recommended.
*filter
:INPUT ACCEPT [0:0]
:FORWARD ACCEPT [0:0]
:OUTPUT ACCEPT [0:0]
:RH-Firewall-1-INPUT - [0:0]
-A INPUT -j RH-Firewall-1-INPUT
-A RH-Firewall-1-INPUT -i lo -j ACCEPT
-A RH-Firewall-1-INPUT -p icmp --icmp-type any -j ACCEPT
-A RH-Firewall-1-INPUT -p 50 -j ACCEPT
-A RH-Firewall-1-INPUT -p 51 -j ACCEPT
-A RH-Firewall-1-INPUT -p udp --dport 5353 -d 224.0.0.251 -j ACCEPT
-A RH-Firewall-1-INPUT -p udp -m udp --dport 631 -j ACCEPT
-A RH-Firewall-1-INPUT -p tcp -m tcp --dport 631 -j ACCEPT
-A RH-Firewall-1-INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT
-A RH-Firewall-1-INPUT -m state --state NEW -m tcp -p tcp --dport 22 -j ACCEPT
-A RH-Firewall-1-INPUT -j REJECT --reject-with icmp-host-prohibited
-A FORWARD -j REJECT --reject-with icmp-host-prohibited
COMMIT


where should I add those lines on top or below?
   
> It seems unlikely that it was written correctly since the
> restart did not implement your SNAT rule, and this file is
> what a restart reads. Perhaps there is  a bug in
> iptables-save?  I edit /etc/sysconfig/iptables directly, and
> recommend that if you are not using some firewall front-end
> or tool to do this, that you do the same.
> 
> There is another problem in the rules you listed.  It would
> not prevent the SNAT rule from being implemented, so this is
> an unrelated problem.  But it would prevent the forwarding
> you wanted:
> 
> -A FORWARD -j REJECT --reject-with icmp-host-prohibited
>-A FORWARD -i eth1 -o eth0 -j ACCEPT 
>  -A FORWARD -i eth0 -o eth1 -m
> state --state RELATED,ESTABLISHED -j ACCEPT
> 
> Note that the REJECT is above your ACCEPT rules.  You need
> to move it below them because the REJECT is very general and
> will catch everything, preventing the ACCEPT rules from
> being applied.
> 
> -A FORWARD -i eth1 -o eth0 -j ACCEPT   
>-A FORWARD -i eth0 -o eth1 -m state --state
> RELATED,ESTABLISHED -j ACCEPT
> -A FORWARD -j REJECT --reject-with icmp-host-prohibited
> 
> I presume from the addresses that this is natting one
> private network onto another private network.  So this last
> note is not critical as it would be if connecting onto the
> Internet.  Once you get this working as you intended, I
> recommend you alter or remove these rules too, depending on
> whether you wish people on the 10 network to have access to
> services on your server:
> 
> # Permit IPSEC peer communications.  Unless you are
> configuring IPSEC tunnels, you should comment these out.
> #-A RH-Firewall-1-INPUT -p esp -j ACCEPT
> #-A RH-Firewall-1-INPUT -p ah -j ACCEPT
> 
> # Permit hosts to announce themselves to the
> avahi-daemon's multicast dns service
> -A RH-Firewall-1-INPUT -d 224.0.0.251/32 -p udp -m udp
> --dport 5353 -j ACCEPT
> 
> # Permit connections to the CUPS service (successful
> connections may be governed by the CUPS config)
> -A RH-Firewall-1-INPUT -p udp -m udp --dport 631 -j ACCEPT
> -A RH-Firewall-1-INPUT -p tcp -m tcp --dport 631 -j ACCEPT
> 
> # Permit access to the ssh server.  There is nothing wrong
> with that as long as you harden /etc/ssh/sshd_config
> # to be more restrictive. By default it allows password
> authentication of all users including root, and
> # other service accounts.
> -A RH-Firewall-1-INPUT -p tcp -m state --state NEW -m tcp
> --dport 22 -j ACCEPT
> 
> 
> 
> Antonio Olivares wrote:
> > *nat  
>   :PREROUTING ACCEPT [1:233]
>   :POSTROUTING ACCEPT [0:0] 
>   :OUTPUT ACCEPT [0:0]  
>   -A POSTROUTING -s 192.168.1.0/24 -o
> eth0 -j SNAT --to-source 10.154.19.210 COMMIT   
>  #
> Completed on Thu Nov 20 06:52:04 2008   
> # Generated by iptables-save v1.4.1.1 on Thu Nov
> 20 06:52:04 2008  *filter   

thunderbird and broken sig delimiter when using enigma

[g]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

greetings,

if any one using thunderbird is having problems with broken sig delimiter
when using enigma and would like to know a cure, contact me via;

[EMAIL PROTECTED]

please use above link so that my filters will pass your email.

tho there maybe some who are aware of a fix, i do not care to publishing
fix do to reasons of harassment received on support-thunderbird list.

and yes, all crying was from msbsos kitties.

later.


peace out.

tc,hago.

g
.


in a free world without fences, who needs gates.

learn linux:
'Rute User's Tutorial and Exposition'   http://rute.2038bug.com/index.html.gz
'The Linux Documentation Project'   http://www.tldp.org/
'LDP HOWTO-index'   http://www.tldp.org/HOWTO/HOWTO-INDEX/index.html
'HowtoForge'   http://howtoforge.com/

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.5 (GNU/Linux)
Comment: Using GnuPG with Red Hat - http://enigmail.mozdev.org

iD8DBQFJJXWW+C4Bj9Rkw/wRAj2bAKC2uN3QtrrDoU6tlOn/JLi/kgNN5gCePBP9
WRriveSh1m4YBJ67nURcE30=
=mNn+
-END PGP SIGNATURE-

-- 
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

Evolution and the Global Catalog Server Debacle

[Christopher A. Williams]

I could really use a hand on this one:

I'm running Evolution (on F10 PR/Rawhide) with the Exchange Connector,
and have always had incredible problems browsing my employer's Exchange
Global Address List. I picked up what I believe is the Global Catalog
Server by using Outlook 2007 and going through all of the motions to
find it there.

When I plug in that server name from outside of my company network, I
get squat.

When I use the same configuration from _inside_ the company network, it
seems to work fine.

So, why can't Evolution see this from outside, but Outlook 2K7 can when
configured using RPC over HTPPS? I won't even begin to ask why I need to
know and enter the Global Catalog Server name in the first place since
Outlook seems to be able to find this out on its own using pretty much
the same way of connecting.

Ideas? This couldn't be as simple as needing a different GC server or
knowing that I need a specific TCP port open. It doesn't make sense that
this works with one but not the other...

Cheers,

Chris


-- 
==
"If we don't succeed,
we run the risk of failure."

-- Former President Bill Clinton

-- 
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

Re: set up NAT (network address translation) on local server

[Christopher K. Johnson]

Does /etc/sysconfig/iptables actually contain the lines

*nat 
:PREROUTING ACCEPT [1:233]   
:POSTROUTING ACCEPT [0:0]
:OUTPUT ACCEPT [0:0] 
-A POSTROUTING -s 192.168.1.0/24 -o eth0 -j SNAT --to-source 10.154.19.210 
COMMIT 

It seems unlikely that it was written correctly since the restart did 
not implement your SNAT rule, and this file is what a restart reads. 
Perhaps there is  a bug in iptables-save?  I edit 
/etc/sysconfig/iptables directly, and recommend that if you are not 
using some firewall front-end or tool to do this, that you do the same.


There is another problem in the rules you listed.  It would not prevent 
the SNAT rule from being implemented, so this is an unrelated problem.  
But it would prevent the forwarding you wanted:


-A FORWARD -j REJECT --reject-with icmp-host-prohibited
-A FORWARD -i eth1 -o eth0 -j ACCEPT   
-A FORWARD -i eth0 -o eth1 -m state --state RELATED,ESTABLISHED -j ACCEPT


Note that the REJECT is above your ACCEPT rules.  You need to move it 
below them because the REJECT is very general and will catch everything, 
preventing the ACCEPT rules from being applied.


-A FORWARD -i eth1 -o eth0 -j ACCEPT   
-A FORWARD -i eth0 -o eth1 -m state --state RELATED,ESTABLISHED -j ACCEPT

-A FORWARD -j REJECT --reject-with icmp-host-prohibited

I presume from the addresses that this is natting one private network 
onto another private network.  So this last note is not critical as it 
would be if connecting onto the Internet.  Once you get this working as 
you intended, I recommend you alter or remove these rules too, depending 
on whether you wish people on the 10 network to have access to services 
on your server:


# Permit IPSEC peer communications.  Unless you are configuring IPSEC tunnels, 
you should comment these out.
#-A RH-Firewall-1-INPUT -p esp -j ACCEPT
#-A RH-Firewall-1-INPUT -p ah -j ACCEPT

# Permit hosts to announce themselves to the avahi-daemon's multicast dns 
service
-A RH-Firewall-1-INPUT -d 224.0.0.251/32 -p udp -m udp --dport 5353 -j ACCEPT

# Permit connections to the CUPS service (successful connections may be 
governed by the CUPS config)
-A RH-Firewall-1-INPUT -p udp -m udp --dport 631 -j ACCEPT
-A RH-Firewall-1-INPUT -p tcp -m tcp --dport 631 -j ACCEPT

# Permit access to the ssh server.  There is nothing wrong with that as long as 
you harden /etc/ssh/sshd_config
# to be more restrictive. By default it allows password authentication of all 
users including root, and
# other service accounts.
-A RH-Firewall-1-INPUT -p tcp -m state --state NEW -m tcp --dport 22 -j ACCEPT



Antonio Olivares wrote:
*nat 
:PREROUTING ACCEPT [1:233]   
:POSTROUTING ACCEPT [0:0]
:OUTPUT ACCEPT [0:0] 
-A POSTROUTING -s 192.168.1.0/24 -o eth0 -j SNAT --to-source 10.154.19.210 
COMMIT 
# Completed on Thu Nov 20 06:52:04 2008
# Generated by iptables-save v1.4.1.1 on Thu Nov 20 06:52:04 2008  
*filter
:INPUT ACCEPT [0:0]
:FORWARD ACCEPT [0:0]  
:OUTPUT ACCEPT [8:452] 
:RH-Firewall-1-INPUT - [0:0]   
-A INPUT -j RH-Firewall-1-INPUT
-A FORWARD -j REJECT --reject-with icmp-host-prohibited
-A FORWARD -i eth1 -o eth0 -j ACCEPT   
-A FORWARD -i eth0 -o eth1 -m state --state RELATED,ESTABLISHED -j ACCEPT

-A RH-Firewall-1-INPUT -i lo -j ACCEPT
-A RH-Firewall-1-INPUT -p icmp -m icmp --icmp-type any -j ACCEPT
-A RH-Firewall-1-INPUT -p esp -j ACCEPT
-A RH-Firewall-1-INPUT -p ah -j ACCEPT
-A RH-Firewall-1-INPUT -d 224.0.0.251/32 -p udp -m udp --dport 5353 -j ACCEPT
-A RH-Firewall-1-INPUT -p udp -m udp --dport 631 -j ACCEPT
-A RH-Firewall-1-INPUT -p tcp -m tcp --dport 631 -j ACCEPT
-A RH-Firewall-1-INPUT -m state --state RELATED,ESTABLISHED -j ACCEPT
-A RH-Firewall-1-INPUT -p tcp -m state --state NEW -m tcp --dport 22 -j ACCEPT
-A RH-Firewall-1-INPUT -j REJECT --reject-with icmp-host-prohibited
COMMIT
# Completed on Thu Nov 20 06:52:04 2008
  



--
  "A society grows great when old men plant trees whose shade they know
  they shall never sit in" - Greek Proverb

--
fedora-list mailing list
fedora-list@r

Re: [sudo-users] How to disable ( deny ) user to change the password of root

[Patrick O'Callaghan]

On Thu, 2008-11-20 at 17:25 +0800, [EMAIL PROTECTED] wrote:
> Would you mind to tell me what different between "passwd" and 
> "/usr/bin/passwd" ?

If you administer a Unix/Linux system, it essential that you understand
this. Even if you're only a user, it's highly relevant.

Typing "passwd" at the Shell command prompt (or equivalently, in a
script) tells the Shell to look for an executable file called "passwd"
in a series of directories defined by the $PATH variable. The first one
it finds, it executes. If the $PATH variable has been altered to put
some sneaky directory ahead of /usr/bin in the list the Shell will
search, that's what gets executed.

On the other hand, "/usr/bin/passwd" means exactly that file, with no
ambiguity.

BTW, this is why it's strongly recommended not to include "." as a
member of your $PATH. Think about it ...

poc

-- 
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

Re: set up NAT (network address translation) on local server

[Antonio Olivares]

--- On Wed, 11/19/08, Christopher K. Johnson <[EMAIL PROTECTED]> wrote:

> From: Christopher K. Johnson <[EMAIL PROTECTED]>
> Subject: Re: set up NAT (network address translation) on local server
> To: "Community assistance, encouragement, and advice for using Fedora." 
> 
> Date: Wednesday, November 19, 2008, 4:00 PM
> No snat rule in effect!
> 
> Was the rule you provided in your original post verbatim? 
> Because it had 'a' instead of the public address. 
> In fact the rule seemed overly specific in other ways too.
> Here is what I have for a snat rule where the public
> (Internet) interface is eth1 (substitute your public ip
> address for a.b.c.d:
> 
> -A POSTROUTING -o eth1 -j SNAT --to-source a.b.c.d
> 
> Resulting in (again substituted a.b.c.d for the real public
> address):
> Chain POSTROUTING (policy ACCEPT 36819 packets, 4482K
> bytes)
> pkts bytes target prot opt in out source   
>destination39065 2513K SNAT   all  --  * 
> eth10.0.0.0/00.0.0.0/0  
> to:a.b.c.d
> 
> If your rule is correct, then you need to activate your
> iptables file rules by:
> service iptables restart
> 
> Chris
> >  pkts bytes target prot opt in out source 
>  destination
> > 
> > Chain POSTROUTING (policy ACCEPT 0 packets, 0 bytes)
> >  pkts bytes target prot opt in out source 
>  destination
> >   
> 
> 
> --   "A society grows great when old men plant trees
> whose shade they know
>   they shall never sit in" - Greek Proverb
> 
> -- fedora-list mailing list

I have done the following: 

[EMAIL PROTECTED] ~]$ su -
Password:   
[EMAIL PROTECTED] ~]# lsmod | grep ipta*
[EMAIL PROTECTED] ~]# modprobe iptable_nat
[EMAIL PROTECTED] ~]# iptables -A POSTROUTING -t nat -o eth0 -j MASQUERADE
[EMAIL PROTECTED] ~]# service dhcpd stop
Shutting down dhcpd:   [  OK  ]
[EMAIL PROTECTED] ~]# service dhcpd start
Starting dhcpd:[  OK  ]
[EMAIL PROTECTED] ~]# service dhcpd stop
Shutting down dhcpd:   [  OK  ]
[EMAIL PROTECTED] ~]# iptables -A FORWARD -i eth1 -o eth0 -j ACCEPT  
[EMAIL PROTECTED] ~]# iptables -A FORWARD -i eth0 -o eth1 -m state --state 
ESTABLISHED,RELATED -j ACCEPT   
   
[EMAIL PROTECTED] ~]# iptables -A POSTROUTING -t nat -s 192.168.1.0/24 -o eth0 
-j SNAT --to-source 10.154.19.210
[EMAIL PROTECTED] ~]# service dhcpd start
Starting dhcpd:[  OK  ]
[EMAIL PROTECTED] ~]# iptables -vnL -t nat   
Chain PREROUTING (policy ACCEPT 186 packets, 24044 bytes)  
 pkts bytes target prot opt in out source   destination 


Chain POSTROUTING (policy ACCEPT 3 packets, 144 bytes)
 pkts bytes target prot opt in out source   destination 

  108  6705 MASQUERADE  all  --  *  eth00.0.0.0/00.0.0.0/0  

0 0 SNAT   all  --  *  eth0192.168.1.0/24   0.0.0.0/0   
to:10.154.19.210

Chain OUTPUT (policy ACCEPT 111 packets, 6849 bytes)
 pkts bytes target prot opt in out source   destination 

[EMAIL PROTECTED] ~]# service iptables restart
iptables: Flushing firewall rules: [  OK  ]
iptables: Setting chains to policy ACCEPT: nat filter  [  OK  ]
iptables: Unloading modules:   [  OK  ]
iptables: Applying firewall rules: [  OK  ]
iptables: Loading additional modules: ip_conntrack_netbios_[  OK  ]
[EMAIL PROTECTED] ~]# iptables -vnL -t nat   
Chain PREROUTING (policy ACCEPT 0 packets, 0 bytes)
 pkts bytes target prot opt in out source   destination 


Chain POSTROUTING (policy ACCEPT 0 packets, 0 bytes)
 pkts bytes target prot opt in out source   destination 


Chain OUTPUT (policy ACCEPT 0 packets, 0 bytes)
 pkts bytes target prot opt in out source   destination 

[EMAIL PROTECTED] ~]# service dhcpd stopShutting down dhcpd:
   [  OK  ]
[EMAIL PROTECTED] ~]# iptables -A FORWARD -i eth1 -o eth0 -j [EMAIL PROTECTED] 
~]# ip

Re: Whois - unable to connect.

[Simon Slater]

On Thu, 2008-11-20 at 12:02 +0800, Ed Greshko wrote:
> Simon Slater wrote:
> >
> > ACCEPT tcp  --  anywhere anywheretcp
> > spt:nicname state NEW,ESTABLISHED
> > ACCEPT udp  --  anywhere anywhereudp
> > spt:nicname state NEW,ESTABLISHED
> >   
> spt=source port 
> 
> You want the destination port.
> 
Thanks Ed,  Connects fine now!  I got my ins and outs mixed up.  But
I'll need to check the rest of the script now because this morning I
just copied the syntax from another part in the script.  I've been
putting off learning iptables, but after last weeks classroom session
and this today I'd better start this weekend.

Thanks again

-- 
Hooroo,
Simon
Registered Linux User #463789. Be counted at: http://counter.li.org/


-- 
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

Re: getting /lib/ld-linux.so.2 on a 64-bit f10 preview install?

[Alexander Apprich]

just wild guessing... isn't there a glibc-32bit package somewhere
in the repos? don't have a 64bit system by hand other then suse
but for compatibility reasons there should be a glibc-32bit
package...

Alex
-- 
Vorstand/Board of Management:
Dr. Bernd Finkbeiner, Dr. Florian Geyer,
Dr. Roland Niemeier, Dr. Arno Steitz, Dr. Ingrid Zech
Vorsitzender des Aufsichtsrats/
Chairman of the Supervisory Board:
Prof. Dr. Hanns Ruder
Sitz/Registered Office: Tuebingen
Registergericht/Registration Court: Stuttgart
Registernummer/Commercial Register No.: HRB 382196 


-- 
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

Re: Jackd Problems -- alsa_pcm: xrun of at least 1227061150613.504 msecs

[Jeremy]

Hello Jonathan,

To get jack running properly you need:
- Planet CCRMA packages 
(http://ccrma.stanford.edu/planetccrma/software/) which are not 
available for F9
- low latency kernel, Planet CCRMA also provides these, unfortunately 
not for F9
- zero latency soundcard, an onboard card probably never works without 
an xrun every now and then


An xrun is indeed a buffer under/overrun and could be caused by numerous 
things, always hard to put a finger on it. Could be software, hardware. 
Best is to run jack with a light weight WM like fluxbox or IceWM and to 
use as little other programs as possible. And to switch to another 
version of Fedora (like 7 or 8) for which there are Planet CCRMA 
packages available, otherwise it's no use I think.


Good luck!

Jeremy

Paulo Cavalcanti wrote:



On Wed, Nov 19, 2008 at 1:28 AM, Jonathan Ryshpan <[EMAIL PROTECTED] 
> wrote:


In the past I've never had any problems running jackd.  Now I'm getting
a very large number of messages reading:
    alsa_pcm: xrun of at least 1227061150613.504 msecs
I'm running F9 on an x86_64 system with all updates installed.
Pulseaudio is not running.  Jackd is started via qjackctl.  No past
problems with audio beyond the usual conflicts between pulseaudio and
firefox.

Questions:
(1) What exactly does this message mean?  An "xrun" is a buffer under-
or over-run -- but what does the time interval represent?

(2) Whatever the time interval means, it looks rather large.
1227061150613.504 msec is many days (or maybe years if msec means
millisec and not microsec)  This looks like a misconfiguration of some
kind or a missing component.  Any idea what it might be?


The solution depends on your card (I have an Intel onboard card).
But this material may give you an idea on what you can try:

 http://people.atrpms.net/~pcavalcanti/alsa-1.0.15rc2_snd-hda-intel.html#jack


--
Paulo Roma Cavalcanti
LCG - UFRJ



--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

Re: getting /lib/ld-linux.so.2 on a 64-bit f10 preview install?

[Itamar - IspBrasil]

I am also need this for the oracule database

On 11/19/2008 11:34 PM, Robert P. J. Day wrote:

   long story short:  x86-64 f10 preview install on AMD64 laptop.
install coldfire cross-compile toolchain, which immediately fails
looking for /lib/ld-linux.so.2, which it obviously won't find since
the system has /lib64/ld-2.9.so (along with various symlinks).

   solution?

rday
--


Robert P. J. Day
Linux Consulting, Training and Annoying Kernel Pedantry:
 Have classroom, will lecture.

http://crashcourse.ca  Waterloo, Ontario, CANADA


   



--


Itamar Reis Peixoto

e-mail/msn: [EMAIL PROTECTED]
sip: [EMAIL PROTECTED]
skype: itamarjp
icq: 81053601
+55 11 4063 5033
+55 34 3221 8599


--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

Re: [sudo-users] How to disable ( deny ) user to change the password of root

[edwardspl]

Gordon Messmer wrote:


[EMAIL PROTECTED] wrote:



Sorry, what means about the sentence ?



The last line of the script that I suggested to you was:

passwd -- "$1"

That line would be more secure if it were specific about where 
"passwd" should be:


/usr/bin/passwd -- "$1"


Hello,

Sorry,
Would you mind to tell me what different between "passwd" and 
"/usr/bin/passwd" ?


Many thanks !

Edward.

--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines