Port-atari archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: Testing sysinst.fs



On Tue, Nov 4, 2008 at 6:39 PM, David Brownlee <abs%netbsd.org@localhost> wrote:
>        You can test/read and modify the contents of sysinst.fs
>        and other similar files on a running NetBSD system. (See
>        later note if you want to do this on a non NetBSD/atari
>        system). As root:
>
>                # vnconfig vnd0 sysinst.fs
>                # mount /dev/vnd0a /mnt
>
>                The contents of sysinst.fs are now available to be
>                read, run or modified under /mnt
>
>                You can also simulate running the files inside the
>                miniroot in a chroot() so the shell can only see
>                the files inside.  Obviously if you let the install
>                try to write to the disk containing the sysinst.fs
>                file its all going to crash, but it should be
>                possible to test installing to another disk.
>
>                # env SHELL=/bin/sh chroot /mnt
>
>                Finally when you are done:
>
>                # umount /mnt
>                # vnconfig -u vnd0
>
>        I've had a look inside the latest current build of sysinst.fs
>        and I can't see any issues with the .profile file. Can you
>        see any your end or possibly make the file you are using
>        available?
>
>
>  
> http://ftp.netbsd.org/pub/NetBSD/NetBSD-daily/HEAD/200811020002Z/atari/installation/miniroot/sysinst.fs.gz

Thanks for the sysinst testing/reading information! As a quick test I tried
NetBSD 4.0.1 sysinst and current sysinst.

Differences are that NetBSD 4.0.1 installer executes .profile file, but
complains following:

mount_ffs: realpath /kern/rootdev: bad file descriptor
cp: /tmp/.root_writable: read-only file system

and then it proceeds to ask keyboard map.

Current installer just complains about unterminated quoted string and
drops to sh prompt.

I copied and checked .profile files from both installers and they're identical.
so there seems to be some odd thing that causes this issue.

-Tuomo


Home | Main Index | Thread Index | Old Index