I am running FC3 x86_64 on a DSL-connected pc, which works great by
itself; I have another machine running windoze XP, and would like to
use the first pc as a gateway, so that windoze can have access to the
In the linux machine, with 2 ethernet devices, eth0-> connected to
windoze, eth1-> connected to the ADSL modem (under ppp0), eth0 is set
with ip address 192.168.1.1, netmask 255.255.255.0, and eth1 is set by
adsl-setup... The windoze pc has an ip address 192.168.1.2, netmask
255.255.255.0, gateway 192.168.1.1 ( = the FC3 ip address).
Using this setup, windoze can ping linux, but linux can't ping windoze
(no response). I even tried running ping with -I eth0 with no luck :(
Well, i started doing the usual stuff in order to set the gateway under fedora:
1) enabling ip_forwarding on /etc/sysctl.conf
2) modprobing iptables_nat
3) adding iptables masquerading rules to table nat (iptables -t nat -A
POSTROUTING -o ppp0 -j MASQUERADE)
needless to say that windoze remains unconnected... what am I missing????
Thanks in advance
Thiago dos Santos Guzella
Electrical Enginnering Student - UFMG (www.ufmg.br), Brazil
Linux User #354160
UIN: 13465286. Jabber: tguzella @ jabber.org
"Faith: not wanting to know what is true."
jim lawrence wrote:
hi all,I just want to make sure this line that I put into fsab is going to allow me to automount my "D drive" and allow me to read & write to that drive without being root.
here is my /etc/fstab file
# This file is edited by fstab-sync - see 'man fstab-sync' for details
/dev/VolGroup00/LogVol00 / ext3 defaults 1 1
LABEL=/boot /boot ext3 defaults 1 2
none /dev/pts devpts gid=5,mode=620 0 0
none /dev/shm tmpfs defaults 0 0
none /proc proc defaults 0 0
none /sys sysfs defaults 0 0
/dev/VolGroup00/LogVol01 swap swap defaults 0 0
/dev/hda2 /mnt/hda2 vfat auto,rw.user 0 0
/dev/hdc /media/cdrecorder auto pamconsole,fscontext=system_u:object_r:removable_t,ro,exec,noauto,managed 0 0
/dev/fd0 /media/floppy auto pamconsole,fscontext=system_u:object_r:removable_t,exec,noauto,managed 0 0
on boot the message "...bad option...bad superblock...too many..." flashes across too fast across the screen to get it all. I edited the /etc/fstab to now boot /dev/hda2.
err, is the problem that rw.user should be rw,user?
if so...well, since i already wrote the post i'll click on send in case someone spots a different problem. doh!
This is an email sent via the webforum on http://fcp.homelinux.org
I have recently updated my FC3 kernel from 2.6.9-1.667 to
2.6.10-1.766_FC3. The system has had all available updates applied. I
am using a Seagate STT8000A ATAPI tape drive for backup. I am loading
the ide-scsi module. Prior to the update, tar and dump both worked
without any problems using this tape drive.
Since the kernel update, tar and dump appear to write the files to the
tape drive: no error messages are generated during the write and the
tape is positioned at the correct block following the write. However, I
am not able to restore any of the backup files to the hard disk. Using
tar, no errors are returned, and no files are restored. Using restore,
the following error is generated: "restore: Tape is not a dump tape."
I can use mt and cpio without any problems.
What do I need to do to get this ide tape drive working with tar and
dump? Please help, I am stuck. I have searched Google and the archive
of this list without any luck.
After upgrading from FC2 to FC3 (which was a SMOOTH and easy upgrade)
my logwatch reports no longer include a section on yum activity. I
have compared the old logwatch.conf and yum.conf files, but did not
catch a difference which might be a factor.
I choose to let yum automatically install changed rpm files. Yes, I
know this can be dangerous, but I prefer the risk of potential
surprises over the risk of not getting around to manual involvement in
In FC1 and FC2, the "yum" sections were useful so that I could get a
sense of what changed that showed up in my Tripwire reports.
After upgraded directly from RH9 to FC3 the Gnome desktop is very
spartan and not displaying the Bluecurve theme. Instead a default
desktop is displayed with virtually empty panels. After adding the
Main Menu it only contains names and no icons. Lost more ugly
default theme everywhere, no key binding including Alt-TAB, etc ...
Also running gnome-theme-manager (Main Menu / Preferences / Theme)
produces an error dialog box containing:
The default there schemas could not be found on your system. This
means that you probably don't have meatcity installed, or that your
gconf is configured incorrectly.
metacity-theme-viewer reports loading "Atlanta" theme.
Is there someway to get Bluecurve theme and associated settings back?
__ __ _ _ ___ ____ _ ___ ___ _ ___ ___ _
| \/ (_| | _ / _ \ | ___| | / _ \/ _ \| |_ _ _ _/ \/ \ _| |
| |\/| | | |/ | ___| | _| | |_| __| ___| __| \/ \/| O | O / _ |
|_| |_|_|_|\_\\___| |_| |____\___|\___||____\_/^\_/\___/\___/\___|
On Thu, 2004-11-25 at 01:11 +0000, Donald Ray Lott wrote:
> On Thu, 2004-11-25 at 00:09 +0000, Donald Ray Lott wrote:
> > Hi,
> > I thought I had figured out why my zip drive was not working, but looks
> > like FC3 is tricky!
> > The problem is that now /etc/fstab is re-written every time the system
> > is booted by the hal daemon (hald). /ect/fstab reports the zip drive as
> > hdd when it really is hdd4. You can no longer change the settings
> > in /etc/fstab so how do you get it to work correctly?
> > I can mount hdd4 by command line ok.
> man fstab-sync
> is called by hald. I tried commands in a terminal but received a
> message to the effect that fstab-sync was nowhere to be found.
> >From there, one is lead to all the files in hald and even to udev.
> So, does anyone know the fix?
The executable for fstab-sync is in /usr/sbin which is not typically on
your path unless you are logged in as root. You can get rpm to show you
where the various parts of a package such as hal are installed:
rpm -qil hal
As far as your question about correctly mounting the zip drive, check
out the following URL. It doesn't address exactly your issue, but it
should get you pointed in the right direction.
That combined with the section of the output from 'lshal' pertinent to
your zip drive should give an idea of what needs to happen.
C. Linus Hicks <lhicks(a)nc.rr.com>
At my company, we have a redhat 9 server which is a nfs and nis
server. It handles our logins and home-dirs. After updating my Fedora
3 machine with util-linux, i cannot log on anymore. In my log it says:
Mar 31 13:58:54 localhost automount: >> mount to NFS server
'artemis' failed: server is down.
Mar 31 13:58:54 localhost automount: >> mount: backgrounding
But the server isn't down.
If i replace the new util-linux rpm, with the old one, it works fine.
Does anybody know why??
total used free shared buffers cached
Mem: 507584 325348 182236 0 28296 139788
-/+ buffers/cache: 157264 350320
Swap: 1043272 0 1043272
The output of slabtop taken at the same time is a printscr (I am not running any gui on the fedora machine) at this location [url=http://www.hughes-family.com/slabtop.jpg]Slabtop Jpeg[/url]
Kernel = 2.6.10-1.760_FC3
I have seen all the posts that state that the memory usage is normal, and I can understand growth on demand - the release of cache pages will depend on the wash methods (fifo etc). I don't understand the constant decrement of 64k off physical and 4k or 8k added to cache that happens every 4 mins (or so) without the corresponding growth in the program sizes. If the 64k was being added to cache, then I would expect it to match. Or is this the method that fedora uses to build up the physical memory.
Why does the disk spin and the machine lock up when it hits swap? If the memory is cache, then surely it won't start swapping until the cache memory is utilised.
Any help or direction as to where to look is appreciated.
This is an email sent via the webforum on http://fcp.homelinux.org