Greetings, all!
Tomorrow (or today for those of you not in North America) will be the first
Atomic Testday! The Fedora Atomic host is a new image designed to securely and
easily run Docker containers - all based on Project Atomic [0]. Because it's
new ground, testing is required for a successful r
Hi all,
I am having an issue getting F21 to dual boot with Windows 7 on
an EFI
system.
The first thing I did was to install Windows 7. This worked fine
and had
no issues.
Then I installed F21 from a LiveUSB. After some hickups, which
have now
>>
On Wed, Nov 19, 2014 at 2:29 PM, Bidski wrote:
>>> Hi all,
>>>
>>> I am having an issue getting F21 to dual boot with Windows 7 on an EFI
>>> system.
>>>
>>> The first thing I did was to install Windows 7. This worked fine and had
>>> no issues.
>>>
>>> Then I installed F21 from a LiveUSB. After s
>> Hi all,
>>
>> I am having an issue getting F21 to dual boot with Windows 7 on an
EFI
>> system.
>>
>> The first thing I did was to install Windows 7. This worked fine
and had
>> no issues.
>>
>> Then I installed F21 from a LiveUSB. After some hickups, which
have now
>> been resolved, F2
On 11/19/2014 12:38 PM, drago01 wrote:
> On Wed, Nov 19, 2014 at 6:19 PM, Daniel J Walsh wrote:
>> On 11/19/2014 09:16 AM, Paul Knox-Kennedy wrote:
>>> On a clean installation built from
>>> Fedora-Live-Workstation-x86_64-21_Beta-4.iso, I installed mongodb-server
>>> but it failed to start due to
==
#fedora-blocker-review: F21-blocker-review
==
Meeting started by pschindl at 16:03:55 UTC. The full logs are available
at
http://meetbot.fedoraproject.org/fedora-blocker-review/2014-11-19/f21-blocker-review.2014-11
On Tue, Nov 18, 2014 at 10:18 PM, Bidski wrote:
> Hi all,
>
> I am having an issue getting F21 to dual boot with Windows 7 on an EFI
> system.
>
> The first thing I did was to install Windows 7. This worked fine and had
> no issues.
>
> Then I installed F21 from a LiveUSB. After some hickups, whi
On Wed, Nov 19, 2014 at 6:19 PM, Daniel J Walsh wrote:
>
> On 11/19/2014 09:16 AM, Paul Knox-Kennedy wrote:
>> On a clean installation built from
>> Fedora-Live-Workstation-x86_64-21_Beta-4.iso, I installed mongodb-server
>> but it failed to start due to selinux: "SELinux is preventing mongod
>> f
On 11/19/2014 09:16 AM, Paul Knox-Kennedy wrote:
> On a clean installation built from
> Fedora-Live-Workstation-x86_64-21_Beta-4.iso, I installed mongodb-server
> but it failed to start due to selinux: "SELinux is preventing mongod
> from name_bind access on the tcp_socket port 27017."
>
> Followi
The following Fedora 20 Security updates need testing:
Age URL
55
https://admin.fedoraproject.org/updates/FEDORA-2014-11430/ca-certificates-2014.2.1-1.1.fc20
47
https://admin.fedoraproject.org/updates/FEDORA-2014-11969/krb5-1.11.5-16.fc20
38
https://admin.fedoraproject.org/updates/FED
The following Fedora 19 Security updates need testing:
Age URL
389
https://admin.fedoraproject.org/updates/FEDORA-2013-19963/openstack-glance-2013.1.4-1.fc19
201 https://admin.fedoraproject.org/updates/FEDORA-2014-5896/nrpe-2.15-2.fc19
152
https://admin.fedoraproject.org/updates/FEDORA-20
Hello all,
Did a fresh install of Fedora 21 beta via boot.iso (essentially, so not a
Workstation flavour).
Transferred my F20 configuration over, to the best of my ability, this involved:
- removing /etc/sysconfig/network-scripts/ifcfg-* and moving my networking to
be controlled by NetworkManag
On a clean installation built from
Fedora-Live-Workstation-x86_64-21_Beta-4.iso, I installed mongodb-server
but it failed to start due to selinux: "SELinux is preventing mongod
from name_bind access on the tcp_socket port 27017."
Following the selinux instructions from the journal resolves this:
#
I just rebooted and the boot process stopped on this dracut error on the
newest kernel, 3.17-3-300:
dracut-initqueue[271]: Warning: Cancelling resume operation. Device not
found
I was able to boot into the older 3.17-2-300 kernel
uname -a
Linux localhost.localdomain 3.17.2-300.fc21.x86_64 #1 SMP
On Wed, 2014-11-19 at 07:37 -0500, Gene Czarcinski wrote:
> Well, I am sure it is not a show stopper but tracker is going to be a
> royal PITA for some users.
>
> In Fedora 20 we have tracker-0.16.5-1.fc20.x86_64 and in Fedora 21 it
> is tracker-1.2.4-3.fc21.x86_64. That difference in version/rel
Well, I am sure it is not a show stopper but tracker is going to be a
royal PITA for some users.
In Fedora 20 we have tracker-0.16.5-1.fc20.x86_64 and in Fedora 21 it is
tracker-1.2.4-3.fc21.x86_64. That difference in version/release means
that the tracker developer has been very busy adding
Compose started at Wed Nov 19 07:15:02 UTC 2014
Broken deps for armhfp
--
[audtty]
audtty-0.1.12-9.fc20.armv7hl requires libaudclient.so.2
[authhub]
authhub-0.1.2-3.fc19.armv7hl requires libjson.so.0
[avro]
avro-mapred-
Compose started at Wed Nov 19 05:15:02 UTC 2014
Broken deps for i386
--
[3Depict]
3Depict-0.0.16-3.fc22.i686 requires libmgl.so.7.2.0
[Sprog]
Sprog-0.14-27.fc20.noarch requires perl(:MODULE_COMPAT_5.18.0)
[audtty]
audtt
Hi,
I don't know, if my comment is useful for You. I always have an running Windows
system, XP, 8.1. To get both system with F21 in a bootlist, in my case F12
while running through bios, I have to whitelist my current F21. In my case I
think this is hardware dependency.
Kind Regards
--
19 matches
Mail list logo
