|
|
#
?
Nov 20, 2014 23:18
|
|
|
|
| # ? May 14, 2024 19:39 |
|
|
tip shat
|
|
#
?
Nov 21, 2014 00:42
|
|
|
lol
|
|
#
?
Nov 21, 2014 02:04
|
|
|
Friends, Debianites, developers, lend me your ears; I come to bury Ian, not to praise him. The evil that men do lives after them; The good is oft interred with their bones; So let it be with Ian. The noble Bdale Hath told you Ian was ambitious: If it were so, it was a grievous fault; And grievously hath Ian answer'd it. Here, under leave of Bdale and the rest, — For Bdale is an honorable man; So are they all, all honorable men, — Come I to speak of Ian's stepping down. He was my friend, faithful and just to me: But Bdale says he was ambitious; And Bdale is an honorable man. -- Init Freedom
|
|
#
?
Nov 21, 2014 02:44
|
|
|
Shaggar posted:for ipads/iphones there are management tools so you can lock down their devices if they're on your network and since they're closed source you can trust them. w/ android or just a regular old laptop you aren't gonna be able to lock them down so your choice are don't allow them or let them be used as thin clients that access ur network thru a vpn and remote desktop/app virtualization https://play.google.com/store/apps/details?id=com.google.android.apps.enterprise.dmagent&hl=en
|
|
#
?
Nov 21, 2014 03:18
|
|
|
no open source will enter this building!! not on my watch!! - shaggar
|
|
#
?
Nov 21, 2014 05:14
|
|
|
ShadowHawk posted:https://support.google.com/a/users/answer/190930?hl=en you cant trust any of that
|
|
#
?
Nov 21, 2014 05:15
|
|
|
welp
|
|
#
?
Nov 21, 2014 13:07
|
|
|
the one dude in our DevOps group who runs Linux as his os on a system76 hidpi laptop has given it up immediately when offered a retina mbp
|
|
#
?
Nov 21, 2014 13:12
|
|
|
pram posted:r u telling me we could have the worlds most advanced filesystem in the kernel if it wasnt for loving stallman more like sun deliberately choosing CDDL to protect solaris i want a fs with transactions and featherstitch  ((((
|
|
#
?
Nov 21, 2014 13:21
|
|
|
why do you need that poo poo in the filesystem end to end principle bro the fs should be transactional with respect to its own metadata, everything else is an application-level problem
|
|
#
?
Nov 21, 2014 17:51
|
|
|
If I understand this thread correctly, support for zfs in kernel space is the only thing keeping Linux from breaking through to 1.5% of desktops?
|
|
#
?
Nov 21, 2014 18:08
|
|
|
oh i think i understand what docker is for now it's a containment system for fuckup ruby developers (trying to install gitlab at the moment, it is a fun time)
|
|
#
?
Nov 21, 2014 18:33
|
|
|
just use coreos
|
|
#
?
Nov 21, 2014 21:01
|
|
|
also docker owns. a lot of people think its just vanilla vms so they get pissed when it doesnt work how they expect
|
|
#
?
Nov 21, 2014 21:02
|
|
|
sure lemme just go ahead and install 50 copies of all my framework dlls and patch them all separately and let's have separate database servers that i have to back up separately for each of this thing too let's just multiply all of my system administration by the number of applications i'm running and run every single version of every single flavour of linux for each of the precious snowflake ruby developers who wrote the poo poo i'm running seriously is there something like gitlab but written by people who have heard of the fhs and understand why it's a good idea? and who have also heard of concepts like "versioning"? tia
|
|
#
?
Nov 21, 2014 21:50
|
|
|
try gogs, its a gitlab written in Gods own language Go http://gogs.io/
|
|
#
?
Nov 21, 2014 21:53
|
|
|
Mr Dog posted:sure lemme just go ahead and install 50 copies of all my framework dlls and patch them all separately How is this a problem unless you a retard and admin things by hand?
|
|
#
?
Nov 21, 2014 22:56
|
|
|
pram posted:try gogs, its a gitlab written in Gods own language Go that looks pretty cool though it doesn't have an integrated wiki and issue tracker (yet?)
|
|
#
?
Nov 21, 2014 23:22
|
|
|
Mr Dog posted:that looks pretty cool so like all golang things, including the language itself, they implemented the easiest 40% of the problem
|
|
#
?
Nov 22, 2014 00:16
|
|
|
Malcolm XML posted:more like sun deliberately choosing CDDL to protect solaris cddl was about patents
|
|
#
?
Nov 22, 2014 00:17
|
|
|
Mr Dog posted:that looks pretty cool thats the beauty of open source projects mr. dog. just pull up vim and get a pull request going
|
|
#
?
Nov 22, 2014 00:28
|
|
|
i am amused that http://uselessd.darknedgy.net/ is a thing
|
|
#
?
Nov 22, 2014 03:13
|
|
|
im the useless d
|
|
#
?
Nov 22, 2014 03:18
|
|
|
that FAQ is so dark so edgy
|
|
#
?
Nov 22, 2014 03:29
|
|
|
use less d
|
|
#
?
Nov 22, 2014 04:26
|
|
|
linked from that page: http://homepage.ntlworld.com/jonathan.deboynepollard/Softwares/nosh.html looks like another response to systemd that's heavy on code and light on whining. it actually looks a lot like that "wouldn't be nice if" fractured systemd i sketched out earlier, i'll have to look at it in more detail i don't necessarily think systemd is some bastion of perfection, i just think it's a gently caress of a lot better than anything else going at the moment. the fact that systemd has been adopted by debian in spite of all the political bickering seems to have kicked some actual competing development efforts into gear.
|
|
#
?
Nov 22, 2014 04:55
|
|
|
Cos no-one made an init system until Poettering, then everyone copied him.
|
|
#
?
Nov 22, 2014 13:21
|
|
|
self signed ssl certificate
|
|
#
?
Nov 22, 2014 23:38
|
|
|
pram posted:try gogs, its a gitlab written in Gods own language Go cool
|
|
#
?
Nov 22, 2014 23:51
|
|
|
Notorious b.s.d. posted:so like all golang things, including the language itself, they implemented the easiest 40% of the problem what's wrong with go
|
|
#
?
Nov 22, 2014 23:57
|
|
|
he doesnt know hes just a contrarian retard
|
|
#
?
Nov 22, 2014 23:59
|
|
|
is there like a good summary anywhere of why systemd is the way it is? i mean i don't really give a rat's rear end what init system ends up winning but i can at least understand why some people might be a little worried about it being PID 1 also learning about init systems seems like a totally good and fruitful use of my time 
|
|
#
?
Nov 23, 2014 00:32
|
|
|
Avenging Dentist posted:is there like a good summary anywhere of why systemd is the way it is? i mean i don't really give a rat's rear end what init system ends up winning but i can at least understand why some people might be a little worried about it being PID 1 Systemd won.
|
|
#
?
Nov 23, 2014 01:05
|
|
|
Avenging Dentist posted:is there like a good summary anywhere of why systemd is the way it is? i mean i don't really give a rat's rear end what init system ends up winning but i can at least understand why some people might be a little worried about it being PID 1 my tldr understanding: - a key goal is to manage dependencies among services - this management requires direct, reliable information about each service's process status - the linux kernel provides that information to pid 1 by default - there are also ways to provide it to a different process (i.e. process grouping and subreaping) but using these merely displaces the work to be done, and all the potential hazards, without otherwise changing them Gazpacho fucked around with this message at 02:41 on Nov 23, 2014 |
|
#
?
Nov 23, 2014 02:21
|
|
|
Avenging Dentist posted:is there like a good summary anywhere of why systemd is the way it is? It is the way it is because that's the way it was written. Anything more specific?
|
|
#
?
Nov 23, 2014 02:22
|
|
|
its written that way because its emulating how services are handled on far more advanced systems (launchd on osx)
|
|
#
?
Nov 23, 2014 02:26
|
|
|
Gazpacho posted:read lennart's master post on the subject There's also the fiddly little things (set the hostname, set the locale, load the keyboard map, set the machine UUID, etc.) that init takes care of after the initramfs mounts the root file system and starts init and before init can start the system proper. In sysvinit this was handled by a gigantic tangled mess of a shell script custom written for each distribution; systemd came along and looked at what each distribution was doing, chose the least retarded method (typically whatever Debian was doing because they tended towards the least idiotic), standardized on that, and then supplied little C language tools to do that thing, with full backward compatibility for each distribution that was involved in systemd development. A part of managing system services is keeping track of their event logs, and the standard syslog interface is an unstructured flat text file that programs can fill with any lies they feel like (including basic things like the program name). This makes simple tasks like quickly answering "What were the last 10 log messages from service $X" pointlessly difficult, so the journal was introduced to bring Linux logging kicking and screaming into the 1990s. Log entries are indexed and structured and include trustworthy metadata supplied by the journal daemon itself about the application doing the logging in addition to whatever log messages the application supplied itself. The indexing requires a binary file format, which beardos hate because they can't read it using less, although for some reason the fact they can't read ext4 using less either still doesn't bother them.
|
|
#
?
Nov 23, 2014 03:19
|
|
|
|
| # ? May 14, 2024 19:39 |
|
|
Suspicious Dish posted:It is the way it is because that's the way it was written. Anything more specific? lennart's bigass post (which i haven't read yet but thx for the link) probably answers my question, but i was mainly wondering about why it needed to be pid 1 in particular, since i would have naively assumed that putting everything in pid 1 would have problems (e.g. if systemd crashed or if you tried to update systemd, which i expect would happen a lot more often than a minimalist pid 1) i mean surely there was some logic to why XYZ got moved into systemd and that's what i wanna read about. hopefully the link will explain that
|
|
#
?
Nov 23, 2014 04:00
|
|