Date: Fri, 19 Apr 2002 10:30:10 -0700 From: "Drew Tomlinson" <drew@mykitchentable.net> To: <questions@freebsd.org> Subject: Re: Tracking Source on Multiple Machines (Was Re: FreeBSD Security Advisory FreeBSD-SA-02:21.tcpip) Message-ID: <006a01c1e7c7$db6f57e0$0301a8c0@bigdaddy> References: <01c501c1e7af$41de8640$0301a8c0@bigdaddy>
next in thread | previous in thread | raw e-mail | index | archive | help
----- Original Message -----
From: "Ken McGlothlen" <mcglk@artlogix.com>
To: "Drew Tomlinson" <drew@mykitchentable.net>
Cc: "Brett Glass" <brett@lariat.org>; "Christopher Schulte"
<schulte+freebsd@nospam.schulte.org>
Sent: Friday, April 19, 2002 10:06 AM
Subject: Re: Tracking Source on Multiple Machines (Was Re: FreeBSD
Security Advisory FreeBSD-SA-02:21.tcpip)
> "Drew Tomlinson" <drew@mykitchentable.net> writes:
>
> | > Then, on the machines you want to keep updated, you'd mount
/usr/src and
> | > /usr/obj from that build machine.
> |
> | I've tried this by mounting with shlight. Although not NFS, the
principle is
> | the same, right?
>
> Should be, but I don't know. I've never used shlight.
>
> | I actually do the make installkernel part first because that's the
"official"
> | way, IIRC.
>
> Is it? I recall the other way, and it makes sense to me because
having all the
> core libraries and everything updated before you updated the kernel
makes more
> sense. But I guess I should research that before I go spouting my
mouth off;
> it's been long enough since I've looked at that part of the
installation
> instructions that I may have forgotten or messed up.
I just checked. From /usr/src/UPDATING:
To update from 4.0-RELEASE or later to the most current
4.x-STABLE
----------
make buildworld
make buildkernel KERNCONF=YOUR_KERNEL_HERE
make installkernel KERNCONF=YOUR_KERNEL_HERE
reboot (in single user) [1]
make installworld
mergemaster [2]
reboot
> | cd /usr/src/include/../sys; install -C -o root -g wheel -m 444
> | cam/*.h /usr/include/cam
> | Illegal instruction - core dumped
>
> Now, THAT is a very odd place for an illegal instruction. Does it
die
> consistently there every time?
Yes, every time.
> | If I do the cd /usr/src/include/../sys ... command by hand I don't
receive an
> | error. If I build on the actual machine, the installworld process
runs just
> | fine. Any ideas why I'm having trouble? Is there some reason
shlight (smb)
> | mounts won't work while NFS will?
>
> It's conceivable. If shlight has some sort of odd namespace limits,
or does
> EOL translation, or somesuch, it could be. NFS at least is a Unixy
protocol
> between Unixy boxes, whereas shlight/Samba has to look at things
through a FAT
> lens. But I haven't done it (in fact, I don't even have any Windows
boxes
> around anymore, so I don't even run Samba), and so I'm a poor person
to advise
> in this case.
I'm still pretty green with FBSD and have never submitted a PR as
anytime something doesn't work, I just assume it's me. Would this be
something to submit in a PR? Or am I asking the OS to do something
more than it was designed to do. Or is it not appropriate as it might
be a shlight problem?
> | I'd really like to get this resolved so I don't have to continue
to run
> | builds on my poor old 486. :)
>
> Ugh. Understandable. Could you try it with NFS and see if the
results are
> different?
I guess I could as this is just my home network. Because I've come
from a Windows environment, my desktops are Win machines so I've kept
the file sharing on smb connections for simplicity, even between the
FBSD firewall (the 486) and FBSD network server (running Samba).
Thanks for your response. Maybe someone whose a little more familiar
with smb connections will respond.
Drew
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?006a01c1e7c7$db6f57e0$0301a8c0>