Re: What is seen in 'Local Network' ? (newbie)
From: Kevin Nathan (knathan_at_project54.com)
Date: 05/23/04
- Next message: David Nettles: "Re: Problem with bootdisk and Suse 9.1"
- Previous message: houghi: "Re: Mail won't copy"
- In reply to: AC: "Re: What is seen in 'Local Network' ? (newbie)"
- Next in thread: Karen: "Re: What is seen in 'Local Network' ? (newbie)"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Sat, 22 May 2004 17:26:27 -0600
On Sat, 22 May 2004 23:24:21 +0100
AC <aec$news@candt.demon.co.uk> wrote:
> I was finding that samba *did* apparently work - I could see windows
> boxes on my linux box.
> However since I could not actually *see* anything from the linux box
> displayed on itself,
>
That's because Linux doesn't communicate with SMB (the Windows protocol)
so you have to setup a Samba server to define items to make viewable in
Windows (or even another Linux box running Samba). I will assume this is
partially working from the config file in a previous post. You should
see your /home/user directory.
If you want to share some other dir, you need to setup a public share
(you can have as many as you want). The way I did it was to add a dir
in /home named public:
su
mkdir /home/public
chgrp users /home/public
chmod 770 /home/public
and then had this part in my /etc/samba/smb.conf file:
--------------------------------------------
#
# The following share is publicly accessible from Windows
# machines on my home network.
#
[public]
comment = Public Storage for all users
path = /home/public
read only = no
create mask = 666
directory mask = 777
browseable = Yes
guest ok = Yes
--------------------------------------------
I don't use this much anymore, no Windows boxes at home, but it's handy
if someone brings a computer or laptop over and I need to transfer some
files. (I also can share it with NFS for the other Linux boxes.)
> Although one question I now have is - what *are* the limits of yast? I
> come from a win environment, and although it might sound silly to
> linux users, I do not yet know when I *should* be using command line
> stuff.
>
YaST is pretty comprehensive. If you run up against something it can't
work with, then you will have to edit config files manually. This can
be done at the command line or via Konqueror and your favorite editor.
My suggestion is to use YaST as much as possible and gradually work
your way into hand-editting files.
If you want to work with the command line, get a good book on BASH or
bookmark sites like:
http://www.icon.co.za/~psheer/book/index.html.gz
(if you're on dial up, download that file and view it locally.) This
site is geared more toward's Red Hat, but it's generally applicable to
any distro.
> And reading and using 12) as a total newbie is a bit like trying to
> learn English by reading a shakespeare sonnet.
>
I'll see if I can make it more accessible to new users. It's a fine
balancing act, where you don't want a complete tutorial, but then it
*must* be usable as is and at least get you moving. :-)
> I am still not sure what is a 'suse user' as distinct from a 'samba
> user', although things have moved on somewhat anyway. I presume suse
> user means the login name used for logging into suse. It took a while
> of research to presume that, I do hope it is correct.
>
Yes, that's correct. The Samba user is simply a 'mapping' between your
Linux user and how that user looks to Samba/Windows.
> If yast does not create a samba user semi automatically then I am
> still finding my way around.
>
I don't think it does, but my previous post to you (today) I believe
*has* answered that.
> Some of my problems may have been associated with use of dhcp in my
> lan, I am not sure, but I have reconfigured to run the linux box as
> fixed IP, outside the (new) limits of the dhcp range. It allows easier
> simple trouble shooting.
>
For a small home network, DHCP is overkill -- it's do-able but adds
more complexity than is necessary, especially for newbies.
> Not knowing *How* to find my way around linux (suse) I could do almost
> nothing, apart from use yast,
>
Take your time getting familiar with it. KDE is close enough to the
*feel* of Windows to allow a Windows user some familiarity, then it's
just a matter of learning what programs do what. Play with it and
experiment -- just don't put anything really important on it at first,
so you don't worry about trashing something. As your comfort level
increases, so will your ability to solve problems.
> btw *can* I set up a 'samba username' in yast?
>
I'm not sure, but I don't think so. You'd be better off installing
webmin and using that for configurations that YaST doesn't handle.
> If I use yast as user1 I find I have no rights to change (samba),
> hence root.
>
If you run YaST as a normal user, it should ask you for root password
after you click on it. What Karen was referring to was 'logging in' as
root and running KDE, et.al., *that* way.
> note 1)
> Please be clear I will most *certainly* be out of root as soon as I
> can do what I need to as user1 (!)
>
Basically, do everything as user and only 'su' to root when it doesn't
let you do something as user. I know it *seems* more convenient, but
there is more work running some things in root. For instance, SUSE sets
up a pretty limited PATH variable as root (which is as it should be), so
running Mozilla (or many other programs) from a command line requires
you to enter the full pathname to it; running as a regular user, you
just type 'mozilla' (or whatever).
Another reason for not running a GUI as root comes from my experience
early on: I was using GNOME in Red Hat (4.x or 5.x) and ignored the
warning about running it as root. I had a file manager open on the
desktop and, while moving the mouse to the other side of the screen to
click on something there, I accidentally clicked the mouse as it was
moving over the file manager. This moved some files, I had no idea
which ones, or where to, and Linux wouldn't come up on the next boot. :-)
> btw, although is it heresy in linux (and I am very glad of that),
> having to reinstall is not too big a price to pay for some experience.
> Coming from a windows environment I have become quite hardened to it.
> Just don't mention it in front of the children please! (see note 1)
>
The very first time I installed Linux (Red Hat 4.2 in 1998) it took all
of 15 minutes. I then proceeded to hose the installation many times
while experimenting, which led to something like eight or nine installs
that weekend (was firmly in the Windows mind-set back then!), but at
fifteen minutes each, I didn't care! :-) I would have learned more if I
would have investigated each problem. You may be tempted to re-install,
but try to fix it first -- at least for the learning experience . . .
:-)
-- Kevin Nathan (Montana, USA) Open standards. Open source. Open minds. The command line is the front line. Linux 2.4.20-4GB-athlon 4:39pm up 11 days 3:12, 7 users, load average: 0.00, 0.05, 0.01
- Next message: David Nettles: "Re: Problem with bootdisk and Suse 9.1"
- Previous message: houghi: "Re: Mail won't copy"
- In reply to: AC: "Re: What is seen in 'Local Network' ? (newbie)"
- Next in thread: Karen: "Re: What is seen in 'Local Network' ? (newbie)"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
