Re: [Cooker] 7.2beta. nfs daemon STILL not being started!!!
Ron Stodden <[EMAIL PROTECTED]> writes:
> Pixel,
>
> The below is for a {customized, install, development} install.
>
> The situation is much worse for an {expert, install, workstation}
> vanilla install. In this case the nfs-utils RPM is not even
> installed The nfs-utils-clients RPM is installed. No sense
> here.
for workstation, nfs-utils will *not* be installed, done on purpose!
no server service installed in workstation install.
Re: [Cooker] 7.2beta. nfs daemon STILL not being started!!!
Pixel,
The below is for a {customized, install, development} install.
The situation is much worse for an {expert, install, workstation}
vanilla install. In this case the nfs-utils RPM is not even
installed The nfs-utils-clients RPM is installed. No sense
here.
Ron Stodden wrote:
>
> The sysvinit installation of Mandrake 7.2 beta, just like all its
> predecessors, still fails to start the nfs daemon.
>
> This means that remote machines are unable to get a mount of a local
> file system at all - Permission Refused.
...
> The post-install fix is easy - ksysv and move nfs to runlevels 3 and
> 5 at, say, S27.
--
Regards,
Ron. [AU]
Re: [Cooker] 7.2beta. nfs daemon STILL not being started!!!
I'd disagree with that - I think that for security reasons all network services should not be started by default until configured to do so by the user no matter what they say the machine is going to be used as. Anyone who plans on running a server of any kind should at least know what service they need to turn on to do it. There are linux zombies all over the place just because so many people install bind and didn't even know it was running a caching nameserver and never updated their system, then they got cracked. On Mon, 09 Oct 2000, you wrote: > Florin Grad wrote: > > now, this is a great debate. > > Should we or should we not start nfs at boot time ? > > > > The default option is set on NOT to run nfs at boot. Why ? > > I see several reasons for this: > > - A newbie with enough space on his hard drive would choose full install > > (in custom section) so he will get dhcp server nfs-server and nfs-client > > and many other servers. > > - This will really slow down the boot process and he > > - will not know that he can disable or either how to disable this > > services at boot. > > I think if a user requests networking at install time, he should get > all the things you mention, plus the nfs daemon. Otherwise he does > not have a usable (out of the box) network*. > > Without the nfs daemon he can mount file systems from other network > nodes, but they cannot mount filesystems from his node "Permission > Refused" - with no clue what is wrong or what to do about it. > > * He doesn't anyway, because today's install does not fully set up > networking. /etc/fstab, /etc/hosts, /etc/resolv, /etc/exports (and > exportfs), /etc/hosts.lpd, are not set up for his network at all!
Re: [Cooker] 7.2beta. nfs daemon STILL not being started!!!
Florin Grad wrote: > now, this is a great debate. > Should we or should we not start nfs at boot time ? > > The default option is set on NOT to run nfs at boot. Why ? > I see several reasons for this: > - A newbie with enough space on his hard drive would choose full install > (in custom section) so he will get dhcp server nfs-server and nfs-client > and many other servers. > - This will really slow down the boot process and he > - will not know that he can disable or either how to disable this services > at boot. I think if a user requests networking at install time, he should get all the things you mention, plus the nfs daemon. Otherwise he does not have a usable (out of the box) network*. Without the nfs daemon he can mount file systems from other network nodes, but they cannot mount filesystems from his node "Permission Refused" - with no clue what is wrong or what to do about it. * He doesn't anyway, because today's install does not fully set up networking. /etc/fstab, /etc/hosts, /etc/resolv, /etc/exports (and exportfs), /etc/hosts.lpd, are not set up for his network at all! -- Regards, Ron. [AU]
Re: [Cooker] 7.2beta. nfs daemon STILL not being started!!!
On Sun Oct 08, 2000 at 08:02:44PM +1100, Ron Stodden wrote: > The sysvinit installation of Mandrake 7.2 beta, just like all its > predecessors, still fails to start the nfs daemon. Huh? I've installed RC1 on my desktop machine twice this past weekend and once on a laptop... in all three cases NFS started just fine. [...] > This situation plainly tells the world that no use of nfs is made > within MandrakeSoft development. How are files shared if there is > no networking? How can a package be tested without having the > context of all the other developers current work? Which is completely inaccurate. I use nfs, many other developers use nfs, and it's being used in the office. Obviously we use it and, quite frankly, it starts just fine. > The post-install fix is easy - ksysv and move nfs to runlevels 3 and > 5 at, say, S27. Or chkconfig --level 35 nfs on -- [EMAIL PROTECTED], OpenPGP key available on www.keyserver.net // Danen Consulting Serviceswww.danen.net, www.freezer-burn.org // MandrakeSoft, Inc. www.linux-mandrake.com 1024D/FE6F2AFD 88D8 0D23 8D4B 3407 5BD7 66F9 2043 D0E5 FE6F 2AFD Current Linux uptime: 1 day 16 hours 37 minutes.
Re: [Cooker] 7.2beta. nfs daemon STILL not being started!!!
[EMAIL PROTECTED] (Tom Massey) writes: > On 9 Oct 2000, Florin Grad wrote: > > > now, this is a great debate. > > Should we or should we not start nfs at boot time ? > > Hi, IMHO the best option is by default to have the bare minimum of > services started after install - if people need a service they should have > to explictly turn it on. This means that you don't get a lot of newbies > running services they don't need or understand, consuming system resources > and weakening security. What might be nice is to build something like > Bastille into the install, so people are taken through and explained the > purposes of each service, and given the option to run it or not. > well, the nfs is now set for the 345 runlevels... -- Florin http://www.linux-mandrake.com
Re: [Cooker] 7.2beta. nfs daemon STILL not being started!!!
Florin Grad <[EMAIL PROTECTED]> writes: [...] > now, this is a great debate. > Should we or should we not start nfs at boot time ? we've chosen that services get started if the package is installed. The install takes care of not installing stuff in desktop install for eg. so change it!
Re: [Cooker] 7.2beta. nfs daemon STILL not being started!!!
On 9 Oct 2000, Florin Grad wrote: > now, this is a great debate. > Should we or should we not start nfs at boot time ? Hi, IMHO the best option is by default to have the bare minimum of services started after install - if people need a service they should have to explictly turn it on. This means that you don't get a lot of newbies running services they don't need or understand, consuming system resources and weakening security. What might be nice is to build something like Bastille into the install, so people are taken through and explained the purposes of each service, and given the option to run it or not.
Re: [Cooker] 7.2beta. nfs daemon STILL not being started!!!
Pixel <[EMAIL PROTECTED]> writes: > Ron Stodden <[EMAIL PROTECTED]> writes: > > > The sysvinit installation of Mandrake 7.2 beta, just like all its > > predecessors, still fails to start the nfs daemon. > > yeah, good question. florin any reason why in /etc/init.d/nfs there is > > # chkconfig: - 60 20 > > where it should be > > # chkconfig: 345 60 20 > > or > > # chkconfig: 2345 60 20 > > ??? > How'di, now, this is a great debate. Should we or should we not start nfs at boot time ? The default option is set on NOT to run nfs at boot. Why ? I see several reasons for this: - A newbie with enough space on his hard drive would choose full install (in custom section) so he will get dhcp server nfs-server and nfs-client and many other servers. - This will really slow down the boot process and he - will not know that he can disable or either how to disable this services at boot. -- Florin http://www.linux-mandrake.com
Re: [Cooker] 7.2beta. nfs daemon STILL not being started!!!
Jason Straight wrote: > > There is one difference - I compile my own kernel - I wonder if nfs got left > out of the mdk kernel you are using? No, nfs and its daemon are installed, just the daemon isn't started. But Pascal R. (aka Pixel) is on to it now, and concedes a problem in the /etc/rc.d/init.d/nfs script - incomplete weightings for the installer - and has asked Florian to correct it. -- Regards, Ron. [AU]
Re: [Cooker] 7.2beta. nfs daemon STILL not being started!!!
There is one difference - I compile my own kernel - I wonder if nfs got left out of the mdk kernel you are using? On Sun, 08 Oct 2000, you wrote: > Jason Straight wrote: > > same except for expert and with DNS. > > > > nfs-utils-clients-0.2.1-1mdk > > nfs-utils-0.2.1-1mdk > > portmap-4.0-11mdk > > initscripts-5.27-37mdk > > Here: > > VERSION: Linux-mandrake Ulysses-i586 20001007 17:53 > > nfs-utils-clients-0.2.1-1mdk > nfs-utils-0.2.1-1mdk > portmap-4.0-11mdk > initscripts-5.27-37mdk > > Same as yours, Jason. So the nfs activation must be from expert > (and not from customized) or from specifying DNS for a local network, > either of which seems an very odd way for the installer to work. ANY > networking should cause nfs inclusion.
Re: [Cooker] 7.2beta. nfs daemon STILL not being started!!!
Jason Straight wrote: > > same except for expert and with DNS. > > nfs-utils-clients-0.2.1-1mdk > nfs-utils-0.2.1-1mdk > portmap-4.0-11mdk > initscripts-5.27-37mdk Here: VERSION: Linux-mandrake Ulysses-i586 20001007 17:53 nfs-utils-clients-0.2.1-1mdk nfs-utils-0.2.1-1mdk portmap-4.0-11mdk initscripts-5.27-37mdk Same as yours, Jason. So the nfs activation must be from expert (and not from customized) or from specifying DNS for a local network, either of which seems an very odd way for the installer to work. ANY networking should cause nfs inclusion. -- Regards, Ron. [AU]
Re: [Cooker] 7.2beta. nfs daemon STILL not being started!!!
Ron Stodden <[EMAIL PROTECTED]> writes: > The sysvinit installation of Mandrake 7.2 beta, just like all its > predecessors, still fails to start the nfs daemon. yeah, good question. florin any reason why in /etc/init.d/nfs there is # chkconfig: - 60 20 where it should be # chkconfig: 345 60 20 or # chkconfig: 2345 60 20 ???
Re: [Cooker] 7.2beta. nfs daemon STILL not being started!!!
same except for expert and with DNS. nfs-utils-clients-0.2.1-1mdk nfs-utils-0.2.1-1mdk portmap-4.0-11mdk initscripts-5.27-37mdk On Sun, 08 Oct 2000, you wrote: > Jason Straight wrote: > > NFS works fine here. > > What kind of install? > > My standard is en_UK - US international keyboard - customized - > install - development - all packages - local network, no DNS, no > proxy.
Re: [Cooker] 7.2beta. nfs daemon STILL not being started!!!
Jason Straight wrote: > NFS works fine here. What kind of install? My standard is en_UK - US international keyboard - customized - install - development - all packages - local network, no DNS, no proxy. -- Regards, Ron. [AU]
Re: [Cooker] 7.2beta. nfs daemon STILL not being started!!!
NFS works fine here. On Sun, 08 Oct 2000, you wrote: > The sysvinit installation of Mandrake 7.2 beta, just like all its > predecessors, still fails to start the nfs daemon. > > This means that remote machines are unable to get a mount of a local > file system at all - Permission Refused. > > I have personally reported this a number of times, and am justifiably > angry that, again, noone effective at MandrakeSoft is acting. I must > say that portmap and nfs-clients are now installed and brought up, > which is great progress. > > This situation plainly tells the world that no use of nfs is made > within MandrakeSoft development. How are files shared if there is > no networking? How can a package be tested without having the > context of all the other developers current work? > > No-one would believe this if you tried to tell them. > > The post-install fix is easy - ksysv and move nfs to runlevels 3 and > 5 at, say, S27.
[Cooker] 7.2beta. nfs daemon STILL not being started!!!
The sysvinit installation of Mandrake 7.2 beta, just like all its predecessors, still fails to start the nfs daemon. This means that remote machines are unable to get a mount of a local file system at all - Permission Refused. I have personally reported this a number of times, and am justifiably angry that, again, noone effective at MandrakeSoft is acting. I must say that portmap and nfs-clients are now installed and brought up, which is great progress. This situation plainly tells the world that no use of nfs is made within MandrakeSoft development. How are files shared if there is no networking? How can a package be tested without having the context of all the other developers current work? No-one would believe this if you tried to tell them. The post-install fix is easy - ksysv and move nfs to runlevels 3 and 5 at, say, S27. -- Regards, Ron. [AU]
