Antti, I was able to get through the tutorial fine without needing a separate buildrump. I can edit the wiki in a bit if you want, but I'm going to keep playing around with it for a bit, just to make sure. Thanks, Robert On Thu, Feb 26, 2015 at 6:29 PM, Robert Gifford <robertgif@xxxxxxxxx> wrote: > Thanks for the quick response! I'll check it out and I'll let you know if > I have any other questions. > > Robert > > > Sent via the Samsung GALAXY S® 5, an AT&T 4G LTE smartphone > > > -------- Original message -------- > From: Antti Kantee <pooka@xxxxxx> > Date:02/26/2015 6:18 PM (GMT-05:00) > To: robertgif@xxxxxxxxx, rumpkernel-users@xxxxxxxxxxxxx > Cc: > Subject: Re: Kernel Development Tutorial > > On 26/02/15 21:56, Robert Gifford wrote: > > Good Evening > > > > I had a question concerning the Kernel Development tutorial on the > > rumpkernel wiki. I was curious as to why the tutorial has you download > both > > rumprun_posix and buildrump.sh as two separate directories? If > > rumprun_posix comes with its own buildrump.sh, why can't I just use that > > buildrump to edit my kernel driver source code? > > Robert, > > Good question, but my answer is better: I don't remember. > > There are 3 possible explanations: > > 1) I wasn't thinking when I wrote that tutorial. For such a glaring > thing, it's unlikely I wasn't thinking *that* much (though possible). > 2) The way buildrump.sh *was* run from rumprun-posix was not compatible > with carrying out the tutorial > 3) The way buildrump.sh *is* run from rumprun-posix is not compatible > with carrying out the tutorial > > If you think that a separate buildrump.sh is not necessary -- and I'm > not saying you are wrong -- the best thing is to try it out. The worst > that can happen is that you have to rm -rf the repo and start from scratch. > > If you can complete the tutorial, you can edit the wiki page and remove > the separate buildrump.sh bit. If not, you can edit the wiki and add a > short explanation of why you need both. Everyone wins ;) > > - antti >