On Sat, 3 Jan 2004, Clodoaldo Pinto Neto wrote:
> > > could no create /var/yp: no such file or directory
> >
> > This is important. You need to figure out why it can't create /var/yp
> >
>
> Is ltsp supposed to write to the ltsp file system tree?
> I exported the tree as rw:
>
> [EMAIL PROTECTED] etc]$ cat exports
> #
> ## LTSP-begin ##
> #
>
> /opt/ltsp 192.168.0.0/255.255.255.0(rw,no_root_squash,sync)
> /var/opt/ltsp/swapfiles 192.168.0.0/255.255.255.0(rw,no_root_squash,async)
>
> ## LTSP-end ##
> /home 192.168.0.0/255.255.255.0(rw,no_root_squash,sync)
> ---------------------------------------------
> then:
> [EMAIL PROTECTED] etc]# exportfs -r
No, even if you change the /etc/exports file, the filesystem will NOT
be writeable. You would need to modify the /linuxrc script on the
initrd image.
But, that's not the correct way to fix this.
If you are getting an error trying to write to /var, then it
probably indicates that the /var directory isn't a symlink to /tmp/var
Did you do something to remove the /opt/ltsp/i386/var symlink ?
if you get into your /opt/ltsp/i386 directory and do:
ls -l
You should see something that looks like this:
[EMAIL PROTECTED] i386]$ l
total 68
drwxr-xr-x 2 root root 4096 Dec 23 14:19 bin
drwxr-xr-x 2 root root 4096 Dec 14 01:28 dev
drwxr-xr-x 8 root root 4096 Dec 28 21:49 etc
drwxr-xr-x 2 root root 4096 Dec 14 01:28 home
drwxr-xr-x 2 root root 4096 Dec 14 03:20 include
drwxr-xr-x 2 root root 4096 Dec 14 02:12 info
drwxr-xr-x 2 root root 4096 Dec 17 22:37 initrd
drwxr-xr-x 5 root root 4096 Dec 14 03:50 lib
drwxr-xr-x 2 root root 4096 Dec 14 03:19 libexec
drwxr-xr-x 9 root root 4096 Dec 14 03:49 man
lrwxrwxrwx 1 root root 8 Dec 14 01:28 mnt -> /tmp/mnt
drwxr-xr-x 2 root root 4096 Dec 14 01:28 oldroot
drwxr-xr-x 2 root root 4096 Dec 14 01:28 proc
drwxr-xr-x 2 root root 4096 Dec 15 15:25 root
drwxr-xr-x 2 root root 4096 Dec 14 03:50 sbin
drwxr-xr-x 4 root root 4096 Dec 14 03:19 share
drwxr-xr-x 2 root root 4096 Dec 14 01:28 tmp
drwxr-xr-x 12 root root 4096 Dec 14 22:31 usr
lrwxrwxrwx 1 root root 8 Dec 14 03:16 var -> /tmp/var
Notice the 2 symlinks in that listing ?
Make sure yours has those too.
Jim McQuillan
[EMAIL PROTECTED]
>
> Now the message is:
> cannot create var/yp/biding : read only file system (or something very similar)
>
> > Try setting 'SCREEN_01 = shell' and see if you see any more errors.
> >
> It already was as shell
>
> --- [EMAIL PROTECTED] escreveu: > On Sat, 3 Jan 2004, Clodoaldo Pinto Neto wrote:
> >
> > > Jim,
> > >
> > > The s00 name is in the /etc/hosts file.
> > >
> > > I can ping it from a Windows machine:
> > >
> > > C:\>ping s00
> > > Disparando contra s00 [192.168.0.2] com 32 bytes de dados:
> > > Resposta de 192.168.0.2: bytes=32 tempo<1ms TTL=64
> > > Resposta de 192.168.0.2: bytes=32 tempo<1ms TTL=64
> > > Resposta de 192.168.0.2: bytes=32 tempo<1ms TTL=64
> > > Resposta de 192.168.0.2: bytes=32 tempo<1ms TTL=64
> > > Estatísticas do Ping para 192.168.0.2:
> > > Pacotes: Enviados = 4, Recebidos = 4, Perdidos = 0 (0% de perda),
> > > Aproximar um número redondo de vezes em milissegundos:
> > > Mínimo = 0ms, Máximo = 0ms, Média = 0ms
> > > ------------------------------------------------------------
> > > I don't know how the Windows machine knows about it but as you see it
> > knows.
> > > C:\>ping 192.168.0.2 also works
> > >
> > > When I hook the monitor to the workstation at booting I get the messages:
> > > syslogd: cannot write to remote file handle on 192.168.0.2:514
> >
> > This isn't important. It just means you need to configure your syslogd
> > on your server to accept remote logging. It's a good idea to fix
> > this, so that you can get logging messages from the workstation.
> > but it isn't causing your problem.
> >
> >
> > > could no create /var/yp: no such file or directory
> >
> > This is important. You need to figure out why it can't create /var/yp
> >
> > Try setting 'SCREEN_01 = shell' and see if you see any more errors.
> >
> > Jim.
> >
>
> ______________________________________________________________________
>
> Conheça a nova central de informações anti-spam do Yahoo! Mail:
> http://www.yahoo.com.br/antispam
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: IBM Linux Tutorials.
> Become an expert in LINUX or just sharpen your skills. Sign up for IBM's
> Free Linux Tutorials. Learn everything from the bash shell to sys admin.
> Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
> _____________________________________________________________________
> Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto:
> https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
> For additional LTSP help, try #ltsp channel on irc.freenode.net
>
-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills. Sign up for IBM's
Free Linux Tutorials. Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id78&alloc_id371&op=click
_____________________________________________________________________
Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto:
https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
For additional LTSP help, try #ltsp channel on irc.freenode.net
