From e579e2aa506a773d553c5d20b4a7ffa28b0dd4b3 Mon Sep 17 00:00:00 2001 From: Thomas Schwinge Date: Mon, 18 Jul 2011 09:10:29 +0200 Subject: IRC. --- open_issues/systemd.mdwn | 68 +++++++++++++++++++++++++++++++++++++++++++++++- 1 file changed, 67 insertions(+), 1 deletion(-) (limited to 'open_issues/systemd.mdwn') diff --git a/open_issues/systemd.mdwn b/open_issues/systemd.mdwn index bf8ae70a..12a2699f 100644 --- a/open_issues/systemd.mdwn +++ b/open_issues/systemd.mdwn @@ -1,4 +1,4 @@ -[[!meta copyright="Copyright © 2010 Free Software Foundation, Inc."]] +[[!meta copyright="Copyright © 2010, 2011 Free Software Foundation, Inc."]] [[!meta license="""[[!toggle id="license" text="GFDL 1.2+"]][[!toggleable id="license" text="Permission is granted to copy, distribute and/or modify this @@ -24,3 +24,69 @@ Introduction: [*Ressourcen-Verwaltung mit Control Groups (cgroups)* Daniel Gollub, Stefan Seyfried, 2010-10-14. Likely there's also some other porting needed. + + +# IRC, OFTC, #debian-hurd, 2011-05-19 + + pochu: http://news.gmane.org/gmane.comp.gnome.desktop - the + "systemd as dependency" and all the messages in it don't give me a bright + future for gnome on hurd... + yeah, I've read the thread + it's only a proposal so far... hopefully it'll be rejected, or they + will only accept the interfaces that other OSes can implement... + we'll see + you can always help me with kde on hurd, would be nice ;) + hehe + pochu: well, even if the depenency is rejected, the whole «don't + give a damn about non-linux and only bless linux for the "gnome os"» is a + bit... worrying attitude + yeah... it doesn't come from all the community though + I'm sure some people have always thought that way + Or we could get systemd going? :-) + good luck with that :p + tschwinge: haha!? :) + That bad? + tschwinge: if you mean by that forking indefinitely then maybe + tschwinge: upstream has expressely stated multiple times, no + interest whatsoever in any kind of portability to anything non-Linux + or even older Linux versions! + to the point of rejecting patches, because they "clutter" the + source code... + Well, then let's ``just'' implement the Linux interfaces. :-) + tschwinge: then you'll be always playing catch up + tschwinge: for example several of the Linux-only things upstream + makes heavy use of, are pretty recent Linux-only additions to the kernel, + but equivalents have been present on FreeBSD for years + Yeah. I'm half-serious, half-joking. + I haven't looked at the systemd code at all. + + https://mail.gnome.org/archives/desktop-devel-list/2011-May/msg00447.html + for a list of its dependencies + some are just glibc extensions though + and some are IMO optional and should be conditionalized, but... + pochu: I don't think that attitude is that old, there was a time + when Linux was not used widely, or even that functional, I think it has + been taking strength since the Linux Plumbers Cartel started :) + as in one thing is not caring about anything non-Linux, the other + is outright rejecting portability fixes + tschwinge: in any case, these "recent" events are "pissing me + off" to the point of having considered several times implementing + portable replacements for some of those Utopia projects, the problem as + always is time though :) + tschwinge: and the issue is not only with systemd, upstart's + upstream has the same approach to portability, if you want to port it, + you'll have to maintain a fork + let's create our own init system, make it better than anyone else, + and when people start switching to it, let's start using hurd-only APIs + :) + We already had someone work on that. Like ten years ago. DMD. + Daemon Managing Daemons. + the real problem with that attitude is not the lack of care for + portabilty, the real problem is that these people are pushing for their + stuff all over the stack, and most of the time deprecating their own + stuff after a while when they have rewritten it from scratch, leaving the + burden of maintaining the old stuff to the other ports + witness HAL, ConsoleKit, etc etc + (anyway enough ranting I guess :) + Yeah, it's true, though. + agreed -- cgit v1.2.3 From 08afda435b8ed287400f263e7be8af329fd276c9 Mon Sep 17 00:00:00 2001 From: Thomas Schwinge Date: Mon, 18 Jul 2011 09:11:01 +0200 Subject: open_issues/systemd: List from debian-devel post. --- open_issues/systemd.mdwn | 58 ++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 58 insertions(+) (limited to 'open_issues/systemd.mdwn') diff --git a/open_issues/systemd.mdwn b/open_issues/systemd.mdwn index 12a2699f..1d774307 100644 --- a/open_issues/systemd.mdwn +++ b/open_issues/systemd.mdwn @@ -90,3 +90,61 @@ Likely there's also some other porting needed. (anyway enough ranting I guess :) Yeah, it's true, though. agreed + + +# Requires Interfaces + +In the thread starting +[here](http://lists.debian.org/debian-devel/2011/07/threads.html#00269), a +[message](http://lists.debian.org/debian-devel/2011/07/msg00281.html) has been +posted that contains the following list (no claim for completeness) of +interfaces that are used in (two source code files of) systemd: + + * cgroups + * namespaces + * selinux + * autofs4 + * capabilities + * udev + * oom score adjust + * RLIMIT_RTTIME + * RLIMIT_RTPRIO + * ionice + * SCHED_RESET_ON_FORK + * /proc/$PID/stat + * fanotify + * inotify + * TIOCVHANGUP + * IP_TRANSPORT + * audit + * F_SETPIPE_SZ + * CLONE_xxx + * BTRFS_IOC_DEFRAG + * PR_SET_NAME + * PR_CAPBSET_DROP + * PR_SET_PDEATHSIG + * PR_GET_SECUREBITS + * /proc/$PID/comm + * /proc/$PID/cmdline + * /proc/cmdline + * numerous GNU APIs like asprintf + * SOCK_CLOEXEC, O_CLOEXEC + * /proc/$PID/fd + * /dev/tty0 + * TIOCLINUX + * VT_ACTIVATE + * TIOCNXCL + * KDSKBMODE + * /dev/random + * /dev/char/ + * openat() and friends + * /proc/$PID/root + * waitid() + * /dev/disk/by-label/ + * /dev/disk/by-uuid/ + * /sys/class/tty/console/active + * /sys/class/dmi/id + * /proc/$PID/cgroup + * \033[3J + * /dev/rtc + * settimeofday() and its semantics -- cgit v1.2.3