hencb got a reaction from NikosAlexandris in Learning to create newer versions of e-builds
Ok there's quite a few outdated documents and command warnings that cause problems here.
First of, emerge <ebuildname>.ebuild from the current overlay directory tends to work. I generally don't use it since the ebuild
tool allows you to install a package just like emerge does, but it does this by going through different stages.
Let's start with the prerequisite: The manifest file.
You don't have to run ebuild *.ebuild manifest, just run ebuild <ebuildname>.ebuild manifest, which will generate a manifest for all ebuilds in the current directory. There's also repoman, which Gentoo uses, and which can create manifests as well: repoman manifest will create manifest entries for all ebuilds that don't have one already.
I highly recommend reading "man ebuild" on how to use the ebuild tool. It will make debugging ebuild problems a lot easier. A basic way to install a custom ebuild using the ebuild tool can be done like this, if the manifest is correct:
ebuild gdal-2.0.3.ebuild fetch (downloads the package and verifies that its integrity using the manifest file) ebuild gdal-2.0.3.ebuild unpack (downloads the package and untars it into /var/tmp/portage/sci-libs/gdal-2.0.3.ebuild) ebuild gdal-2.0.3.ebuild prepare (applies any patches and prepares the ebuild) ebuild gdal-2.0.3.ebuild configure (runs the configure script of autotools) ebuild gdal-2.0.3.ebuild compile (compiles the packages) ebuild gdal-2.0.3.ebuild install (this will install the package into a sandbox, that is, into /var/tmp/portage/sci-libs/gdal-2.0.3/image folder) ebuild gda1 qmerge (install the package into the system. At this point, the whole process is completed and is equivalent to running emerge) Some phases also include others. Typically, you'll skip the fetch and configure phase, they are included in the other commands (unpack and compile). I haven't listed some of the phases due to brevity. This is still a very verbose way to install an ebuild, and a bit tedious. A simpler way to use the ebuild tool is to run:
ebuild <ebuildname>.ebuild merge ,which is equivalent to running: emerge <ebuildname>.ebuild.
Consider reading both man ebuild (for the tool) and man 5 ebuild (for the ebuild syntax). They're the most accurate documents at the moment.
It seems somebody masked the newer versions of gdal for some reason. This needs further investigation. It might be a malformed mask and you should add an entry to package.unmask for the time being:
Drop by on IRC sometime and I'll be glad to assist you with any questions. Just ping me (bhenc) and I'll help you get started with the ebuilds. If you're unfamiliar with IRC, the www.funtoo.org/Getting_Help page might be a good place to start.
hencb reacted to captfrito in PXE Network Boot Server
I built a PXE server system as described at http://www.funtoo.org/PXE_network_boot_server
There were a few things I needed to do differently to get things to work even partially. For example, I needed to add these additional files to my /tftproot:
ldlinux.c32 libcom32.c32 libutil.c32 There is another quirk in that the initial menu displayed on the system that is trying to boot via PXE is allowing a 1,000sec timeout versus the 10sec I was expecting via the pxelinux.cfg/default file.
The issue I am having now is that I get all the way through the loading of the initrd=srcd/isolinux/initram.igz loading, but then the system trying to boot can never find the netboot=http://172.16.3.213/sysrcd.datfile. What happens instead is that the system booting completes the network configuration via the initrd but then reports
Searching for device with /sysrcd.dat It fails to find it, then tries to mount all the SATA partitions (3 disks with a total of 22 partitions among them), then reports again
!! Cannot find a device with /sysrcd.dat. Retrying... It does this several times, then gives up dumping me to a "mini shell".
I searched the at-large internet, and can't really find anything that helps.
I have tried offering the sysrcd.dat and the sysrcd.md5 files via apache and vsftp.
Here is the output from tcpdump:
bolan tftproot # tcpdump -n port 80 or port 69 dropped privs to tcpdump tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on eth0, link-type EN10MB (Ethernet), capture size 262144 bytes 18:58:46.837984 IP 172.16.3.229.2070 > 172.16.3.213.69: 27 RRQ "pxelinux.0" octet tsize 0 18:58:46.841925 IP 172.16.3.229.2071 > 172.16.3.213.69: 32 RRQ "pxelinux.0" octet blksize 1456 18:58:47.004463 IP 172.16.3.229.49152 > 172.16.3.213.69: 41 RRQ "ldlinux.c32" octet tsize 0 blksize 1408 18:58:47.018249 IP 172.16.3.229.49153 > 172.16.3.213.69: 63 RRQ "pxelinux.cfg/01-00-24-1d-27-ec-7f" octet tsize 0 blksize 1408 18:58:47.018995 IP 172.16.3.229.49154 > 172.16.3.213.69: 51 RRQ "pxelinux.cfg/AC1003E5" octet tsize 0 blksize 1408 18:58:47.019703 IP 172.16.3.229.49155 > 172.16.3.213.69: 50 RRQ "pxelinux.cfg/AC1003E" octet tsize 0 blksize 1408 18:58:47.020374 IP 172.16.3.229.49156 > 172.16.3.213.69: 49 RRQ "pxelinux.cfg/AC1003" octet tsize 0 blksize 1408 18:58:47.021047 IP 172.16.3.229.49157 > 172.16.3.213.69: 48 RRQ "pxelinux.cfg/AC100" octet tsize 0 blksize 1408 18:58:47.021758 IP 172.16.3.229.49158 > 172.16.3.213.69: 47 RRQ "pxelinux.cfg/AC10" octet tsize 0 blksize 1408 18:58:47.022460 IP 172.16.3.229.49159 > 172.16.3.213.69: 46 RRQ "pxelinux.cfg/AC1" octet tsize 0 blksize 1408 18:58:47.023147 IP 172.16.3.229.49160 > 172.16.3.213.69: 45 RRQ "pxelinux.cfg/AC" octet tsize 0 blksize 1408 18:58:47.023822 IP 172.16.3.229.49161 > 172.16.3.213.69: 44 RRQ "pxelinux.cfg/A" octet tsize 0 blksize 1408 18:58:47.024459 IP 172.16.3.229.49162 > 172.16.3.213.69: 50 RRQ "pxelinux.cfg/default" octet tsize 0 blksize 1408 18:58:47.025334 IP 172.16.3.229.49163 > 172.16.3.213.69: 42 RRQ "vesamenu.c32" octet tsize 0 blksize 1408 18:58:47.028685 IP 172.16.3.229.49164 > 172.16.3.213.69: 42 RRQ "libcom32.c32" octet tsize 0 blksize 1408 18:58:47.047745 IP 172.16.3.229.49165 > 172.16.3.213.69: 41 RRQ "libutil.c32" octet tsize 0 blksize 1408 18:58:47.053732 IP 172.16.3.229.49166 > 172.16.3.213.69: 50 RRQ "pxelinux.cfg/default" octet tsize 0 blksize 1408 18:58:47.283029 IP 172.16.3.229.49167 > 172.16.3.213.69: 43 RRQ "netboot-1.png" octet tsize 0 blksize 1408 And here's what happens when I wget the files directly:
vaughan ~ # wget 172.16.3.213/sysrcd.md5 . --2017-01-05 23:44:04-- http://172.16.3.213/sysrcd.md5 Connecting to 172.16.3.213:80... connected. HTTP request sent, awaiting response... 200 OK Length: 45 [application/x-md5] Saving to: 'sysrcd.md5' sysrcd.md5 100%[=======================================================================================================================================================>] 45 --.-KB/s in 0s 2017-01-05 23:44:04 (11.8 MB/s) - 'sysrcd.md5' saved [45/45] --2017-01-05 23:44:04-- http://./ Resolving .... failed: No address associated with hostname. wget: unable to resolve host address '.' FINISHED --2017-01-05 23:44:04-- Total wall clock time: 0.02s Downloaded: 1 files, 45 in 0s (11.8 MB/s) Not sure what is happening here, any help is gratefully accepted (-:
hencb reacted to hjozwiak in Converting From Gentoo to Funtoo
I am a blind Gentoo user who is looking to switch to Funtoo on account of issues with my Alienware laptop, and I have a few questions to ensure that I can hop the fence.
1. What kernel best supports the Alienware hardware, and, more importantly, has speakup available out of the box?
2. Where can I find the list of available ebuilds, most importantly, app-accessibility/espeakup and app-accessibility/orca?
hencb reacted to drobbins in Converting From Gentoo to Funtoo
Hi, and thanks for considering Funtoo. I think that debian-sources is the best kernel to use. It does have speakup modules enabled by default.
99% of the ebuilds in Funtoo are identical to those in Gentoo. So, both the ebuilds you mention are available and come direct from Gentoo. The best way to get a list of available ebuilds is to grab our Portage tree via git and look at its contents into the funtoo branch.
The greatest challenge for installing Funtoo would be to find a LiveCD that has speakup support for the installation process. As long as you know of a good livecd with speakup support that gives you a bash shell and has all the necessary commands for installation (which basically is just your mkfs commands of choice and fdisk or gdisk, and chroot, and can establish a network connection) then you should be ready to go.
hencb reacted to rspartz in Error 403: Forbidden downloading a 'snapshot' from either mirror
Great! Thank you hencb, I appreciate it!
hencb reacted to Sandro in Error 403: Forbidden downloading a 'snapshot' from either mirror
I might add that ... in case of problems with "timing", there are more "ways" :)
# Cd /usr/portage && git reset --hard && emerge --sync or drastically
# rm -rf /usr/portage && emerge --sync Clearly occur before the connection is available .. otherwise be necessary to re-perform the chroot in this case (II) _'_
hencb got a reaction from AdiosKid in Stages4 and a LiveDVD
This could be done in a smaller fashion to include a general 64bit subarch instead of a plethora of stage4s.
The complexity goes through the roof when we consider the number of subarches Funtoo currently supports:
We'd have to compile at least 4x (LXDE, XFCE, KDE and GNOME desktops) the number of subarches to create every
That's not really realistic.
Creating a stage4 that could be a general 64 bit architecture to install on a system through a GUI could be sensible. Reviewers
generally loose patience when they review source-based distributions. This could bridge the gap and allow them to compile
and tweak smaller packages without spending hours on compiling.
Bottom line is: There's no distribution that offers such a wide variety of stage3s optimized for different hardware. I'd much rather
expand our reach into the embedded market with IoT and mobile devices. Except for android, it's mostly uncharted territory.
YOCTO should not have to exist when we have a source-based distribution that can produce stage4s with ease.
There's no reason why a Funtoo Linux Live CD should be needed if the Gentoo Linux one works fine: we share bug fixes with
Gentoo and remain largely intercompatible , and we shouldn't have to duplicate the effort put into managing a Live CD without any need.
Fragmentation in the Linux community is a plague; let's not create another split between distributions if we don't have to.
hencb reacted to AdiosKid in Stages4 and a LiveDVD
Hi folks, I create a article on (vivaolinux) is a great forum about Linux and software on Brazil.
link : https://www.vivaolinux.com.br/topico/Funtoo/LiveDVD-e-Stage4-para-o-Funtoo
is not a article but more a ideia to request users to help to make that ideia real.
so, that is the resume of the text :
I'm a Funtoo user about 2 years and Gentoo user one year before and I think that missing a Livedvd to Funtoo and Stages4 with more packges as "Xorg" or some desktop as "Plasma 5"
Gentoo has now "again" a LiveDVD
Gentoo LiveDVD : http://gentoo.mirrors.tds.net/pub/gentoo//releases/amd64/20160704/
and Stages4 to Cloud :
the Area31 has a Livecd too, but is not like I talk about :
so, the question is reduse the time to install the system of course more one option not change to a easy system like sabayon as a example.
but has stages with more packges and few desktops, to make the installation more faster, of course all of this optimized by arch as the current Stages3 that Funtoo has
and a liveDVD as Gentoo with a installer, to new users, again as other option beyond CLI
to make the Distro more popular, to explore more the potention of this amazing distro.
so what your members think about it ?
hencb got a reaction from drobbins in Getting Rid of Forums and Moving to Reddit?
I think it's a good idea,
- If it lowers the strain on you guys and allows you to focus on more important issues, I'm all for it.
- More exposure is great.
But there are downsides (or rather, issues to be resolved):
this one hurts the most in the long run. Can we connect reddit to the chat in the same way the bugtracker and git commits are
integrated into the chat? Reddit might be more interested in displaying ads than helping us with using their platform. And you
cannot display ads to an automated script.
- How do you create backups of reddit posts?
I mean, not everyone posts to the bug tracker, and if for example a bug is resolved in a reddit post, how do you index that?
I've heard of mailing lists containing priceless information on the fine details of how a distro works, without backups. If you loose
the mailing list, you'd be in serious trouble.
- How do you distinguish real funtoo users from gentoo users on reddit?
I'm not against them helping people, but I really would like some visual identification that someone actually using funtoo is
replying to issues. The more funtoo diverges from gentoo (like the epro profiles) the more we'll be in trouble with gentoo
users assuming they know what they are doing.
If I see a reddit post, I really want to be able to glance at a reddit post and see that a funtoo user responded.
Also, there are also guides on the funtoo forums on how to setup stuff e.g.:
- If we're in the same boat as reddit, we also inherit the reddit community
All the trolling, spamming, DDoSing etc. If reddit goes down (hell, github was taken
down some time ago) do I loose anything?
I think they shouldn't be lost, A half-decent backup would be great.
But I'd make a good backup of the forums and store it somewhere safe.
This is a serious issue: reddit is a company and should be distrusted in the same manner as any other company.
They're not a community: they are a company.
I'd recommend to do a complete search on the bad sides of reddit, and to do it with multiple search engines.
I'd post more but I'm kinda strapped for time this week.
TL;DR I'm for it, but make sure you're aware of the disadvantages.
hencb reacted to drobbins in How we're keeping our users at the center of the Funtoo Universe
Hey everyone, I've written up a news item detailing all the stuff that's going on with Funtoo to keep it focused on you, our users. Give it a read: