Re: [Voyage-linux] sshd in voyage 5.2

[Ben Kochie]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Sure.. here was my plan to fix the install issues.

On the build side, everything can be installed using fakeroot.  After the 
build of the root that is tared up is done we can build a map file that 
contains all the permissions/ownership of all the files.  Something simple 
like a file that contains: (perms owner group file/dirname)


0755 0 0 /path/to/file

After the files have been copied to the new rootfs, the script can be run 
to verify the perms are correct.


The same thing can be done for the /dev devices, instead of keeping them 
in the tarball, they can be scanned for their info, and then a script will 
just walk through and mknod as root after the files are copied to the 
target rootfs.


It's a bit complicated, and there's probably room for optimization, but 
this setup would allow people to extract the installer as a user, and 
install with minimal root incursion on their host.


- -ben

 "UNIX is user-friendly, it's just picky about its friends."

On Wed, 25 Mar 2009, Kim-man 'Punky' TSE wrote:


Hi Ben,

From this thread, I eventually learned some answers of the previous 
installation problems reported. 


It doesn't say you need to be root when you do that.  (maybe adding sudo to 
that command line would make it clear)

Thanks.  Will add this to README.


Either way, I think the installation method should be cleaned up so that 
the tarball doesn't need to be --numeric-owner, nor have root extract it.

Can you elaborate more how this could be done in practice?


The voyage.update script should have a post-install devicenode create 
script, and a permission/owner cleanup script.
Can you explain why device node creation script is needed and how to achieve 
permission/owner cleanup?

- -ben


--

Regards,
Punky

Voyage Solutions (http://solution.voyage.hk)
* Embedded Solutions and Systems
- Mesh Networking, Captive Portal, IP Surveillance, VoIP/PBX
- Network Engineering, Development Platform and Consultation



-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFJyaBDfYg2asD844oRAupQAJ9BwMSIYqoK2QYv3HcGmTMzAwXnXACfZy7h
xJw11zay3JX2AwY9cqbc5R4=
=73bi
-END PGP SIGNATURE-

___
Voyage-linux mailing list
Voyage-linux@list.voyage.hk
http://list.voyage.hk/mailman/listinfo/voyage-linux

Re: [Voyage-linux] sshd in voyage 5.2

[Kim-man 'Punky' TSE]

Hi Ben,

From this thread, I eventually learned some answers of the previous 
installation problems reported. 


It doesn't say you need to be root when you do that.  (maybe adding 
sudo to that command line would make it clear)

Thanks.  Will add this to README.


Either way, I think the installation method should be cleaned up so 
that the tarball doesn't need to be --numeric-owner, nor have root 
extract it.

Can you elaborate more how this could be done in practice?


The voyage.update script should have a post-install devicenode create 
script, and a permission/owner cleanup script.
Can you explain why device node creation script is needed and how to 
achieve permission/owner cleanup?

- -ben


--

Regards,
Punky

Voyage Solutions (http://solution.voyage.hk)
* Embedded Solutions and Systems
 - Mesh Networking, Captive Portal, IP Surveillance, VoIP/PBX
 - Network Engineering, Development Platform and Consultation
 
	



___
Voyage-linux mailing list
Voyage-linux@list.voyage.hk
http://list.voyage.hk/mailman/listinfo/voyage-linux

Re: [Voyage-linux] sshd in voyage 5.2

[Ben Kochie]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

I agree, hence my request to change the installation method.
However it's also on the website right next to the download link 
as well.


- -ben

 "UNIX is user-friendly, it's just picky about its friends."

On Tue, 24 Mar 2009, Jeff Ramin wrote:



Yes, I see it is in README. However, the README is in
the tarball itself, so it's a little late to be telling people
how to extract it.  =)

Ben Kochie wrote:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Yup, it is explicitly stated in the README.

extract the software tarball:
tar --numeric-owner -jxf voyage-.tar.bz2



-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFJyQhxfYg2asD844oRAtaMAKCtNn05jrx4mkqBGsuaGGVf/9y6QwCfYHJ2
hVMFmQ4K7C5OIcy7PWHYqXs=
=f+DA
-END PGP SIGNATURE-

___
Voyage-linux mailing list
Voyage-linux@list.voyage.hk
http://list.voyage.hk/mailman/listinfo/voyage-linux

Re: [Voyage-linux] sshd in voyage 5.2

[Jeff Ramin]

Yes, I see it is in README. However, the README is in
the tarball itself, so it's a little late to be telling people
how to extract it.  =)

Ben Kochie wrote:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Yup, it is explicitly stated in the README.

extract the software tarball:
tar --numeric-owner -jxf voyage-.tar.bz2



___
Voyage-linux mailing list
Voyage-linux@list.voyage.hk
http://list.voyage.hk/mailman/listinfo/voyage-linux

Re: [Voyage-linux] sshd in voyage 5.2

[Ben Kochie]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Yup, it is explicitly stated in the README.

extract the software tarball:
tar --numeric-owner -jxf voyage-.tar.bz2

It doesn't say you need to be root when you do that.  (maybe adding sudo 
to that command line would make it clear)


