Hi This bug contains an ebuild for netkit-bootparamd-0.17 Bootparamd is an Sun RPC server which sends netboot parameters to Sun SPARC machines. The server is a part of linux-netkit. You can find it`s home repository at ftp://ftp.uk.linux.org/pub/linux/Networking/netkit I suggest putting it into net-misc where other netboot related ebuilds are.
Created attachment 132558 [details] netkit-bootparamd-0.17.ebuild
Uhm, net-misc/netkit-bootpd-0.17-r1 already provides this.
(In reply to comment #2) > Uhm, net-misc/netkit-bootpd-0.17-r1 already provides this. > Unfortunately, it doesn`t. The netkit-bootpd package implements the BOOTP protocol and netkit-bootparamd is a bootparams RPC server. See below: richese ~ # bootparamd richese ~ # rpcinfo -p | grep bootparam 100026 1 udp 873 bootparam Bootparam is used by the Solaris network installer to get the location of package sources or rootfs mount options - see http://znark.com/tech/solarisinstall.html This is very different from BOOTP which can only provide information about netmasks, gateways, DNS servers, TFTP boot images and other network-related parameters (similar to DHCP).
(In reply to comment #3) > (In reply to comment #2) > > Uhm, net-misc/netkit-bootpd-0.17-r1 already provides this. > > > > Unfortunately, it doesn`t. The netkit-bootpd package implements the BOOTP > protocol and netkit-bootparamd is a bootparams RPC server. Did you try to install it? I guess not. :)
> > Unfortunately, it doesn`t. The netkit-bootpd package implements the BOOTP > > protocol and netkit-bootparamd is a bootparams RPC server. > > Did you try to install it? I guess not. :) Yes, I did install both of them. I`ve even checked the source of both packages :). And I`m pretty sure, that netkit-bootpd and netkit-bootparamd do different things. They even listen on different ports, have different protocols and read different parameters from different files. I`m not trying to be pesky about this, I simply wanted to offer others the solution to a problem I`ve encountered. If the issue is maintenance burden for this ebuild (which I believe is close to 0) then so be it. It`s not the world`s most popular software so it may not be worth the effort. But netkit-bootpd *doesn`t* provide the functionality netkit-bootparamd has.
Well, I seriously don't know what you installed, because netkit-bootpd-0.17-r1 installs bootparamd/rpc.bootparamd from the *exact* *same* tarball that your ebuild does. No, 2.4 doesn't provide it but noone wanted to rename/move the ebuild, shrug. See Bug 124510.
Reopen this to get rid of this confusion caused by mishandling of Bug 124510. - 0.17-r1 installs netkit-bootparamd, *not* netkit-bootpd (see Bug 124510 and this one wrt the mess). - Meanwhile, someone punted 0.17-r2 thinking it's unneeded keyword-wise, which is causing a regression wrt Bug 63940, the patch got lost. Solution: - restore net-misc/netkit-bootpd-0.17-r2, move <=net-misc/netkit-bootpd-0.17-r2, to net-misc/netkit-bootparamd, stabilize 0.17-r2 - stabilize net-misc/netkit-bootpd-2.4 to get a stable version of the real app, which it is supposed to install, not of a different package.
@mips/ppc/sparc/x86 - plz. stabilize net-misc/netkit-bootpd-2.4 meanwhile, until I get someone to handle the rest of this bug. @hppa - your keyword went MIA between (now removed netkit-bootpd-0.17-r2) and 2.4, do you want to re-add yourself?
x86 stable
(In reply to comment #8) > @hppa - your keyword went MIA between (now removed netkit-bootpd-0.17-r2) and > 2.4, do you want to re-add yourself? There seems to be a ~hppa in place for 2.4. I think we might wait for a user to ask us to stabilise.
ppc stable
(In reply to comment #10) > There seems to be a ~hppa in place for 2.4. I think we might wait for a user to > ask us to stabilise. As noted above, that's a completely different package. :) To restate - 0.17 is netkit-bootparamd, 2.4 is netkit-bootpd, so you might want to re-keyword 0.17
Marked net-misc/netkit-bootpd-0.17-r1 ~hppa. Now stop confusing me. :)
Closing.
