Jump to content
funtoo forums

sitquietly

Members
  • Content count

    21
  • Joined

  • Last visited

  1. Over in our upstream, the Gentoo portage tree, kde-frameworks ebuilds were updated to the 5.14 release. I think that update occurred 18 days ago. We still haven't pulled those updates into our Funtoo portage tree. I don't know if this is a normal delay pending some review by our own team (thank you all!) or if there is some particular problem. Maybe syncing is problematic right now as Gentoo switches to git? How much delay is normal between updates to Gentoo portage and syncing them into Funtoo portage? I appreciate help understanding the process --- the delay is problematic for me right now because I use the Gentoo KDE Overlay. When that overlay moves packages from the overlay into the main Gentoo portage tree they "disappear" from my Funtoo system and suddenly my system is in an inconsistent state and can't be updated.
  2. I sometimes boot into Funtoo ~amd64, and sometimes boot into FreeBSD 10 stable with current (HEAD) ports. They are on separate drives with their own boot managers but share a common /home on a ZFS mirrored pool. I'd like to try running the 32-bit Linux google-chrome in FreeBSD. It appears to be almost possible to do that using the CentOS 6.x system from ports and utilizing the FreeBSD "linuxulator". In other words FreeBSD can run Linux binaries "natively" (but it only emulates the Linux 2.6.x kernel). I can chroot into the FreeBSD linux subsystem at /compat/linux and run Linux gui apps using the FreeBSD X server. e.g. # script to chroot into bash in linux cp /etc/resolv.conf /compat/linux/etc/ mount -t linprocfs linproc /compat/linux/proc mount_nullfs /dev /compat/linux/dev mount_nullfs /sys /compat/linux/sys mount -t fdescfs fdesc /compat/linux/dev/fd export DISPLAY="192.168.1.1:0.0" xhost +localhost DISPLAY=localhost:0 chroot /compat/linux /bin/bash but I run into problems with missing libraries for Google Chrome -- it would be so much more flexible to just put Funtoo in /compat/linux and use portage to install stuff into that chrooted system. Before I spend time installing Funtoo into a FreeBSD chroot (or optionally a jail) I would appreciate hearing from anyone who has tried running a recent Gentoo or Funtoo in a FreeBSD chroot or jail. Any advice? Pitfalls? Is there any reason it can't work? Can pigs fly?
  3. I installed a hardened amd64 profile for three KDE / xmonad / fluxbox desktops. One by one I had to abandon the hardened profile on each machine and switch them to pure64. "Hardened" was easy to install and mostly well supported, but over time I ran into repeated blocks and emerge failures with that profile. Often problems with hardened packages are fixed within a few days but not always. It was sufficiently frustrating to motivate the effort to switch away from it. Some problems were not just that packages could not be emerged but that my own local software and programming projects would fail because they were incompatible with some hardening feature. I gradually turned off PaX features trying to keep my own stuff compileable. I still run hardened on my file server and am glad for the extra security there. The simpler your "desktop", the more likely that you'll be happy with a hardened system, but it just receives less feedback and bug fixing to make everything work all of the time. It would be a great service, maybe a worthwhile project for you, if you would install a hardened system and commit to making bug reports for every problem that arises over time.
  4. boot-update can't find bzImage

    Probably reading `man boot.conf` and considering the examples there will resolve the problem for you. You will need to edit /etc/boot.conf to describe your setup for boot-update. Especially notice that the line in the kernel entry that names the kernel, e.g. kernel vmlinuz[-v] must correspond to your own kernel naming convention. If the kernel in /boot/ have names like bzImage-3.9-gentoo then the line must be kernel bzImage[-v] but if they are named like kernel-3.9-gentoo then the line must be kernel kernel[-v]
  5. Your requirements list probably excludes all of the binary distros. I've used Arch/Manjaro extensively and can't agree that they are light in any sense except that the original install is a small base. After that their packages have the same extensive, all-inclusive, dependencies as Fedora. For me it was impossible to accept anything less than Funtoo for my last notebook installation (Toshiba Satellite with amd dual-core, radeon graphics - 4GB ram). I did want to know if everything was going to work so I got the latest Calculate Linux iso, partitioned the drive with a swap, two "root" parttiions and a home partition, installed Calculate KDE, and tested the wireless, trackpad, etc. Calculate could easily be the end of the line; it is built with Gentoo, uses standard emerge and allows you to build packages with your own USE flags if necessary. It is a really nice and very flexible binary distro that allows you to "lighten" it as much as you need. Of course it uses OpenRC. I suspect that it ticks all of your checkboxes. But to get exactly what I want, which is a system that uses openrc and avoids unnecessary or trouble-prone daemons (e.g. avahi, pulseaudio, dbus, kdepim, notifications) I build my own set of binary packages on my workstation and share those via http so that I can install Funtoo on the other partition, drawing packages from my own binary repo. In order to support different USE flags and CPU_FLAGS_X86 and CFLAGS in the repo than I have on my workstation I do the package building in a chroot, rather like is done with Poudriere for FreeBSD.
  6. No route to local network on new install

    Now I'm laughing... That was a silly question. :D But the answer is probably just as silly. I just haven't discovered my own silliness yet. Thank you for all of your inputs, it has been a really useful sanity check. I may just start over in a few days with a fresh stage3 and a fresh mind. [i've done a half dozen Funtoo installs in the past year and it has always proven to be a dead-simple and foolproof process with current or stable, hardened or not, pure64 or multiarch. They've all installed sweetly.]
  7. No route to local network on new install

    No. :( ping always complains of "No route to host" I even checked the Funtoo script /etc/init.d/netif.tmpl for changes but it is identical between the functioning and non-functioning installations. I haven't found any real difference between the good and bad systems, except that the bad system is a new install from a new stage3. I'm afraid of finding that I've done something really stupid (it would not be the first time), but I'm not seeing it.
  8. No route to local network on new install

    Here is the netif.eth0 config file I've been using on my previous install (which is ok) and my new install (which does not work): template="interface" ipaddr="192.168.1.1/24" gateway="192.168.1.254" nameservers="8.8.8.8 208.67.222.222" domain="launchmodem.com" Has it been wrong all along??
  9. No route to local network on new install

    Here's the addressing for my existing Funtoo installation (I'm accessing this forum using these settings) __> ip route default via 192.168.1.254 dev eth0 127.0.0.0/8 dev lo scope host 192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.1 So you see 192.168.1.254 is the address of my router, and 192.168.1.1 is the address of my workstation. So it still seems that my new installation is correctly setup and should be working. But isn't working. :blink:
  10. No route to local network on new install

    ip route actually says what we would expect for the interface: default via 192.168.1.254 dev eth0 127.0.0.0/8 dev lo scope host 192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.1 and netstat -r reports (after hanging for about a minute) Kernel IP routing table Destination Gateway Genmask Flags MSS Window irtt Iface default 192.168.1.254 0.0.0.0 UG 0 0 0 eth0 loopback 0.0.0.0 255.0.0.0 U 0 0 0 lo 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 These look ok. But I can't connect to or ping the other computers on the 192.168.1.0/255 network. Can't get out to the internet of course. This seems very weird to me... The eth0 interface is UP. The routing table is correct (but netstat hangs for a long time). The dns info is correctly in /etc/resolv.conf. And the network is not accessible: # ping 192.168.1.2 # my file server PING 192.168.1.2 (192.168.1.2) 56(84) bytes of data. From 192.168.1.1: icmp_seq=1 Destination Host Unreachable From 192.168.1.1: icmp_seq=2 Destination Host Unreachable From 192.168.1.1: icmp_seq=3 Destination Host Unreachable
  11. I've installed Funtoo Current core-i7 hardened onto an empty partition alongside my existing Funtoo system, and followed the usual easy steps http://www.funtoo.org/Funtoo_Linux_Networking for setting up a static interface on eth0, but there is no route to the local network. Everything boots ok. eth0 is UP with correct address and mask. resolv.conf looks good /etc/conf.d/netif.eth0 is the same as on my old (functioning) install BUT I can't ping other machines on my local network. netstat -r hangs for a long time and then does not show any entry for the local network. i.e. the line 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 is missing [EDIT: if I wait long enough that line is printed] BTW, the interface comes up functioning if I use dhcp instead of the static addressing (on this network dhcp is reserved for guests and assigns addresses that lack certain priviledges). I don't understand how the system (using the Funtoo networking scripts) can fail to create an entry in the routing table for the eth0 interface. Anyone have an idea what could be wrong? I've already come to the end of my knowledge and don't know how to proceed on this networking problem. I've even tried to copy my old /etc directory onto the new system for testing, editing the fstab of course. The new install still fails to bring up a functioning network (using same kernel config, same configuration files in /etc, same hardware).
  12. fails to update glibc to 2.19 (hardened profile)

    I definitely don't believe in magic, so it was embarrasing to report that the problem resolved with no apparent reason. Sometimes that suggests a race condition -- when I reported the problem I was "-j4" and I intended to check it with "-j1" but then it just compiled to completion with "-j4". Yes I'm using XFS for / but I compile in tmpfs. My report above shows PORTAGE_TMPDIR="/tmp", which is tmpfs, and notice that I don't use -pipe in my CFLAGS. (/home is on ZFS raidz.)
  13. fails to update glibc to 2.19 (hardened profile)

    Two days later: eix-sync && emerge -auvDN --quiet-build @world and everything updated. And I have no idea what the problem was. But it resolved itself.
  14. Why does it want to upgrade linux-headers?

    Yeah, it's Evil. It sometimes turns a person Evil. Be careful, don't read that last link, it could happen to you!
  15. Why does it want to upgrade linux-headers?

    I enjoy your stories. Thanks. I don't like emacs either :D and really like vim's modality. It makes a lot of sense so I use a vi mode inside emacs and am mostly happy with org / latex and still my beloved editing modes and ex commands. yeah, thank the holy ones for Funtoo as a haven of sanity. I once did extensive work on '386 and '486 control systems that could handle hundreds of tasks with guarenteed latency of under a millisecond. Now our thousand times faster systems are ten times slower. :< AND they crash...
×