ruby ports and PREFIX
So, what I'm doing here is experimenting with encap, a nifty little
package standard where the idea is that you install your software with
PREFIX set to /usr/local/encap/pkgname-version, and the package manager,
epkg, will look through that dir and symlink files from that hierarchy
in to /usr/local for you. It makes stuff like identifying the source of
a file, or rolling back to an earlier version of a software package,
downright trivial,
Of course, in terms of FreeBSD, I like to use ports to build packages,
so I've patched up bsd.port.mk to re-define PREFIX for intallations, and
run the package manager after install completes, etc. Most ports work
really well, assuming they honor PREFIX.
Which, ruby add-ons do not seem to do. For example, optparse:
do-install:
${MKDIR} ${RUBY_SITELIBDIR}/${PORTNAME}
${INSTALL_DATA} ${WRKSRC}/optparse.rb ${RUBY_SITELIBDIR}/
${INSTALL_DATA} ${WRKSRC}/optparse/*.rb ${RUBY_SITELIBDIR}/${PORTNAME}/
What the heck is that? On my test system, the RUBY_SITELIBDIR is
defined by interrogating RUBY, and the result is
/usr/local/encap/ruby-1.6.7.2002.05.02p/lib/ruby/site_ruby/1.6 ... what
I REALLY want is for the Port to install files based on PREFIX,
/usr/local/encap/ruby-optparse-0.8.6, and then I will link them in to
the proper ruby site directories which contain files in /usr/local
symlinked to their appropriate source packages.
A few questions:
1) Shouldn't the ruby add-on ports honor PREFIX?
2) To that end, is there a good way to define RUBY_SITELIBDIR and
friends in bsd.ruby.mk to honor PREFIX?
3) Once I symlink new files in to the ruby file hierarchy, so I have to
do any magic for Ruby to pick up to this fact? Is ruby going to do
anything troublesome like go looking in the encap directory it was built
for, instead of /usr/local?
Thanks,
-danny
--
http://dannyman.toldme.com/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-hackers in the body of the message
Re: creating an fdisk partition in an automated way
On Sat, Apr 07, 2001 at 07:31:18PM -0700, Doug White wrote:
On Fri, 6 Apr 2001, dannyman wrote:
On Wed, Apr 04, 2001 at 08:58:12PM -0700, Doug White wrote: [...]
fdisk -I is your friend. (DANGER: THIS IS DESTRUCTIVE -- READ THE MAN
PAGE FIRST!)
Yeah ... I use it. It seems to do the right thing. Then disklabel
doesn't work. :
Well, I should have commented that for best results, dd if=/dev/zero
of=/dev/${DISK} count=32 to make sure there's no leftovers for anything to
trip on.
Hehehe, yeah done already tried that. Now I'm thinking maybe take the first
64 blocks of a dick I know is good and use that as my fdisk -I. :/
Well, we'll see on Monday.
Thanks,
-danny
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
Re: creating an fdisk partition in an automated way
On Wed, Apr 04, 2001 at 08:58:12PM -0700, Doug White wrote:
[...]
fdisk -I is your friend. (DANGER: THIS IS DESTRUCTIVE -- READ THE MAN
PAGE FIRST!)
Yeah ... I use it. It seems to do the right thing. Then disklabel doesn't
work. :
I'm looking like this:
#!/bin/sh
disk='da0'
fdisk -I ${disk}
disk=${disk}s1
disklabel -r -w $disk auto
Disklabel pukes. I've found a similar case at:
http://groups.google.com/groups?q=%22cannot+find+label%22+%22no+disk+label%22+fdiskhl=enlr=safe=offrnum=1seld=972266336ic=1
I emailed Matt Dillon to see if he solved the problem. You have no idea, eh?
Or do you do something slightly different? These commands work great if I run
sysinstall over to DTRT at first, but on a virgin bare disk, ... nada. :
Thanks,
-danny
--
http://dannyman.toldme.com/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
creating an fdisk partition in an automated way
Ooookay ... So, I gave up on sysinstall and wrote a script that beautifully runs disklabel and newfs slices for me, writing an fstab and installing packages after starting off a PXE boot. It is just COOL! Now all my test machines wont boot. The hard disk boot just doesn't DO anything, and the pxeboot crashes once it sees the SCSI disk. Best I can tell from some Deja searches, this is related to the Adaptec controller reviling at the thought of a "dangeously dedicated" disk. But I can not for the life of me figure out how to do it the right way. Because it's cute, I attach my script. I've tried changing disk to da0s1 and it works JUST FINE on another IDE-based system on its spare SCSI disk, but gets upset at me when I try to run the disklabel commands on my test machines. I believe I need to do something with fdisk but I can not fathom quite what it is from the man page. The working disk looks like so: 0-17:55 root@cronic /usr/local/share/netboot# fdisk da0 *** Working on device /dev/da0 *** parameters extracted from in-core disklabel are: cylinders=1115 heads=255 sectors/track=63 (16065 blks/cyl) Figures below won't work with BIOS for partitions not in cyl 1 parameters to be used for BIOS calculations are: cylinders=1115 heads=255 sectors/track=63 (16065 blks/cyl) Media sector size is 512 Warning: BIOS sector numbering starts with sector 1 Information from DOS bootblock is: The data for partition 1 is: sysid 165,(FreeBSD/NetBSD/386BSD) start 63, size 17912412 (8746 Meg), flag 80 (active) beg: cyl 0/ sector 1/ head 1; end: cyl 1023/ sector 63/ head 254 The data for partition 2 is: UNUSED The data for partition 3 is: UNUSED The data for partition 4 is: UNUSED The SCSI drives on my test machines, larger Seagates, start out similar, but they have their goods in partition 4. In their previous lives they were Solaris x86 boxen, which is why I figure the sysid 165 stuff looks the same. :) Can someone please clue me in? :) Thanks, -danny -- http://dannyman.toldme.com/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: tuning a VERY heavily (30.0) loaded server
On Tue, Mar 20, 2001 at 09:50:51AM -0800, Matt Dillon wrote: One thing that comes to mind is that you can smarthost your outgoing email to another host so the queues don't build up. This should greatly reduce mail load. In fact, I would recommend offloading email entirely if possible... email always hits disks hard. Definitely get rid of MFS. MFS wastes 2x the memory allocated to it. Use a softupdates-enabled filesystem in place of MFS, or use a swap-backed VN-based partition with softupdates enabled. Alfred's vmiodirenable suggestion is a good one. [...] This might make a tiny help: mount things -noatime? If you are reading the same files over and over and over again you needn't bother WRITEing an atime ... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
No Subject
Has anyone patched 4.x OpenSSH and/or the relevant ports to deal with the CRC checksum exploit? I've got to get 2.3 working on my 3.x box, but just incrementing the number in the Makefile causes patch-aa to go rejected ... -d -- http://dannyman.toldme.com/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: your mail
On Fri, Feb 09, 2001 at 02:03:28PM -0800, dannyman wrote: Has anyone patched 4.x OpenSSH and/or the relevant ports to deal with the CRC checksum exploit? I've got to get 2.3 working on my 3.x box, but just incrementing the number in the Makefile causes patch-aa to go rejected ... Ohhh, fat fingers. Meant to pester -security. -d To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: nslookup deprecation [was 4.2 complaint]
On Tue, Dec 05, 2000 at 11:48:26AM -0500, Brandon Fosdick wrote: Dag-Erling Smorgrav wrote: Yusuf Goolamabbas [EMAIL PROTECTED] writes: Recently there was a message indicating that ISC is deprecating nslookup. "Recently"? nslookup has been officially deprecated for about a year and a half, I believe. Will a replacement be added to the base distro? When? The host(1) man page dates from late 1994. -danny To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
specifying probe order for scsi controllers
so, i have a production system with an ncr0 to which i would like to add an aha0 in addition to the existing controller. when i do this, though, the aha0 comes up before the ncr0, so the numbering on the system disk gets thrown off. i tried changing the fstab entries for the system disk, but the slices for da1s1 weren't MAKEDEV'ed and apparently you can not MAKEDEV the slices within the partition ... perhaps that is because my existing da1 is a dedicated disk? nyways, can I specify the order in which these controllers come up in the system? i had guessed that you could based on the admonition about ISA ethernet probe orders ... but by default the ncr0 is listed first. or is there some way i can config things to keep da0 on the ncr and da1 on the aha? thanks, -danny -- come.to/dannyman To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Using legacy sysinstall to upgrade live system
On Sat, Aug 14, 1999 at 12:29:42PM +0200, Sheldon Hearn wrote: On Fri, 13 Aug 1999 17:51:10 MST, dannyman wrote: Uhmmm, what if we don't have a floppy drive? Then you probably have a CDROM drive or a network interface, both of which can be used to get sysinstall onto your machine. :-) The point of it is, it's easy enough to download the floppies, but it's really hard to boot a system off an .flp image. :p Or, the real point of it is, that aside from "make world from source" there is no good way to update an existing system without doing something lame like having to boot ... off ... a floppy ... uncompressing kernel ... please wait ... But, on to my original question, has anybody been looking at a more "user friendly" "upgrade the darn thing *REAL EASY*" kind of setup? maybe invoke a networked pkg_add to run the latest sysinstall w dependencies? -dman -- dannyman - http://www.dannyland.org/~dannyman/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Using legacy sysinstall to upgrade live system
On Sat, Aug 14, 1999 at 12:29:42PM +0200, Sheldon Hearn wrote: On Fri, 13 Aug 1999 17:51:10 MST, dannyman wrote: Uhmmm, what if we don't have a floppy drive? Then you probably have a CDROM drive or a network interface, both of which can be used to get sysinstall onto your machine. :-) The point of it is, it's easy enough to download the floppies, but it's really hard to boot a system off an .flp image. :p Or, the real point of it is, that aside from make world from source there is no good way to update an existing system without doing something lame like having to boot ... off ... a floppy ... uncompressing kernel ... please wait ... But, on to my original question, has anybody been looking at a more user friendly upgrade the darn thing *REAL EASY* kind of setup? maybe invoke a networked pkg_add to run the latest sysinstall w dependencies? -dman -- dannyman - http://www.dannyland.org/~dannyman/ To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: Using legacy sysinstall to upgrade live system
On Wed, Aug 11, 1999 at 12:07:41AM -0700, Jordan K. Hubbard wrote: The use of /stand/sysinstall to do a live upgrade has always been discouraged, though it's not outright disallowed since I believe in every man's right to blow his feet off if he really wants to. Nonetheless, for the expected installation experience one is encouraged to boot the desired OS release's installation media and select an upgrade instead of a new install. Uhmmm, what if we don't have a floppy drive? I suggested my colleague score /stand/sysinstall off one of my 3.2 systems so he could upgrade his 3.1. Has there been though put in to making a net-able upgrade set, maybe you have a sysinstall which pops the new kernel in to place, reboots into sysinstall like a floppy, and then gets ready to upgrade. Maybe we could use an MFS floppy? Might be a fun project to take on ... can one reboot into an MFS partition, or how hard would it be to try a "reboot system into upgrade floppy" without trashing the underlying system, in case the user wanted to bail ... maybe a kernel that chroot's itself into an /upgrade directory? Thoughts? -dman -- dannyman - http://www.dannyland.org/~dannyman/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Using legacy sysinstall to upgrade live system
On Wed, Aug 11, 1999 at 12:07:41AM -0700, Jordan K. Hubbard wrote: The use of /stand/sysinstall to do a live upgrade has always been discouraged, though it's not outright disallowed since I believe in every man's right to blow his feet off if he really wants to. Nonetheless, for the expected installation experience one is encouraged to boot the desired OS release's installation media and select an upgrade instead of a new install. Uhmmm, what if we don't have a floppy drive? I suggested my colleague score /stand/sysinstall off one of my 3.2 systems so he could upgrade his 3.1. Has there been though put in to making a net-able upgrade set, maybe you have a sysinstall which pops the new kernel in to place, reboots into sysinstall like a floppy, and then gets ready to upgrade. Maybe we could use an MFS floppy? Might be a fun project to take on ... can one reboot into an MFS partition, or how hard would it be to try a reboot system into upgrade floppy without trashing the underlying system, in case the user wanted to bail ... maybe a kernel that chroot's itself into an /upgrade directory? Thoughts? -dman -- dannyman - http://www.dannyland.org/~dannyman/ To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: Budget on user-ppp
On Tue, Jul 06, 1999 at 12:20:00AM +0200, Leif Neland wrote: It could be nice with some sort of budget control in ppp. A few days ago I found out bb caused a dialup every 5 minutes. Today I found I had been online 27 hours uninterrupted. Some dialup-routers allows a setup of max a connects/b minutes online over c hours. I had things set up so that the users on my system could bring up ppp at will, and bring it down. I also had /etc/daily bring up ppp when it needed it. The problem being, of course, that the on-demand stuff gets pretty nasty at times ... *shrug* -- dannyman - http://www.dannyland.org/~dannyman/ To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: GRE encapsulation under FreeBSD 3.2
On Wed, Jun 30, 1999 at 03:35:42PM -0700, Ron 'The InSaNe One' Rosson wrote: Does this mean NATD/VPN using the -pptpalias will work for the clients that are using M$ VPN? If so, the sooner the better for me. I second that but I'm in no particular hurry there. Supporting CHAP could be a pain? -d -- dannyman - http://www.dannyland.org/~dannyman/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: GRE encapsulation under FreeBSD 3.2
On Wed, Jun 30, 1999 at 03:35:42PM -0700, Ron 'The InSaNe One' Rosson wrote: Does this mean NATD/VPN using the -pptpalias will work for the clients that are using M$ VPN? If so, the sooner the better for me. I second that but I'm in no particular hurry there. Supporting CHAP could be a pain? -d -- dannyman - http://www.dannyland.org/~dannyman/ To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
