Re: [gentoo-user] Small computing recommendations?
Hello, > I've looked around at the Raspberry Pi 3 > > [...] > > I would prefer running Gentoo on it > > [...] > > Any opinions or use cases and stories would be much appreciated. well I'm running Gentoo on a Raspberry Pi 2. Getting Gentoo basically running on it wasn't too hard. There's some good information on the wiki: https://wiki.gentoo.org/wiki/Raspberry_Pi I got the Raspberry primarily for multimedia type of applications and experimentations. In the end I ended up with quite an array of extra hardware: - a good USB power supply that can provide at least 2.0 A which is recommended - a 32 GB microSD card for holding the (mostly) read-only part of Gentoo - a 16 GB USB drive for holding read/write partitions like /tmp which speeds things up a bit and improves the lifetime of the microSD card - the official raspberry pi touch display https://www.raspberrypi.org/products/raspberry-pi-touch-display/ - a USB wifi WLAN/Bluetooth dongle for wireless connectivity - a USB soundcard, because the onboard audio on the Raspberry has a terrible sound quality These are my experiences: - compiling your own Kernel for the Raspberry can be challenging until all devices are running as expected. - compilation for the Raspberry for Gentoo is *very* slow even with using distcc to distribute the load on bigger machines. - all kinds of file system writes tend to be slow due to the of memory devices used (microSD card, USB flash drive). - the touchscreen works fine so far even with the touch and some basic gestures working. Some special drivers from Gentoo Portage overlays are required, however. - booting is acceptably fast. I'm running an X server and fluxbox as window manager. It's finished booting after about a minute. - I got hardware accelerated video decoding running but it was a real pain. The broadcom graphics chip is only supported by either a proprietary video player or by the gstreamer framework. I think I compiled gstreamer and OpenGL/Mesa stuff for days in different configurations until I got something out of it. - Getting a fast and fully featured web browser for the Raspberry is something I've still not achieved. Currently I'm running firefox on it which is unbearably slow. So in conclusion it's a fun embedded device to work with. It was not too cheap (especially because of the touchscreen). I use it regularly for listening to music or watching short videos. It's too slow, however, for web browsing and much interactive/GUI use. Compiling software on it requires patience. And getting all the drivers and devices working in the first place can be a challenge. Best regards Matthias -- Matthias Gerstner, Dipl.-Wirtsch.-Inf. (FH) Entwicklung NCP engineering GmbH Dombühler Straße 2, D-90449, Nürnberg Geschäftsführer Peter Söll, HRB-Nr: 77 86 Nürnberg Telefon: +49 911 9968-153, Fax: +49 911 9968-229 E-Mail: matthias.gerst...@ncp-e.com Internet: http://www.ncp-e.com signature.asc Description: Digital signature
Re: [gentoo-user] Vim puts command in when starting up
Hi, > Hmm, I've just upgraded to vim v8 and it is still doing it. I'm quite > confused. I'm sorry to hear that. I didn't try an update myself yet. Maybe the cause of your issue is a different one then. I think the cause of this effect is in the area of the terminal handling and termcap information within vim. You may try experimenting with different terminal emulators and TERM variable values (for example you can test whether the bug still triggers with 'export TERM=dump' set). Maybe you can find a workaround this way. Or gather enough information for a bug report. Best regards Matthias -- Matthias Gerstner, Dipl.-Wirtsch.-Inf. (FH) Entwicklung NCP engineering GmbH Dombühler Straße 2, D-90449, Nürnberg Geschäftsführer Peter Söll, HRB-Nr: 77 86 Nürnberg Telefon: +49 911 9968-153, Fax: +49 911 9968-229 E-Mail: matthias.gerst...@ncp-e.com Internet: http://www.ncp-e.com signature.asc Description: Digital signature
Re: [gentoo-user] Vim puts command in when starting up
Hi, > For some reason, on one box, whenever I start vim it puts > "://" on the command line. I've looked in vimrc and can't > see any reference to this. Hitting Enter yields "E486: Pattern not found > :" I've had a similar issues for the past months with my vim. It was related to my using the "urxvt" terminal and its TERM variable being set to "rxvt-unicode". In my case the effect didn't always show up but only under certain conditions. I remember having seen a bug report for vim back then but can't seem to find it right now. There are similar, older bug reports, however, like this one: https://bbs.archlinux.org/viewtopic.php?id=199362 I also remember there was a bugfix to vim back then to fix the issue. But the version containing the bugfix was not yet stable in portage and so I've lived with the occasional bug until now. I'm currently using vim-7.4.769 and I think the bugfix was contained just a few micro versions later if I'm not mistaken. Hope this helps you somewhat. Best regards Matthias -- Matthias Gerstner, Dipl.-Wirtsch.-Inf. (FH) Entwicklung NCP engineering GmbH Dombühler Straße 2, D-90449, Nürnberg Geschäftsführer Peter Söll, HRB-Nr: 77 86 Nürnberg Telefon: +49 911 9968-153, Fax: +49 911 9968-229 E-Mail: matthias.gerst...@ncp-e.com Internet: http://www.ncp-e.com signature.asc Description: Digital signature
[gentoo-user] rc_hotplug and udev network interface renaming
Hi! I'm running into problems combining network device hotplugging and udev network device renaming rules. Everything on its own works well: - I have a udev rule in /etc/udev/rules.d/... telling udev to rename an ethernet device based on its MAC address from say eth_old to eth_new. When I plug the device in its name it correctly changed by udev. - I have rc_hotplug="net.eth_old !net.*" in /etc/rc.conf. When I plug in the device it is automatically started and the dhcpcd client runs for it. When I combine both by using rc_hotplug="net.eth_new !net.*" then the device is renamed but no hotplugging occurs. When I use rc_hotplug="net.eth_old !net.*" then OpenRC tries to start up eth_old but fails to do so, because it has already been renamed to eth_new. Am I missing something here? Any help? Regards Matthias -- Matthias Gerstner, Dipl.-Wirtsch.-Inf. (FH) Entwicklung NCP engineering GmbH Dombühler Straße 2, D-90449, Nürnberg Geschäftsführer Peter Söll, HRB-Nr: 77 86 Nürnberg Telefon: +49 911 9968-153, Fax: +49 911 9968-229 E-Mail: matthias.gerst...@ncp-e.com Internet: http://www.ncp-e.com signature.asc Description: Digital signature
Re: [gentoo-user] Can I suppress the bleep when shutting down?
Hi Alan, > I simply want to disable that one particular beeping at shutdown time. well this topic made me curious where the beep is coming from. It does originate from the shutdown command itself which is part of the sys-apps/sysvinit package. In this package's source you find can a file "src/dowall.c", where you will in turn find a function "wall(...)". This is the function where the warning messages will be produced that show up in the terminal and the message is produced like this: snprintf(line, sizeof(line), "\007\r\nBroadcast message from %s@%s %s(%s):\r\n\r\n", user, hostname, tty, date); The "\007" is the beep you're getting. It's a bell character that you can produce manually by doing this, too: echo -e "\007" Unfortunately the bell character is hard coded into the warning message. Also there seems to be no way to suppress the warning message. But you could still try is to disable the interpretation of the bell character by your terminal. Then you could make an alias or wrapper around the original shutdown command that does this. According to Arch Linux docs here: https://wiki.archlinux.org/index.php/Disable_PC_speaker_beep You can locally disable the bell in the terminal by calling "setterm -blength 0". But this doesn't work with my terminals. Says it's unsupported. Then you can put this in your ~/.inputrc: "set bell-style none". This works for me. Then, however, all terminals stop beeping. The pcspkr is still loaded though and can be used. As you only want to stop the beep only during shutdown you might also be able to call "xset -b", disabling the bell on the X-server (globally?). This is not persistent across reboots and you won't have any beeps until the machine shuts down. Regards Matthias signature.asc Description: Digital signature