Either way, I think the installation method should be cleaned up so that 
the tarball doesn't need to be --numeric-owner, nor have root extract it.


The voyage.update script should have a post-install devicenode create 
script, and a permission/owner cleanup script.


- -ben

 "UNIX is user-friendly, it's just picky about its friends."

On Tue, 24 Mar 2009, Jeff Ramin wrote:


Kim-man 'Punky' TSE wrote:

Hi Jeff,

Obviously, it is not a known bug.  Everyone here in this list happy used 
0.5.2 without problem for 9 months.


Can you be more details on:
1.  What is the ownership and permission of voyage-0.5.2/ro/var/run/sshd 
set in the host machine for installing voyage?

My host shows
voyage-0.5.2# ls -lad ro/var/run/sshd/
drwxr-xr-x 2 root root 4096 May 15  2008 ro/var/run/sshd/


On my machine, that file is owned by the user that unpacked
the tar ball (not root).


2.  Did you use --numeric-owner flag when you extract the tarball?

No, I didn't.

So, when unpacking the voyage tar ball, either it must be done as
root, or by using the --numeric-owner flag apparently.

___
Voyage-linux mailing list
Voyage-linux@list.voyage.hk
http://list.voyage.hk/mailman/listinfo/voyage-linux


-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFJyO/CfYg2asD844oRAqDDAJ9K2/1nvhXlyYLImSaTt5IHaz6fuQCgtY+c
Y4C0bgE/tLoFJaOD6ivP5ag=
=OHMH
-END PGP SIGNATURE-

___
Voyage-linux mailing list
Voyage-linux@list.voyage.hk
http://list.voyage.hk/mailman/listinfo/voyage-linux

Re: [Voyage-linux] sshd in voyage 5.2

[Jeff Ramin]

Kim-man 'Punky' TSE wrote:

Hi Jeff,

Obviously, it is not a known bug.  Everyone here in this list happy 
used 0.5.2 without problem for 9 months.


Can you be more details on:
1.  What is the ownership and permission of 
voyage-0.5.2/ro/var/run/sshd set in the host machine for installing 
voyage?

My host shows
voyage-0.5.2# ls -lad ro/var/run/sshd/
drwxr-xr-x 2 root root 4096 May 15  2008 ro/var/run/sshd/


On my machine, that file is owned by the user that unpacked
the tar ball (not root).


2.  Did you use --numeric-owner flag when you extract the tarball?

No, I didn't.

So, when unpacking the voyage tar ball, either it must be done as
root, or by using the --numeric-owner flag apparently.

___
Voyage-linux mailing list
Voyage-linux@list.voyage.hk
http://list.voyage.hk/mailman/listinfo/voyage-linux

Re: [Voyage-linux] sshd in voyage 5.2

[Kim-man 'Punky' TSE]

Hi Jeff,

Obviously, it is not a known bug.  Everyone here in this list happy used 
0.5.2 without problem for 9 months.


Can you be more details on:
1.  What is the ownership and permission of voyage-0.5.2/ro/var/run/sshd 
set in the host machine for installing voyage?

My host shows
voyage-0.5.2# ls -lad ro/var/run/sshd/
drwxr-xr-x 2 root root 4096 May 15  2008 ro/var/run/sshd/

2.  Did you use --numeric-owner flag when you extract the tarball?

Regards,
Punky


Jeff Ramin 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@list.voyage.hk
http://list.voyage.hk/mailman/listinfo/voyage-linux



--
Regards,
Punky

Voyage Solutions (http://solution.voyage.hk)
* Embedded Solutions and Systems
 - Mesh Networking, Captive Portal, IP Surveillance, VoIP/PBX
 - Network Engineering, Development Platform and Consultation
 
	



___
Voyage-linux mailing list
Voyage-linux@list.voyage.hk
http://list.voyage.hk/mailman/listinfo/voyage-linux

Re: [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 
mailto:jeff.ra...@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@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@list.voyage.hk
http://list.voyage.hk/mailman/listinfo/voyage-linux




___
Voyage-linux mailing list
Voyage-linux@list.voyage.hk
http://list.voyage.hk/mailman/listinfo/voyage-linux

Re: [Voyage-linux] sshd in voyage 5.2

[Jeff Ramin]

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 
mailto:jeff.ra...@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@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@list.voyage.hk
http://list.voyage.hk/mailman/listinfo/voyage-linux

Re: [Voyage-linux] sshd in voyage 5.2

[Jeff Ramin]

Nick L. wrote:



On Mon, Mar 23, 2009 at 10:34 AM, Jeff Ramin 
mailto:jeff.ra...@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@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@list.voyage.hk
http://list.voyage.hk/mailman/listinfo/voyage-linux

Re: [Voyage-linux] sshd in voyage 5.2

[Nick L.]

On Mon, Mar 23, 2009 at 10:34 AM, Jeff Ramin 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@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.
___
Voyage-linux mailing list
Voyage-linux@list.voyage.hk
http://list.voyage.hk/mailman/listinfo/voyage-linux

[Voyage-linux] sshd in voyage 5.2

[Jeff Ramin]

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@list.voyage.hk
http://list.voyage.hk/mailman/listinfo/voyage-linux