Displaying 20 results from an estimated 200 matches similar to: "udev on CEntOS7 - can't get a match, looking for tips..."
2019 Oct 29
2
udev on CEntOS7 - can't get a match, looking for tips...
Thanks, I did catch the mistype (after IU posted). Still no match with
the typo fixed... :-(
Thanks,
John H. Nyhuis
Desk: (206)-685-8334
jnyhuis at uw.edu
Box 359461, 15th floor, 106
On 10/29/2019 4:03 AM, Tony Mountifield wrote:
> In article <7025a0a8-1471-530d-dad0-3770e902ca31 at uw.edu>,
> John H Nyhuis <jnyhuis at uw.edu> wrote:
>> The mtx binary requires my tape
2019 Oct 29
1
udev on CEntOS7 - can't get a match, looking for tips...
hmmm, I thought := assigned a key just like +=, except := locked it so
it could not be changed later. Am I misunderstanding the man page for udev?
Thanks,
John H. Nyhuis
Desk: (206)-685-8334
jnyhuis at uw.edu
Box 359461, 15th floor, 106
On 10/29/2019 4:31 PM, Leon Fauster via CentOS wrote:
> Am 29.10.19 um 23:41 schrieb John H Nyhuis:
>> Thanks, I did catch the mistype (after IU
2019 Oct 29
0
udev on CEntOS7 - can't get a match, looking for tips...
Am 29.10.19 um 23:41 schrieb John H Nyhuis:
> Thanks, I did catch the mistype (after IU posted). Still no match with
> the typo fixed... :-(
>
> Thanks,
>
> John H. Nyhuis
> Desk: (206)-685-8334
> jnyhuis at uw.edu
> Box 359461, 15th floor, 106
>
> On 10/29/2019 4:03 AM, Tony Mountifield wrote:
>> In article <7025a0a8-1471-530d-dad0-3770e902ca31 at
2019 Oct 29
0
udev on CEntOS7 - can't get a match, looking for tips...
In article <7025a0a8-1471-530d-dad0-3770e902ca31 at uw.edu>,
John H Nyhuis <jnyhuis at uw.edu> wrote:
> The mtx binary requires my tape library to be assigned a sg# driver, but
> the kernel periodically renumbers the sg devices. Normally, we would
> write a udev rule to manually assign a persistent name, but it looks
> like things have changed as I can't seem to get
2020 Jan 01
1
Nasty Fail2Ban update for Centos 7
P? Tue, 31 Dec 2019 18:53:38 +0000
John H Nyhuis <jnyhuis at uw.edu> skrev:
> Just a random stab in the dark, but CEntOS6 was iptables, and CentOS7
> is firewalld. They take different fail2ban packages.
>
> CentOS6 = fail2ban
> CentOS7 = fail2ban-firewalld
>
> Are you sure you are running the correct fail2ban package for your
> firewall? (I screwed this up myself
2019 Dec 31
7
Nasty Fail2Ban update for Centos 7
Hi all...
Recently a new Fail2Ban was available among some other updates for my
Centos 7 system, and I just updated all.
It seems that was a very BAD idea.
Just noticed that Fail2Ban have generated a 6MB error log because
of the update, and FirewallD a 1MB log of errors !
(not sure if any of those were really working after this)
ok, I'll just run yum downgrade fail2ban I thought.
Naa, no
2016 Mar 17
1
Questions regarding hostdev scsi
Hi!
I'm oVirt developer responsible for most of 'hostdev' support. While
working on SCSI passthrough (that is hostdev type='scsi'), I've
encountered few issues I'm not sure how to solve somewhat effectively
and nicely.
Just a note - oVirt by default disables 'dynamic_ownership', meaning
we have to handle endpoint ownership/labeling ourselves. This
is not
2012 Aug 21
5
[PATCH 1/2 v1] blkdrv: Add queue limits parameters for sg block drive
This patch adds some queue limit parameters into block drive. And inits them
for sg block drive. Some interfaces are also added for accessing them.
Signed-off-by: Cong Meng <mc at linux.vnet.ibm.com>
---
block/raw-posix.c | 58 +++++++++++++++++++++++++++++++++++++++++++++++++++++
block_int.h | 4 +++
blockdev.c | 15 +++++++++++++
hw/block-common.h | 3 ++
4 files
2012 Aug 21
5
[PATCH 1/2 v1] blkdrv: Add queue limits parameters for sg block drive
This patch adds some queue limit parameters into block drive. And inits them
for sg block drive. Some interfaces are also added for accessing them.
Signed-off-by: Cong Meng <mc at linux.vnet.ibm.com>
---
block/raw-posix.c | 58 +++++++++++++++++++++++++++++++++++++++++++++++++++++
block_int.h | 4 +++
blockdev.c | 15 +++++++++++++
hw/block-common.h | 3 ++
4 files
2004 Jun 27
2
Samba3 Win95 interoperability
Greetings,
I am trying to get samba3 to work well with W95. The windows 95
box can see the samba server, but cannot authenticate (claims wrong
password) to get to any shares. I know the smbpasswd is good as I can
authenticate and get to the shares using the same account and password on
a W2000 machine. I suspect I am doing something wrong in the [global]
section of the samba server.
Would
2019 Feb 08
1
persistent generic device for tape changer
> Am 08.02.2019 um 00:13 schrieb Ron Loftin <reloftin at twcny.rr.com>:
>
> On Thu, 2019-02-07 at 22:29 +0100, Helmut Drodofsky wrote:
>> Hello Ron,
>>
>> sounds good. I have 2 tape changer. I persume, udev creates the same
>> link for both.
>>
>> Can I modify
>> SYMLINK+="changer-$env{ID_SERIAL}"
>>
>> The serial
2003 Sep 20
1
Q: Share Definitions, how to make a 'truely public' area
Greetings,
I am trying to set up a "Public" share that visitors who do not
have accounts in our system have ro access to, while staff members
(who do have accounts) have rw access.
Our department has visitors who plug laptops into our network who
will only be there once, and want to copy some of our software. However,
with the following share definition, staff have rw access, but
2019 Aug 21
3
CentOS 5 file system read only issue
Hello Everyone,
We are using CentOS 5 system for certain application. Those are VM guests
running in VMware. There is datastore issue occasionally, causing all file
systems becoming read only file systems. So application stop working, and
opened files cannot be written either. We cannot even ssh login to the
system. Typically we had to power cycle the VM. We are trying to add
reliability to the
2010 Jun 10
1
Re: Recognising an unrecognisable scanner
Hi from Z?rich,Schweiz and a hot , humid day.
The SCANNER,Canoscan LiDE 600F,is not detected by XSANE/SIMPLE SCAN.
It is probably detected :- here is the OUTPUT from TERMINAL COMMAND "sane-find-scanner -v"
*****************************************************
found USB scanner (vendor=0x04a9 [Canon], product=0x2224 [CanoScan]) at libusb:001:005
2016 Feb 08
2
Re: Getting "unknown device type" when attaching NPIV (vHBA) to vm
Thank you for your reply,
I'm still getting hard time to attach the hostdev, I couldn't make it work out of the doc.
I took the address details from:
# ll /sys/bus/scsi/devices/7:*
lrwxrwxrwx 1 root root 0 Feb 8 12:58 /sys/bus/scsi/devices/7:0:0:0 -> ../../../devices/pci0000:00/0000:00:03.0/0000:08:00.1/host7/rport-7:0-0/target7:0:0/7:0:0:0
lrwxrwxrwx 1 root root 0 Feb 8 12:58
2007 Jul 20
2
Searching an Scsi Controller for CentOS 5
Hello,
does CentOs 5 supports an Adaptec AHA-2940W/2940UW scsi controller
(pci)? Is this controller maybe supported by the aic7xxx driver?
I want to install CentOS 5 on my desktop pc but the currently installed
pci scsi controller for my scanners (drivers: 2x tmscsim, 1x advansys)
are not supported by CentOS. So I am searching for something else.
Thanks in advanced.
regards
Olaf
2019 Dec 31
0
Nasty Fail2Ban update for Centos 7
Just a random stab in the dark, but CEntOS6 was iptables, and CentOS7 is
firewalld. They take different fail2ban packages.
CentOS6 = fail2ban
CentOS7 = fail2ban-firewalld
Are you sure you are running the correct fail2ban package for your
firewall? (I screwed this up myself before I noticed and fixed it...)
Good Luck!
Thanks,
John H. Nyhuis
Desk: (206)-685-8334
jnyhuis at uw.edu
Box 359461,
2003 Dec 03
1
[CSI] smb.conf share definition "force group =" option
Greetings,
I am using samba-3.0.1pre3-1, and have noticed that the "force
group" and "force user" option no longer seems to work. In spite of the
option being set, the files copied are set to the current users
user and primary group. Am I missing something with regards to how this
is supposed to work or is this a bug?
This is one of my share definitions for a team of
2008 Aug 07
1
rsync: hlink.c:271: check_prior: Assertion `node->data != ((void *)0)' failed.
BLS #rsync --version
rsync version 3.0.4pre2 protocol version 30
Copyright (C) 1996-2008 by Andrew Tridgell, Wayne Davison, and others.
Web site: http://rsync.samba.org/
Capabilities:
64-bit files, 64-bit inums, 32-bit timestamps, 64-bit long ints,
socketpairs, hardlinks, symlinks, IPv6, batchfiles, inplace,
append, ACLs, xattrs, iconv, symtimes
rsync comes with ABSOLUTELY NO
2015 Oct 28
11
[Bug 11578] New: Rsync does start with an error directly connecting an USB drive to a port
https://bugzilla.samba.org/show_bug.cgi?id=11578
Bug ID: 11578
Summary: Rsync does start with an error directly connecting an
USB drive to a port
Product: rsync
Version: 3.1.1
Hardware: x64
OS: Linux
Status: NEW
Severity: normal
Priority: P5
Component: core