On Wed, Dec 16, 2015 at 10:03:46AM +0530, Deepak Shetty wrote:
> Why not provide a image that has root or non-root user with std. passwd ?
> whats the problem with that ?
Security team told us in no uncertain terms to not to. :)
--
Matthew Miller
Fedora Project Leader
On Wed, 16 Dec 2015 09:59:54 +0530
Deepak Shetty wrote:
> On Tue, Dec 15, 2015 at 6:09 PM, Matthew Miller
> wrote:
>
> > On Tue, Dec 15, 2015 at 08:41:30AM +, P J P wrote:
> > > Today in another conversation[1], I received this feedback about
On Mon, 2015-12-14 at 23:30 +0530, Kushal Das wrote:
> Major Hayden did some excellent write up [3] [4] [5] about Networkd
> in Fedora [6].
>
> "Features", and "First" are part of our four foundations. I
> personally think putting Networkd on our cloud images will certainly
> help us to grow the
===
#fedora-meeting-1: cloud_wg
===
Meeting started by kushal at 17:01:15 UTC. The full logs are available
at
http://meetbot.fedoraproject.org/fedora-meeting-1/2015-12-16/cloud_wg.2015-12-16-17.01.log.html
.
Meeting summary
---
*
On Mon, Dec 14, 2015, at 01:00 PM, Kushal Das wrote:
> This email is to resume the discussion on putting Networkd as network
> stack in Fedora Cloud Atomic and base images.
FWIW, my opinion on this from the Atomic Host perspective hasn't really changed
since:
On Wed, Dec 16, 2015 at 09:59:54AM +0530, Deepak Shetty wrote:
> Vagrant is fine, but there are instances where one needs to be as
> close to reality than the abstraction / layering added by Vagrant. I
> would want to use it directly either using the qemu cmd line or
> virsh/virt-* tools which is
On Wed, Dec 16, 2015 at 07:51:05AM +, Chris Murphy wrote:
> It seems to me the easier thing to do is tolerate baking more stuff
> into the images and ISO.
> OK I just rewound this in my head, and said WTS out loud. There's one cloud
> atomic tree, right? So adding a bunch of hardware stuff
#136: vagrant boxes fixups
---+-
Reporter: dustymabe | Owner:
Type: task | Status: new
Priority: normal | Milestone: Future
Component: ---| Resolution:
Keywords: meeting|
On Tue, Dec 15, 2015 at 11:59:41AM -0500, Jonathan Lebon wrote:
> I've also been working on a similar feature for the Atomic
> image (although it should work just fine for the Base images
> as well if we want). Basically, it adds a new boot menu item
> labeled "Developer Mode" (working title ;) ).
On 14/12/15, Matthew Miller wrote:
> On Mon, Dec 14, 2015 at 12:31:45PM -0800, Adam Williamson wrote:
> > The situation is not at all the same; there is no clear expectation
> > that networkd will replace NetworkManager, indeed AFAIK it's been
> > explicitly stated that it won't, because it's not
Successfully booted using 'configfile' and editing the grub.cfg to use
linuxefi/initrdefi instead of linux16 and initrd16...
# bash -x grub2-mkconfig
http://fpaste.org/301941/30720114/
That's a bug. I just don't know whose bug it is. This is definitely a
UEFI system, the CSM is not used
At the grub menu, I hit, c to get to a grub shell, and then use
'configfile' command pointed to /boot/loader.0/grub.cfg - it reads
that configuration file instead of the one on
/boot/efi/EFI/fedora/grub.cfg, and both 23.29 and 23.34 tree menu
entries appear.
Both contain an error, however. They
rpm-ostree entry .conf
http://fpaste.org/301944/45030746/
What translates this file's linux/initrd into either linux16/initrd16
vs linuxefi/initrdefi?
--
Chris Murphy
___
cloud mailing list
cloud@lists.fedoraproject.org
On 12/15/2015 10:58 PM, Kushal Das wrote:
On 14/12/15, Adam Williamson wrote:
On Tue, 2015-12-15 at 01:53 +0530, Kushal Das wrote:
The thing is that it's almost impossible to say "if we just run all X
tests, we can guarantee everything is fine!" in real life, especially
at the level of
14 matches
Mail list logo