Re: Problem setting up NFS on Ubuntu

In comp.os.linux.setup Alan Adams <alan.adams@xxxxxxxxxxxxxxxxxxxxxxxxxxx>:
> In message <lh7o73-8jc.ln1@xxxxxxxxxxxxxxx>
> Michael Heiming <michael+USENET@xxxxxxxxxxxxxx> wrote:

>> In comp.os.linux.setup Alan Adams <alan.adams@xxxxxxxxxxxxxxxxxxxxxxxxxxx>:
>> > Michael Heiming <michael+USENET@xxxxxxxxxxxxxx> wrote:
>> >> In comp.os.linux.setup Alan Adams <alan.adams@xxxxxxxxxxxxxxxxxxxxxxxxxxx>:
>> >> > Alan Adams <alan.adams@xxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
>> >>
>> >> [ exporting vfat via NSF? ]
>>
>> [ permission/ownership problems on vfat ]
>>
>> >> Those are forced/faked while mounting from the kernel, see 'man
>> >> mount' for vfat mount options. In general it's a rather bad idea
>> >> exporting vfat via NFS, it's not designed for multiuser systems
>> >> and the outcome might not be as expected. Hopefully you have a
>> >> good backup?
>>
>> > Thank you. This is the backup. The idea is to use this as a backup server,
>> > for a PC and a RISC OS system. Since I am very new to Linux, and have
>> > forgotten most of the litle I knew about commercial Unix, I used FAT32 so I
>> > could set it up initially using Windows, and revert to that in emergency.
>> > This system boots Ubuntu, Win98 and WinXP.
>>
>> > I have managed to get the share r/w now, by putting uid, gid and umask
>> > options in fstab.
>>
>> Again it's not recommended to export vfat via nfs, put ext3 or
>> alike on the FS and use samba to export it to doze clients.
>>
>> > I have also discovered how to login to the gui as root, which helps
>> > enormously.
>>
>> Please *don't!* This is completely unneeded, this is a multi-user
>> system not doze, you can use sudo/su from the next xterm to do
>> what you need to do as root, but please never ever login as root
>> via X.

> OK maybe I missed something, but that way I have to use command line tools,
> whereas using X I can use a sensible editor.

Wrong, you can use any app you like just start it from some
xterm, or use sudo and make some menu with apps to start as root.

> vi is possible the single most important reason why I've avoided Unix as
> long as possible.

That's the most powerful editor you should find on almost any
unix system, if you think vim is hard, try some original vi on an
old sun, then come back and complain. ;-)

> What's wrong with using the graphical tools, apart from the fact that it
> isn't geeky enough?

Nothing wrong with them, use them if they suit your needs. For
others they are just to slow, inflexible or not installed on the
system you just logged in. CLI tools are more or less the same
over all unix, making knowledge portable over a large amount of
OS. With GUI you'll just stay an idiot clicking on pictures and
do what the person programming the app thought you should do. CLI
gives you all those extremely powerful tools and an environment to
chain them together just as you need.

>>
>> > Depending on the results of some tests, I might try samba rather than nfs,
>> > which should make windows client access easier, and does work also from RISC
>> > OS. I tried samba a while ago, and couldn't get it to work, but I have
>> > learnt a bit more since then.
>>
>> Indeed, I'd highly recommend using samba.

> OK, I can now log in to samba using RISC OS, but not from windows. Ironic
> maybe, but also annoying. Among the things I changed was allowing plaintext
> passwords, as I think that is what was stopping RISC OS. However Windows
> wasn't working before. I get "Workgroup is not accessible... (bit about
> permissions). The account is not authorised to log in from this station."
> Both machines should be in Workgroup.

There are various docs/howto (www.tldp.org + www.samba.org) to
get you going it's not rocket science.

[..]

--
Michael Heiming (X-PGP-Sig > GPG-Key ID: EDD27B94)
mail: echo zvpunry@xxxxxxxxxx | perl -pe 'y/a-z/n-za-m/'
#bofh excuse 323: Your processor has processed too many
instructions. Turn it off immediately, do not type any
.

Relevant Pages

  • Re: Network Printing...Finally
    ... You do not need Print Services for Unix running on the Windows machine to ... service simply allows Windows to act as an LPR server. ... Samba is not the best way to go! ...
    (comp.unix.bsd.freebsd.misc)
  • Re: version control using subversion
    ... Some applets that help designers get in ... If you want to cross boundary between unix and windows, you may find complications and need system administrators help anyway... ... There is in Samba a way to send winpopup notifications like those defined in windows for workgroups. ...
    (comp.cad.cadence)
  • Re: Why are there few viruses for UNIX/Linux systems?
    ... Most of my daemons _aren't_ running as root, ... The OTHER big problem on Windows is that typical configurations ... Typical software written for Unix is written by people that have ... thus have an underlying security model that involves there only being ...
    (comp.os.linux.security)
  • Re: Next project, C programming problem.
    ... >> But while it may be able to tell what a windows file is (actually, ... >> file formats) there is no way it can know what a file on a Unix ... SAMBA should not be converting files. ... > good time saver. ...
    (comp.os.vms)
  • Re: SFU3.5 and getting permissions to work
    ... You associate a Windows user with a Unix user (eg root). ... Whenever a file is written there by the unix server, it typically comes across as having permissions only of SYSTEM and read. ...
    (microsoft.public.win2000.active_directory)
Loading