I don't know if this a generalize problem; but any of you is getting long
times to actually get into the (Cinnamon) desktop? I had this issue with
old version and I though that was because it was another shell for GNOME
instead of a desktop made with GTK+ libraries from scratch, like it's
supposedly now. Is there a solution (obviously there is), that it doesn't
have the need to hack the code of Cinnamon (I'm not in a rush to learn
up to F20, I used the respective 4 GB full DVD image to install
Fedora, which also contained the XFCE desktop. Now, with F21, there's
a desktop and a server edition, and it seems the full DVD is missing.
Does the desktop edition also contain the XFCE desktop, or do I have
to use any XFCE spin now to get XFCE? And where are all the
development packages and libs, are they still on both editions?
On 25.11.2014 21:49, Paul Bolle wrote:
> On Tue, 2014-11-25 at 21:07 +0100, poma wrote:
>> On 25.11.2014 20:59, Josh Boyer wrote:
>>> Answers can be precise without actually being helpful. Yours tend to
>>> lack context that would allow people to easily understand them. In the
>>> future, it would be more helpful to fill in some of the context and use
>>> words and sentences in communcations instead of just dumping the output
>>> of various commands or linking to random youtube videos.
>> Interpretation is an obstacle to perfection.
> There's no perfection in communication.
> Communication is messy. Communicating in a foreign language is even more
> messy. (It seems English isn't your first language. Dutch is my first
> language). Don't try to be perfectly precise.
> Try to be clear. That's hard enough.
> Paul Bolle
We go perfectly nowhere with this subthread, therefore it is perfect.
Is there an elegant way to install two versions of Fedora at the same
I like to keep the existing version running, while I test/setup new
version, then swap when I'm happy everything is running ok. Previously
I've done with a boot loader like Air-Boot ( http://sourceforge.net/
projects/air-boot/ ) and partitioned my hard drive with
p1 boot1 ( F19)
p2 boot2 ( F20)
/ for F19
/ for F20
Then told the installer to use the relevant /boot to install the
bootloader. However that sort of broke from F18 and I've had to use the
workaround in bug 872826 to get that to work.
Can I just use grub2 ? to manage booting, I guess one version of F20 will
have to be the owner. How will updates work, can they both update the
grub2 config when the kernel is updated ? I've googled around and not
really found any simple solutions. This artificial looks possible, but
seem to require some manual fiddling around https://
I don't think its too much of a mad idea to want to do a staged upgrade
to next version, and I quite like have a clean install to get rid of all
the stuff I've installed just to play with.
- Any suggestions, or link's I haven't found.
Thanks in advance
On 25.11.2014 20:59, Josh Boyer wrote:
> On Tue, Nov 25, 2014 at 08:34:15PM +0100, poma wrote:
>> On 25.11.2014 18:57, Paul Bolle wrote:
>>> On Tue, 2014-11-25 at 15:40 +0100, poma wrote:
>>>> [snip unedited copy from someone's reply]
>>> I assume you removed me from the lists of recipients by accident.
>>>> [PATCH] xprtrdma: add separate Kconfig options for NFSoRDMA client and server support
>>> Yes, that's the patch that ended up as mainline commit 2e8c12e1b765
>>> ("xprtrdma: add separate Kconfig options for NFSoRDMA client and server
>>> support"). I mentioned that commit in my reply. Which was, by the way,
>>> not a unedited chunk of terminal output but an attempt to answer the
>>> question at hand.
>>> Paul Bolle
>> It was a precise answer to Ian, related to kernel versions, man.
> Answers can be precise without actually being helpful. Yours tend to
> lack context that would allow people to easily understand them. In the
> future, it would be more helpful to fill in some of the context and use
> words and sentences in communcations instead of just dumping the output
> of various commands or linking to random youtube videos.
Interpretation is an obstacle to perfection.
On 25.11.2014 18:57, Paul Bolle wrote:
> On Tue, 2014-11-25 at 15:40 +0100, poma wrote:
>> [snip unedited copy from someone's reply]
> I assume you removed me from the lists of recipients by accident.
>> [PATCH] xprtrdma: add separate Kconfig options for NFSoRDMA client and server support
> Yes, that's the patch that ended up as mainline commit 2e8c12e1b765
> ("xprtrdma: add separate Kconfig options for NFSoRDMA client and server
> support"). I mentioned that commit in my reply. Which was, by the way,
> not a unedited chunk of terminal output but an attempt to answer the
> question at hand.
> Paul Bolle
It was a precise answer to Ian, related to kernel versions, man.
>> On 11/24/2014 06:33 PM, jd1008 wrote:
>>> Has anyone been able to run Safari under wine without showstopper
>> Checking the app database at Wine HQ, I find this:
>> Note that the best rating it gets is Silver. If you need more details,
>> you can follow the links on that page to specific reviews.
> This might benefit all who want to use Safari under Linux.
> I downloaded Safari 4.0.4 and it installs and runs flawlessly.
> Thank you Wine Dev and Support Teams.
> Thank you Apple.
Just for clarification, you were able to get Safari 4.0.4 working with
Wine 1.7.30-1? What was the version of Safari you tried before that
On 25.11.2014 16:03, Chuck Lever wrote:
> On Nov 25, 2014, at 9:26 AM, poma <pomidorabelisima(a)gmail.com> wrote:
>> On 25.11.2014 14:29, Josh Boyer wrote:
>>> On Tue, Nov 25, 2014 at 02:12:08PM +0100, Paul Bolle wrote:
>>>> On Tue, 2014-11-25 at 13:40 +0100, poma wrote:
>>>>> On 25.11.2014 11:14, Ian Chapman wrote:
>>>>>> Is anyone successfully running NFS over RDMA on Fedora 20+?
>>>>>> I've edited /etc/sysconfig/nfs and set the the following config paramter.
>>>>>> Upon restarting the nfs server I get the following:
>>>>>> modprobe: FATAL: Module svcrdma not found
>>>>>> /usr/libexec/nfs-utils/scripts/nfs-server.postconfig: line 12: echo:
>>>>>> write error: Protocol not supported
>>>>>> So it looks like the kernel module svcrdma is missing and the last
>>>>>> kernel to have it was 3.11.10-301.fc20. The postconfig script belongs to
>>>>>> Is svcrdma intentionally not built in the current kernels or has it been
>>>>>> replaced by something else?
>>>>> [snip unedited copy from someone's terminal]
>>>> 0) In mainline kernel v3.15 the config option SUNRPC_XPRT_RDMA was split
>>>> in two options: SUNRPC_XPRT_RDMA_CLIENT and SUNRPC_XPRT_RDMA_SERVER. See
>>>> commit 2e8c12e1b765 ("xprtrdma: add separate Kconfig options for
>>>> NFSoRDMA client and server support").
>>>> 1) Fedora 20 first shipped v3.15 in last July (kernel-3.15.3-200.fc20).
>>>> Looking at the git history of the Fedora kernel package I found commit
>>>> commit fd469c7db4e6 ("Linux v3.15.2"). It dropped
>>>> CONFIG_SUNRPC_XPRT_RDMA=m from the config files (as it was useless). It
>>>> set CONFIG_SUNRPC_XPRT_RDMA_CLIENT to 'm' but did not set
>>>> CONFIG_SUNRPC_XPRT_RDMA_SERVER. The commit offers no explanation of this
>>>> choice. Perhaps it was discusses somewhere else.
>>>> 2) A similar commit for Rawhide was 700baa35a69e ("Linux
>>>> v3.14-12042-g69cd9eba3886"), but it doesn't comment on this choice
>>>> 3) Perhaps Justin or Josh, authors of those commits, might recall why
>>>> only CONFIG_SUNRPC_XPRT_RDMA_CLIENT was set.
>>> At the time, server support for NFSoRDMA wasn't in the greatest shape
>>> and we disabled it at the request of the NFS developers.
> The NFS/RDMA server crashed often and there was no identified
> upstream resource to help with it, so it was surgically
> disabled rather than fixed.
>>> I believe this
>>> also matches what wound up in RHEL7.
>>> The NFS developers haven't asked us to turn it back on, so it has stayed
>>> off since.
>> Chuck, what is the current recommendation for 'CONFIG_SUNRPC_XPRT_RDMA_SERVER’?
> The server in 3.17 and later kernels no longer crashes
> As to whether you should re-enable it, here’s full
> As I understand it the NFS/RDMA server-side transport
> effort was defunded after a prototype was merged. It was
> hoped that a production-quality implementation would be
> funded but it never was.
> The code as it stands needs some work, but is operational.
> I use it for NFS/RDMA client work every day, so it is
> getting some exercise.
> Distributions can enable this if they have the resources
> (ie, test and support engineers and RDMA adapters) to test
> and support customer issues. I assume RH/Fedora do, as
> they support client side NFS/RDMA already. But perhaps
> consider it as “tech preview” for your enterprise
> Or they may choose to wait until upstream has changed the
> default setting of CONFIG_SUNRPC_XPRT_RDMA_SERVER.
> Note that community support for NFS/RDMA server-side is
> still best-effort only. We don’t have any designated
> specialists, just a few folks who need the server to work
> for other reasons. We are actively looking for interested
> Upstream bugs can be filed here:
> Chuck Lever