That's why some people need to use UPS while the thunderstorms is on, or make a ground of house

Holy shit

sparking on wallsocket

Maybe Ill do that scan later

good afternoon, humans

good afternoon, humans

haaii

Let the file system check run

ty

sparking on wallsocket

I would definitely invest in a surge protector or a UPS for the future.

I would definitely invest in a surge protector or a UPS for the future.

srry…actually it was sparking on the surge protector…

srry…actually it was sparking on the surge protector…

That doesnt sound like a good surge protector

Try grounding, if you can make it

http://thehackernews.com/2017/01/bitcoin-price.html?m=1 A real new years blast...

nice growthrate

I was just watching YouTube and the thunderstorms shutdown all my electronic devices

Yes, as @Tobias4X said, the sudden shutdown corrupted your filesystem. Happened to me too (different reasons though). You may want to use a live and memory SD card or USB stick to see if you can recover your files from there. But the filesystem itself is... well, buggered.

sparking on wallsocket

Honestly, I would check your electrical installation. Not only because of your computer but because of your own safety.

guys what do you think about flatpak?

I'm interested in this too ^

guys what do you think about flatpak?

Useless piece of crap.

Useless piece of crap.

Why?

how's it compare to snap

Useless piece of crap.

not entirely, its got pros and cons like everything else

Why?

Windows way with runtimes and DLL Hell.

Really?

https://en.wikipedia.org/wiki/DLL_Hell

personally between flatpak and snappy I'd trust flatpak more, just because canonical have nothing to do with it. I like things that are built to be distro agnostic and not built for ubuntu first and then maybe everything else second.

I know you can run snappy on other distros but its not without issue, like in Fedora they tell you to disable selinux for it to work

which is just madness

MADNESS

is there a workaround to make it work with selinux?

Flatpak can be used only for proprietary packages. All other must be dynamically linked and packaged as RPM.

it's a shame really, if it's not compatible with selinux

not to my knowledge but I haven't really looked into it tbh. That is canonicals advice btw, so if they couldn't get it to work without disabling selinux then god knows.

both systems have the capacity to make everything bloated when shipping with duplicates of a dependency you already have installed, but they're working on that problem and its still early days. Theres no reason that several key applications shouldn't be distributed in a sandboxed environment though

things like web browsers and messengers become more more secure

which tbh, I think is worth it for the sake of a few duplicate dependencies in the early days

I'm not saying everything will be flatpak/snappy, far from it. RPMs and DEBs aren't going anywhere, sandboxed distribution is not a replacement for them

its just a more secure way and in some cases easier way of running certain applications

ones that either require libraries not available on all distros, or libraries that are just weird and obscure, or applications that are a high security risk like a web browser.

on paper they also make it easier for developers to package up their applications for Linux at large since they only have to make one package.

which can only be a good thing for all Linux users, and especially for Fedora

Sounds good. I'll probably install a flatpack browser for the sandbox feature then

which tbh, I think is worth it for the sake of a few duplicate dependencies in the early days

I think it would be much more than "a few duplicate dependencies" But it always a good idea to handle distro independent apps. I'm not sure if it's worth it

which can only be a good thing for all Linux users, and especially for Fedora

Flatpak/snap designed to be universal packages between different distributions. But maintainers will continue build their own packages with special flags/patches, etc.

ones that either require libraries not available on all distros, or libraries that are just weird and obscure, or applications that are a high security risk like a web browser.

Just use noexec mount flag on /home and /tmp (/var/tmp) and forget about malwares. ?

ERROR: S client not available

That's a good thing. Usually there's just a debian or fedora based package on website. So having this would be awesome

Sandboxed browser cannot even save files to desktop. Useless crap.

It's alright. We could wget that

That's a good thing. Usually there's just a debian or fedora based package on website. So having this would be awesome

You *MUST* install packages only from your distro repositories!

You *MUST* install packages only from your distro repositories!

I don't remember how many times I broke this rules

It's alright. We could wget that

No. This is not OK. Fedora is not Android.

tfw my pc is a botnet

I think it would be much more than "a few duplicate dependencies" But it always a good idea to handle distro independent apps. I'm not sure if it's worth it

That would really depend on how many applications you installed with it I guess. But like I said there are pros and cons, the cons don't necessarily negate the pros in most cases imo. The pros don't necessarily negate the cons in certain circumstances either. It depends on your priorities with your own system.

tfw my pc is a botnet

lol ?

That would really depend on how many applications you installed with it I guess. But like I said there are pros and cons, the cons don't necessarily negate the pros in most cases imo. The pros don't necessarily negate the cons in certain circumstances either. It depends on your priorities with your own system.

Openssl will be shipped with almost all Flatpak packages and when new vulnerability will be found, maintainers will need to rebuild not just openssl package, but all this FP packages. This is too bad.

so there's only one "true" way to make apps distro independent and it is a source code right?

That would really depend on how many applications you installed with it I guess. But like I said there are pros and cons, the cons don't necessarily negate the pros in most cases imo. The pros don't necessarily negate the cons in certain circumstances either. It depends on your priorities with your own system.

For example i would like to use flatpak like dnf. Every app should be installed from it

Openssl will be shipped with almost all Flatpak packages and when new vulnerability will be found, maintainers will need to rebuild not just openssl package, but all this FP packages. This is too bad.

no, it is part of "runtime"

Flatpak/snap designed to be universal packages between different distributions. But maintainers will continue build their own packages with special flags/patches, etc.

aye the package mainteners will continue to knock 'em together. But I was referring more to overcoming the hurdles for devs looking to distribute their applications or games on Linux for the first time. A ubiquitous package system makes that introduction a little easier rather than them having to learn about RPMs and DEBS and why their are two, and who package maintainers are, which may or may not be application to them if what they are looking to release is open source or not.

Openssl will be shipped with almost all Flatpak packages and when new vulnerability will be found, maintainers will need to rebuild not just openssl package, but all this FP packages. This is too bad.

btw, this is how Go and Rust works ;)

since they are compiling statically

I'm sure both flatpak and snappy are capable of using libraries installed on the system itself instead of the ones that are shipped

I'm sure both flatpak and snappy are capable of using libraries installed on the system itself instead of the ones that are shipped

nope

that's against concept

so they lumped everything in one package? The filesize will be significant I'd imagine.

I'm not sure but I think that the flatpak runtime can incorporate libraries from the host system, and you don't have to bundle libraries in with the application itself