[ previous ] [ next ] [ threads ]
 
 From:  "Chris Bond" <chris at logics dot co dot uk>
 To:  "'Thomas Hertz'" <thomas at hz dot se>
 Cc:  <m0n0wall at lists dot m0n0 dot ch>
 Subject:  RE: [m0n0wall] M0n0wall PC Image fails to work
 Date:  Fri, 26 Sep 2003 15:03:47 +0100
Thinking about this logically - is there any reason you couldn't run a
script on boot that generates /etc/fstab based on where it boots from so it
doesn't have this problem on the standard image.  Im sure someone did
something similar for ipcop at some stage.

-----Original Message-----
From: Thomas Hertz [mailto:thomas at hz dot se] 
Sent: 26 September 2003 2:45 PM
To: chris at logics dot co dot uk
Cc: term at hz dot se; m0n0wall at lists dot m0n0 dot ch
Subject: Re: [m0n0wall] M0n0wall PC Image fails to work

It's the same process as with the generic-image, copy it to some other 
directory, gunzip it and mount it loopback.

cp mfsroot.tgz /tmp && cd /tmp
gunzip mfsroot.tgz
mdconfig -a -t vnode -f mfsroot
mount /dev/md<number> /mnt2

When you've modified the mfsroot image, gzip it again to mfsroot.gz, 
copy it back to the mounted generic-image.
Then unmount all md0 devices, and unconfig them.

--
Thomas Hertz

>Ok that worked - im assuming that /etc/fstab is in mfsroot.gz - how do I
get
>at that file tried gunzip and untar but nothing...
>
>
>
>-----Original Message-----
>From: Thomas Hertz [mailto:thomas at hz dot se] 
>Sent: 26 September 2003 2:34 PM
>To: chris at logics dot co dot uk
>Cc: term at hz dot se; m0n0wall at lists dot m0n0 dot ch
>Subject: Re: [m0n0wall] M0n0wall PC Image fails to work
>
>Ah, of course. I'm sorry. The image is gzipped, so you will have to 
>unzip it:
>
>gzcat generic-pc-pb15r497.img >generic.img
>
>then you can mount it as I've described.
>
>--
>Thomas Hertz
>
>
>Chris Bond wrote:
>
>  
>
>>I get this when doing that.
>>
>>mount: /dev/md0 on /mnt/flash: incorrect super block
>>
>>-----Original Message-----
>>From: term at hz dot se [mailto:term at hz dot se] 
>>Sent: 26 September 2003 11:10 AM
>>To: Chris Bond
>>Cc: m0n0wall at lists dot m0n0 dot ch
>>Subject: RE: [m0n0wall] M0n0wall PC Image fails to work
>>
>>Try:
>>
>>mdconfig -a -t vnode -f mylittleimage.img
>>
>>It will show up as /dev/md<number> , and you mount it with:
>>
>>mount /dev/md<number> /mnt
>>
>>Cheers,
>>
>>--
>>Thomas Hertz
>>
>>Try vnconfig vn0 image.im
>>On Fri, 26 Sep 2003, Chris Bond wrote:
>>
>> 
>>
>>    
>>
>>>Date: Fri, 26 Sep 2003 09:57:27 +0100
>>>From: Chris Bond <chris at logics dot co dot uk>
>>>To: "m0n0wall at lists dot m0n0 dot ch" <m0n0wall at lists dot m0n0 dot ch>
>>>Subject: RE: [m0n0wall] M0n0wall PC Image fails to work
>>>
>>>Ok got freebsd5 installed and grabbed the image onto the box - whats the
>>>cmds to mount the image so I can modify the fstab.  It seems its mdconfig
>>>now not vnconfig.
>>>
>>>Sorry to be a pain =)
>>>
>>>-----Original Message-----
>>>From: Thomas Hertz [mailto:thomas at hz dot se]
>>>Sent: 25 September 2003 4:16 PM
>>>To: m0n0wall at lists dot m0n0 dot ch
>>>Subject: Re: [m0n0wall] M0n0wall PC Image fails to work
>>>
>>>Just mount the image loopback, and edit /etc/fstab and change all
>>>occurances of "ad0a" to "ad2a".
>>>In *BSD you use the "vnconfig" command, and in linux "mount -o
>>>generic-pc-pb15r497.img /mnt".
>>>
>>>--
>>>Thomas Hertz
>>>
>>>
>>>Chris Bond wrote:
>>>
>>>   
>>>
>>>      
>>>
>>>>Just installed the PC Image on a compactflash.  It boots you get the
>>>>     
>>>>
>>>>        
>>>>
>>kernel
>> 
>>
>>    
>>
>>>>loading etc but you get the following messages on boot and consequently
>>>>     
>>>>
>>>>        
>>>>
>>you
>> 
>>
>>    
>>
>>>>can not run assign ip or any of the first 2-3 options on the console
>>>>     
>>>>
>>>>        
>>>>
>>screen
>> 
>>
>>    
>>
>>>>nor is 192.168.1.1 pingable.
>>>>
>>>>Mount root from uds /dev/md0c
>>>>Mount /dev/ad0a: Device not configured
>>>>
>>>>Warning: fopen(conf/config.xml): failed to open stream: No such file or
>>>>directory in /etc/inc/xmlparse.inc on line 123
>>>>
>>>>Is there anyway to fix this?  Its running on the linux eqvil of /dev/hdc
>>>>     
>>>>
>>>>        
>>>>
>>-
>> 
>>
>>    
>>
>>>>cant change this as it's a lex light board.
>>>>
>>>>Kind Regards,
>>>>Chris Bond
>>>>
>>>>
>>>>---------------------------------------------------------------------
>>>>To unsubscribe, e-mail: m0n0wall dash unsubscribe at lists dot m0n0 dot ch
>>>>For additional commands, e-mail: m0n0wall dash help at lists dot m0n0 dot ch
>>>>
>>>>
>>>>
>>>>     
>>>>
>>>>        
>>>>
>>>---------------------------------------------------------------------
>>>To unsubscribe, e-mail: m0n0wall dash unsubscribe at lists dot m0n0 dot ch
>>>For additional commands, e-mail: m0n0wall dash help at lists dot m0n0 dot ch
>>>
>>>
>>>
>>>---------------------------------------------------------------------
>>>To unsubscribe, e-mail: m0n0wall dash unsubscribe at lists dot m0n0 dot ch
>>>For additional commands, e-mail: m0n0wall dash help at lists dot m0n0 dot ch
>>>
>>>
>>>   
>>>
>>>      
>>>
>>---------------------------------------------------------------------
>>To unsubscribe, e-mail: m0n0wall dash unsubscribe at lists dot m0n0 dot ch
>>For additional commands, e-mail: m0n0wall dash help at lists dot m0n0 dot ch
>>
>> 
>>
>>    
>>
>
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: m0n0wall dash unsubscribe at lists dot m0n0 dot ch
>For additional commands, e-mail: m0n0wall dash help at lists dot m0n0 dot ch
>
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: m0n0wall dash unsubscribe at lists dot m0n0 dot ch
>For additional commands, e-mail: m0n0wall dash help at lists dot m0n0 dot ch
>
>  
>



---------------------------------------------------------------------
To unsubscribe, e-mail: m0n0wall dash unsubscribe at lists dot m0n0 dot ch
For additional commands, e-mail: m0n0wall dash help at lists dot m0n0 dot ch