On 05/10/2014 04:28 AM, Gary Stainburn wrote:
Hi folks.
I've got a virtual server running on 123-reg's farm which is running F17.
I'm looking for adivce, suggestions, gocha's etc regarding upgrading this
system at least as far as F19 if not F20.
I'm looking at probably using fedup as I've use
Hi folks.
I've got a virtual server running on 123-reg's farm which is running F17.
I'm looking for adivce, suggestions, gocha's etc regarding upgrading this
system at least as far as F19 if not F20.
I'm looking at probably using fedup as I've used that in the past but always
on boxes that I w
ebcam built in.
So: How can I get the damned thing to "work properly"? Is there
something I need to do to switch it on? Does it need "drivers"
installed? If so, do there exist drivers that will work under Linux,
specifically under Fedora 17?
Please try not to be *too*
to "work properly"? Is there
something I need to do to switch it on? Does it need "drivers"
installed? If so, do there exist drivers that will work under Linux,
specifically under Fedora 17?
Please try not to be *too* cryptic in your responses! There are many
lacunae in my kn
re
something I need to do to switch it on? Does it need "drivers"
installed? If so, do there exist drivers that will work under Linux,
specifically under Fedora 17?
Please try not to be *too* cryptic in your responses! There are many
lacunae in my knowledge and many acronyms and pieces of jar
ed "drivers"
installed? If so, do there exist drivers that will work under Linux,
specifically under Fedora 17?
Please try not to be *too* cryptic in your responses! There are many
lacunae in my knowledge and many acronyms and pieces of jargon bewilder me!
Thanks
On Thu, Dec 19, 2013 09:50:01 AM +, Frank Murphy wrote:
> Fedora 17 has python 2.7 as can be seen
> and python modules built against 2.7 (normal practise)
>
> Check the src, and see if you need to install some lib*
> https://github.com/gaubert/gmvault/tree/v1.8-beta-20130321
On Thu, 19 Dec 2013 07:32:44 +0100
"M. Fioretti" wrote:
> This is why, while being perfectly aware that Fedora 17 is
> unsupported, that even those other packages may stop working etc..
> I'd really like to know what, exactly, makes gmvault fail in that
> way, on tha
On Wed, Dec 18, 2013 10:22:18 AM +, Frank Murphy wrote:
> >
> The first thing they will say is you are using an unsupported Fedora
> release. http://gmvault.org/report_pb.html
First, albeit not worth discussing here, there ARE reasons why that
specific box still has to be on Fed
On Wed, 18 Dec 2013 11:11:49 +0100
"M. Fioretti" wrote:
> Greetings,
>
> I'm testing gmvault (http://gmvault.org/) a gmail backup tool, on
> fedora 17 x86_64.
>
> I have followed all the instructions (enable the app, change gmail
> settings etc) in the i
Greetings,
I'm testing gmvault (http://gmvault.org/) a gmail backup tool, on fedora 17
x86_64.
I have followed all the instructions (enable the app, change gmail
settings etc) in the install page:
http://gmvault.org/gmail_setup.html
However, the program aborts with the python error
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 12/17/2013 12:05 PM, Lars Poulsen wrote:
> I have been gradually updating my Fedora servers from a variety of
> releases ranging to F14 to F18 to more current versions. In order
> to do these as in-place updates rather than re-installs (which
> s
I have been gradually updating my Fedora servers from a variety of
releases ranging to F14 to F18 to more current versions. In order to do
these as in-place updates rather than re-installs (which saves many
headaches) I have had to do this gradually. Most are now running F19
with one "pioneer" at
On Mon, 2013-10-14 at 13:01 -0700, Jack Craig wrote:
>
>
>
> On Mon, Oct 14, 2013 at 12:53 PM, Rick Stevens
> wrote:
> On 10/14/2013 12:16 PM, Carlos "casep" Sepulveda issued this
> missive:
>
> On 14 October 2013 16:07, Jack Craig
> wro
On Mon, Oct 14, 2013 at 12:53 PM, Rick Stevens wrote:
> On 10/14/2013 12:16 PM, Carlos "casep" Sepulveda issued this missive:
>
> On 14 October 2013 16:07, Jack Craig wrote:
>>
>>> Is there an updated version of Skype that would work on F17 ?
>>>
>>
> F17 has been EOL'd so you should think abou
Thx! i'll check it out!
On Mon, Oct 14, 2013 at 12:16 PM, Carlos "casep" Sepulveda <
ca...@fedoraproject.org> wrote:
> On 14 October 2013 16:07, Jack Craig wrote:
> > Is there an updated version of Skype that would work on F17 ?
>
>
> Hi:
> The latest available on skype's site** is 4.2.0.11 and
On 10/14/2013 12:16 PM, Carlos "casep" Sepulveda issued this missive:
On 14 October 2013 16:07, Jack Craig wrote:
Is there an updated version of Skype that would work on F17 ?
F17 has been EOL'd so you should think about upgrading. That being
said, I'm running skype 4.2.0.11 on an F17 box I h
On 14 October 2013 16:07, Jack Craig wrote:
> Is there an updated version of Skype that would work on F17 ?
Hi:
The latest available on skype's site** is 4.2.0.11 and says to be
compiled for Fedora 16... maybe you could give it a try...
http://www.skype.com/en/download-skype/skype-for-linux/
Hi Folks,
I am running Skype 4.1.0.20 on my Fedora 17 on a 64bit platform and having
video issues.
Is there an updated version of Skype that would work on F17 ?
Tia, jackc...
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https
I did a fresh install of fedora 17 a couple of months ago.
I did yum update after the install.
After almost two months, I don't have any new updates, which I find odd.
I've done a yum clean all.
package-cleanup --problems, orphans is all clean.
How can I diagnose if the yum/rpm insta
> -Original Message-
> From: users-boun...@lists.fedoraproject.org [mailto:users-
> boun...@lists.fedoraproject.org] On Behalf Of Jim Duda
> Sent: Thursday, September 12, 2013 10:39 AM
> To: users@lists.fedoraproject.org
> Subject: fedora 17 yum update
>
> I did a
On Thu, Sep 12, 2013 at 01:39:11PM -0400, Jim Duda wrote:
> I did a fresh install of fedora 17 a couple of months ago.
> I did yum update after the install.
> After almost two months, I don't have any new updates, which I find odd.
> I've done a yum clean all.
> package-cl
Hi Jim,
This is because F17 has reached its EOL. Typically, FX's reach their
EOL one month after the release of F(X+2).
So, suggestion to you would be to upgrade.
Ranjan
On Thu, 12 Sep 2013 13:39:11 -0400 Jim Duda wrote:
> I did a fresh install of fedora 17 a couple of months ago.
fedora-upgrade
Another method of upgrading Fedora, looks pretty familiar. :)
Based on 'yum upgrade'.
https://github.com/xsuchy/fedora-upgrade
https://fedoraproject.org/wiki/Features/FedoraUpgrade
Successfully tested.
poma
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or ch
On 04/21/13 22:30, Mateusz Marzantowicz wrote:
> Thanks, for all suggestions. I'll choose subjects and terms more
> precisely next time. Sorry for all your inconvenience and I hope you're
> not going to blacklist my next messages.
No But I may decide to blacklist others for being overly pedan
On 21.04.2013 02:16, Bill Davidsen wrote:
> The fact that you continue to deny a poor choice of subject rather
> than just make a note to be very clear in future subjects makes me
> sorry I spent time composing two answers, one to your subject and one
> to your real problem.
>
> Reindl tends to be
Am 21.04.2013 03:23, schrieb Joe Zeff:
> On 04/20/2013 05:05 PM, Bill Davidsen wrote:
>> Reindl Harald wrote:
>>>
>>>
>>> Am 18.04.2013 23:08, schrieb Mateusz Marzantowicz:
No, because I don't want to upgrade from f17 to f18. I'm just doing
regular system update (or at last, I'm trying)
Am 21.04.2013 01:46, schrieb Bill Davidsen:
> Mateusz Marzantowicz wrote:
>> I can't cleanly upgrade my Fedora installation (I use --skip-broken),
>> below is error reported by yum:
>>
> You have gained wisdom, the fc17->fc18 upgrade path(s) are not robust.
> Sometime f'ed-up will work,
and if
On 04/20/2013 05:05 PM, Bill Davidsen wrote:
Reindl Harald wrote:
Am 18.04.2013 23:08, schrieb Mateusz Marzantowicz:
No, because I don't want to upgrade from f17 to f18. I'm just doing
regular system update (or at last, I'm trying)
* so please do NOT use the term "upgrade"
Update would be
Mateusz Marzantowicz wrote:
On 19.04.2013 10:15, Reindl Harald wrote:
Am 19.04.2013 08:24, schrieb Mateusz Marzantowicz:
On 18.04.2013 23:18, Reindl Harald wrote:
Am 18.04.2013 23:08, schrieb Mateusz Marzantowicz:
No, because I don't want to upgrade from f17 to f18. I'm just doing
regular sy
Reindl Harald wrote:
Am 18.04.2013 23:08, schrieb Mateusz Marzantowicz:
No, because I don't want to upgrade from f17 to f18. I'm just doing
regular system update (or at last, I'm trying)
* so please do NOT use the term "upgrade"
Update would be easier to understand here
* do not use "--s
Mateusz Marzantowicz wrote:
I can't cleanly upgrade my Fedora installation (I use --skip-broken),
below is error reported by yum:
You have gained wisdom, the fc17->fc18 upgrade path(s) are not robust. Sometime
f'ed-up will work, sometimes yum will work, always fresh install will work.
NOTE: b
2013-04-19 10:15 keltezéssel, Reindl Harald írta:
Am 19.04.2013 08:24, schrieb Mateusz Marzantowicz:
On 18.04.2013 23:18, Reindl Harald wrote:
Am 18.04.2013 23:08, schrieb Mateusz Marzantowicz:
No, because I don't want to upgrade from f17 to f18. I'm just doing
regular system update (or at la
Am 19.04.2013 10:50, schrieb Mateusz Marzantowicz:
> I don't like arguments about terms.
and i don't like discussions about clear subjects
like "yum does not solve dependencies" instead
"can't upgrade" while it is pretty clear that
such dep-problems in case of a normal update
are going away as t
On 19.04.2013 10:15, Reindl Harald wrote:
>
> Am 19.04.2013 08:24, schrieb Mateusz Marzantowicz:
>> On 18.04.2013 23:18, Reindl Harald wrote:
>>> Am 18.04.2013 23:08, schrieb Mateusz Marzantowicz:
No, because I don't want to upgrade from f17 to f18. I'm just doing
regular system update (o
Am 19.04.2013 08:24, schrieb Mateusz Marzantowicz:
> On 18.04.2013 23:18, Reindl Harald wrote:
>>
>> Am 18.04.2013 23:08, schrieb Mateusz Marzantowicz:
>>> No, because I don't want to upgrade from f17 to f18. I'm just doing
>>> regular system update (or at last, I'm trying)
>> * so please do NOT
On 18.04.2013 23:22, Michael Schwendt wrote:
> On Thu, 18 Apr 2013 22:41:06 +0200, Mateusz Marzantowicz wrote:
>
>> I can't cleanly upgrade my Fedora installation (I use --skip-broken),
>> below is error reported by yum:
>>
>> Resolving Dependencies
>> --> Running transaction check
>> ---> Package
On 18.04.2013 23:18, Reindl Harald wrote:
>
> Am 18.04.2013 23:08, schrieb Mateusz Marzantowicz:
>> No, because I don't want to upgrade from f17 to f18. I'm just doing
>> regular system update (or at last, I'm trying)
> * so please do NOT use the term "upgrade"
Why? Yum uses this term.
> * do not
On Thu, 18 Apr 2013 22:41:06 +0200, Mateusz Marzantowicz wrote:
> I can't cleanly upgrade my Fedora installation (I use --skip-broken),
> below is error reported by yum:
>
> Resolving Dependencies
> --> Running transaction check
> ---> Package febootstrap-supermin-helper.x86_64 0:3.20-1.fc17 will
Am 18.04.2013 23:08, schrieb Mateusz Marzantowicz:
> No, because I don't want to upgrade from f17 to f18. I'm just doing
> regular system update (or at last, I'm trying)
* so please do NOT use the term "upgrade"
* do not use "--skip-broken"
* analyze what deps are failing
* consider to wait a fe
On 18.04.2013 23:02, Steven Stern wrote:
> On 04/18/2013 03:41 PM, Mateusz Marzantowicz wrote:
>> I can't cleanly upgrade my Fedora installation (I use --skip-broken),
>> below is error reported by yum:
>>
>> Resolving Dependencies
>> --> Running transaction check
>> ---> Package febootstrap-superm
On 04/18/2013 03:41 PM, Mateusz Marzantowicz wrote:
> I can't cleanly upgrade my Fedora installation (I use --skip-broken),
> below is error reported by yum:
>
> Resolving Dependencies
> --> Running transaction check
> ---> Package febootstrap-supermin-helper.x86_64 0:3.20-1.fc17 will be
> obsolet
Am 18.04.2013 22:41, schrieb Mateusz Marzantowicz:
> I can't cleanly upgrade my Fedora installation (I use --skip-broken),
> below is error reported by yum:
>
> Resolving Dependencies
> --> Running transaction check
> ---> Package febootstrap-supermin-helper.x86_64 0:3.20-1.fc17 will be
> obsole
I can't cleanly upgrade my Fedora installation (I use --skip-broken),
below is error reported by yum:
Resolving Dependencies
--> Running transaction check
---> Package febootstrap-supermin-helper.x86_64 0:3.20-1.fc17 will be
obsoleted
--> Processing Dependency: febootstrap-supermin-helper >= 3.3 f
On 04/12/2013 11:35 PM, Suvayu Ali wrote:
Hi Rolf,
On Fri, Apr 12, 2013 at 10:43:50PM +1200, Rolf Turner wrote:
I don't, didn't, never have, and never will use hypdestopt!!! Do you
see any reference to hypdestopt in the "demo" code?
I figured that it had to come from somewhere i
Sorry, I did not mean to send my previous message to the list, since
Joe Zeff had asked to email him off-list. I just clicked on "Reply"
thinking
my message would just go to the sender. (I didn't click on "Reply List"
or "Reply All".) And then I didn't notice that the To field was the list
On 04/13/2013 05:16 AM, Joe Zeff wrote:
On 04/12/2013 03:32 AM, Rolf Turner wrote:
I realized that I should have been doing
ps2pdf demo.ps
not
ps2pdf demo
and *that* was the source of the error that I was getting.
Brain fart. Don't worry about it. Tish happens. If you want to
On 04/12/2013 03:32 AM, Rolf Turner wrote:
I realized that I should have been doing
ps2pdf demo.ps
not
ps2pdf demo
and *that* was the source of the error that I was getting.
Brain fart. Don't worry about it. Tish happens. If you want to know
about one that had me going round i
> I said ***explicitly*** that "powerdot is not compatible with pdftex".
> I did
> "latex demo", ***NOT*** "pdflatex demo" and got the error that I
> reported.
>
You may install kerTeX^{1} and in there latex is latex :)
If you don't have Development Tools/Libraries installed do,
# yum installgr
On Fri, 2013-04-12 at 21:37 +1200, Rolf Turner wrote:
> So I need somehow to get an installation of texlive where "latex" really
> means
> ***latex*** and not "pdftex". How the hell do I arrange that?
>
I'm a bit late to this party, but Jindrich Novy's Fedora TeXLive repo
for F17 works well.
Hi Rolf,
On Fri, Apr 12, 2013 at 10:43:50PM +1200, Rolf Turner wrote:
> I don't, didn't, never have, and never will use hypdestopt!!! Do you
> see any reference to hypdestopt in the "demo" code?
>
> I figured that it had to come from somewhere in the bowels of powerdot.
> God know
Please see inline below.
On 04/12/2013 10:29 PM, Suvayu Ali wrote:
Hello Rolf,
On Fri, Apr 12, 2013 at 09:37:43PM +1200, Rolf Turner wrote:
I said ***explicitly*** that "powerdot is not compatible with pdftex". I
did
"latex demo", ***NOT*** "pdflatex demo" and got the error that I reported.
Further to my previous message: Maybe I *am* a moron and not just
an idiot studying hard to be one. I realized that I should have been doing
ps2pdf demo.ps
not
ps2pdf demo
and *that* was the source of the error that I was getting.
So it all seems to be working now. I guess the pro
Hello Rolf,
On Fri, Apr 12, 2013 at 09:37:43PM +1200, Rolf Turner wrote:
>
> I said ***explicitly*** that "powerdot is not compatible with pdftex". I
> did
> "latex demo", ***NOT*** "pdflatex demo" and got the error that I reported.
A little patience and being concise helps a lot. If you knew
No. I certainly ***DID NOT*** "expect it to work with pdflatex"!!! Please
read what I wrote. It's very irritating to be taken for a moron when
one is
only an idiot studying hard to be a moron and flunking the course!
I said ***explicitly*** that "powerdot is not compatible with pdftex".
Hi Ed,
On Fri, Apr 12, 2013 at 02:46:52PM +0800, Ed Greshko wrote:
> First, I am not a Latex user. But decided to try your demo
> file on an F17 system where I installed using yum... I "think" it
> is OK?
>
> [egreshko@f17x ~]$ latex demo.tex
[...]
I think the OP expected it to work w
On 04/12/13 08:09, Rolf Turner wrote:
> On 04/12/2013 01:12 AM, Mike Williams wrote:
>
>
>
>> The texlive that comes with fedora 17 is texlive 2007, the version from the
>> tug link is texlive 2013. On my system I used yum to remove texlive, then
>> downloaded
On Fri, Apr 12, 2013 at 12:09:42PM +1200, Rolf Turner wrote:
> >! Package hypdestopt Error: This package requires pdfTeX in PDF mode.
> >
> >See the hypdestopt package documentation for explanation.
> >Type H for immediate help.
> > ...
> >
> >l.55 }\@ehc
> But powerdot is incompatible with pd
Turner
> On 04/12/2013 01:12 AM, Mike Williams wrote:
>
>
>
>
> The texlive that comes with fedora 17 is texlive 2007, the version from
>> the tug link is texlive 2013. On my system I used yum to remove texlive,
>> then downloaded the .iso from tug, mounted the iso,
On 04/12/2013 01:12 AM, Mike Williams wrote:
The texlive that comes with fedora 17 is texlive 2007, the version
from the tug link is texlive 2013. On my system I used yum to remove
texlive, then downloaded the .iso from tug, mounted the iso, installed
from that and it works fine.
OK. I
On Thu, Apr 11, 2013 at 10:31:17PM +1200, Rolf Turner wrote:
>
> I'm not completely sure if I installed texlive using yum, or if texlive came
> with the initial install of Fedora 17. My vague recollection is that there
> was
> a latex facility that came with Fedora 17 but it
On Thu, 11 Apr 2013 17:46:15 +0300, Susi Lehtola
wrote:
> Don't install stuff manually when things have already been packages.
> Fedora 18 features a complete TeXLive 2012 distribution; you can also
> get it on Fedora 17 by
Except that I think Fedora installs the versions fro
Quoting Rolf Turner :
Under Fedora 17 I recently had problems with running latex on a file that
previously (under Ubuntu) I had no difficulty with. (A while back I had to
switch from Ubuntu to Fedora for reasons that I won't go into here.)
I thought that perhaps I might be able to get r
On Thu, 11 Apr 2013 21:03:23 +1200, Rolf Turner wrote:
>
> Under Fedora 17 I recently had problems with running latex on a file that
> previously (under Ubuntu) I had no difficulty with. (A while back I had to
> switch from Ubuntu to Fedora for reasons that I won't go into here
>
> On 04/11/2013 09:20 PM, Ed Greshko wrote:
>
>> On 04/11/13 17:03, Rolf Turner wrote:
>>
>>> Under Fedora 17 I recently had problems with running latex on a file that
>>> previously (under Ubuntu) I had no difficulty with. (A while back I had
>>>
I'm not completely sure if I installed texlive using yum, or if texlive came
with the initial install of Fedora 17. My vague recollection is that
there was
a latex facility that came with Fedora 17 but it was incomplete, and that
I did indeed do "yum install texlive" to fix
On 04/11/13 17:03, Rolf Turner wrote:
>
> Under Fedora 17 I recently had problems with running latex on a file that
> previously (under Ubuntu) I had no difficulty with. (A while back I had to
> switch from Ubuntu to Fedora for reasons that I won't go into here.)
>
> I
Under Fedora 17 I recently had problems with running latex on a file that
previously (under Ubuntu) I had no difficulty with. (A while back I had to
switch from Ubuntu to Fedora for reasons that I won't go into here.)
I thought that perhaps I might be able to get rid of the flakiness
Steve wrote:
>
> Recently the F17 (x64) install on my Dell XPS 17 isn't waking up from
> the sleep state. I'm not sure if I'm invoking it to go into sleep or
> if its an inactivity induced sleep. Prior to recently, it always woke
> up from sleep without any issues.
>
> Furthermore, once in
Recently the F17 (x64) install on my Dell XPS 17 isn't waking up from
the sleep state. I'm not sure if I'm invoking it to go into sleep or
if its an inactivity induced sleep. Prior to recently, it always woke
up from sleep without any issues.
Furthermore, once in a while when I reset af
Solved.
The correct keyword is pgsql_servers - with a 's' on the end.
Gary
On Tuesday 26 March 2013 11:16:32 Gary Stainburn wrote:
> Hi folks
>
> I'm setting up a new server and trying to configure Exim. For the first
> time I'm trying to use Postgresql with it, so have installed the exim-pgsql
Hi folks
I'm setting up a new server and trying to configure Exim. For the first time
I'm trying to use Postgresql with it, so have installed the exim-pgsql RPM
which silly me thought enabled Postgresql support.
However, I get errors on the
hide pgsql_server=(/tmp/.s.PGSQL_.5432)/exim/exim/
On Fri, Mar 22, 2013 at 13:59:56 +,
Frank Murphy wrote:
I have a swap drive (/dev/sdf 20gb) that is giving some read errors
during boot-up. What would be most suitable options
badblocks -svwfBX -o /boot/badblocks/sdf.log
from the same pc with swap unmounted.
You might try writing over
I have a swap drive (/dev/sdf 20gb) that is giving some read errors
during boot-up. What would be most suitable options
badblocks -svwfBX -o /boot/badblocks/sdf.log
from the same pc with swap unmounted.
--
Regards,
Frank
http//www.frankly3d.com
--
users mailing list
users@lists.fedoraproject.
On 03/20/2013 11:35 PM, Frank Murphy issued this missive:
On Wed, 20 Mar 2013 15:00:30 -0700
Rick Stevens wrote:
"ifconfig eth0 up" does NOT invoke the DHCP client software needed
to get an IP from your DHCP server. The old "ifup eth0" should do
it, or run the dhclient app yourself (as root).
On Wed, 20 Mar 2013 12:18:50 -0700
Joe Zeff wrote:
> If the IP is reserved, why not just set it to a static IP and be
> done with it? I don't know if it would help in this case, but it
> might simplify things. And, while I'm thinking about it, are there
> other machines set up the same way? If
On Wed, 20 Mar 2013 15:00:30 -0700
Rick Stevens wrote:
> "ifconfig eth0 up" does NOT invoke the DHCP client software needed
> to get an IP from your DHCP server. The old "ifup eth0" should do
> it, or run the dhclient app yourself (as root).
>
> # ifconfig eth0 up
> # dhclient eth0
>
On 03/20/2013 12:07 PM, Frank Murphy issued this missive:
Have googled, and done all I can think
NIC works fine with F17-boot disc in rescue mode.
cat5 cables have been changed and work on other nodes.
Box normally gets it's reserved-ip from Dovado router.
Jumbo frames disabled on everything
#
On 03/20/2013 12:07 PM, Frank Murphy wrote:
NIC works fine with F17-boot disc in rescue mode.
cat5 cables have been changed and work on other nodes.
Box normally gets it's reserved-ip from Dovado router.
Jumbo frames disabled on everything
If the IP is reserved, why not just set it to a static
Have googled, and done all I can think
NIC works fine with F17-boot disc in rescue mode.
cat5 cables have been changed and work on other nodes.
Box normally gets it's reserved-ip from Dovado router.
Jumbo frames disabled on everything
# ifconfig eth0 up
# ifconfig
eth0: flags=-28669 mtu 1500
Hello,
Thank you very much for your advice.
I will do it after I will have backed up the machine, ie when I will
have some quiet sometime
Did you test your suggestion?
Thank.
On 3/17/13, Patrick Dupre wrote:
the problem is that the update to fedora 17 failed (probably) because the
/usr
On 3/17/13, Patrick Dupre wrote:
> the problem is that the update to fedora 17 failed (probably) because the
> /usr /usr/lib and /
> partitions need to be on the same partition!
Fedora 17+ supports a separate /usr just fine. It's the separate
/usr/lib that's screwing it
On Tue, Feb 26, 2013 at 2:34 PM, Ed Greshko wrote:
> On 02/26/13 14:18, Amit Karpe wrote:
> >
> >
> > On Mon, Feb 25, 2013 at 1:53 PM, Amit Karpe amitka...@gmail.com>> wrote:
> >
> > 1. I have install Fedora 17 (64 Bit). Now I mount any nfs part
On 02/26/13 14:18, Amit Karpe wrote:
>
>
> On Mon, Feb 25, 2013 at 1:53 PM, Amit Karpe <mailto:amitka...@gmail.com>> wrote:
>
> 1. I have install Fedora 17 (64 Bit). Now I mount any nfs partition.
> # uname -a
> Linux localhost.localdomain 3.3.4-5.fc17.x8
On Mon, Feb 25, 2013 at 1:53 PM, Amit Karpe wrote:
> 1. I have install Fedora 17 (64 Bit). Now I mount any nfs partition.
> # uname -a
> Linux localhost.localdomain 3.3.4-5.fc17.x86_64 #1 SMP Mon May 7 17:29:34
> UTC 2012 x86_64 x86_64 x86_64 GNU/Linux
>
> 2. I have few parti
dit "/boot/grub/grub.conf"
--Greg
I tried using that in Fedora 17, but it did not work for me as the
nvidia driver still complained it could not load its module while the
nouveau driver was active, and I found that the method documented on the
net of rebuilding the initrd with the nvi
On Mon, 2013-02-25 at 07:15 +1100, Stephen Morris wrote:
> I have all sorts of problems installing the
> proprietary nvidia driver from the rpmfusion directories as the install
> does not remove the nouveau driver from the initrd
This has been covered on this list before. You need to add
"rdbla
1. I have install Fedora 17 (64 Bit). Now I mount any nfs partition.
# uname -a
Linux localhost.localdomain 3.3.4-5.fc17.x86_64 #1 SMP Mon May 7 17:29:34
UTC 2012 x86_64 x86_64 x86_64 GNU/Linux
2. I have few partitions, which works without any problem.
But one partition is giving problem
repositories, but does remove it from the initrd of
the kernel installed from the dvd. I have uninstall the repository
kernels and then reinstall them so that I can get to the point of
starting xorg. The nvidia and nouveau drivers cannot coexist, I had the
same problem in fedora 17 as well, but
>
> Just found this
>
> https://bugzilla.redhat.com/show_bug.cgi?id=868584
>
> --
I am going through this bug report. But could not find final solution.
Can I force mount to use nfs2 ??
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://
>
> OK quite a bit of memory available.
>
> Heck, even on my VM (running F18-64) with just over 1GB of memory I have
>
> [root@f18x ~]# modprobe -v nfs
> insmod /lib/modules/3.7.9-201.fc18.x86_64/kernel/fs/fscache/fscache.ko
> insmod
> /lib/modules/3.7.9-201.fc18.x86_64/kernel/net/dns_res
On 02/22/13 17:01, Amit Karpe wrote:
> On Fri, Feb 22, 2013 at 4:50 PM, Ed Greshko wrote:
>> On 02/22/13 16:43, Amit Karpe wrote:
>>> While loading module I got following error:
>>> [root@localhost ~]# modprobe -v nfs
>>> insmod /lib/modules/3.6.11-1.fc17.i686.PAE/kernel/fs/nfs/nfs.ko
>>> ERROR: c
On 02/22/13 17:01, Amit Karpe wrote:
> On Fri, Feb 22, 2013 at 4:50 PM, Ed Greshko wrote:
>> On 02/22/13 16:43, Amit Karpe wrote:
>>> While loading module I got following error:
>>> [root@localhost ~]# modprobe -v nfs
>>> insmod /lib/modules/3.6.11-1.fc17.i686.PAE/kernel/fs/nfs/nfs.ko
>>> ERROR: c
On Fri, Feb 22, 2013 at 4:50 PM, Ed Greshko wrote:
> On 02/22/13 16:43, Amit Karpe wrote:
>> While loading module I got following error:
>> [root@localhost ~]# modprobe -v nfs
>> insmod /lib/modules/3.6.11-1.fc17.i686.PAE/kernel/fs/nfs/nfs.ko
>> ERROR: could not insert 'nfs': Cannot allocate memor
On 02/22/13 16:43, Amit Karpe wrote:
> While loading module I got following error:
> [root@localhost ~]# modprobe -v nfs
> insmod /lib/modules/3.6.11-1.fc17.i686.PAE/kernel/fs/nfs/nfs.ko
> ERROR: could not insert 'nfs': Cannot allocate memory
What does the output of "free" show?
--
From now on,
Hi,
I am facing problem using nfs on Fedora 17.
While mounting nfs partition by following command:
[root@localhost ~]# mount borneo:/home/ /mnt/home -v
mount.nfs: timeout set for Fri Feb 22 16:40:07 2013
mount.nfs: trying text-based options
'vers=4,addr=172.21.123.225,clientaddr=172.21.12
Jim wrote:
F17 > F18
I have finally figured out how to install F18 and saving my existing /home
partition, so as not to loose my home directory.
But I would be Damd to explain how in a email , I would just confuse the H out
of everyone and myself. the guy at Fedora that came up with this instal
F17 > F18
I have finally figured out how to install F18 and saving my existing
/home partition, so as not to loose my home directory.
But I would be Damd to explain how in a email , I would just confuse the
H out of everyone and myself. the guy at Fedora that came up with this
installer, mus
On 02/15/2013 10:45 AM, Rick Stevens wrote:
This is like the eighth time I've seen xulrunner updated without its
requirements being pushed out first. I'm not sure who the maintainer
is, but (s)he needs a spanking.
You are aware, aren't you, that for some people that would be a reward,
not a p
On Sat, 16 Feb 2013 09:59:00 +0800
Ed Greshko wrote:
> Can you be more specific?
Actually this one looks like my problem rather than
a repo error. Ignore the Qt message :-).
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedorapro
1 - 100 of 944 matches
Mail list logo
