5 ms·

> Lennart seems to harbor this very strange belief that developing your software in one repository makes you Unix-like, and that this alone is sufficient entire

> Lennart seems to harbor this very strange belief that developing your software in one repository makes you Unix-like, and that this alone is sufficient entirely. He is saying that a trait of the Unix systems was the development in a single repository. In that particular aspect, a fully integrated DOS clone might be more Unix-like than, say, Linux. This is a response to the people who mistake the "Linux way" for the "Unix way".

vezzy-fnord 12y ago
The thing is, the aforementioned trait is far too generic - it's a characteristic of how development is structured, and has little or nothing to do with the more technical aspects of the Unix design, which is what is being contested. It's not just Unix. Development in a single repository has been how almost all operating systems were done. In fact, standalone kernels have usually been research projects throughout the years. Linux is a notable exception.
- the_why_of_y 12y ago
  Of course you can get more specific - for example, the Solaris kernel/libc combination is so tightly coupled that it is described as a "welded unit" https://www.youtube.com/watch?v=TrfD3pC0VSs#t=29m10 https://www.youtube.com/watch?v=TrfD3pC0VSs#t=29m10 OpenBSD solved the Year 2038 problem by incompatibly changing the kernel and libc ABI in lockstep, which broke every single existing binary application using time_t - how's that for tight coupling... http://www.openbsd.org/papers/eurobsdcon_2013_time_t/ http://www.openbsd.org/papers/eurobsdcon_2013_time_t/
digi_owl 12y ago
Maintained in a single repository and maintained as a single blob of code is two different things. Can i get the systemd repository to hand over just udev as a tarball, and then compile it? Or do i have to grab the whole of systemd, extract udev from that, and then attempt to compile? for example XFCE is maintained in a single repository, but each part is released on their own.

vezzy-fnord 12y ago

The thing is, the aforementioned trait is far too generic - it's a characteristic of how development is structured, and has little or nothing to do with the more technical aspects of the Unix design, which is what is being contested. It's not just Unix. Development in a single repository has been how almost all operating systems were done. In fact, standalone kernels have usually been research projects throughout the years. Linux is a notable exception.

the_why_of_y 12y ago
Of course you can get more specific - for example, the Solaris kernel/libc combination is so tightly coupled that it is described as a "welded unit" https://www.youtube.com/watch?v=TrfD3pC0VSs#t=29m10 https://www.youtube.com/watch?v=TrfD3pC0VSs#t=29m10 OpenBSD solved the Year 2038 problem by incompatibly changing the kernel and libc ABI in lockstep, which broke every single existing binary application using time_t - how's that for tight coupling... http://www.openbsd.org/papers/eurobsdcon_2013_time_t/ http://www.openbsd.org/papers/eurobsdcon_2013_time_t/

digi_owl 12y ago

Maintained in a single repository and maintained as a single blob of code is two different things. Can i get the systemd repository to hand over just udev as a tarball, and then compile it? Or do i have to grab the whole of systemd, extract udev from that, and then attempt to compile? for example XFCE is maintained in a single repository, but each part is released on their own.