On Thu, Aug 05, 2004, Alexander Belck wrote:
I don't know exactly what is needed for the openpkg_binaryies.
I set up the sugested opa() function and after login I issue opa /opkg.
That works nice, but if I need to execute a bin without login ?
Is it fine to give the full path for the openpkg
On Thu, Aug 05, 2004, Alexander Belck wrote:
Is there any plan to include FreeRadius in OpenPKG ?
[...]
We have a freeradius package in OpenPKG-CURRENT since 2 weeks. It is a
little bit weak in build-time portability and not still well tested by
us under run-time, but try it out and feel free
On Thu, Aug 05, 2004, [EMAIL PROTECTED] wrote:
Whats needed to put freeradius under ftp.openpkg.org/release/2.1/SRC/PLUS/ ?
Well, there _is_ a freeradius package, but only in
ftp://ftp.openpkg.org/current/SRC/ because it is still
not part of any release...
On Thu, Aug 05, 2004, Alexander Belck wrote:
1st) Is OpenPKG ver of bind chroot enabled (-t chrootdir) ?
No, not out of the box. If you really want this you have to establish your
own chroot(2) environment under /foo for BIND and use bind_flags=... -t
/foo ... in rc.conf.
2nd) opkg_bind uses
On Thu, Aug 05, 2004, Bill Campbell wrote:
On Thu, Aug 05, 2004, Alexander Belck wrote:
Some perl scripts use #!/usr/bin/perl
I recommend you replace that with /opkg/bin/perl.
Could I just symlink ln -s /opkg/bin/perl /usr/bin/ ?
I do not recommend replacing such a critical part of the OS
I thought that being able to use the most up to date version of perl should
avoid bug or security problems corrected in newer versions (while correct
scripts should further run as the language syntax and standarts should not
change).
Yes, but it can also break existing scripts that depend on
