Displaying 20 results from an estimated 7000 matches similar to: "small lan - 2 solved"
2005 Jul 08
1
small lan - novice - 2
Hi,
armed with Samba-3 -by example I proceeded to test my 2 linux lan
[suselinux pro 9.1 with Samba 3.0.9-2.6-suse].
I followed instructions and made the smb.config as small as possiblw:
[global]
workgroup = snj
server string = Samba Server
guest ok = yes
[orb]
comment = removable 2.2 gb hd
path = /orb
browsable = yes
read only = no
However, I was stumped practically immediately as you can
2005 Jun 13
0
novice - samba3+; suse linuxpro9.1
hi,
I thought it would be easy and over quickly - it has been anything
but...
I decided to test and use Samba 3.+ on my Suse linux pro 9.1 lan but
cannot get it to work and need some help/guidance.
I have two essentially identical linux computers [east and west] and I
have both of them as both server AND client. At a later date, after
this `simple' lan works, I plan to add a ms portable
2005 Aug 06
0
printer loss [susepro9.1]-mostly solved-samba the problem?
Hi,
Thanks for the suggestions - the immediate problem is solved. I feel
that a monstrous weight has been lifted.
I tried the suggestions and the printer connection is back -
wonderful!!!!! what a relief!
I stopped the firewall and samba so it is one of them, or both which is
causing the problem?
I would vote for samba3 as the culprit because the printer loss occurred
on both machines on a 2
2005 Apr 18
1
error msg using testparm
hi,
I'm new to Samba.
I use Suse linux 9.1pro & kde on a small network with Samba 3.0.9.
I tried the testparm from the Official Samba -3 howto.
Unfortunately the book, etc. does not address the error msg given,
follows.
Can somebody help?
scn@scn:~> testparm -s -v | egrep "(lp|print|spool|driver|ports|\[)"
Load smb config files from /etc/samba/smb.conf
Processing section
2005 Jun 28
0
small lan - novice
Hi,
John, thanks for replying.
I am fully aware that this is a volunteer effort and do appreciate it
very much. I really didn't expect an automatic answer - I was suggesting
an automatic response which could indicate the objection[s]?
I have downloaded the S3be `book' and ordered it from amazon.
I was puzzled by your comment:
`Please do not refer to smbfs's friends as Samba. The
2005 Jun 24
1
Samba3 - small lan [2] - fstab & smbfstab
Hi,
This is the second of 2 emails
I have two essentially identical linux computers [east and west] both
running Samba 3.0.9-2.6-suse with Suse linux pro 9.1 on a two machine
lan - [east & west] connected by a hub.
I am using `The Official Samba-3 HowTo & ref guide by Terpstra et al' as
my samba reference.
I am not clear which fstab to use.
/etc/samba/smbfstab
2005 Jun 24
1
Samba3 - small lan [1]
Hi,
I have posted to this list once before without any reply. It would be
nice if some reply could indicate why the posting was not appropriate
and some indication as to what one should do - the last time I included
my smbconf. This time I have reworked my questions, limited their scope
, and put them in two emails.
I have two essentially identical linux computers [east and west] both
running
2005 Jul 18
0
loss of cups printer definition - suse linux pro 9.1 & samba 3.0.9-2.6-suse - small lan
On a working printer & system
I needed to change the printer definition on one of two systems each
with a printer [samsung laser and hplj4].
Yast2-printer stalled at 50% [loading configuration] and had to be
closed.
When I tried again the cups daemon died when trying to save the printer
definition.
I found that /etc/cups/ was empty!
Re-installing the printer function in Yast2 did not do any
2003 Jun 03
1
wine-win3.1 program in SuSE8.2 - help
Help
I am not having much success getting the program to work and would
appreciate some pointers and suggestions for further tests.
I ran the program: wine accts.exe
from its program directory
without debug and got the following:
wine already configured, run 'winesetup' to reconfigure.
why is the above msg considering that wine would not run if it wasn't
configured?
I hope the
2003 Mar 16
3
win3.1 in wine & suse8.1
I'm new to wine and suse 8.1.
I d/l the most current wine version for suse8.1 = 200303.. and rpmed it.
I was surprised that wine was not updated with Yast but only directly
with rpm.-F ...
Does anybody you know why? I had tried it first and it seemed to work
but rpm -q showed the same date!
I now have doubts on all the other rpm patches/updates ...
The win3.1 program is special purpose
2018 Jan 31
0
[ANNOUNCE] xkeyboard-config 2.23
Here is another release...
David Paleino (1):
Added it(intl), it(scn) and us(scn)
Marko Myllynen (1):
Minor fidvorak adjustment
Sergey Udaltsov (9):
Typo fixed
Refreshed the default Arabic keyboard layout
more robust comment handling
replace 'ʼ' (0x10002bc) with '՚' (0x100055a) in armenian layout
Add polish layout for use glagolica
2007 Jan 05
3
Dovecot's deliver trouble (...probably bug?)
Hello everybody!
I am a Linux admin trying to move my mail
system based on qmail to the software which is more spam-protected:
exim4 + dovecot-1.0rc15 + pgsql . I've downloaded and rebuild dovecot
from src.rpm (for fc4). During
the testing stage I've discovered two troubles:
1) the problem with deliver (...I'm not sure it's a really bug). Here
is relevant part
of my
2017 Jan 26
2
Critical XRay fixes for Arm32
I see. Thanks for clarifying.
I'm Ok with merging these if Dean agrees, as I believe he's the code owner.
Thanks,
Hans
On Thu, Jan 26, 2017 at 11:47 AM, Serge Rogatch <serge.rogatch at gmail.com> wrote:
> There were no LLVM tests for presence of XRay instrumentation map in the
> emitted assembly. You can see that https://reviews.llvm.org/D28624 adds this
> check to the
2017 Jan 26
2
Critical XRay fixes for Arm32
I'm wondering why the lit tests didn't catch this as part of testing rc1 on ARM.
On Thu, Jan 26, 2017 at 11:25 AM, Serge Rogatch <serge.rogatch at gmail.com> wrote:
> XRay is tested automatically on build-bots with tests in LLVM and
> compiler-rt . Or are you asking for manual testing instructions?
> Of these 2 patches, the compiler-rt patch depends on LLVM patch because
2017 Jan 26
2
Critical XRay fixes for Arm32
How is XRay tested? IIRC, Renato didn't see any test failures on ARM?
Merging sounds reasonbaly, I'd just like to understand what's the risk
for the branch.
On Thu, Jan 26, 2017 at 10:29 AM, Serge Rogatch <serge.rogatch at gmail.com> wrote:
> Hans, these changes reached trunk in https://reviews.llvm.org/rL292516 and
> https://reviews.llvm.org/rL292517 . Could you look?
2006 Jan 16
1
multiple config files
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
is there a way for isolinux to have multiple config files for the same
isolinux.bin (in grub it's configfile (cd)/boot/grub/other.lst and in
cdshell it's script file.scn) to have recursive f1-f10 ability and make
the isolinux.cfg less bulky
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (MingW32)
Comment: Created with GnuPG
2013 Jun 07
0
[PATCH RFC] s390/virtio-ccw: Adapter interrupt support.
Handle the new CCW_CMD_SET_IND_ADAPTER command enabling adapter interrupts
on guest request. When active, host->guest notifications will be handled
via global_indicator -> queue indicators instead of queue indicators +
subchannel I/O interrupt. Indicators for virtqueues may be present at an
offset.
Signed-off-by: Cornelia Huck <cornelia.huck at de.ibm.com>
---
hw/s390x/css.c |
2013 Jul 09
0
[RFC PATCH v2] s390/virtio-ccw: Adapter interrupt support.
Handle the new CCW_CMD_SET_IND_ADAPTER command enabling adapter interrupts
on guest request. When active, host->guest notifications will be handled
via global_indicator -> queue indicators instead of queue indicators +
subchannel I/O interrupt. Indicators for virtqueues may be present at an
offset.
Signed-off-by: Cornelia Huck <cornelia.huck at de.ibm.com>
---
hw/s390x/css.c |
2019 Apr 09
0
[RFC PATCH 05/12] s390/cio: add protected virtualization support to cio
On Fri, 5 Apr 2019 01:16:15 +0200
Halil Pasic <pasic at linux.ibm.com> wrote:
> Virtio-ccw relies on cio mechanisms for bootstrapping the ccw device.
Well, a ccw device is, by definition, using cio mechanisms ;)
Better say: "As virtio-ccw devices are channel devices, we need to use
the dma area for any communication with the hypervisor."
Or something like that.
> Thus we
2019 Jun 12
0
[PATCH v5 3/8] s390/cio: add basic protected virtualization support
As virtio-ccw devices are channel devices, we need to use the
dma area within the common I/O layer for any communication with
the hypervisor.
Note that we do not need to use that area for control blocks
directly referenced by instructions, e.g. the orb.
It handles neither QDIO in the common code, nor any device type specific
stuff (like channel programs constructed by the DASD driver).
An