stop e-mail
by Emil Stefanov
--
Поздрави
Емил Стефанов
Best Regards
Emil Stefanov
11 years, 6 months
About 'cost' in repo conf?
by Sergio
In the yum.conf manual is:
"cost: relative cost of accessing this repository. Useful for weighing one repo's packages as greater/less than any other. defaults to 1000"
At first I thought I could use that to set a repo priority but it doesn't work (I set cost to both >1000 and <1000 and ran 'yum clean all' after any change to check). The latest version of a package is offered regardless of those settings.
So that 'cost' setting is only for packages of the same version in different repos?
I know there's a priority plugin for yum and I'll use it.
Best regards.
11 years, 6 months
Re: [Lxc-users] [systemd-devel] Unable to run systemd in an LXC / cgroup container.
by Michael H. Warfield
On Mon, 2012-10-22 at 09:06 +0100, John wrote:
> On 22/10/12 03:06, Michael H. Warfield wrote:
> > On Mon, 2012-10-22 at 02:53 +0200, Kay Sievers wrote:
> >> On Sun, Oct 21, 2012 at 11:25 PM, Michael H. Warfield <mhw(a)wittsend.com> wrote:
> >>> This is being directed to the systemd-devel community but I'm cc'ing the
> >>> lxc-users community and the Fedora community on this for their input as
> >>> well. I know it's not always good to cross post between multiple lists
> >>> but this is of interest to all three communities who may have valuable
> >>> input.
> >>>
> >>> I'm new to this particular list, just having joined after tracking a
> >>> problem down to some systemd internals...
> >>>
> >>> Several people over the last year or two on the lxc-users list have been
> >>> discussions trying to run certain distros (notably Fedora 16 and above,
> >>> recent Arch Linux and possibly others) in LXC containers, virualizing
> >>> entire servers this way. This is very similar to Virtuoso / OpenVZ only
> >>> it's using the native Linux cgroups for the containers (primary reason I
> >>> dumped OpenVZ was to avoid their custom patched kernels). These recent
> >>> distros have switched to systemd for the main init process and this has
> >>> proven to be disastrous for those of us using LXC and trying to install
> >>> or update our containers.
> >>>
> >>> To put it bluntly, it doesn't work and causes all sorts of problems on
> >>> the host.
> >>>
> >>> To summarize the problem... The LXC startup binary sets up various
> >>> things for /dev and /dev/pts for the container to run properly and this
> >>> works perfectly fine for SystemV start-up scripts and/or Upstart.
> >>> Unfortunately, systemd has mounts of devtmpfs on /dev and devpts
> >>> on /dev/pts which then break things horribly. This is because the
> >>> kernel currently lacks namespaces for devices and won't for some time to
> >>> come (in design). When devtmpfs gets mounted over top of /dev in the
> >>> container, it then hijacks the hosts console tty and several other
> >>> devices which had been set up through bind mounts by LXC and should have
> >>> been LEFT ALONE.
> >>>
> >>> Yes! I recognize that this problem with devtmpfs and lack of namespaces
> >>> is a potential security problem anyways that could (and does) cause
> >>> serious container-to-host problems. We're just not going to get that
> >>> fixed right away in the linux cgroups and namespaces.
> >>>
> >>> How do we work around this problem in systemd where it has hard coded
> >>> mounts in the binary that we can't override or configure? Or is it
> >>> there and I'm just missing it trying to examine the sources? That's how
> >>> I found where the problem lay.
> >> As a first step, this probably explains most of it:
> >> http://www.freedesktop.org/wiki/Software/systemd/ContainerInterface
> > A very long ways, yeah. That looks like it could be just what we've
> > been looking for. Just gotta figure out how to set that environment
> > variable but that's up to a couple of others to comment on in the
> > lxc-users list. Then we'll see where we go from there.
> >
> > Many thanks!
> >
> >> Kay
> > Regards,
> > Mike
> >
>
> I've just performed a very quick check on my Arch Linux system here.
>
> on host (running systemd):
> # cat /proc/1/environ
> TERM=linuxRD_TIMESTAMP=
>
> In a container (running sysvinit):
> # cat /proc/1/environ
> STY=623.systemd-lithiumTERM=screenTERMCAP=SC|screen|VT 100/ANSI X3.64
> virtual terminal:\
> :DO=\E[%dB:LE=\E[%dD:RI=\E[%dC:UP=\E[%dA:bs:bt=\E[Z:\
> :cd=\E[J:ce=\E[K:cl=\E[H\E[J:cm=\E[%i%d;%dH:ct=\E[3g:\
> :do=^J:nd=\E[C:pt:rc=\E8:rs=\Ec:sc=\E7:st=\EH:up=\EM:\
> :le=^H:bl=^G:cr=^M:it#8:ho=\E[H:nw=\EE:ta=^I:is=\E)0:\
> :li#24:co#80:am:xn:xv:LP:sr=\EM:al=\E[L:AL=\E[%dL:\
> :cs=\E[%i%d;%dr:dl=\E[M:DL=\E[%dM:dc=\E[P:DC=\E[%dP:\
> :im=\E[4h:ei=\E[4l:mi:IC=\E[%d@:ks=\E[?1h\E=:\
> :ke=\E[?1l\E>:vi=\E[?25l:ve=\E[34h\E[?25h:vs=\E[34l:\
> :ti=\E[?1049h:te=\E[?1049l:k0=\E[10~:k1=\EOP:k2=\EOQ:\
> :k3=\EOR:k4=\EOS:k5=\E[15~:k6=\E[17~:k7=\E[18~:\
> :k8=\E[19~:k9=\E[20~:k;=\E[21~:F1=\E[23~:F2=\E[24~:\
> :kh=\E[1~:@1=\E[1~:kH=\E[4~:@7=\E[4~:kN=\E[6~:kP=\E[5~:\
> :kI=\E[2~:kD=\E[3~:ku=\EOA:kd=\EOB:kr=\EOC:kl=\EOD:WINDOW=0SHELL=/bin/shPATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/binLANG=en_GB.UTF-8container=lxc
> So it looks like that "container" environment variable is already set on
> PID1
Yeah, I saw that myself last night. Testing that out and it's still not
working here (although it doesn't seem to be grabbing the host console
now) if I use systemd but upstart fires right up and I see that
container variable set. Looked like a number of mounts listed on that
wiki page. Maybe something is missing. Right now it's just hanging
trying to start the container and, when I subsequently try to shut the
container down it results in a hung resource and it can't delete the
cgroups directory because it's busy. Only thing I did was change the
link to /sbin/init from upstart to systemd and it's now dead and I'll
have to reboot the host to free the resource. :-P
> Regards,
> John
Regards,
Mike
--
Michael H. Warfield (AI4NB) | (770) 985-6132 | mhw(a)WittsEnd.com
/\/\|=mhw=|\/\/ | (678) 463-0932 | http://www.wittsend.com/mhw/
NIC whois: MHW9 | An optimist believes we live in the best of all
PGP Key: 0x674627FF | possible worlds. A pessimist is sure of it!
11 years, 6 months
Whatever happened to Wayland?
by Junayeed Ahnaf
Well, Back in 2010 I heard f15 will feature experimental wayland support (from Alan Jackson AKA ajax). Anyone knows what's the latest update on that issue? Will we ever gonna see wayland replacing X?
Junayeed Ahnaf Nirjhor
11 years, 6 months
RE:Re: Javascript problem Fedora 16
by Roger
------------------------------------------
From: Reindl Harald <h.reindl(a)thelounge.net>
To: users(a)lists.fedoraproject.org;
CC: arelem(a)bigpond.com;
Subject: Re: Javascript problem Fedora 16
Am 22.10.2012 11:13, schrieb Roger:
> I do hope someone can help me here.
> I am learning Ruby on Rails.
> It requires javascript to be installed for both Firefox and Chromium browsers.
>
> Following the instructions at http://www.java.com/en/download/help/linux_x64rpm_install.xml
> jre installed,
> made link sudo ln -s /usr/java/jre1.6.0_07/plugin/i386/ns7/libjavaplugin_oji.so
> /usr/lib/mozilla/plugins/libjavaplugin.so
>
> Restarted firefox but it does not find jre.
> I have <Enable Javascript> enabled in preferences.
> Still get Ruby on Rails ExecJS::RuntimeError.
>
> Can someone instruct me in what to do to get jre working on firefox and Chromium in Fedora 16 please.
> I have also installed as per instructions at: http://www.java.com/en/download/help/linux_x64_install.xml This also
> fails, it appears to be only an upgrade
first: JAVA != JAVASCRIPT - REALLY!
why do you not try the openjdk which starting with JDK7 is
the reference-implementation before mangling with third
party software outside the RPMDB and taint your system?
this is not windows where the frist step is download
something manually from the internet
F16: yum install java-1.7.0-openjdk icedtea-web
F17: yum install java-1.6.0-openjdk icedtea-web
however, i do not know how the rpm-install behaves after manual
dealing with symlinks, without after install the packages all
is working out of the box
Thanks Reindl.
I know that java and javascript are not the same, I thought jre was needed.
Did not know about yum install java-1.7.0-openjdk icedtea-web
I googled install javascript fedora16 for every avenue I could think of but openjdk did not appear otherwise I may have remembered it.
Roger
11 years, 6 months
f17 no video signal on nVidia 8800
by Rafnews
Hi,
i've just downloaded F17 and i tried to install it on my computer x86
having a nVidia 8800 GT video card.
after seeing only the logo at boot process, now everything i can see is a
black screen :( and the Led of my monitor is blinking so it means no video
signal.
is there any compatibility issue with f17 and nvidia 8800 ?
thank
--
Alain
-----------------------------------------------------------
Windows 7 x64 / Fedora 17x64
MySQL 5.x
Apache 2.5.2
PHP 5.x
11 years, 6 months
Re: [systemd-devel] Unable to run systemd in an LXC / cgroup container.
by Michael H. Warfield
On Mon, 2012-10-22 at 02:53 +0200, Kay Sievers wrote:
> On Sun, Oct 21, 2012 at 11:25 PM, Michael H. Warfield <mhw(a)wittsend.com> wrote:
> > This is being directed to the systemd-devel community but I'm cc'ing the
> > lxc-users community and the Fedora community on this for their input as
> > well. I know it's not always good to cross post between multiple lists
> > but this is of interest to all three communities who may have valuable
> > input.
> >
> > I'm new to this particular list, just having joined after tracking a
> > problem down to some systemd internals...
> >
> > Several people over the last year or two on the lxc-users list have been
> > discussions trying to run certain distros (notably Fedora 16 and above,
> > recent Arch Linux and possibly others) in LXC containers, virualizing
> > entire servers this way. This is very similar to Virtuoso / OpenVZ only
> > it's using the native Linux cgroups for the containers (primary reason I
> > dumped OpenVZ was to avoid their custom patched kernels). These recent
> > distros have switched to systemd for the main init process and this has
> > proven to be disastrous for those of us using LXC and trying to install
> > or update our containers.
> >
> > To put it bluntly, it doesn't work and causes all sorts of problems on
> > the host.
> >
> > To summarize the problem... The LXC startup binary sets up various
> > things for /dev and /dev/pts for the container to run properly and this
> > works perfectly fine for SystemV start-up scripts and/or Upstart.
> > Unfortunately, systemd has mounts of devtmpfs on /dev and devpts
> > on /dev/pts which then break things horribly. This is because the
> > kernel currently lacks namespaces for devices and won't for some time to
> > come (in design). When devtmpfs gets mounted over top of /dev in the
> > container, it then hijacks the hosts console tty and several other
> > devices which had been set up through bind mounts by LXC and should have
> > been LEFT ALONE.
> >
> > Yes! I recognize that this problem with devtmpfs and lack of namespaces
> > is a potential security problem anyways that could (and does) cause
> > serious container-to-host problems. We're just not going to get that
> > fixed right away in the linux cgroups and namespaces.
> >
> > How do we work around this problem in systemd where it has hard coded
> > mounts in the binary that we can't override or configure? Or is it
> > there and I'm just missing it trying to examine the sources? That's how
> > I found where the problem lay.
> As a first step, this probably explains most of it:
> http://www.freedesktop.org/wiki/Software/systemd/ContainerInterface
A very long ways, yeah. That looks like it could be just what we've
been looking for. Just gotta figure out how to set that environment
variable but that's up to a couple of others to comment on in the
lxc-users list. Then we'll see where we go from there.
Many thanks!
> Kay
Regards,
Mike
--
Michael H. Warfield (AI4NB) | (770) 985-6132 | mhw(a)WittsEnd.com
/\/\|=mhw=|\/\/ | (678) 463-0932 | http://www.wittsend.com/mhw/
NIC whois: MHW9 | An optimist believes we live in the best of all
PGP Key: 0x674627FF | possible worlds. A pessimist is sure of it!
11 years, 6 months
Unable to run systemd in an LXC / cgroup container.
by Michael H. Warfield
Hello,
This is being directed to the systemd-devel community but I'm cc'ing the
lxc-users community and the Fedora community on this for their input as
well. I know it's not always good to cross post between multiple lists
but this is of interest to all three communities who may have valuable
input.
I'm new to this particular list, just having joined after tracking a
problem down to some systemd internals...
Several people over the last year or two on the lxc-users list have been
discussions trying to run certain distros (notably Fedora 16 and above,
recent Arch Linux and possibly others) in LXC containers, virualizing
entire servers this way. This is very similar to Virtuoso / OpenVZ only
it's using the native Linux cgroups for the containers (primary reason I
dumped OpenVZ was to avoid their custom patched kernels). These recent
distros have switched to systemd for the main init process and this has
proven to be disastrous for those of us using LXC and trying to install
or update our containers.
To put it bluntly, it doesn't work and causes all sorts of problems on
the host.
To summarize the problem... The LXC startup binary sets up various
things for /dev and /dev/pts for the container to run properly and this
works perfectly fine for SystemV start-up scripts and/or Upstart.
Unfortunately, systemd has mounts of devtmpfs on /dev and devpts
on /dev/pts which then break things horribly. This is because the
kernel currently lacks namespaces for devices and won't for some time to
come (in design). When devtmpfs gets mounted over top of /dev in the
container, it then hijacks the hosts console tty and several other
devices which had been set up through bind mounts by LXC and should have
been LEFT ALONE.
Yes! I recognize that this problem with devtmpfs and lack of namespaces
is a potential security problem anyways that could (and does) cause
serious container-to-host problems. We're just not going to get that
fixed right away in the linux cgroups and namespaces.
How do we work around this problem in systemd where it has hard coded
mounts in the binary that we can't override or configure? Or is it
there and I'm just missing it trying to examine the sources? That's how
I found where the problem lay.
Regards,
Mike
--
Michael H. Warfield (AI4NB) | (770) 985-6132 | mhw(a)WittsEnd.com
/\/\|=mhw=|\/\/ | (678) 463-0932 | http://www.wittsend.com/mhw/
NIC whois: MHW9 | An optimist believes we live in the best of all
PGP Key: 0x674627FF | possible worlds. A pessimist is sure of it!
11 years, 6 months