General Linux Chat and Small Questions v. I broke my Arch Install
6,886 replies, posted
[QUOTE=danharibo;45298577][url=http://www.maartenbaert.be/simplescreenrecorder/live-streaming/]SimpleScreenRecorder can be used to stream[/url] as well, I haven't tried it myself but I've seen other use it.[/QUOTE]
holy shit son, how did i miss this
it's even already packaged for opensuse i mean damn
I don't understand. It says it's faster than ffmpeg, but then it says it uses ffmpeg libraries?
I wish ffmpeg had OpenGL recording, it'd beat x11grab by far.
Oh my lord E19 is so smooooooooth. so much smoother than E18/E17. And Steam seems to act a little bit better.
Now if only there was a Numix port.
[QUOTE=Little Donny;45302062]holy shit son, how did i miss this
it's even already packaged for opensuse i mean damn[/QUOTE]
holy crap it kinda sorta works
[url]http://www.twitch.tv/donany[/url]
[QUOTE=Little Donny;45302824]holy crap it kinda sorta works
[url]http://www.twitch.tv/donany[/url][/QUOTE]
bye froh :c
i should stream some when that server actually has people on it
[quote]Hi everyone!
It's time to summarize where we are with Fedora 21 release as we're now
really close to all that release fun.[B] Tomorrow, on 2014-07-08 we will
branch Fedora 21 from rawhide, according to the schedule[/B] [1].
* If there is anything blocking you/your product or if there's potential
risk of delays, let us know. Ml, directly, through FESCo ticket,
as always. *
For Changes freeze, it's the same day as Branch day - thank you everyone
for your updates. And if you haven't done it yet, please take a look on it
by Wednesday's FESCo meeting as I'm going to prepare the list of incomplete
changes. See bz listing [2].
Alpha Release Readiness and the first Alpha Go/No-Go meetings are in three
weeks, on 2014-07-31. With Alpha Change Deadline on 2014-07-22.
FESCo Summer 2014 special elections nominations [3] are still open, will be
closed today at midnight (UTC)!!!
And of course Flock - the Fedora contributors conference is on August 6-9
in Prague [4]. As there's potential conflict with Fedora 21 schedule, FESCo
agreed to skip release effort during Flock in case of Alpha slip.
[1] [url]https://fedoraproject.org/wiki/Releases/21/Schedule[/url]
[2] [url]http://bit.ly/f21changesfreeze[/url]
[3] [url]https://fedoraproject.org/wiki/Development/SteeringCommittee/Nominations[/url]
[4] [url]http://flocktofedora.org/[/url]
_______________________________________________
devel-announce mailing list
[email]devel-announce@lists.fedoraproject.org[/email]
[url]https://admin.fedoraproject.org/mailman/listinfo/devel-announce[/url][/quote]
[b]get hype![/b]
Was F21 the version where Wayland is available (Wayland GNOME-session etc.)?
CentOS 7 is out.
get hype
[editline]7th July 2014[/editline]
[url]http://wiki.centos.org/Manuals/ReleaseNotes/CentOS7#head-76148df6f2cc6a03ab2ceaa23204ace3e2acbfb9[/url]
[url]http://lists.centos.org/pipermail/centos-announce/2014-July/020393.html[/url]
[url]http://isoredirect.centos.org/centos/7/isos/x86_64/CentOS-7.0-1406-x86_64-DVD.iso[/url]
I finally got around to begin reinstalling Arch on my new SSD, but I did something wrong. doing the usual stuff with UEFI, I formatted and mounted what I assumed was my EFI partition but apparently I formatted the wrong one. I picked /dev/sda1, but /dev/sda2 was my EFI partition apparently after double checking the flags. /dev/sda1 had a hidden flag and I wiped whatever used to be there. Windows still works so I have no clue what I just removed. it feels like something important, but stuff still boots. any clue what I just removed?
[QUOTE=PredGD;45321582]I finally got around to begin reinstalling Arch on my new SSD, but I did something wrong. doing the usual stuff with UEFI, I formatted and mounted what I assumed was my EFI partition but apparently I formatted the wrong one. I picked /dev/sda1, but /dev/sda2 was my EFI partition apparently after double checking the flags. /dev/sda1 had a hidden flag and I wiped whatever used to be there. Windows still works so I have no clue what I just removed. it feels like something important, but stuff still boots. any clue what I just removed?[/QUOTE]
Most default Windows installs have a 100mb recovery/backup partition with a bunch of bullshit on it. You're fine.
another issue on hand, I'm not able to boot into Arch :v:
it hangs on boot. the line it gets stuck on
[code][ OK ] Found device Samsung_SSD_840_EVO_250GB 6.
Starting File System Check on /dev/disk/by-uuid/9ec1bc73-e446-4854-94e7-24d3aad36537. . .[/code]
and then it hangs. I haven't seen this before and my google-fu isn't working out
[editline]8th July 2014[/editline]
scratch that, got that solved. tried infinality for the first time ever and uhh
[img]http://i.imgur.com/0Ki5fmE.png[/img]
this only happens on facepunch on Firefox. whats up?
What's your filesystem?
And you may want to disable any "quiet" boot parameters to see if there's more to the message.
[editline]asf[/editline]
wow right when I posted too.
[QUOTE=Naelstrom;45321871]Most default Windows installs have a 100mb recovery/backup partition with a bunch of bullshit on it. You're fine.[/QUOTE]
Actually, if he's using GPT (and he probably is, that's the popular standard nowadays from what I hear), the 100MB partition contains data important to Windows booting (essentially the Windows equivalent to /boot). With old MBR partition tables, Windows just stores all that on the first NTFS partition it happens to notice (and not necessarily sdX1).
If he deleted that partition, he just made Windows unbootable. Which isn't a big deal if you're removing Windows entirely anyway.
[QUOTE=lavacano;45323830]Actually, if he's using GPT (and he probably is, that's the popular standard nowadays from what I hear), the 100MB partition contains data important to Windows booting (essentially the Windows equivalent to /boot). With old MBR partition tables, Windows just stores all that on the first NTFS partition it happens to notice (and not necessarily sdX1).
If he deleted that partition, he just made Windows unbootable. Which isn't a big deal if you're removing Windows entirely anyway.[/QUOTE]
But his Windows is still booting, which is the weird part. So either that 100MB sector didn't get changed or deleted at all, or it wasn't key to Windows booting.
[QUOTE=Dr. Deeps;45324261]But his Windows is still booting, which is the weird part. So either that 100MB sector didn't get changed or deleted at all, or it wasn't key to Windows booting.[/QUOTE]
If it wasn't key to Windows booting then it wasn't the partition I'm thinking of.
Since you can't really fit a recovery partition in 100MB, I'm guessing the partition was a bit larger than that (the actual dude never said) and he probably is going to be OK.
Alright if systemd gets forced on me I'm migrating back to Windows.
Non modular bloated horseshit like systemd is why I migrated [b]away[/b] from Windows in the first place and if I'm going to be forced right back into it I might as well not even fucking bother.
[QUOTE=lavacano;45324305]If it wasn't key to Windows booting then it wasn't the partition I'm thinking of.
Since you can't really fit a recovery partition in 100MB, I'm guessing the partition was a bit larger than that (the actual dude never said) and he probably is going to be OK.[/QUOTE]
iirc the 100 mb system partition that windows makes has bitlocker stuff and also contains boot data, but if you make it so that windows doesn't create the system partition on install it just shoves the boot data into the main partition
[editline]8th July 2014[/editline]
[QUOTE=lavacano;45324818]Alright if systemd gets forced on me I'm migrating back to Windows.
Non modular bloated horseshit like systemd is why I migrated [b]away[/b] from Windows in the first place and if I'm going to be forced right back into it I might as well not even fucking bother.[/QUOTE]
systemd is going to be split into smaller packages "later" (whenever later is)
I like systemd. What's wrong with it? It's pretty simple to use.
Yeah I've never really had problems with systemd.
[QUOTE=reevezy67;45324924]I like systemd. What's wrong with it? It's pretty simple to use.[/QUOTE]
It might be easy to use (personally I disagree, but whatever, most people seem to agree with you on his), but even so there's a large part that's left without mention. The code base. Systemd is eating away at what init systems do, and it's swallowing a big part of not only the init system itself, but of the services too. Networking, logging facilities, even HTTP and udev. With no alternatives left, it's hard to pick something else.
We do have eudev for now in Gentoo, but if that changes what then?
It's fine that it works for you, and I'm glad it does, but does that mean others should be left with no choice?
The choice that we so proud speak of, when Linux is of the subject? The choices that you made when you left your Windows system, or the choices you made when you picked your browser, while blissfully knowing that you could always rely on the source to be available for you to freely study and distribute and contribute to.
The freedom of choice that many seem to forget, is slowly being pulled from our hands.
That's what's wrong with systemd.
[QUOTE=Bumrang;45325010]Yeah I've never really had problems with systemd.[/QUOTE]
You say that now.
But if a few years down the road systemd starts to monstrously suck, and Poeterring succeeds in being the only major developer available on the operating system's backbone, you'd see why I'm angry now.
This was my big comfort in Linux - if some component begins to royally suck (original SysV), or some developer begins to be a monstrous fucking douchebag (Mark Shuttleworth), you could usually migrate away from that component, even if in more than a few cases you had to wait for the alternative to actually arrive first. systemd became the majority because of this same principle. And we all lived happily ever after because I could go sit in the corner with my OpenRC install because I saw flaws with systemd that I didn't feel comfortable with and nobody would really bother each other.
But now Lennart's on a power trip. Because systemd is winning via the freedom Linux users originally had, he wants to make sure he doesn't start losing later by taking away that very freedom now that he has the edge. So he's making the crucial bits that everyone was relying on not work unless they're using his other programs.
I'm hoping you can see where exactly my problem is here.
He's trying to remove latency and bloat from passing messages with this new stuff, but it's not impossible to implement an alternative userspace kdbus.
Might have problems finding the people to do it though, since the only reason to develop such a thing now that kdbus is in the kernel, is because you're running something other than systemd, which is a small market.
I think the BSD market might actually come up with a solution, I recall udev being handled in a different manner there.
At the end of the day, I really don't care. If systemd starts going bad, I can just disable all modules except for the core, journald and udev-stuff, and use alternative stuff for the other things (NetworkManager etc.)
[QUOTE=nikomo;45325243]He's trying to remove latency and bloat from passing messages with this new stuff, but it's not impossible to implement an alternative userspace kdbus.
Might have problems finding the people to do it though, since the only reason to develop such a thing now that kdbus is in the kernel, is because you're running something other than systemd, which is a small market.
I think the BSD market might actually come up with a solution, I recall udev being handled in a different manner there.
At the end of the day, I really don't care. If systemd starts going bad, I can just disable all modules except for the core, journald and udev-stuff, and use alternative stuff for the other things (NetworkManager etc.)[/QUOTE]
But you can't use a different init system, because the developers decided to fuck your freedom up the ass.
They stopped giving shits about the choices you could make, and disregarded the option for having a nice standard way of doing these things, like we used to.
So now that "small market" is just left to burn in it's own fat until no one wants to use these things anymore.
Merging them all in to one is a smart decision imo. Freedom is difficult to develop for, if you standardize, things become much much easier.
[editline]8th July 2014[/editline]
As for if it goes bad then there won't be alternatives. I don't think that is true.
If it goes bad someone will work on an alternative, somehow.
[QUOTE=reevezy67;45325367]Merging them all in to one is a smart decision imo. Freedom is difficult to develop for, if you standardize, things become much much easier.
[editline]8th July 2014[/editline]
As for if it goes bad then there won't be alternatives. I don't think that is true.
If it goes bad someone will work on an alternative, somehow.[/QUOTE]
I agree that "freedom" in it's completely free form can be difficult to develop for, but most of the time we've got freedom of implementations, which means a large quantity of standard-compliant differently-implemented applications that we could utililize.
However, systemd is NOT a standard. Systemd is a monopolization of this, not a standardization.
[QUOTE=mastersrp;45325269]But you can't use a different init system, because the developers decided to fuck your freedom up the ass.
They stopped giving shits about the choices you could make, and disregarded the option for having a nice standard way of doing these things, like we used to.
So now that "small market" is just left to burn in it's own fat until no one wants to use these things anymore.[/QUOTE]
Developers don't make decisions because they want to "fuck your freedom up the ass", they make them because the new way is more efficient.
I only really see end-users not liking systemd, the only thing that a lot of developers have complained about is that Lennart is a fucking retard, which is a valid observation.
[QUOTE=nikomo;45325403]Developers don't make decisions because they want to "fuck your freedom up the ass", they make them because the new way is more efficient.
I only really see end-users not liking systemd, the only thing that a lot of developers have complained about is that Lennart is a fucking retard, which is a valid observation.[/QUOTE]
I'm a developer, and I'm complaining about this because it means I can either develop for one monopolized singular blob, or try my hardest to support where no actual standard is.
It would be nice with a non-de facto way of doing these things, but I guess that it just so happens that it isn't possible anymore. Or isn't going to be.
I'd stick with my OpenRC, my musl-built runit and runsv, and even busybox init which is used on my netbook, but I guess I can't in the future because it won't work anymore. Or it'll be difficult getting it working.
In any case, a standard would've been enough, but none was formulated, instead a giant sweeped in and swallowed the entire ecosystem with no space left for choice.
Monopolies are a phenomenon that can either be forced, or occur naturally.
In this case, all the other choices seriously just suck, and the monopoly occurred naturally.
If it does end up actually being a problem, competition will happen, since it's extremely hard to control the market with lobbying in the open-source market.
In the meanwhile, you can still technically use the old stuff - hell, enterprise distributions sure as hell have been shipping packages that haven't seen updates in years, and they have no problems.
Sorry, you need to Log In to post a reply to this thread.
