[DNG] resolved
All programmers please read this, and treat it as a list of things not to do. https://lists.dns-oarc.net/pipermail/dns-operations/2016-June/014964.html Systemd manages to shoot itself in the foot, and in the elbow, and trigger a timebomb, all with one single bullet. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Microsoft upgrades Windows 7 to 10 without permission
On 16.03.2016 at 17:27 David Harrison wrote: On 16/03/2016 10:49, dng-requ...@lists.dyne.org wrote: I Dropped back to 7, created a .exe that simply returns to OS, and then replaced c:\Windows\system32\GWX\GWX.exe and c\Windows\SysWOW64\GWX\GWX.exe with my NOP code. Would it be possible to share that .exe off-list? It would come in very handy with killing the nags on my own Win7 box. Use the official method documented by Microsoft. Read https://support.microsoft.com/kb/3080351 Set these registry keys: [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\OSUpgrade] "ReservationsAllowed"=dword: [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate] "DisableOSUpgrade"=dword:0001 [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Gwx] "DisableGwx"=dword:0001 ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] what is sssd?
Am 22.01.2016 um 16:07 schrieb Rowland Penny: On 22/01/16 14:29, Klaus Hartnegg wrote: Am 22.01.2016 um 14:23 schrieb Dr. Nikolaus Klepp: Does anybody know what sssd is good for? This is often used together with Samba to make userids of pure Active Directory users known to the Linux of the domain controller. https://wiki.samba.org/index.php/Sssd The samba developers recommend to use winbindd for this function. But there are cases when this does not exactly do what the admins want. Then they often switch to sssd. Care to expand on what sssd does that winbind doesn't ? I do not use it myself, only read about it on the samba mailinglist. You can probably tell much more precisely what sssd is, than I can. Just wanted to make sure that before devuan leaves it away, they should consider that some samba users want it. I should have added that because winbind improves with time, sssd will probably be less used in the future. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] what is sssd?
Am 22.01.2016 um 14:23 schrieb Dr. Nikolaus Klepp: Does anybody know what sssd is good for? This is often used together with Samba to make userids of pure Active Directory users known to the Linux of the domain controller. https://wiki.samba.org/index.php/Sssd The samba developers recommend to use winbindd for this function. But there are cases when this does not exactly do what the admins want. Then they often switch to sssd. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] pressed root pw
Am 20.10.2015 um 23:58 schrieb aitor_czr: $ echo "XX" | md5sum 52f400d860b7431525a4c5367684de17 - Maybe you need instead this echo -n "XX" | md5sum c0a7ae7d513f4beb2bc203d6f339f1b5 - ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] [Dng] printing (was Re: Readiness notification)
Am 15.06.2015 um 16:35 schrieb Steve Litt: I know that every service has a "provides", that basically gives the service a uniformly agreed upon name. And it has zero to many "requires", which I believe means that the current service (call it A), requires another service (call it B), so it won't start A unless B is started. But then what does "after" mean? Does that mean *immediately* In systemd "requires" is counter-intuitive: it does not say anything about start order. It only says that the other service should also be started eventually. If start order is important, then "requires" and "after" must both be specified. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [Dng] Readiness notification
Am 14.06.2015 um 23:17 schrieb Isaac Dunham: Quite honestly, it really *does* matter to me that I can boot Alpine Linux on my netbook in ~5 seconds rather than the ~10 seconds Just a single issue caused by the complexity by systemd wastes more time than all saved boot seconds can ever sum up to. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [Dng] Readiness notification
Am 13.06.2015 um 13:33 schrieb Laurent Bercot: 30 seconds is a lot. What if you could get your desktop ready in 5 seconds or less ? This would mean less than what most people think. Because everything longer than half a second is perceived as being forced to wait. As long as an improvement stays above this threshold, it just replaces one forced wait with another forced wait. In contrast an iPad is immediately ready to get work done. No perceived wait. This feels like a different world! Good luck getting a PC from sleep to online in half a second. As long as it is slower, the precise number of seconds does not matter much. If you want to make Linux go from sleep to ready faster, there is an easier way: eliminate the waits in dhclient. The IP stack in a firmware which I wrote initializes itself in a few milliseconds. The replies from DHCP servers are lightning fast. Getting confirmation for the last used IP address does not take significantly longer than a ping time. The only slow parts are the waits in the recommended checks whether another PC is errorneously using the same IP address. This is a very rare case, and these cases can usually be detected within 10 milliseconds, because the offending machine must be very nearby. Do just this quick check, then report ready, and then do a more thorough check afterwards, just to be closer to be RFC-compliant. Please make this as systemd-incompatible as possible ;-) And then compare the whole sleep to useable time, not just the time to show the desktop. Btw. boot times tend to get less relevant in the future, because user devices just never go completely offline, and servers are mostly clusters. The whole upgrade downtime for the largest of my servers is over 5 minutes (but only once a month). How much effort would I spend to reduce this by 30 seconds? None! If the users want to get rid of this downtime, they must order a cluster. And then the downtime of the single machines would be completely irrelevant. There is no good reason to completely rewrite Linux just to save a few seconds boot time. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [Dng] Readiness notification
Am 13.06.2015 um 08:40 schrieb Didier Kryn: Yes, daemon writers are good-willing developpers; they want their software to serve as many users as possible; and users install distros. This gives power to the distros. But if someone provides them with a KISS readyness-signaling method, along with a systemd wrapper, then they can satisfy RedHat's requests at no cost. This is great, because usually the way to win is to provide something which is immediately better, not discussing that other ideologies might cause issues in the future. Developers want an easier way to send this signal, which automatically works in all distributions. If there is a library which provides this, they will look at it. And while they are, there they might look at other offers there as well. Redhat will probably not provide such a thing, thus this is an example where Devuan can be better, and gain attention. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [Dng] release names
Am 07.03.2015 um 19:31 schrieb hellekin: On 03/07/15 14:21, william moss wrote: Cool yes, but useful? Numbers have the huge advantage that everybody knows their order, which is quite important when referring to versions. *** Release *NAMES* never replaced version numbers. Hence Debian 8 "Jessie" and Devuan 1.0 "Jessie". Oh yes, they do. Often people familar with the cool names use only them. Many documents and discussions use only the names, omit the numbers. This effectively locks everybody else out of the discussion, or at least forces them to google for a dictionary that translates the arbitrary names back to meaningful numbers. Even the official release information (first google hit) does it: https://www.debian.org/releases/jessie/index.en.html Nowhere on that page is a version number or a release date, so people not familar with cool have no idea how outdated this might be. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [Dng] release names
Am 04.03.2015 um 23:10 schrieb Robert Storey : > Just want to say that I really like this idea of naming releases after minor > planets, such as Ceres. It's a way cool idea. Cool yes, but useful? Numbers have the huge advantage that everybody knows their order, which is quite important when referring to versions. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [Dng] What's new in Systemd
On Mon, 2 Feb 2015 12:31:54 -0500 Steve Litt wrote: > I'm not a Star Trek guy. What is the exact meaning of the two > "Resistance is Futile" slides? What point is the presentation trying > to get across? Whoever put this presentation together couldn't have used a worse analogy, because it induces resistance and hatred. By analogy with Star-Trek it means they know they are the evil, who will eventually loose. The motto of the Borg is 'you will be assimilated, resistance is futile'. They are extremely dangerous, appear to be unstoppable, force everybody to join them, enslave them, take them their free will. But then Picard used his insider knowledge to show how to make a Borg ship explode. And later Janeway managed (in the final episode) to destroy the whole Borg transwarp network, which essentially locked them into their quadrant and made them irrelevant. Game over. It evades me how somebody can use this analogy for himself. It's clearly the wrong side. Sorry for the late reply, but when I first saw this, I was too upset to write something. Does anybody have a version of the presentation cleared of all Star Trek slides? I would like to archive it, could be useful. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [Dng] vdev update and design document
Am 05.01.2015 um 07:21 schrieb Martijn Dekkers: There are several areas where there are significant legal requirements around disallowing the concept of a root / UID 0 user to have overriding access. Please be advised that SELinux was built by the NSA *specifically* to be able to meet these legal requirements. Root *can* disable SELinux. It may require a reboot, but updating the kernel also requires a reboot, thus it happens every other month anyway. Am 05.01.2015 um 18:29 schrieb Rainer H. Rauschenberg: Admin has to take ownership of the file to change permissions and can't give back ownership to the original owner, so the manipulation can be traced back to him (his account). Windows Admin *can* set ownership to any arbitrary user. Also there are lots of other ways to access data. There is only one way to hide data from admins: encrypt it. Reliable separation of processes requires hardware-support, i.e. virtualization, see for example qubes-os.org The effectiveness of pure software methods is always limited. They can be useful, this depends on your threat model. Klaus ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [Dng] Gnome
Am 28.12.2014 21:47, schrieb Renaud (Ron) OLGIATI: OTOH desktop users that will be attracted to Devuan will also be in majority the same who also already renounced Gnome and Kde. Very likely yes. But still the largest number of all is probably server admins. Linux is mostly a server OS anyway, and desktop users probably care less about the init system than server admins do. Am 28.12.2014 22:02, schrieb Dima Krasner: IMHO, if we're *technically* able to deliever GNOME, we definitely should do that YES! The suggestion of the OP was not to drop Gnome, but to avoid a delay by "get Devuan up and running with DEs/WMs that are not so entangled with systemd, then tackle Gnome once the basic structure is in place". Does anybody have an idea how many server admins, and how many desktop users are interested in Devuan? Klaus ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [Dng] Gnome
Am 28.12.2014 20:34, schrieb Go Linux: I understand that Devuan wants to give Debianites who use Gnome an option to move smoothly to a systemd-free future (and stick it to Gnome in the process). But does that have to be a top priority? Why not get Devuan up and running with DEs/WMs that are not so entangled with systemd then tackle Gnome once the basic structure is in place? This depends on the users. I suspect that Devuan attracts more server admins than desktop users. For server admins it would be fine to first get the base system going, and care about GUI later. However maybe making Gnome work will be easier when certain requirements have been taken into account in the design the base system. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
