does anyone happen to know whether or not there's a special XF86 key for disabling the laptop touchpad on LXDE ?

so far I've managed to fix the sound controls with XF86AudioLowerVolume et. al.

naaah, what's local thats local ;)

But hes right, vagrant is <3, especially for development machines. You habe a reliable full environment that matches the deploy in the customers server without any docker weirdness and you have the full range of options from your hypervisor available.

And since it supports ansible by default

containers don't have init system

Well, if you want them to have (which you usually only want for very special reasons) they can have one. For example I test my Ansible client repo using containers

Well, if you want them to have (which you usually only want for very special reasons) they can have one. For example I test my Ansible client repo using containers

I know they can have, but it defeats the purpose of containers. They should be slim. But when it's needed I've always went for dumb-init on Alpine

I know they can have, but it defeats the purpose of containers. They should be slim. But when it's needed I've always went for dumb-init on Alpine

It defeats the purpose in case of usual containers, yes. But for CI purpose that's completely fine and still cheaper than a VM

It defeats the purpose in case of usual containers, yes. But for CI purpose that's completely fine and still cheaper than a VM

true ?

for CI you can bloat the container how much you want

Is there any forks of Unity DE available in Fedora? Was the Unity forked? Did Canonical open its source code?

It defeats the purpose in case of usual containers, yes. But for CI purpose that's completely fine and still cheaper than a VM

But still less isolated. And even vms can reach 50-150 mb naked ram usage nowadays with vagrant prepared images.

I gladly pay the tiny plus on storage and cpu usage for vms until docker gets isolation and some other issues right

I gladly pay the tiny plus on storage and cpu usage for vms until docker gets isolation and some other issues right

Isolation? It's already having cgroups and ulimits

pid limit et. al.

you can limit whatever you want lol

https://docs.docker.com/config/containers/resource_constraints/

Isolation? It's already having cgroups and ulimits

shared kernel, DDOS against local kernel resources, any user that is root in a container and breaks out is root on the host...

If you use a kernel exploit in a container - lucky you the hosts' compromised.

shared kernel, DDOS against local kernel resources, any user that is root in a container and breaks out is root on the host...

container starts with all capabilities dropped

it's default configuration

you can also force it to start by default under nobody:nogroup

fork bomb is easily mitigated with pids_limit

container starts with all capabilities dropped

that is still open to kernel exploits

fork bomb is easily mitigated with pids_limit

doesnt stop you from hammering /abusing ram/i/o

well if we go that way, inside a VM what stops you from running Assembly code to break everything ?

Well, of course VMs are still beyond containers when it comes to isolation

The attack surface of a VM (from inside) is way smaller than the attack surface of a container. But as always the important question is: what do you want to achieve and what do you want to protect yourself from

In most cases containers are easier to maintain, more lightweight and right now, better to orchestrate. This may changes in future, may not, we will see. If containers to the job, they are fine. If I want a high secure setup the actually safest way is to combine both technologies

The hypervisor in most cases.

In most cases containers are easier to maintain, more lightweight and right now, better to orchestrate. This may changes in future, may not, we will see. If containers to the job, they are fine. If I want a high secure setup the actually safest way is to combine both technologies

vagrant + ansible makes vms easier to move around.

Even more so with ovirt. zero dowtime, triple or quadruple backed storage on gluster...

Even more so with ovirt. zero dowtime, triple or quadruple backed storage on gluster...

Ovirt and zero downtime *hems* but let's stay serious. Yes, it's possible and with K8s coming to ovirt it becomes easier to orchestrate the VMs in future. But to bring up your favorite topic: VMs have the ugly problem that not everyone is using KVM. Instead they break their kernels using virtualbox and other nonsense. When it comes to container, people use docker. Some older generation uses chroot but they are almost gone. From a UX perspective it's a huge benefit. Also from the dev perspective Docker feels a bit more natural than ansible and vagrant. With docker hub you have a gigantic source of (mostly shitty) examples and solutions. The reason why containers are currently winning is not that they are a perfect solution or from a security perspective better in any way. The reason is the tooling and UX which is more intuitive than the tooling that exist before. There were tons of container technology around since the late 90s. VM actually came later. But in the past few years containers are ruling the market more and more. And not only because of marketing. If you want the world to switch back to VMs, you need nice tooling, not "but we already…" arguments. As they are all known to everyone.

