chown
by Liloulinx
Hi,
Evry time when I create a directory, automaticaly the system make the
root as the owner of this directory. When I (the user or the root) try
to change its owner (by using the chown commande), the answer of the
system is "not allowed Operation".
Where is the problem? is there a bad parameter...
thanks.
___________________________________________________________________________
Appel audio GRATUIT partout dans le monde avec le nouveau Yahoo! Messenger
Téléchargez cette version sur http://fr.messenger.yahoo.com
18 years, 9 months
Re: Setting Up Linksys Wireless Internet with Fadora
by mindwave＠cfl.rr.com
dont know anything about a key.
but i used this:
https://www.linuxant.com/driverloader/wlan/downloads-installer.php
in my laptop and it works like a charm.
its $20 but WELL worthwhile.
the ndiswrapper would load but i could never get it connected to my
network by manually configuring.
my time is worth a little more than $20.
j
Hello All,
I am trying to set up a wireless network in my house and one of the computers is running Fadora. I know absolutly nothing about the operating system and any help would be greatly appreciated. I need to know where exactly I enter the key so that the adapter can connect to the network.
Thanks in Advance
-John
--
fedora-list mailing list
fedora-list(a)redhat.com
To unsubscribe: http://www.redhat.com/mailman/listinfo/fedora-list
18 years, 9 months
Portmap compilation problem
by Vendra, Hari Prasad V V P CH S H (Hari V)
I am trying to compile portmapper source code down loaded from Linux web
site <ftp://ftp.porcupine.org/pub/security/>
I am getting the following error. Anybody have any idea, how to resolve
this.
portmap_4]# make
cc -Dconst= -Dperror=xperror -DHOSTS_ACCESS -DCHECK_PORT
-DFACILITY=LOG_MAIL -O -c -o portmap.o portmap.c
portmap.c: In function `xperror':
portmap.c:239: error: argument "what" doesn't match prototype
/usr/include/stdio.h:742: error: prototype declaration
portmap.c: In function `reg_service':
portmap.c:293: warning: passing arg 2 of `svc_sendreply' from incompatible
pointer type
portmap.c:302: warning: passing arg 2 of pointer to function from
incompatible pointer type
portmap.c:302: warning: passing arg 3 of pointer to function from
incompatible pointer type
portmap.c:344: warning: passing arg 2 of `svc_sendreply' from incompatible
pointer type
portmap.c:356: warning: passing arg 2 of pointer to function from
incompatible pointer type
portmap.c:356: warning: passing arg 3 of pointer to function from
incompatible pointer type
portmap.c:390: warning: passing arg 2 of `svc_sendreply' from incompatible
pointer type
portmap.c:402: warning: passing arg 2 of pointer to function from
incompatible pointer type
portmap.c:402: warning: passing arg 3 of pointer to function from
incompatible pointer type
portmap.c:417: warning: passing arg 2 of `svc_sendreply' from incompatible
pointer type
portmap.c:429: warning: passing arg 2 of pointer to function from
incompatible pointer type
portmap.c:441: warning: passing arg 2 of `svc_sendreply' from incompatible
pointer type
portmap.c: In function `xdr_encap_parms':
portmap.c:484: warning: passing arg 3 of `xdr_bytes' from incompatible
pointer type
portmap.c: In function `callit':
portmap.c:588: warning: passing arg 2 of pointer to function from
incompatible pointer type
portmap.c:588: warning: passing arg 3 of pointer to function from
incompatible pointer type
portmap.c:617: warning: passing arg 3 of pointer to function from
incompatible pointer type
portmap.c:617: warning: passing arg 4 of pointer to function from
incompatible pointer type
portmap.c:617: warning: passing arg 5 of pointer to function from
incompatible pointer type
portmap.c:617: warning: passing arg 6 of pointer to function from
incompatible pointer type
portmap.c:619: warning: passing arg 2 of `svc_sendreply' from incompatible
pointer type
make: *** [portmap.o] Error 1
Thanks in Advance for your response.
V V V P CH S Hari Prasad ( Hari )
(Off : 0091-402-337-9334 X 2052)
(Mob : 0091-944-085-7322)
18 years, 9 months
Server Dedicated to Fedora Community
by Ryno Burger
Hello Fedora list members,
I would like to take the opportunity to provide something back to the
community and want to ask you as Fedora List Member to help me provide that
something...
Over the years I have been involved with Linux and Software Development I
gained so much knowledge and would like to give something in return.
I have a spare server that I would like to dedicate to the community and for
the community ONLY!
I am looking for any suggestions from you the community as what kind of free
services you guys would like to have or would like to do with it.
Any suggestion will be welcome, especially suggestions related to Linux and
Open Source Programming / Development.
I'm looking forward to hear from you.
Thank you for you time.
Kind Regards,
Ryno Burger
18 years, 9 months
Re: Share internet connection/make a small server
by Antonio Olivares
--- Jeff Vian <jvian10(a)charter.net> wrote:
> On Wed, 2005-08-31 at 17:16 -0700, Antonio Olivares
> wrote:
> >
> > --- Jeff Vian <jvian10(a)charter.net> wrote:
> >
> > > On Wed, 2005-08-31 at 12:20 -0700, Antonio
> Olivares
> > > wrote:
> > > >
> > > > --- Antonio Olivares <olivares14031(a)yahoo.com>
> > > wrote:
> > > >
> > > > >
> > > > >
> > > > > --- Alexander Dalloz <ad+lists(a)uni-x.org>
> wrote:
> > > > >
> > > > > > Am Di, den 30.08.2005 schrieb Antonio
> Olivares
> > > um
> > > > > > 15:02:
> > > > > >
> > > > > > > > Make sure you have forwarding set on
> on
> > > the
> > > > > > gateway
> > > > > > > > host:
> > > > > > > >
> > > > > > > > $ cat /proc/sys/net/ipv4/ip_forward
> > > > > > > >
> > > > > > > > must print out "1" (without quotes).
> If it
> > > > > does
> > > > > > not,
> > > > > > > > then activate it in
> > > > > > > > /etc/sysctl.conf and run "sysctl -p".
> Make
> > > too
> > > > > > sure
> > > > > > > > the gateway does NAT
> > > > > > > > by an iptables rule like:
> > > > > > > >
> > > > > > > > iptables -A POSTROUTING -o eth0 -j
> > > MASQUERADE
> > > > > > > >
> > > > > > > > [eth0 should be in your case the
> outgoing
> > > > > > device]
> > > > > > >
> > > > > > > eth0 is the incoming connection should
> eth1
> > > be
> > > > > the
> > > > > > > outgoing. I'm a little confused but
> getting
> > > > > > there.
> > > > > >
> > > > > > The device given with -o <device> has to
> be
> > > the
> > > > > > public net device.
> > > > > >
> > > > > > > [root@rio ~]# cat
> > > /proc/sys/net/ipv4/ip_forward
> > > > > > > 1
> > > > > >
> > > > > > Ok.
> > > > > >
> > > > > > > [root@rio ~]# iptables -A POSTROUTING -o
> > > eth0 -j
> > > > > > > MASQUERADE
> > > > > > > iptables: No chain/target/match by that
> name
> > > > > >
> > > > > > Sorry, my fault. Above should have been
> for
> > > the
> > > > > NAT
> > > > > > table (by default
> > > > > > iptables takes the filter table):
> > > > > >
> > > > >
> > > > >
> > > > === message truncated ===
> > >
> > > > I'm trying continually to solve this issue and
> I
> > > have
> > > > tried with a windows2000 machine and I get
> this
> > > >
> > >
> > > Reading thru what you have below, this seems to
> most
> > > certainly be a
> > > routing/firewalling/masquerading issue on the
> linux
> > > box.
> > >
> > > >From the windows box try this and let us know
> the
> > > results.
> > > 1. ping 192.168.100.1
> >
> > [olivares@rio floppy]$ cat ping1
> >
> > Pinging 192.168.100.1 with 32 bytes of data:
> >
> > Reply from 192.168.100.1: bytes=32 time<10ms
> TTL=64
> > Reply from 192.168.100.1: bytes=32 time<10ms
> TTL=64
> > Reply from 192.168.100.1: bytes=32 time<10ms
> TTL=64
> > Reply from 192.168.100.1: bytes=32 time<10ms
> TTL=64
> >
> > Ping statistics for 192.168.100.1:
> > Packets: Sent = 4, Received = 4, Lost = 0 (0%
> > loss),
> > Approximate round trip times in milli-seconds:
> > Minimum = 0ms, Maximum = 0ms, Average = 0ms
> >
> >
> > > 2. ping 10.154.19.136
> >
> > [olivares@rio floppy]$ cat ping2
> >
> > Pinging 10.154.19.136 with 32 bytes of data:
> >
> > Reply from 10.154.19.136: bytes=32 time<10ms
> TTL=64
> > Reply from 10.154.19.136: bytes=32 time<10ms
> TTL=64
> > Reply from 10.154.19.136: bytes=32 time<10ms
> TTL=64
> > Reply from 10.154.19.136: bytes=32 time<10ms
> TTL=64
> >
> > Ping statistics for 10.154.19.136:
> > Packets: Sent = 4, Received = 4, Lost = 0 (0%
> > loss),
> > Approximate round trip times in milli-seconds:
> > Minimum = 0ms, Maximum = 0ms, Average = 0ms
> >
> >
> > >
> > > 3. If both those work, then try a ping to
> > > 10.154.19.130
> >
> > [olivares@rio floppy]$ cat ping3
> >
> > Pinging 10.154.19.130 with 32 bytes of data:
> >
> > Request timed out.
> > Request timed out.
> > Reply from 10.154.19.136: Destination host
> > unreachable.
> > Request timed out.
> >
> > Ping statistics for 10.154.19.130:
> > Packets: Sent = 4, Received = 1, Lost = 3 (75%
> > loss),
> > Approximate round trip times in milli-seconds:
> > Minimum = 0ms, Maximum = 0ms, Average = 0ms
> > [olivares@rio floppy]$
> >
>
> Ok, this clearly shows that it is likely you are
> having problems with
> NAT (masquerading) &/or routing/firewalling. Your
> windows machine can
> connect to and see both interfaces on the Linux
> server but cannot get
> beyond that. I assume your Linux box has full access
> to the internet
> when I say this.
>
> Check out the basic firewall rules for doing ip
> forwarding and
> masquerading. In your case eth1 is the LAN and eth0
> is the WAN.
>
> I do not have a basic setup available for FC
> firewalling since my
> firewall machine is running RH7.3 with ipchains and
> FC uses iptables.
> (My firewall machine is an old P3 with only 32mb
> memory and cannot run
> any version of FC.)
>
> I will try to set up a list of rules that are basic
> and will handle what
> you need and send a sample to you. Others may beat
> me to it, and
> welcome if they do.
>
> To see what you currently have as iptables rules,
> try "iptables -L" and
> send that.
> Also send the contents of /etc/sysconfig/iptables
>
=== message truncated ===
[olivares@rio ~]$ iptables -L
bash: iptables: command not found
[olivares@rio ~]$ su -
Password:
[root@rio ~]# iptables -L
Chain INPUT (policy ACCEPT)
target prot opt source destination
RH-Firewall-1-INPUT all -- anywhere
anywhere
Chain FORWARD (policy ACCEPT)
target prot opt source destination
RH-Firewall-1-INPUT all -- anywhere
anywhere
Chain OUTPUT (policy ACCEPT)
target prot opt source destination
Chain RH-Firewall-1-INPUT (2 references)
target prot opt source destination
ACCEPT all -- anywhere anywhere
ACCEPT icmp -- anywhere anywhere
icmp any
ACCEPT ipv6-crypt-- anywhere anywhere
ACCEPT ipv6-auth-- anywhere anywhere
ACCEPT udp -- anywhere 224.0.0.251
udp dpt:5353
ACCEPT udp -- anywhere anywhere
udp dpt:ipp
ACCEPT all -- anywhere anywhere
state RELATED,ESTABLISHED
REJECT all -- anywhere anywhere
reject-with icmp-host-prohibited
[root@rio ~]# cat /etc/sysconfig/iptables
# Generated by iptables-save v1.2.11 on Wed Aug 31
07:52:24 2005
*mangle
:PREROUTING ACCEPT [4991:3431359]
:INPUT ACCEPT [4887:3424427]
:FORWARD ACCEPT [96:6000]
:OUTPUT ACCEPT [4459:969407]
:POSTROUTING ACCEPT [4475:971455]
COMMIT
# Completed on Wed Aug 31 07:52:24 2005
# Generated by iptables-save v1.2.11 on Wed Aug 31
07:52:24 2005
*filter
:INPUT ACCEPT [0:0]
:FORWARD ACCEPT [0:0]
:OUTPUT ACCEPT [4467:969967]
:RH-Firewall-1-INPUT - [0:0]
-A INPUT -j RH-Firewall-1-INPUT
-A FORWARD -j RH-Firewall-1-INPUT
-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 ipv6-crypt -j ACCEPT
-A RH-Firewall-1-INPUT -p ipv6-auth -j ACCEPT
-A RH-Firewall-1-INPUT -d 224.0.0.251 -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 -m state --state
RELATED,ESTABLISHED -j ACCEPT
-A RH-Firewall-1-INPUT -j REJECT --reject-with
icmp-host-prohibited
COMMIT
# Completed on Wed Aug 31 07:52:24 2005
# Generated by iptables-save v1.2.11 on Wed Aug 31
07:52:24 2005
*nat
:PREROUTING ACCEPT [759:76421]
:POSTROUTING ACCEPT [4:288]
:OUTPUT ACCEPT [394:23805]
-A POSTROUTING -o eth1 -j MASQUERADE
-A POSTROUTING -o eth0 -j MASQUERADE
-A POSTROUTING -o eth1 -j MASQUERADE
-A POSTROUTING -o eth0 -j MASQUERADE
-A POSTROUTING -o eth1 -j MASQUERADE
-A POSTROUTING -o eth1 -j MASQUERADE
COMMIT
# Completed on Wed Aug 31 07:52:24 2005
[root@rio ~]# cat /proc/sys/net/ipv4/ip_forward
1
[root@rio ~]#
Thanks for all your help and suggestions. It will
work. It is just a matter of finding where things are
stopping.
Best Regards,
Antonio
____________________________________________________
Start your day with Yahoo! - make it your home page
http://www.yahoo.com/r/hs
18 years, 9 months
Matrox_w1 module with kernel-2.6.12-1.1447_FC4?
by Steve Parker
Hi,
I just upgraded my kernel to 2.6.12-1.1447_FC4 and now I see the
following messages in syslog:
Aug 31 19:14:33 localhost kernel: w1_driver w1_bus_master1: No devices
present on the wire.
Aug 31 19:14:43 localhost kernel: w1_driver w1_bus_master1: No devices
present on the wire.
Aug 31 19:14:53 localhost kernel: w1_driver w1_bus_master1: No devices
present on the wire.
Aug 31 19:15:33 localhost last message repeated 4 times
Aug 31 19:15:43 localhost kernel: w1_driver w1_bus_master1: No devices
present on the wire.
Aug 31 19:15:53 localhost kernel: w1_driver w1_bus_master1: No devices
present on the wire.
Aug 31 19:16:33 localhost last message repeated 4 times
Aug 31 19:17:43 localhost last message repeated 7 times
Well, you get the idea... A little research turned up that this module
is loaded is a Matrox card is present (I have a Matrox G450). Here are
the relevant syslog entries:
Aug 31 19:10:15 localhost kernel: Driver for 1-wire Dallas network protocol.
Aug 31 19:10:15 localhost kernel: matrox_w1 0000:01:00.0: Matrox G400
GPIO transport layer for 1-wire.
I can eliminate the messages simply by 'rmmod matrox_w1' but my
questions are why is it loading in the first place and how do I
permanently disable it? Thanks in advance!
-Steve
18 years, 9 months
Does lpr command support IPv6 in Fedora Core 4?
by Kohki Ohhira
Dear all,
Now, we are trying to use Fedra Core 4 in an IPv6 environment.
However, the `lpr' command doesn't look ipv6 ready.
Does lpr command support IPv6 in Fedora Core 4?
If you know, will you give your knowledge to us?
--
Kohki Ohhira
18 years, 9 months
FC4 - Scanning with the hp psc 750
by Roger Grosswiler
hey,
after googling a lot and find some information about the hp psc750
scanning i remarked - mine doesn't
He prints, ok, but he doesn't scan.
Unfortunately, nowhere has been described, how they got their psc750
working. Do you have a hint for me?
Thanks,
Roger
18 years, 9 months
FC4 - IBM e326 - network problems.
by Naoki
Hi all.
I have a networking problem here I'd like to share.
Cut down FC4 build on an IBM e326.
I am attempting to SCP 2.4MB of data to this box ( from anywhere the
results are the same ).
It connects, asks for password, which I give. And then after a few
packets I see it all go very ugly indeed. Throwing retransmissions and,
segment losts, and DUP ACK messages.
Which just kills the scp with a "Stalled" message. If I leave it then
_eventaully_ the file will transfer.
I've changed switches and have the same result. Starting to wonder if
there is a problem with the Broadcom ethernet controller? One of the
reasons I suspect the controller is performance jumps to normal (good)
after I reinitialise the card.
Server end :
4.913749 10.0.2.27 -> 10.0.2.31 SSHv2 Encrypted request packet
len=144
4.916377 10.0.2.31 -> 10.0.2.27 SSHv2 Encrypted response packet
len=32
4.916533 10.0.2.27 -> 10.0.2.31 TCP 60952 > ssh [ACK] Seq=1293
Ack=1597 Win=8400 Len=0 TSV=2056922151 TSER=5310028
4.916828 10.0.2.27 -> 10.0.2.31 SSHv2 Encrypted request packet
len=64
4.916965 10.0.2.31 -> 10.0.2.27 SSHv2 Encrypted response packet
len=48
4.917276 10.0.2.27 -> 10.0.2.31 SSHv2 Encrypted request packet
len=64
4.918916 10.0.2.31 -> 10.0.2.27 SSHv2 Encrypted response packet
len=48
4.958139 10.0.2.27 -> 10.0.2.31 TCP 60952 > ssh [ACK] Seq=1421
Ack=1693 Win=8400 Len=0 TSV=2056922193 TSER=5310031
4.958153 10.0.2.31 -> 10.0.2.27 SSHv2 Encrypted response packet
len=48
4.958306 10.0.2.27 -> 10.0.2.31 TCP 60952 > ssh [ACK] Seq=1421
Ack=1741 Win=8400 Len=0 TSV=2056922193 TSER=5310070
4.958609 10.0.2.27 -> 10.0.2.31 SSHv2 Encrypted request packet
len=64
4.958762 10.0.2.31 -> 10.0.2.27 SSHv2 Encrypted response packet
len=48
4.962323 10.0.2.27 -> 10.0.2.31 SSHv2 Encrypted request packet
len=1448
4.962446 10.0.2.27 -> 10.0.2.31 SSHv2 Encrypted request packet
len=1448
4.962451 10.0.2.31 -> 10.0.2.27 TCP ssh > 60952 [ACK] Seq=1789
Ack=4381 Win=15424 Len=0 TSV=5310074 TSER=2056922196
4.962986 10.0.2.27 -> 10.0.2.31 SSHv2 Encrypted request packet
len=1448
4.963239 10.0.2.27 -> 10.0.2.31 SSHv2 [TCP Previous segment
lost] Encrypted request packet len=1448
4.963244 10.0.2.31 -> 10.0.2.27 TCP ssh > 60952 [ACK] Seq=1789
Ack=5829 Win=18320 Len=0 TSV=5310075 TSER=2056922197 SLE=7277 SRE=8725
4.963780 10.0.2.27 -> 10.0.2.31 SSHv2 Encrypted request packet
len=1448
4.963785 10.0.2.31 -> 10.0.2.27 TCP [TCP Dup ACK 46#1] ssh >
60952 [ACK] Seq=1789 Ack=5829 Win=18320 Len=0 TSV=5310076
TSER=2056922197 SLE=7277 SRE=10173
5.178550 10.0.2.27 -> 10.0.2.31 SSHv2 [TCP Retransmission]
Encrypted request packet len=1448
5.178557 10.0.2.31 -> 10.0.2.27 TCP ssh > 60952 [ACK] Seq=1789
Ack=10173 Win=21216 Len=0 TSV=5310290 TSER=2056922413
5.179217 10.0.2.27 -> 10.0.2.31 SSHv2 [TCP Previous segment
lost] Encrypted request packet len=1448
5.179221 10.0.2.31 -> 10.0.2.27 TCP [TCP Dup ACK 50#1] ssh >
60952 [ACK] Seq=1789 Ack=10173 Win=21216 Len=0 TSV=5310291
TSER=2056922413 SLE=11621 SRE=13069
5.179741 10.0.2.27 -> 10.0.2.31 SSHv2 Encrypted request packet
len=1448
5.179745 10.0.2.31 -> 10.0.2.27 TCP [TCP Dup ACK 50#2] ssh >
60952 [ACK] Seq=1789 Ack=10173 Win=21216 Len=0 TSV=5310292
TSER=2056922413 SLE=11621 SRE=14517
5.180252 10.0.2.27 -> 10.0.2.31 SSHv2 Encrypted request packet
len=1448
5.180255 10.0.2.31 -> 10.0.2.27 TCP [TCP Dup ACK 50#3] ssh >
60952 [ACK] Seq=1789 Ack=10173 Win=21216 Len=0 TSV=5310292
TSER=2056922413 SLE=11621 SRE=15965
5.391515 10.0.2.27 -> 10.0.2.31 SSHv2 [TCP Retransmission]
Encrypted request packet len=1448
5.391520 10.0.2.31 -> 10.0.2.27 TCP ssh > 60952 [ACK] Seq=1789
Ack=15965 Win=24112 Len=0 TSV=5310503 TSER=2056922626
5.392043 10.0.2.27 -> 10.0.2.31 SSHv2 Encrypted request packet
len=1448
5.392048 10.0.2.31 -> 10.0.2.27 TCP ssh > 60952 [ACK] Seq=1789
Ack=17413 Win=27008 Len=0 TSV=5310504 TSER=2056922626
5.603540 10.0.2.27 -> 10.0.2.31 SSHv2 [TCP Out-Of-Order]
Encrypted request packet len=1448
5.603546 10.0.2.31 -> 10.0.2.27 TCP [TCP Dup ACK 60#1] ssh >
60952 [ACK] Seq=1789 Ack=17413 Win=27008 Len=0 TSV=5310715
TSER=2056922838 SLE=15965 SRE=17413
Broadcom Corporation NetXtreme BCM5704 Gigabit Ethernet - tg3 driver.
# ethtool eth0
Settings for eth0:
Supported ports: [ MII ]
Supported link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Half 1000baseT/Full
Supports auto-negotiation: Yes
Advertised link modes: Not reported
Advertised auto-negotiation: No
Speed: 100Mb/s
Duplex: Full
Port: Twisted Pair
PHYAD: 1
Transceiver: internal
Auto-negotiation: off
Supports Wake-on: g
Wake-on: d
Current message level: 0x000000ff (255)
Link detected: yes
Client end :
5.019926 10.0.2.27 -> 10.0.2.31 SSHv2 [TCP Retransmission]
Encrypted request packet len=1448
5.020438 10.0.2.31 -> 10.0.2.27 TCP ssh > 35380 [ACK] Seq=1789
Ack=7277 Win=21216 Len=0 TSV=6343633 TSER=2057955472 SLE=4381 SRE=5829
5.020513 10.0.2.27 -> 10.0.2.31 SSHv2 Encrypted request packet
len=1448
5.020523 10.0.2.27 -> 10.0.2.31 SSHv2 Encrypted request packet
len=1448
5.263902 10.0.2.27 -> 10.0.2.31 SSHv2 [TCP Retransmission]
Encrypted request packet len=1448
5.264426 10.0.2.31 -> 10.0.2.27 TCP ssh > 35380 [ACK] Seq=1789
Ack=10173 Win=24112 Len=0 TSV=6343877 TSER=2057955920
5.264464 10.0.2.27 -> 10.0.2.31 SSHv2 [TCP Retransmission]
Encrypted request packet len=1448
5.264475 10.0.2.27 -> 10.0.2.31 SSHv2 Encrypted request packet
len=1448
5.500935 10.0.2.27 -> 10.0.2.31 SSHv2 [TCP Retransmission]
Encrypted request packet len=1448
Client shows retransmissions but no DUP Ack or segment lost messages.
Any ideas? I have other servers running with Broadcom BCM5703X chips and
using the tg3 driver without problem.
18 years, 9 months
FC multi version install: re-using partitions
by David Niemi
Yes, generally a multi-version install has been covered just want to
know about re-using some of the partitions.
/dev/sdc2 7.6G 3.8G 3.5G 53% /
/dev/sdc1 145M 31M 107M 22% /boot
/dev/shm 1005M 0 1005M 0% /dev/shm
/dev/sdc7 9.7G 1.1G 8.1G 12% /home
/dev/sdc3 7.7G 2.5G 4.9G 34% /os2
/dev/sdc5 6.7G 938M 5.4G 15% /var
I've FC4 i386_x64 installed and for testing compilation would like to
install the regular i386 version. Reusing the swap partition should be
fine, install /boot onto the / partition instead of causing problems
with my main install. The /os2 partition is where I'm going to install
the other version.
Will it cause problems re-using /home and /var (probably problems with
the latter). I'll probably have to backup /home (cp -pR), install,
create user(s), login then out and then as root copy everything back.
Thanks
18 years, 9 months
