Re: Interface for SCSI transactions ?

[Thomas Schmitt]

Hi,

me:
> > Will a 3 GB "disk" suffice ? Shall i install Hurd to a larger one ?

Jeremie Koenig wrote:

> I'd recommend using a larger image 
> As a data point, one of my VMs has a 20 GB "disk" and I'm still running
> into disk space problems occasionally 

olafBuddenhagen@gmx.net wrote:

> Well, it should suffice, as long as you only build small packages with
> few dependencies.  For anything larger, it will be too small very soon

Currently it is stunningly small (if df / tells the truth).
But i will re-install to a 32 GB "disk" before i invest more time into
exploring and installing.

For now i built my own upstream packages and got the test cases running,
as far as applicable without contact to a CD drive.


> > Even if i had a detailed plan of what to code where, i still lack of
> > an idea how the development cycle for a kernel change would look like.

> Well, not that much different from userspace stuff: you frob the source,
> launch a "make" to build the binary, and then test it...

Testing is still quite obscure to me. So first i will concentrate on
making a plan.

After re-install i will try to get the Hurd sources.
Then i'll try to identify the point where device_get_status() materializes
on the kernel side. From there i'll have to find a path to
scsi_ioctl_send_command() (which i yet only know from googling).


> BTW, do you use IRC? #hurd on freenode should be a good place to get
some handholding :-)

Not yet. I'm quite asynchronous.


> Don't be afraid -- it's really not as scary as most people seem to think
> :-)

That's what i tell myself since i began driving CD burners, five years ago.
(USB boxes brought a big relief for the pain of rebooting because of
 a stuck drive. I hope that virtual machines will do the same for
 kernel adventures.)

Well, i will see how far i get. 


... Now i installed basic Hurd in 32 GB. All looks well so far.

Except i cannot find out why logging in from the hosting system by
  ssh -p5555 localhost
demands a password.
With the previous installation it sufficed to copy .ssh/authorized_keys 
to silence the password prompt.
There is no file
  ~/.ssh/known_hosts
in the new installation. But copying from the old one does not help.
Neither ~/.ssh/* nor /etc/ssh/* show differences which would give me a clue.

Somehow i do not have this system under control yet. {:|


Have a nice day :)

Thomas