Manuel Bouyer wrote:

>On Wed, Jun 09, 2004 at 04:16:39PM +0300, Bogdan Mihalcea wrote:
>  
>
>>I have installed NetBSD-2.0 both at office and home. At office I have a 
>>permanent LAN connection while at home I use a dial-up connection. I had 
>>no problem whatsoever configuring and running NetBSD-2.0 at office.  I 
>>have a problem on my home computer, which I realized it's caused by the 
>>fact that I do not have a permanent LAN connection. My mainboard is 
>>based on the nVIDIA Ultra2 chipset (which includes the LAN chipset, not 
>>seen by the NetBSD-2.0 kernel).
>>I have installed the system, but after detecting all the hardware I get
>>
>>    
>>
>>>Setting tty flags.
>>>      
>>>
>>chmod : /dev/ttyp0   Read-only file system
>>.
>>.
>>.
>>chmod : /dev/ttypz   Read-only file system
>>    
>>
>
>It looks like your fstab has a problem here. Can you post the content
>of /etc/fstab ?
>
>  
>
Indeed, my fstab file had a BIG problem.  It resides in the fact that my 
/ partition for FreeBSD comes next after my  NetBSD  slice. Two months 
ago, I upgraded my computer and chose a Soltek75-FRN2/RL2 mainboard, 
nVIDIA Ultra 2 chipset (comprising sound, LAN and IDE controller) with a 
Promise PDC20376 RAID controller together with a SATA 120GB Western 
Digital hard-disk.  I could install  Win2003 (I dislike Windows, but I 
am a research scientist in physics and bureaucracy here in Romania is 
heavily based on Winblowz), then FreeBSD (which could only be booted 
from floppies at install time). NetBSD (1.6.2, 1.6-CZ and 2.0) could not 
detect my SATA disk and the situation is unchanged. That's why I was 
brought to the situation of buying a new IDE hard-disk. At boot time, 
the BIOS fist initializes the IDE disk, then the SATA disk. I was forced 
to reinstall the operating systems again, make a primary NTFS partition, 
then a NetBSD slice and a primary partition for the FreeBSD  /. The rest 
of the partitions are located on the SATA hard-disk (an extended 
partiton for Winblowz  and a FreeBSD slice).
After you gave me the hint, I searched through the fstab file and found 
the following:

/dev/wd0a  /  ffs  rw,noauto   1   1                 (which is in fact 
the FreeBSD / partition, physically located after the NetBSD slice) This 
is where the conflict was
/dev/wd0b  none  swap  sw    0    0
/dev/wd0e  /  ffs    rw    1    1                       (which stands 
for the NetBSD / partition)  
/dev/wd0f   /usr   ffs   rw   1   2
/dev/wd0g   /var   ffs    rw    1    2
/dev/wd0h    /home    ffs    rw    1    2   
/dev/wd0b    /tmp    mfs    rw,-s=358848
kernfs    /kern    kernfs    rw
procfs    /proc    procfs    rw,noauto

The two / partitions appear from the installation phase, where I 
indicated a 'none' mount point for the /dev/wd0a partition. My new fstab 
file has teh first line modified as follows:

#/dev/wd0a   /mnt   ffs   rw,noauto   1   2

As a consequence, I am able to login as a normal user and su to root, 
without any error messages at boot.
 

>>After booting for the first time I was able to create and login as a 
>>normal user, then su to root. After booting for the second, third time 
>>and so on, I can only login as root. While trying to login as a normal 
>>user I get:
>>
>>    
>>
>>>login:
>>>Password:
>>>      
>>>
>>NO LOGINS : System going down at 17:55 (let's say)
>>    
>>
>
>remove the file /etc/nologins
>
>  
>
Fortunately, after the above modifications, it wasn't needed any more.

In the end, I would like to express my graditude and thank you very much 
for your help.
Je n'ai pas assez de mots pour exprimer ma reconnaissance, mais je veux 
vous dire mille fois merci, Monsieur Bouyer. Pour votre temps et votre 
gentillesse.

Avec les meilleures voeux :-) ,
Bogdan

One more question. How do I run sysinst for modifications  after the 
installation is  done? Let's say I would like to modify the active or 
default partition in the NetBSD boot menu.  I come from FreeBSD where 
one can simply run sysinstall and effectuate the desired modifications.