Hi, I'm ready to implement Amiga SmartFileSystem into NetBSD. For the time being, read-only. To do that, I would like someone with vnode/vfs experience to help me on the BSD side. I already have some SFS-related procedures, and they work fine with my test-file-partition. Thank you :) kind regards - Adam
Hi Not a huge problem or a bug but a request for enhancement to the iso image provided from your ftp site. The file miniroot.fs that must be placed on swap is only available gzipped. I do not have gunzip for the amiga and have had to burn another CD with the gunzipped miniroot.fs on it. As this CD is far from full can I request that future versions have this file uncompressed on them. One other quick question, any plans to support the mediator PCI bus board and pci stuff in the future? Many thanks, Gary Pentland
On Tue, 21 May 2002, Pentland G. wrote:
> The file miniroot.fs that must be placed on swap is only available
> gzipped. I do not have gunzip for the amiga and have had to burn
> another CD with the gunzipped miniroot.fs on it. As this CD is far
> from full can I request that future versions have this file
> uncompressed on them.
I don't have anything to do with the NetBSD development, but I hope you
have heared of AmiNet, world largest software collection, where you will
find gzip for AmigaOS, take a look at de.aminet.net
//Aho \|||/
(. .)
----------------------------------------------------------oOoo-ooOo-----
E-Mail: trizt <at> iname.com URL: http://www.kotiaho.net/~trizt/
ICQ: 13696780
System: MorphOS/Linux System (PPC603e/160 AMD K7D/700)
------------------------------------------------------------------------
Find useful software, surf to www.trogsoft.org
------------------------------------------------------------------------
Hi, I have never used the keypad very much (maybe the A1000 experience is telling). But today I was messing around with the keyboard both on the console and with X and I have noticed the following (NetBSD 1.5.2): X: Although I see the X symbol 'Num_lock' in the output of 'xev' when I press 'RightAlt' (the X Modeswitch) together with the key labeled 'NumL', the state for the keypad keys does not seem to switch. I understand that the Amiga keyboard has no LED to display the state of 'Num_lock' but wouldn't it be more convenient to have this kind of switching available? As it is now, we can _only_ get the alternate function of those keys by always pressing 'Shift' at the same time. There is also a deviation from the behaviour I have observed with X on i386: The key '5' on the keypad always produces 'KP_5', even when pressed together with 'Shift'. On NetBSD/i386 I get 'KP_Begin' as the alternate function. Console: Pressing 'Shift' with any of the keypad number keys does _not_ give me the alternate function (e.g. SHIFT 8 = 'UP'). The 'Backspace' key and the 'Del' key give me '^?' (ASCII 127) and '^H' (ASCII 8). Both erase the character left of the cursor. I remember faintly that I wondered about this years ago (maybe 1993 ?) and it is still the case. Can anyone explain why those two keys should have swapped their ASCII code and why both do the same ?(Continue reading)
On Sun, May 26, 2002 at 03:47:46PM +0300, Jaromir Dolecek wrote: > > Module Name: syssrc > Committed By: jdolecek > Date: Sun May 26 12:47:45 UTC 2002 > > Modified Files: > syssrc/sys/arch/amiga/conf: Makefile.amiga files.amiga > Added Files: > syssrc/sys/arch/amiga/dev: Makefile grf_ultms.c > > Log Message: > pregenerate grf_ultms.c, so that gspa isn't needed during kernel build Hmm, I thought there was a problem with adding gspa binary code and thats why we have to use gspa during the kernel build. Bernd
Nono, the output was just plain C code, not binary output - see generated grf_ultms.c. Previously, it would generate the C file and compile it using C compiler. Now, the C file is pre-generated. Jaromir Bernd Ernesti wrote: > On Sun, May 26, 2002 at 03:47:46PM +0300, Jaromir Dolecek wrote: > > > > Module Name: syssrc > > Committed By: jdolecek > > Date: Sun May 26 12:47:45 UTC 2002 > > > > Modified Files: > > syssrc/sys/arch/amiga/conf: Makefile.amiga files.amiga > > Added Files: > > syssrc/sys/arch/amiga/dev: Makefile grf_ultms.c > > > > Log Message: > > pregenerate grf_ultms.c, so that gspa isn't needed during kernel build > > Hmm, I thought there was a problem with adding gspa binary code and thats > why we have to use gspa during the kernel build. > > Bernd > -- --(Continue reading)
On Mon, May 27, 2002 at 01:18:13PM +0200, Jaromir Dolecek wrote: > Nono, the output was just plain C code, not binary output - see > generated grf_ultms.c. > > Previously, it would generate the C file and compile it using > C compiler. Now, the C file is pre-generated. As far as i remeber this IS the problem and the reason why the C file couldn't be included in the source tree. Sorry you right that this is not a binary file itself, but it contains the binary output. Please ask Ignatios about this part. I can't find a mail now which describes why we have to use the gspa 'compiler' and can't add a generated c file. Bernd
G. Pentland wrote:
> One other quick question, any plans to support the mediator PCI bus
> board and pci stuff in the future?
I would say this depends on available information for this device
and someone with access to the hardware needing it enough to start
writing code.
As this is the first sign of interest in this product here (that I
know of) I would not hold my breath...
ciao
Klaus
Bernd Ernesti wrote:
> Please ask Ignatios about this part.
>
> I can't find a mail now which describes why we have to use the gspa 'compiler'
> and can't add a generated c file.
I would also be interested in why the build broke in the first place.
When I looked at this on sunday evening I could find no reason for the broken
build mechanism on Amiga. My only guess, from the logfile on the releng
machine:
gspa: not found
*** Error code 127
gspa somehow disappeared from /usr/sbin/ on the build machine.
ciao
Klaus
Hi A few days ago, I decided to give a try to NetBSD on my 3000. I've setup 2 partitions (root and swap), copied the miniroot.fs to swap, and loaded bsd using the loadbsd -b bsdkernel. The machine booted bsd, and stopped at "root> ok." Now, anything I enter there will lead to kernel panic. I cant find the way to mount the root partition. I've tried sda*, sd0*, everything, you name it. Nothing works. I'm using an old bsd distribution (I think it's 1.2 or something), my 3k has a 040. The hard disk is a 4.3 G which is recognised when bsd boots. The root partition though, and the swap are above the 4G limit. Could this have anything to do with my problem? Thanks, Emm Vasilakis
RSS Feed7 | |
|---|---|
2 | |
3 | |
13 | |
1 | |
15 | |
20 | |
6 | |
7 | |
10 | |
18 | |
6 | |
10 | |
1 | |
1 | |
9 | |
7 | |
20 | |
1 | |
14 | |
9 | |
12 | |
9 | |
43 | |
46 | |
1 | |
31 | |
7 | |
1 | |
1 | |
2 | |
31 | |
1 | |
21 | |
13 | |
9 | |
42 | |
35 | |
63 | |
20 | |
9 | |
1 | |
32 | |
1 | |
51 | |
1 | |
1 | |
3 | |
5 | |
1 | |
5 | |
2 | |
6 | |
9 | |
11 | |
13 | |
26 | |
6 | |
27 | |
14 | |
5 | |
9 | |
9 | |
4 | |
26 | |
18 | |
3 | |
2 | |
14 | |
18 | |
31 | |
19 | |
13 | |
35 | |
6 | |
7 | |
1 | |
5 | |
14 | |
1 | |
2 | |
7 | |
23 | |
69 | |
58 | |
13 | |
12 | |
18 | |
31 | |
10 | |
17 | |
9 | |
3 | |
2 | |
16 | |
13 | |
18 | |
21 | |
8 | |
17 | |
11 | |
62 | |
11 | |
12 | |
4 | |
8 | |
3 | |
121 | |
29 | |
20 | |
19 | |
12 | |
3 | |
19 | |
43 | |
15 | |
6 | |
11 |