Ovirt and zero downtime *hems* but let's stay serious. Yes, it's possible and with K8s coming to ovirt it becomes easier to orchestrate the VMs in future. But to bring up your favorite topic: VMs have the ugly problem that not everyone is using KVM. Instead they break their kernels using virtualbox and other nonsense. When it comes to container, people use docker. Some older generation uses chroot but they are almost gone. From a UX perspective it's a huge benefit. Also from the dev perspective Docker feels a bit more natural than ansible and vagrant. With docker hub you have a gigantic source of (mostly shitty) examples and solutions. The reason why containers are currently winning is not that they are a perfect solution or from a security perspective better in any way. The reason is the tooling and UX which is more intuitive than the tooling that exist before. There were tons of container technology around since the late 90s. VM actually came later. But in the past few years containers are ruling the market more and more. And not only because of marketing. If you want the world to switch back to VMs, you need nice tooling, not "but we already…" arguments. As they are all known to everyone.

gigantic source of (mostly shitty) examples true that ?

truth be told, Docker was very fast adopted because it did the job quicker

Also docker images are more universal than vagrant images. If you don't believe me, work on KVM and talk to a Windows user using VMware fusion :D

Also docker images are more universal than vagrant images. If you don't believe me, work on KVM and talk to a Windows user using VMware fusion :D

Windows sucks anyway ?

in many considerations

Also docker images are more universal than vagrant images. If you don't believe me, work on KVM and talk to a Windows user using VMware fusion :D

Wrong. Centos base vm runs on: vmware esxi/vmworkstation/player kvm xen aws hyper-v and more And can be assigned the same ip, amount of ram, virtual cpus and more across all of these.

Plus then follows ansible deployment against the centos base which just doesnt care where its run on. And the vagrant delta rsync works across hypervisors and can even run on remote machines.

plus qemu-img is able to convert to and from every major vhdd format since years.

plus qemu-img is able to convert to and from every major vhdd format since years.

The point why you use containers is because they provide images. images you run preferly in read-only mode with a few temp filesystems. And converting them is exactly what you don't want to do. With this we are again at the point that you want simply tooling. 1 command and it works. Not more, not less ^^

and in best case, the same command on all machines ^^

And yes, you can wrap it into a shellscript but it doesn't really solve the problem

same for vagrant. 1 command.

vagrant up on any machine that has any hypervisor installed.

And you will end up with the same end result, same ansible-deployed machine with even the same ip if needed

My personal experience with vagrant was a bit different, but that's not the point. Let's say it's like it is, what did vagrant wrong to not be as popular as docker is?

why my fedora can not start

i just wanna my libinput startup

Where have you put that, why do you need libinput to start seperately, what calls that, is it maroed executable?

i need libinput startup , cuz i wanna my touchpad support multi finger when i entry my system

on my terminal it work well

but when i put this command into rc.local

it just wait this command finished

but when i put this command into rc.local

rc.local is not supported.

You are on a systemd system, rc.local is blissfully ignored.

what can i do

what can i do

Either add it into your users crontab as @reboot script or make a systemd unit

And why does libinput not come with multitouch by default? I didnt need to change anything for it to be supportd on my craplet

it's libinput-gesture

i don't know.

ERROR: S client not available

my touchpad need it to support multi finger gesture

my touchpad need it to support multi finger gesture

not in GNOME under wayland, right?

i guess i fixed it

right in ~/.zshrc

in gnome-xorg

nice

anyone wanna watch vitoria secure show

chinese version

How do you close Telegram Desktop so it doesn't run in the background? Clicking on X seems to somehow minimise it somewhere. ?

How do you close Telegram Desktop so it doesn't run in the background? Clicking on X seems to somehow minimise it somewhere. ?

installing the notification bar back trough an extension, rightclick, quit

installing the notification bar back trough an extension, rightclick, quit

Which one is that?

Where did you get that icon from? Mine doesn't show quit.

gnome extension

dash to dock

dash to dock

OK, thanks. Really weird. I need to install an extension to close an app. ?

or u can

kill it by terminal

at fedora 26

you can see a dash at left bottom

kill it by terminal

Yeah but this is not very user friendly...

it show all backend tasks

on feodra 27, gnome delete it

i dont know why

on feodra 27, gnome delete it

I am going to research a bit, thanks!

like this

Just disable tray icon and settings. Telegram Desktop will quit on main window close.