#!/bin/bash

ip link set dev eth0 up

ip addr add dev eth0 192.168.1.253/24

ip route add default via 192.168.1.254

#now I wont to copy the folder to rw fs in order to write status files and logs so

cp -r /mnt/grmlcfg/openvpn /root/ 

cd /root/openvpn

openvpn --config /root/openvpn/server.conf &

echo 1 > /proc/sys/net/ipv4/ip_forward

#and to start ssh server to access the box

/etc/init.d/ssh start

From: Lupe Christoph <lupe <at> lupe-christoph.de>
To: Bojan Sukalo <shukalo83 <at> yahoo.com>
Cc: "grml <at> mur.at" <grml <at> mur.at>
Sent: Monday, September 5, 2011 11:26 AM
Subject: Re: [Grml] Problem with grml autoconfig

On Monday, 2011-09-05 at 01:28:29 -0700, Bojan Sukalo wrote:

> So I have openvpn folder with all the necesary stuff, I formatted usb stick in following way:
> 1. 3GB FAT32 wiht grml on it (grml2usb --bootoptions="nodhcp")        /dev/sdb1
> 2 1GB ext3 with GRMLCFG label with scripts dir and inside it grml.sh script  /dev/sdb5
--------------------------------^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

The grml.sh must be in the root of the filesystem, AFAIK. At least
that's what works for me(TM). I use about the same setup (except that I
use a physical partition for GRMLCFG).

HTH,
Lupe Christoph
--
| It is a well-known fact in any organisation that, if you want a job    |
| done, you should give it to someone who is already very busy.          |
| Terry Pratchett, "Unseen Academicals"                                  |

From: Lupe Christoph <lupe <at> lupe-christoph.de>
To: Bojan Sukalo <shukalo83 <at> yahoo.com>
Cc: "grml <at> mur.at" <grml <at> mur.at>
Sent: Monday, September 5, 2011 4:17 PM
Subject: Re: [Grml] Problem with grml autoconfig

On Monday, 2011-09-05 at 06:50:05 -0700, Bojan Sukalo wrote:
> Thank You.
> That helped a lot.

You're welcome.

> I know we supposed to finish this thread and start another but I need hint a bout ssh server.

> Starting an sshd from script does the job but I have problem because root password is empty so I not access the server.

I would propose that you use a key to access root on this server rather
than a password. While you could overwrite /etc/passwd from grml.sh or
config.tbz, I would not recommend to do that.

Here is what I do:

1) Create /root/.ssh/authorized_keys
2) Save these files and directories to /mnt/GRMLCFG/config.tbz:
/etc/ssh/ssh_host_dsa_key
/etc/ssh/ssh_host_dsa_key.pub
/etc/ssh/ssh_host_ecdsa_key
/etc/ssh/ssh_host_ecdsa_key.pub
/etc/ssh/ssh_host_key
/etc/ssh/ssh_host_key.pub
/etc/ssh/ssh_host_rsa_key
/etc/ssh/ssh_host_rsa_key.pub
/root/.ssh
3) Log in with the key

> Is there a workaroud. bootoption ssh:mysecret does not seem to start the sshd or to change password for grml user.

That should be ssh=password not ssh:password.

> Even if it does, will I abe able to change from grml to root without knowing the root pass.

May I suggest "sudo su -"? The grml user has full sudoers rights,
without a password. But with the default /etc/shadow, "su -" does not
request a password.

If you want to use /mnt/GRMLCFG/config.tbz, here is what I use to manage
it. I write the file and directory names to /mnt/GRMLCFG/config.list and
run this little script (/mnt/GRMLCFG/save-config) to refresh
/mnt/GRMLCFG/config.tbz:

#!/bin/sh

tar cvfjpP /mnt/GRMLCFG/config.tbz -T /mnt/GRMLCFG/config.list

HTH,
Lupe Christoph
--
| It is a well-known fact in any organisation that, if you want a job    |
| done, you should give it to someone who is already very busy.          |
| Terry Pratchett, "Unseen Academicals"                                  |