Longer version: to trod on some well-worn ground here, I'm able to get my
Apple IIe (with Workstation Card attached to AsanteTalk bridge) to log in
and access volumes shared by netatalk 2.0.5 on Ubuntu 10.04, on my MacBook
(either natively or in Parallels). Yay.
But now I want it to netboot, and I am stuck. Boo. I can get it to find the
server and the Apple //e boot blocks and get as far as the login
application. I can login as my user or guest, and I get the option of which
volume I want. I choose A2BOOT, which contains the system image that Marsha
Jackson (via Steven Hirsch) provided. And then I get: Your startup
configuration has not been set up properly. Contact the network
administrator.
I can't figure out what's going wrong; it seems like I figured out the hard
parts, and now there's a baffling endgame. One suspicion I have is that
AppleShare 3 actually let you specify the path of what gets run upon login
(e.g. /myshare/SYSTEM/BASIC.SYSTEM); I can't find any way to do the same
with netatalk. (Though if that path is invalid, the login client politely
lets you know about it, and that's not happening with the error I'm
getting.)
A couple of posts by Steven Hirsch seemed relevant, such as this:
http://groups.google.com.au/group/comp.sys.apple2/msg/a0bb6b3c1a77d8e6
I tried to follow it but it turns out there are some significant differences
between netatalk 2.0.3 (which he used) and 2.0.5, and it looks like his
contributions to a2boot were added to 2.0.5. I tried to build 2.0.3 per his
instructions, but it had a compile error related to the database, so I have
to try to build an older version of that, or perhaps try Ubuntu 6.06 as he
did (though that feels like working backwards).
Thanks for any help.
--- news://freenews.netfront.net/ - complaints: ne...@netfront.net ---
Why don't you grab the package (binary or source) from the a2 google group?
The Ubuntu source package ought to build without any problems.
Geoff
On 9/7/10 9:15 PM, in article Y7mdnYqQiIEwfhvR...@giganews.com,
"Steven Hirsch" <snhi...@gmail.com> wrote:
> Why don't you grab the package (binary or source) from the a2 google group?
> The Ubuntu source package ought to build without any problems.
Oh, hi, Steven! Thanks for responding.
I ran into several hiccups (like a libdb-4.2 dependency) trying to use your
binary or source under Ubuntu 10.04, so before trying to figure those out, I
figured I'd first try to exactly replicate what you had working. So I
installed Ubuntu 6.06, grabbed your modified netatalk 2.0.3 from the google
group, and I installed the .deb package (after first installing its various
dependency packages -- cracklib, libssl-dev, libdb4.2-dev, and others). I
then used your configuration files (I even created a user called "hirsch"
just for grins), and put Marsha's system startup files in /home/A2BOOT.
The result? Exactly the same: "Your startup configuration has not been set
up properly. Contact the network administrator."
Weird. Network boot, AppleShare client launch, and logon authentication is
clearly succeeding both in my original setup, and the one designed to mimic
yours. But then the software seems to expect something from the server it's
not getting. I assume the problem must lie in the A2BOOT folder, but I've
tried everything I can think of in there. Do you know which path/file the
server tells the software to run upon login? I'm assuming
/SHARENAME/BASIC.SYSTEM, but it ain't happening. I trawled around the source
but couldn't find anything obvious at first pass. Also, /var/log/syslog
doesn't reveal anything interesting, though I may need to rebuild with
--enable-debug (and then would there be anything else I need to do?)
Any thoughts would be much appreciated.
Thanks for the response, Geoff -- this is an good clue.
Of course I'd love to have your help, but if you could tell me a little more
about the ATINIT file, that would be a great start. Can I take the one on
the Workstation Disk and put it somewhere within the netatalk or shared
volume folder structure? Or something like that? What does your folder
structure look like?
Thanks,
Ivan.
> I ran into several hiccups (like a libdb-4.2 dependency) trying to use your
> binary or source under Ubuntu 10.04
Thanks for the heads-up. I'll take a look at that.
ie
/Volume/Users/userid/Setup/atinit
It's possible to get older binaries to behave on newer Ubuntu
installs, you just have to find the old libc packages -- I had to pull
some from a redhad rpm and use alien to convert it to a .deb package.
(I did this for something unrelated to what you guys are working on,
but same concept...)
Is there a possible permissions issue? Anything interesting in the
logs (/var/log)?
Second to all of that, has anyone tried the Jaunty packages for
netatalk? They're in the main repo:
http://packages.ubuntu.com/jaunty/netatalk
-Brendan
No, nothing to report there.
> Second to all of that, has anyone tried the Jaunty packages for
> netatalk? They're in the main repo:
> http://packages.ubuntu.com/jaunty/netatalk
I first tried the Lucid packages, but they don't include the a2boot binary
necessary for netbooting (presumably because it's not compiled by default).
Steven's modified 2.0.3 package (which he used on Ubuntu 6.06) addressed
various netbooting and other Apple II issues. It appears to me that some or
most of those changes were incorporated into 2.0.5; at this point, I'm 98%
convinced that the 2.0.5 source, when compiled correctly on 10.04, works
just fine, and that it's only a configuration issue that I'm having, because
clearly it's netbooting and authenticating login; it's only post-login that
there is an issue, and the symptom is the same even when I use his version
in his similar environment.
All of the stock packages I've seen have problems of one sort or another.
Typically, they are built (or build) without support for URANDOM
authentication or netbooting. And, the last time I looked there was a bug in
the handling of file dates on P8 files. I've given up trying to get fixes
into the official upstream sources. The developers could care less about
Apple 2 support and have been utterly unresponsive in the past.
Steve
> Steven's modified 2.0.3 package (which he used on Ubuntu 6.06) addressed
> various netbooting and other Apple II issues. It appears to me that some or
> most of those changes were incorporated into 2.0.5; at this point, I'm 98%
> convinced that the 2.0.5 source, when compiled correctly on 10.04, works
> just fine
That's nice to hear. Are you sure that urand authentication is supported out
of the box? The Ubuntu/debian folks had that turned off due to perceived
licensing issues (IIRC).
Steve
> That's nice to hear. Are you sure that urand authentication is supported out
> of the box? The Ubuntu/debian folks had that turned off due to perceived
> licensing issues (IIRC).
Not exactly out of the box. What I have discovered is that if I use vanilla
Ubuntu Desktop 10.04, then I use Synaptics Package Manager to install these
six packages:
libdb-4.8-dev
libcrack2
libcrack2-dev
libpam-cracklib
cracklib-runtime
libssl-dev
And then download netatalk 2.0.5 source, and use:
./configure --enable-debian --enable-a2boot --with-cracklib
and then make the appropriate tweaks to the config files and initscripts, I
can log in from an Apple IIe client (I haven't tried a IIgs yet), and
probably netboot (if I ever get my A2BOOT folder sorted out).
Interestingly, you don't seem to need --with-cracklib to log in with the Log
On v1.0 client on the Workstation Card disk. You do however, need those
libraries for the Log On v1.5 client that is embedded in the Apple //e Boot
Blocks file which is loaded during netboot, as well as the v1.3 client used
during netboot from an Apple IIe Card (for Macintosh LC). The v1.0 client
must permit clear text for login (you can omit uams_randnum.so from
afpd.conf, or have that file missing completely), while the newer ones seem
to require randnum number exchange (and you do need uams_randnum.so).
I can't vouch one way or the other for the datestamp fix, yet, nor anything
having to do with IIgs.
Once I get netboot working, hopefully before 2011, I'll try all this using
the latest netatalk (2.1.3) to see what holds up.
Finally, I has success!
This was definitely a big help -- I never actually noticed that this folder
gets made with the actual AppleShare 3 software and that netatalk mimics it.
I only was able to make it work by actually making a user in AppleShare 3,
mounting my A2BOOT folder (now empty), and then copying SYSTEM and USERS
into it. Then, voila, netboot. Before, I was trying to adapt the premade
folder provided by Marsha Jackson; so evidently there's some
ownership/permissions/username/metadata issue in play, which I'll run down
later. It would in fact be nice to have a utility to generate the files and
folders necessary in the correct configuration, or at least understand
precisely what needs to be done to a preexisting archive like Marsha's. But
for now, I'm satisfied.
Thanks for your help! (And yours too, Steven!)
That all looks familiar. I think those were all mentioned in a readme that I
posted along with my modified debian source package.
> and then make the appropriate tweaks to the config files and initscripts, I
> can log in from an Apple IIe client (I haven't tried a IIgs yet), and
> probably netboot (if I ever get my A2BOOT folder sorted out).
>
> Interestingly, you don't seem to need --with-cracklib to log in with the Log
> On v1.0 client on the Workstation Card disk. You do however, need those
> libraries for the Log On v1.5 client that is embedded in the Apple //e Boot
> Blocks file which is loaded during netboot, as well as the v1.3 client used
> during netboot from an Apple IIe Card (for Macintosh LC). The v1.0 client
> must permit clear text for login (you can omit uams_randnum.so from
> afpd.conf, or have that file missing completely), while the newer ones seem
> to require randnum number exchange (and you do need uams_randnum.so).
The IIgs with stock login support definitely needs randnum. At least it always
has for me :-).
> I can't vouch one way or the other for the datestamp fix, yet, nor anything
> having to do with IIgs.
Try placing a file in the shared volume on the server side and note the modify
data. Then, copy it to the IIe in ProDOS and see if it's propagated. That
was broken in the most recent netatalk I played with here.
> Once I get netboot working, hopefully before 2011, I'll try all this using
> the latest netatalk (2.1.3) to see what holds up.
Really glad to see more folks using this. I hacked in the original AFP "short
name" support and A2 authentication code over ten years ago and until recently
was wondering if Marsha and I were the only folks who ever used it.
Steve
Really glad you're still responding to "support" for it. Once I get the the
hang of all the ins and outs of it, I plan to write about it in a future
issue of Juiced.GS.
My ultimate goal is to see if I can get to the point where I can use a NAS
as a host (it's already possible to use netatalk on the NAS I have, but I
have to somehow get AppleTalk into its Linux kernel for Apple II support;
any volunteer to help me do this? I've never compiled a Linux kernel).
And, if I can do that, then I also want to see if I can hack the logon
client embedded in the boot blocks (at least the //e version, I am not a
IIgs guy) so that, security be damned, I can turnkey straight from machine
power-on to BASIC.SYSTEM (or a program selector) without typing anything.
Will tell you what I discover with the date bug.
Ivan.
> My ultimate goal is to see if I can get to the point where I can use a NAS
> as a host (it's already possible to use netatalk on the NAS I have, but I
> have to somehow get AppleTalk into its Linux kernel for Apple II support;
> any volunteer to help me do this? I've never compiled a Linux kernel).
Are you saying the kernel on the NAS does not have appletalk protocol support
compiled into it? If that's the case then I'm guessing netatalk supports only
AFP over IP (whatever Apple calls that). What brand of NAS is it? Is the
kernel source available? Shouldn't be rocket science to build a new kernel
with atalk protocol support.
Steve
Please, do a full write-up in Juiced.GS! I'm sure there are a lot of
people who have tried and have given up with this. A full rundown on how
you got everything kosher on your Ubuntu NAS machine would be a good,
good thing.
And your point would be... what?
Under Ubuntu 6.06 running in VMWare Fusion, I can make Steven Hirsch's
modified netatalk 2.0.3 share files with and netboot an Apple //e, connected
via AsanteTalk bridge. I've been able to do the same under Ubuntu 10.04 with
the standard netatalk 2.0.5 (last version before long hiatus) and 2.1.3
(current), if appropriate compile options are set, and dependent packages
preinstalled. So I'm pretty happy. Thanks to all who helped me get here!
I was able to finally make Marsha Jackson's premade A2BOOT folder work only
after chown -R root:root and chmod -R ugo+rw, creating an ubuntu user called
local2e, and then doing the same with afppasswd, and then logging in with
that. Or I can use my own username (or guest) and default program and prefix
by using AppleShare 3 and then copying the SYSTEM and USERS folders over to
the A2BOOT folder.
I haven't yet tested to see whether the fixes in Steven's modified 2.0.3 are
in the newer versions. I did look at the diff file and could see that the
ProDOS date issue doesn't seem fixed in the newer source.
Things to do:
- Look at Steven's 2.0.3 mods and see if they can be applied to the newer
source code and perhaps make an updated diff and/or deb (unless you want to,
Steven...)
- Write a utility to make the a2config and netboot setup easy.
- Try to modify the //e boot blocks so I can netboot straight to my startup
app without having to press a key.
- share files with and netboot from a NAS. To answer Steven's question, I
have a Western Digital My Book World Edition, which has been pretty
extensively documented: (http://mybookworld.wikidot.com). There's already a
premade netatalk package that I'm using, though as you suggested it only
offers AFP-over-TCP because AppleTalk protocol support isn't compiled into
the Linux kernel. WD does provide the kernel source and I downloaded it, and
AppleTalk is there, so yes, it should be doable; I've just never done it.
But I've seen enough to think that this NAS should be able to share files
with and netboot an Apple II!
- Try to do the above goodness with a IIgs.
(snip..)
Nice work, and thanks for the writeup!
> I haven't yet tested to see whether the fixes in Steven's modified 2.0.3 are
> in the newer versions. I did look at the diff file and could see that the
> ProDOS date issue doesn't seem fixed in the newer source.
It's been years since I've bothered to submit patches, so it would be
surprising if that did make it in. Are you able to reproduce the problem? In
thinking about it, I'm not sure that the failure to preserve file date
occurred in both directions.
> Things to do:
> - Look at Steven's 2.0.3 mods and see if they can be applied to the newer
> source code and perhaps make an updated diff and/or deb (unless you want to,
> Steven...)
It's very unlikely that I'll have the cycles to do that. Would appreciate
your being able to put a deb together.
> - Write a utility to make the a2config and netboot setup easy.
Terrific.
> - share files with and netboot from a NAS. To answer Steven's question, I
> have a Western Digital My Book World Edition, which has been pretty
> extensively documented: (http://mybookworld.wikidot.com). There's already a
> premade netatalk package that I'm using, though as you suggested it only
> offers AFP-over-TCP because AppleTalk protocol support isn't compiled into
> the Linux kernel. WD does provide the kernel source and I downloaded it, and
> AppleTalk is there, so yes, it should be doable; I've just never done it.
> But I've seen enough to think that this NAS should be able to share files
> with and netboot an Apple II!
If you are able to setup for cross-compile (is that NAS MIPS-based like so
many of the routers?) then building in atalk protocol is just a matter of
turning on the kernel configuration option. Don't forget that the ddp
protocol entry needs to be in /etc/protocols.
Very cool to see this stuff in use!
Steve
>> I haven't yet tested to see whether the fixes in Steven's modified 2.0.3 are
>> in the newer versions. I did look at the diff file and could see that the
>> ProDOS date issue doesn't seem fixed in the newer source.
I'll check that. I can also check the rest of the diff, but do you remember
if you fixed any other bugs besides the date thing? Also, by commenting the
line for the date fix, does it break any other netatalk functionality (when
used with Mac OS X clients or whatever) to your knowledge?
> If you are able to setup for cross-compile (is that NAS MIPS-based like so
> many of the routers?) then building in atalk protocol is just a matter of
> turning on the kernel configuration option. Don't forget that the ddp
> protocol entry needs to be in /etc/protocols.
Sure, it's "just a matter of" to *you*, but I'll give it a whirl. It's an
ARM-based device but people have definitely cross-compiled new kernels for
it.
> It's very unlikely that I'll have the cycles to do that. Would appreciate
> your being able to put a deb together.
I'll try. It'll be my first deb. I'm not really a Linux guy, as you've
probably figured out by now.
I am honestly not sure. I'd have to go back and look at it and do some
experimentation. So, in the meantime: Caveat Emptor!
>> If you are able to setup for cross-compile (is that NAS MIPS-based like so
>> many of the routers?) then building in atalk protocol is just a matter of
>> turning on the kernel configuration option. Don't forget that the ddp
>> protocol entry needs to be in /etc/protocols.
>
> Sure, it's "just a matter of" to *you*, but I'll give it a whirl. It's an
> ARM-based device but people have definitely cross-compiled new kernels for
> it.
My "just a matter of" would probably be most of a Saturday banging my head
against the wall and uttering shameful language. Don't for a minute mistake
me for someone who would know how to do this off the top of my head :-).
>> It's very unlikely that I'll have the cycles to do that. Would appreciate
>> your being able to put a deb together.
>
> I'll try. It'll be my first deb. I'm not really a Linux guy, as you've
> probably figured out by now.
There is a wealth of information out there on building debian packages.
Unfortunately it's scattered, inconsisent and much of it is out-of-date (read:
you are just supposed to _know_ that it's not done with tool xyz anymore -
which has been replaced with abc and def..).
One of the only coherent books I've ever been able to find is "The Debian
System" by Martin Krafft (Open Source Press). It's a bit dated, but the tools
he uses do still exist and at least it provides complete explanations.
Steve