[Voyage-linux] sshd in voyage 5.2

[Sean]

In Voyage 0.5.2,

/var/run is symbolically linked to /rw/var/run

At boot everything in /ro gets copied to /rw (/rw being in memory).

You can edit your files in /ro/var/run/sshd. Then on boot they get 
copied over.

You can just edit them on your voyage install directory too: 
voyage-0.5.2/ro/var/run/sshd

Hope that helps

Sean

Jeff Ramin wrote:
>
> Can somebody suggest a fix for this problem? My plan
> was to modify /var/run/sshd before building the image
> for the flash drive, but that file doesn't exist at image
> creation time. Apparently it is created at boot time.
>
> My current workaround is to modify that file from rc.local
> so that sshd can start, but this requires that I access the
> machine via the console after the initial boot. I want an
> image that I can ssh to immediately, without having to
> access the console.
>
> Thanks.
>
>
> Jeff Ramin wrote:
>> Nick L. wrote:
>>>
>>>
>>> On Mon, Mar 23, 2009 at 10:34 AM, Jeff Ramin 
>>> <jeff.ramin at singlewire.com <mailto:jeff.ramin at singlewire.com>> wrote:
>>>
>>>
>>>     It seems sshd does not start as configured at boot time,
>>>     because the ownership and permissions of /var/run/sshd
>>>     are not set properly.
>>>
>>>     Has anybody else seen this behavior? Is it a known bug?
>>>
>>>     Thanks.
>>>
>>>     _______________________________________________
>>>     Voyage-linux mailing list
>>>     Voyage-linux at list.voyage.hk <mailto:Voyage-linux at list.voyage.hk>
>>>     http://list.voyage.hk/mailman/listinfo/voyage-linux
>>>
>>>
>>> It happens if you install to media as a normal user. Use the Voyage 
>>> install script as root and all should be well. sshd needs to run as 
>>> root if I recall correctly.
>>
>> I'm fairly certain I ran the script as root...yes, I just checked
>> .bash_history, and it was run as root.
>>
>
>
> _______________________________________________
> Voyage-linux mailing list
> Voyage-linux at list.voyage.hk
> http://list.voyage.hk/mailman/listinfo/voyage-linux
>