Hello All.
If you're using the "freebee" 3B1 emulator, this may be of interest to you.
In https://github.com/arnoldrobbins/s4-3b1-pc7300/ is an updated "sysv"
file system module that should work with modern Linux systems. Also
included are tools for exporting a file system image from a hard disk
image and for importing a file system image back into a hard disk image.
In article <rqtt0l$1537$1@gioia.aioe.org>,
Aharon Robbins <arnold@skeeve.com> wrote:
Hello All.I see you started with my fixes.
If you're using the "freebee" 3B1 emulator, this may be of interest to you. >>
In https://github.com/arnoldrobbins/s4-3b1-pc7300/ is an updated "sysv" >>file system module that should work with modern Linux systems. Also >>included are tools for exporting a file system image from a hard disk
image and for importing a file system image back into a hard disk image.
I did see this issue with your updated kernel module that I reported
against the original repo?
https://github.com/dad4x/s4-3b1-pc7300/issues/3
Do you know if this requires 5.4 kernel or will work on older? I tend to
not update that often.
It seems ustat.h was removed when a new glib came out, in Ubuntu 18.10 and similar. I can't build it out fo the box now, any suggestions?
On Saturday, January 9, 2021 at 4:01:43 PM UTC-5, Aharon Robbins wrote:
In article <i5sc44...@mid.individual.net>,
David Gesswein <d...@pdp8online.com> wrote:
In article <rqtt0l$1537$1...@gioia.aioe.org>,Yes, I was pointed at your repo.
Aharon Robbins <arn...@skeeve.com> wrote:
Hello All.I see you started with my fixes.
If you're using the "freebee" 3B1 emulator, this may be of interest to you.
In https://github.com/arnoldrobbins/s4-3b1-pc7300/ is an updated "sysv" >>file system module that should work with modern Linux systems. Also >>included are tools for exporting a file system image from a hard disk >>image and for importing a file system image back into a hard disk image. >>
I did see this issue with your updated kernel module that I reported >against the original repo? >https://github.com/dad4x/s4-3b1-pc7300/issues/3This remains true. I don't know why. Running s4fsck on the extracted filesystem before mounting it fixes things so that Linux is happy.
Unix then runs fsck on the filesystem when it's imported back. This
seems to work, but there may be some problems with it. This whole thing should be investigated but I don't have the cycles.
Do you know if this requires 5.4 kernel or will work on older? I tend to >not update that often.I did the fix against 4.15.0 kernel sources, and it works fine on kernel 5.4.0 (both Ubuntu 18.04).
Hope this helps,
Arnold
--
Aharon (Arnold) Robbins arnold AT skeeve DOT com
In article <i5sc44...@mid.individual.net>,
David Gesswein <d...@pdp8online.com> wrote:
In article <rqtt0l$1537$1...@gioia.aioe.org>,Yes, I was pointed at your repo.
Aharon Robbins <arn...@skeeve.com> wrote:
Hello All.I see you started with my fixes.
If you're using the "freebee" 3B1 emulator, this may be of interest to you. >>
In https://github.com/arnoldrobbins/s4-3b1-pc7300/ is an updated "sysv" >>file system module that should work with modern Linux systems. Also >>included are tools for exporting a file system image from a hard disk >>image and for importing a file system image back into a hard disk image.
I did see this issue with your updated kernel module that I reported >against the original repo?This remains true. I don't know why. Running s4fsck on the extracted filesystem before mounting it fixes things so that Linux is happy.
https://github.com/dad4x/s4-3b1-pc7300/issues/3
Unix then runs fsck on the filesystem when it's imported back. This
seems to work, but there may be some problems with it. This whole thing should be investigated but I don't have the cycles.
Do you know if this requires 5.4 kernel or will work on older? I tend to >not update that often.I did the fix against 4.15.0 kernel sources, and it works fine on kernel 5.4.0 (both Ubuntu 18.04).
Hope this helps,
Arnold
--
Aharon (Arnold) Robbins arnold AT skeeve DOT com
It seems ustat.h was removed when a new glibc came out, in Ubuntu 18.10
and similar. I can't build it out fo the box now, any suggestions?
In article <cc9b9093-2116-438e...@googlegroups.com>,
Peter Schmidt <pe...@transcend.aero> wrote:
It seems ustat.h was removed when a new glibc came out, in Ubuntu 18.10Replacing it with statfs should do the trick. It looks like an
and similar. I can't build it out fo the box now, any suggestions?
easy fix.
Please open an issue on GitHub and I'll get to it.
Thanks,
Arnold
--
Aharon (Arnold) Robbins arnold AT skeeve DOT com
Will do, and thanks!
On Monday, January 11, 2021 at 1:13:10 AM UTC-5, Aharon Robbins wrote:
In article <cc9b9093-2116-438e...@googlegroups.com>,
Peter Schmidt <pe...@transcend.aero> wrote:
It seems ustat.h was removed when a new glibc came out, in Ubuntu 18.10 >and similar. I can't build it out fo the box now, any suggestions? Replacing it with statfs should do the trick. It looks like aneasy fix.
Please open an issue on GitHub and I'll get to it.
Thanks,
Arnold
--
Aharon (Arnold) Robbins arnold AT skeeve DOT com
Err, sorry, but I'm not seeing the issues tab on >https://github.com/arnoldrobbins/s4-3b1-pc7300 - am I dense or are they >currently disabled?
Err, sorry, but I'm not seeing the issues tab on >https://github.com/arnoldrobbins/s4-3b1-pc7300 - am I dense or are they >currently disabled?
On Monday, January 11, 2021 at 10:20:41 AM UTC-5, Peter Schmidt wrote:
Will do, and thanks!
On Monday, January 11, 2021 at 1:13:10 AM UTC-5, Aharon Robbins wrote:
In article <cc9b9093-2116-438e...@googlegroups.com>,
Peter Schmidt <pe...@transcend.aero> wrote:
It seems ustat.h was removed when a new glibc came out, in Ubuntu 18.10 >> > >and similar. I can't build it out fo the box now, any suggestions?Replacing it with statfs should do the trick. It looks like an
easy fix.
Please open an issue on GitHub and I'll get to it.
Thanks,
Arnold
--
Aharon (Arnold) Robbins arnold AT skeeve DOT com
Harumph. Seems they have to be manually enabled. Done. Sorry
about that.
In article <187e1e2b-3991-4b97...@googlegroups.com>,
Peter Schmidt <pe...@transcend.aero> wrote:
Err, sorry, but I'm not seeing the issues tab on >https://github.com/arnoldrobbins/s4-3b1-pc7300 - am I dense or are they >currently disabled?
On Monday, January 11, 2021 at 10:20:41 AM UTC-5, Peter Schmidt wrote:
Will do, and thanks!
On Monday, January 11, 2021 at 1:13:10 AM UTC-5, Aharon Robbins wrote:
In article <cc9b9093-2116-438e...@googlegroups.com>,
Peter Schmidt <pe...@transcend.aero> wrote:
It seems ustat.h was removed when a new glibc came out, in Ubuntu 18.10 >> > >and similar. I can't build it out of the box now, any suggestions?Replacing it with statfs should do the trick. It looks like an
easy fix.
Please open an issue on GitHub and I'll get to it.
Thanks,
Arnold
--
Aharon (Arnold) Robbins arnold AT skeeve DOT com
--
Aharon (Arnold) Robbins arnold AT skeeve DOT com
Issue opened, cheers!--
On Monday, January 11, 2021 at 10:52:05 PM UTC-5, Aharon Robbins wrote:
Harumph. Seems they have to be manually enabled. Done. Sorry
about that.
In article <187e1e2b-3991-4b97...@googlegroups.com>,
Peter Schmidt <pe...@transcend.aero> wrote:
Err, sorry, but I'm not seeing the issues tab on
https://github.com/arnoldrobbins/s4-3b1-pc7300 - am I dense or are they
currently disabled?
On Monday, January 11, 2021 at 10:20:41 AM UTC-5, Peter Schmidt wrote:
Will do, and thanks!
On Monday, January 11, 2021 at 1:13:10 AM UTC-5, Aharon Robbins wrote:
In article <cc9b9093-2116-438e...@googlegroups.com>,
Peter Schmidt <pe...@transcend.aero> wrote:
It seems ustat.h was removed when a new glibc came out, in Ubuntu 18.10Replacing it with statfs should do the trick. It looks like an
and similar. I can't build it out of the box now, any suggestions?
easy fix.
Please open an issue on GitHub and I'll get to it.
Thanks,
Arnold
--
Aharon (Arnold) Robbins arnold AT skeeve DOT com
--
Aharon (Arnold) Robbins arnold AT skeeve DOT com
OK, I have fixed this thoroughly. The original code checked if
a block device was mounted using ustat. It did not check if a file
system image was mounted.
I have fixed both things by writing some new code and adding an
additional check. Note that the code is Linux-specific. It's all
pushed to the repo and the issue is closed.
Please try it out.
Arnold
In article <14ec6db8-0a28-415c...@googlegroups.com>,
Peter Schmidt <pe...@transcend.aero> wrote:
Issue opened, cheers!
On Monday, January 11, 2021 at 10:52:05 PM UTC-5, Aharon Robbins wrote:--
Harumph. Seems they have to be manually enabled. Done. Sorry
about that.
In article <187e1e2b-3991-4b97...@googlegroups.com>,
Peter Schmidt <pe...@transcend.aero> wrote:
Err, sorry, but I'm not seeing the issues tab on
https://github.com/arnoldrobbins/s4-3b1-pc7300 - am I dense or are they >> >currently disabled?
On Monday, January 11, 2021 at 10:20:41 AM UTC-5, Peter Schmidt wrote:
Will do, and thanks!
On Monday, January 11, 2021 at 1:13:10 AM UTC-5, Aharon Robbins wrote: >> >> > In article <cc9b9093-2116-438e...@googlegroups.com>,
Peter Schmidt <pe...@transcend.aero> wrote:
It seems ustat.h was removed when a new glibc came out, in Ubuntu 18.10easy fix.
and similar. I can't build it out of the box now, any suggestions? >> >> > Replacing it with statfs should do the trick. It looks like an
Please open an issue on GitHub and I'll get to it.
Thanks,
Arnold
--
Aharon (Arnold) Robbins arnold AT skeeve DOT com
--
Aharon (Arnold) Robbins arnold AT skeeve DOT com
Aharon (Arnold) Robbins arnold AT skeeve DOT com
Arnold that is great!
Now, perhaps this is user error, but when I run s4export on my freebee >hd.img, it fails with "badmagic," though s4disk appears to parse it
fine. I opened another issue on that with output, in case that's
helpful. Any advice?
In article <6870aa07-69a7-4603...@googlegroups.com>,
Peter Schmidt <pe...@transcend.aero> wrote:
Arnold that is great!
Now, perhaps this is user error, but when I run s4export on my freebee >hd.img, it fails with "badmagic," though s4disk appears to parse itNo advice, sorry. The s4export and s4import have worked fine
fine. I opened another issue on that with output, in case that's
helpful. Any advice?
for me, without any problems.
As I've noted, there is an impedance mismatch between Unix and Linux
with respect to the free list. You have to s4fsck the exported fs
before mounting it.
I don't have the cycles right now to investigate your issue. To be
honest, I don't know when I will, either.
Hmmm. I notice that you're on a Raspberry Pi. Can you try it on
an Intel Linux system? Preferably x86_64.
If it works on an Intel system, then there's likely an issue relating
to sizeof(int) and sizeof(long) on the RPi, and maybe also related
to big endian vs. little endian.
HTH,
Arnold
--
Aharon (Arnold) Robbins arnold AT skeeve DOT com
OK, will try on an Intel box and report back for thread completeness.
In article <e5eb6111-9fe3-49dd...@googlegroups.com>,
Peter Schmidt <pe...@transcend.aero> wrote:
OK, will try on an Intel box and report back for thread completeness.
You can also try this image and see if it works where its failing for you. https://www.pdp8online.com/3b1/3b1-hd.zip
If it doesn't fail would need to get your failing image to see what is going on.
Hi Peter - I don't think this is 32-bit vs 64-bit related as I didn't see any offending long's in the s4 code. I do think there may be an issue with 17sec/tk, I need to look into further, as I had a similar bagmagic issue with 17sec/tk, but not with my16sec/tk image.
Jesse
David, your image worked fine with s4export, thanks! The one that is
failing is here: >https://drive.google.com/file/d/1dCGTfNSjuX3VM-cJAV7f3euSD9ggDaci/view?usp=sharing
Peter Schmidt <pe...@transcend.aero> wrote:
David, your image worked fine with s4export, thanks! The one that is >failing is here: >https://drive.google.com/file/d/1dCGTfNSjuX3VM-cJAV7f3euSD9ggDaci/view?usp=sharing
I tried to boot your image under my FreeBee and it doesn't boot. Does
it boot fine on your machine? Does my image boot under your FreeBee?
I don't get the loader screen at all.
I wonder if this is FreeBee isn't creating the image properly on your platform.
Peter, I checked out your file. Your hd.img is sized to 1024*8*16*512, but the header info in the hd.img is stating 1024*8*17*512, so this is probably what's causing the issue. The instructions for creating the hd.img recently changed -- theypreviously were 'dd if=/dev/zero of=hd.img bs=512 count=$(expr 16 \* 8 \* 1024)' but that recently was updated to make a file image with 17sec/tk instead of 16sec/tk. ('dd if=/dev/zero of=hd.img bs=512 count=$(expr 17 \* 8 \* 1024)') Or alternatively you
Yours boots on mine, but the one I uploaded does not. Looks like I
screwed up and not only uploaded a corrupted one - possibly from an
earlier version of freebee - but accidentally overwrote the one I had
been booting, d'oh. If it would be of interest, I can make a new one as
I did before, let me know. But given yours is working on mine, seems
likely it was a version skew.
| Sysop: | Keyop |
|---|---|
| Location: | Huddersfield, West Yorkshire, UK |
| Users: | 293 |
| Nodes: | 16 (2 / 14) |
| Uptime: | 213:31:03 |
| Calls: | 6,619 |
| Calls today: | 1 |
| Files: | 12,168 |
| Messages: | 5,317,427 |