I need your help.
I have installed NFS-server on my Fedora 14.
Server is 192.168.1.101
Client is 192.168.1.100
I have stoped my iptables like this:
# su -c 'service iptables stop'
I'm not sure, that I have to write in /etc/hosts.allow and /etc/hosts.deny
>From the client side I do:
# sudo mount.nfs 192.168.1.101:/home/booch/Temp /home/booch/data/
And I have got thos error:
mount.nfs: access denied by server while mounting 192.168.1.101:
Please! Help me to resolve that problem!
Thank you very much in advance!
*+9 72 54 285 952 3
*+9 72 54 285 952 3*
Yet again I'll be very grateful for any help you can give me.....
I just upgraded to F13 on my 2 systems & on both of them, I seem to be
unable to print. The 2 machines are
a) my desktop
Linux Fedora-Blue 184.108.40.206-61.fc13.i686.PAE #1 SMP Tue Oct 19 04:24:06
UTC 2010 i686 i686 i386 GNU/Linux
which was fresh-installed because preupgrade wouldn't reboot(Grrrr)
and b) my laptop which was preupgraded.
The printer is an Epson Stylus DX6050 which "always" worked before....
Strange thing is that under previous Fedoras, I had to fight to get the
scanner recognised, this time, the scanner is recognised & working, but
I can't get any of the print commands to offer me anything but a "write
.pdf to file".
Can anyone suggest what I've forgotten to check?????????
As ever, great thanks for any suggestions!
On Sun, 28 Nov 2010 19:33:54 -0500
I started this topic by saying:
> I need to run X with the fvwm window manager, but the F14 X server
> doesn't play nice with fvwm - or with twm. When fvwm or twm calls
> XCreateFontSet(), the X server dies with a SIGSEGV.
> To get around this, I have copied the F13 /usr/bin/Xorg server binary
> and /usr/lib/xorg/modules directory contents to my F14 system, and
> they work just fine with the F14 fvwm, F14 X libraries, and F14 fonts.
> While this workaround works, it's not exactly a good long term fix.
> Note that this workaround means the problem is with the F14 X server
> or its loadable modules, not the F14 fvwm.
> When twm is used, it calls XCreateFontSet() with a base_font_name_list
> argument different from that in the fvwm XCreateFontSet() call, and
> the F14 server dies, so the problem is not the font asked for by fvwm.
This gets stranger and stranger ...
Before trying to dig into the X server code, I wanted some clues about
where to look, so I put this into root's .xserverrc:
exec /usr/bin/ltrace /usr/bin/Xorg :0
I deleted root's .xinitrc, .fvwmrc, and .fvwm directory and, as root
(only root can ltrace /usr/bin/Xorg) I ran:
xinit fvwm 2>/tmp/Xorg.out
The ltrace output in /tmp/Xorg.out has 176 calls to memmove(), all
with five arguments, like this example:
memmove(0xa352c50, 0xa3535e0, 1648, 0x806892f, 0x40001c)
Can anyone shed some light on what is going on here? The first three
arguments appear to be the usual three memmove() arguments: dest, src,
and count. The extra two aren't documented anywhere I can find, and
memmove() has always been a three-argument function.
To further confuse things, memmove() isn't the only call with too many
arguments. clock_gettime() is supposed to have two arguments, but
it's called 694 times with five arguments. There may well be other
calls with strange argument counts, but the output has 371800 lines,
and I'm not up to examining all of them.
Dick St. Peters, stpeters(a)NetHeaven.com
Gatekeeper, NetHeaven, Saratoga Springs, NY
I have two printers advertised via avahi-daemon as AirPrint printers.
When avahi-daemon starts up, they're seen via the bonjour devices on the
network. (See log, below.)
After some time, usually within the hour, the bonjour devices can no
longer see the printers, but the local avahi-browser application thinks
they're still there, and there are no errors in any of the logs.
Restarting the daemon immediately makes the printers visible again.
$ avahi-daemon --debug
Found user 'avahi' (UID 495) and group 'avahi' (GID 488).
Successfully dropped root privileges.
avahi-daemon 0.6.27 starting up.
Successfully called chroot().
Successfully dropped remaining capabilities.
Loading service file /services/AirPrint-Marilyn_HP.service.
Loading service file /services/AirPrint-PSC-2200-Series.service.
Loading service file /services/ssh.service.
Loading service file /services/udisks.service.
Joining mDNS multicast group on interface wlan0.IPv4 with address
New relevant interface wlan0.IPv4 for mDNS.
Network interface enumeration completed.
Registering new address record for fe80::211:95ff:febc:e5f3 on wlan0.*.
Registering new address record for 192.168.123.10 on wlan0.IPv4.
Registering HINFO record with values 'I686'/'LINUX'.
Server startup complete. Host name is sds-desk.local. Local service
cookie is 2690789964.
Service "sds-desk" (/services/udisks.service) successfully established.
Service "sds-desk" (/services/ssh.service) successfully established.
Service "AirPlay PSC-2200-Series @ sds-desk"
(/services/AirPrint-PSC-2200-Series.service) successfully established.
Service "AirPlay Marilyn_HP @ sds-desk"
(/services/AirPrint-Marilyn_HP.service) successfully established
Here's one of the service files:
# cat /etc/avahi/services/AirPrint-PSC-2200-Series.service
<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE service-group SYSTEM "avahi-service.dtd">
<name replace-wildcards="yes">AirPlay PSC-2200-Series @ %h</name>
<txt-record>note=Hewlett-Packard PSC 2200 Series</txt-record>
And the avahi-daemon.conf file
# grep -v '#' /etc/avahi/avahi-daemon.conf
Not since Fedora have I had such sound problems What worked like a charm
in recent Fedoras does not work now. I can get sound from YouTube, NPR,
CNN,etc but no sound from my CD-DVD drive When I put in an Audio CD
Rhythmbox opens and I can see that it is playing but no sound comes out
of the speaker. DVDs just lock up the machine using VLC.
All this worked up through F13 on the same machine.
"Indecision is the basis of flexibility" -- button at a Science Fiction
Aaron Konstam telephone: (210) 656-0355 e-mail: akonstam(a)sbcglobal.net
I am trying to figure out a way to output some information to the
console (system boots to runlevel 3) from an init script.
Here is what I've tried:
add echo "$SOMEINFO" into the init script and pipe it to wall, and put
that in the init script.
This doesn't seem to work, I was thinking of outputting to motd to
achieve this, but wondered if anyone knows a better way.
Perhaps using the at command?
>Data: 29-nov-2010 19.07
>A: "Community support for Fedora users"<users(a)lists.fedoraproject.org>
>Ogg: Re: Selinuxprevents
from graphical login
>-----BEGIN PGP SIGNED MESSAGE-----
11/27/2010 10:37 AM, antonio montagnani wrote:
>> antonio ha scritto / said the
following il giorno/on 27/11/2010 16:08:
>>> Chris Tyler ha scritto / said
the following il giorno/on 27/11/2010
>>>> On Sat, 2010-11-27 at
15:47 +0100, Antonio M wrote:
>>>>> On one of my systems, if Selinux is
targeted I cannot access to
>>>>> graphical session, as password would be wrong
(all users and root)
>>>>> As soon as Selinux=0 at boot time system works fine.
System is fully updated
>>>>> I cannot find a related bug in bugzilla...
>>>> Did you try relabeling the whole system? May be required if you've run
>>>> with selinux off (permissive is better if you want to temporarily
>>>> touch /.autorelabel; reboot
>>> I used the graphical management tool to relabel it, that should do what
you suggest (and I rebooted): now I will see what happens in Permissive
>>> Any way to see a log of Selinux on my system???
>> I rebooted in permissive mode and of course I can login: but I
>> long list of Selinux ACV that I cannot decode :-(
them to me, and I will look at them. Or run them through
>ausearch -m avc -ts recent | audit2allow
>Should give me an idea of what you
>-----BEGIN PGP SIGNATURE-----
>Version: GnuPG v1.4.11 (GNU/Linux)
>Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/>
>-----END PGP SIGNATURE-----
a look to https://bugzilla.redhat.com/show_bug.cgi?id=657727
Now It seems to
have been solved thannks to the help of Miroslav Grepl
Please let me have your
On one of my systems, if Selinux is targeted I cannot access to
graphical session, as password would be wrong (all users and root)
As soon as Selinux=0 at boot time system works fine.System is fully updated
I cannot find a related bug in bugzilla...
Skype : amontag52