Re: [arch-general] Building in docker?
> I have a very simple container that I use for building Arch packages, just > added it to the Docker Hub so others can use it: > https://registry.hub.docker.com/u/tazjin/arch-pkgbuild/ > I just want to share with you my Docker image as well, which adds a couple of features to Vincent's, which are: - Allows to specify the desired uid for generated files at "docker run"- time. This allow to use the image directly from the registry without needing to re-build it. - It specify Git's global user.name and user.email to allow cloning from servers that requires them. Hope it's useful as well for you: https://hub.docker.com/r/aitorpazos/archlinux-docker-makepkg/ Cheers, Aitor Pazos Instant Messaging (Jabber, GTalk): ai...@aitorpazos.es PGP Public Key: http://aitorpazos.es/publickey.asc
Re: [arch-general] Systemd +1
> > Right, because /sbin/init isn't binary and none of the scripts relied > on a interpreter that wasn't binary code? They are indeed, but it's a matter of size. The size of /sbin/init is 40.592B and /usr/lib/systemd/systemd 866.576B, which is a huge difference. Init responsabilities are much more specific than systemd's and the binary doesn't change much. All systemd's features implies it will be updated frequently and every change introduces some kind of risk. Interpreters are binaries as well, but if one fail you might use another one, if systemd fails you might not be able to get even a rescue console.
Re: [arch-general] Systemd +1
Hi everyone! My experience with systemd is a +1 as well. I use it in my laptop and it provides a nice experience for a desktop user. Starting services on demand, suspend support and all other features gives a nice experience for an end user. > Maybe it's just my idea but I think the system is somewhat faster on > the booting now. True for me as well. From grub to kdm in around 5sec. Nevertheless, this overall good opinion can't hide certain (or significant I might say) worries. Your system now relies in a bunch of binary code that might not be posible to workaround if something goes wrong. Scripts may not be as efficient but they are great in order to skip,modify or run them in case of emergency. Logging using systemd infrastructure provides a very pleasent usage experience for me as you can very easily select the relevant records you're interested in without a lot of grep magic. But I've already suffered the downside of relying on binary stored records. In case of system crash/forced shutdown or power failure log files might end up corrupted. Which is a pretty nasty thing you don't want to happen and it opens a big door to atacks. I would recomend systemd for interactive users but I don't wan't it in a server that much. I can't give an opinion on wether initscripts should be dropped or not. Aitor Pazos Ibarzabal Instant Messaging (Jabber, GTalk): ai...@aitorpazos.es Web: http://aitorpazos.es PGP Public Key: http://aitorpazos.es/publickey.asc
