X-Git-Url: http://pere.pagekite.me/gitweb/homepage.git/blobdiff_plain/081437fbd6263afb4f7fe86af8bd841e06c9f2ba..b8cfdc4c79eda32eae7d84374df6c3660e65f93a:/blog/index.rss diff --git a/blog/index.rss b/blog/index.rss index c75414270e..60979bb258 100644 --- a/blog/index.rss +++ b/blog/index.rss @@ -6,6 +6,114 @@ http://people.skolelinux.org/pere/blog/ + + Testing sysvinit from experimental in Debian Hurd + http://people.skolelinux.org/pere/blog/Testing_sysvinit_from_experimental_in_Debian_Hurd.html + http://people.skolelinux.org/pere/blog/Testing_sysvinit_from_experimental_in_Debian_Hurd.html + Mon, 3 Feb 2014 13:40:00 +0100 + <p>A few days ago I decided to try to help the Hurd people to get +their changes into sysvinit, to allow them to use the normal sysvinit +boot system instead of their old one. This follow up on the +<a href="https://teythoon.cryptobitch.de//categories/gsoc.html">great +Google Summer of Code work</a> done last summer by Justus Winter to +get Debian on Hurd working more like Debian on Linux. To get started, +I downloaded a prebuilt hard disk image from +<a href="http://ftp.debian-ports.org/debian-cd/hurd-i386/current/debian-hurd.img.tar.gz">http://ftp.debian-ports.org/debian-cd/hurd-i386/current/debian-hurd.img.tar.gz</a>, +and started it using virt-manager.</p> + +<p>The first think I had to do after logging in (root without any +password) was to get the network operational. I followed +<a href="https://www.debian.org/ports/hurd/hurd-install">the +instructions on the Debian GNU/Hurd ports page</a> and ran these +commands as root to get the machine to accept a IP address from the +kvm internal DHCP server:</p> + +<p><blockquote><pre> +settrans -fgap /dev/netdde /hurd/netdde +pkill pfinet +pkill devnode +dhclient -v /dev/eth0 +</pre></blockquote></p> + +<p>After this, the machine had internet connectivity, and I could +upgrade it and install the sysvinit packages from experimental and +enable it as the default boot system in Hurd.</p> + +<p>But before I did that, I set a password on the root user, as ssh is +running on the machine it for ssh login to work a password need to be +set. Also, note that a bug somewhere in openssh on Hurd block +compression from working. Remember to turn that off on the client +side.</p> + +<p>Run these commands as root to upgrade and test the new sysvinit +stuff:</p> + +<p><blockquote><pre> +cat > /etc/apt/sources.list.d/experimental.list &lt;&lt;EOF +deb http://http.debian.net/debian/ experimental main +EOF +apt-get update +apt-get dist-upgrade +apt-get install -t experimental initscripts sysv-rc sysvinit \ + sysvinit-core sysvinit-utils +update-alternatives --config runsystem +</pre></blockquote></p> + +<p>To reboot after switching boot system, you have to use +<tt>reboot-hurd</tt> instead of just <tt>reboot</tt>, as there is not +yet a sysvinit process able to receive the signals from the normal +'reboot' command. After switching to sysvinit as the boot system, +upgrading every package and rebooting, the network come up with DHCP +after boot as it should, and the settrans/pkill hack mentioned at the +start is no longer needed. But for some strange reason, there are no +longer any login prompt in the virtual console, so I logged in using +ssh instead. + +<p>Note that there are some race conditions in Hurd making the boot +fail some times. No idea what the cause is, but hope the Hurd porters +figure it out. At least Justus said on IRC (#debian-hurd on +irc.debian.org) that they are aware of the problem. A way to reduce +the impact is to upgrade to the Hurd packages built by Justus by +adding this repository to the machine:</p> + +<p><blockquote><pre> +cat > /etc/apt/sources.list.d/hurd-ci.list &lt;&lt;EOF +deb http://darnassus.sceen.net/~teythoon/hurd-ci/ sid main +EOF +</pre></blockquote></p> + +<p>At the moment the prebuilt virtual machine get some packages from +http://ftp.debian-ports.org/debian, because some of the packages in +unstable do not yet include the required patches that are lingering in +BTS. This is the completely list of "unofficial" packages installed:</p> + +<p><blockquote><pre> +# aptitude search '?narrow(?version(CURRENT),?origin(Debian Ports))' +i emacs - GNU Emacs editor (metapackage) +i gdb - GNU Debugger +i hurd-recommended - Miscellaneous translators +i isc-dhcp-client - ISC DHCP client +i isc-dhcp-common - common files used by all the isc-dhcp* packages +i libc-bin - Embedded GNU C Library: Binaries +i libc-dev-bin - Embedded GNU C Library: Development binaries +i libc0.3 - Embedded GNU C Library: Shared libraries +i A libc0.3-dbg - Embedded GNU C Library: detached debugging symbols +i libc0.3-dev - Embedded GNU C Library: Development Libraries and Hea +i multiarch-support - Transitional package to ensure multiarch compatibilit +i A x11-common - X Window System (X.Org) infrastructure +i xorg - X.Org X Window System +i A xserver-xorg - X.Org X server +i A xserver-xorg-input-all - X.Org X server -- input driver metapackage +# +</pre></blockquote></p> + +<p>All in all, testing hurd has been an interesting experience. :) +X.org did not work out of the box and I never took the time to follow +the porters instructions to fix it. This time I was interested in the +command line stuff.<p> + + + A fist full of non-anonymous Bitcoins http://people.skolelinux.org/pere/blog/A_fist_full_of_non_anonymous_Bitcoins.html @@ -85,7 +193,7 @@ is anonymous. It isn't really a good fit for illegal activites. Use cash if you need to stay anonymous, at least until regular DNA sampling of notes and coins become the norm. :)</p> -<p>As usual, if you use bitcoin and want to show your support of my +<p>As usual, if you use Bitcoin and want to show your support of my activities, please send Bitcoin donations to my address <b><a href="bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&label=PetterReinholdtsenBlog">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b</a></b>.</p> @@ -731,56 +839,5 @@ Scraperwiki for de som vil grave dypere.</p> - - All drones should be radio marked with what they do and who they belong to - http://people.skolelinux.org/pere/blog/All_drones_should_be_radio_marked_with_what_they_do_and_who_they_belong_to.html - http://people.skolelinux.org/pere/blog/All_drones_should_be_radio_marked_with_what_they_do_and_who_they_belong_to.html - Thu, 21 Nov 2013 15:40:00 +0100 - <p>Drones, flying robots, are getting more and more popular. The most -know ones are the killer drones used by some government to murder -people they do not like without giving them the chance of a fair -trial, but the technology have many good uses too, from mapping and -forest maintenance to photography and search and rescue. I am sure it -is just a question of time before "bad drones" are in the hands of -private enterprises and not only state criminals but petty criminals -too. The drone technology is very useful and very dangerous. To have -some control over the use of drones, I agree with Daniel Suarez in his -TED talk -"<a href="https://archive.org/details/DanielSuarez_2013G">The kill -decision shouldn't belong to a robot</a>", where he suggested this -little gem to keep the good while limiting the bad use of drones:</p> - -<blockquote> - -<p>Each robot and drone should have a cryptographically signed -I.D. burned in at the factory that can be used to track its movement -through public spaces. We have license plates on cars, tail numbers on -aircraft. This is no different. And every citizen should be able to -download an app that shows the population of drones and autonomous -vehicles moving through public spaces around them, both right now and -historically. And civic leaders should deploy sensors and civic drones -to detect rogue drones, and instead of sending killer drones of their -own up to shoot them down, they should notify humans to their -presence. And in certain very high-security areas, perhaps civic -drones would snare them and drag them off to a bomb disposal facility.</p> - -<p>But notice, this is more an immune system than a weapons system. It -would allow us to avail ourselves of the use of autonomous vehicles -and drones while still preserving our open, civil society.</p> - -</blockquote> - -<p>The key is that <em>every citizen</em> should be able to read the -radio beacons sent from the drones in the area, to be able to check -both the government and others use of drones. For such control to be -effective, everyone must be able to do it. What should such beacon -contain? At least formal owner, purpose, contact information and GPS -location. Probably also the origin and target position of the current -flight. And perhaps some registration number to be able to look up -the drone in a central database tracking their movement. Robots -should not have privacy. It is people who need privacy.</p> - - -