On 01/21/14 18:50, Neil Bothwick wrote:
On Tue, 21 Jan 2014 10:26:48 -0700, Joseph wrote:
>What is the different between the output of this on both machines?
>
>grep -r tty /{etc,lib}/udev/rules.d
I did asked for the difference, not the whole damn lot. You have to do
some of the work yourself
On Tue, 21 Jan 2014 10:26:48 -0700, Joseph wrote:
> >What is the different between the output of this on both machines?
> >
> >grep -r tty /{etc,lib}/udev/rules.d
I did asked for the difference, not the whole damn lot. You have to do
some of the work yourself.
However, a quick glance shows thi
On 01/21/14 17:07, Neil Bothwick wrote:
On Tue, 21 Jan 2014 09:39:02 -0700, Joseph wrote:
So the settings is identical, and I don't remember entering my own
rules for ttyS0.
But something may have, like...
Though one server is running hylafax the other doesn't.
That could well be relevant
On Tue, 21 Jan 2014 09:39:02 -0700, Joseph wrote:
> So the settings is identical, and I don't remember entering my own
> rules for ttyS0.
But something may have, like...
> Though one server is running hylafax the other doesn't.
That could well be relevant as the hylafax ebuild does set some thi
On 01/21/14 08:22, Alan McKinnon wrote:
[snip]
I recompile the VirtualBox-bin but it doesn't help it still complain
about the /dev/ttyS0 access
and upon rebooting the /dev/ttyS0 has permission and ownership as:
crw-rw 1 root dialout 4, 64 Jan 20 19:14 /dev/ttyS0
and it should be uucp:dialo
On Mon, 20 Jan 2014 19:31:56 -0700, Joseph wrote:
> I recompile the VirtualBox-bin but it doesn't help it still complain
> about the /dev/ttyS0 access
That is a binary package. You are not compiling it, merely unpacking it.
No matter how many times you do this, the binaries it installs will not
c
On 01/21/14 04:31, Joseph wrote:
> On 01/20/14 19:49, Alan McKinnon wrote:
>> On 01/20/14 19:41, Joseph wrote:
>>> On 01/20/14 18:20, Helmut Jarausch wrote:
>>> [snip]
Hi,
I have the same permissions and VirtualBox (4.3.6) runs just fine.
VirtualBox is picky about the
On 01/20/14 19:49, Alan McKinnon wrote:
On 01/20/14 19:41, Joseph wrote:
On 01/20/14 18:20, Helmut Jarausch wrote:
[snip]
Hi,
I have the same permissions and VirtualBox (4.3.6) runs just fine.
VirtualBox is picky about the permission of the hard-disk image (VDI
file)
There it likes group vbo
On 01/20/14 19:41, Joseph wrote:
> On 01/20/14 18:20, Helmut Jarausch wrote:
> [snip]
>>
>>
>> Hi,
>>
>> I have the same permissions and VirtualBox (4.3.6) runs just fine.
>> VirtualBox is picky about the permission of the hard-disk image (VDI
>> file)
>> There it likes group vboxusers and group r/
On 01/20/14 18:20, Helmut Jarausch wrote:
[snip]
Hi,
I have the same permissions and VirtualBox (4.3.6) runs just fine.
VirtualBox is picky about the permission of the hard-disk image (VDI
file)
There it likes group vboxusers and group r/w permissions.
Helmut
Maybe I should recomplile Virtu
On 01/20/2014 06:02:33 PM, Joseph wrote:
On 01/20/14 18:45, Alan McKinnon wrote:
On 01/20/14 18:30, Joseph wrote:
After upgrade to "systemd" my /dev/ttyS0 shows up as: root:dialout
ownership and permission 600
When I change as root manually to: chown uucp:dialout /dev/ttyS0
chmod 666 /dev/ttyS
On 01/20/14 10:02, Joseph wrote:
On 01/20/14 18:45, Alan McKinnon wrote:
On 01/20/14 18:30, Joseph wrote:
After upgrade to "systemd" my /dev/ttyS0 shows up as: root:dialout
ownership and permission 600
When I change as root manually to: chown uucp:dialout /dev/ttyS0
chmod 666 /dev/ttyS0
after
On 01/20/14 18:45, Alan McKinnon wrote:
On 01/20/14 18:30, Joseph wrote:
After upgrade to "systemd" my /dev/ttyS0 shows up as: root:dialout
ownership and permission 600
When I change as root manually to: chown uucp:dialout /dev/ttyS0
chmod 666 /dev/ttyS0
after restart it goes back to previous
On 20/01/14 18:45, Alan McKinnon wrote:
> On 01/20/14 18:30, Joseph wrote:
>> After upgrade to "systemd" my /dev/ttyS0 shows up as: root:dialout
>> ownership and permission 600
>>
>> When I change as root manually to: chown uucp:dialout /dev/ttyS0
>> chmod 666 /dev/ttyS0
>>
>> after restart it goe
On 01/20/14 18:30, Joseph wrote:
> After upgrade to "systemd" my /dev/ttyS0 shows up as: root:dialout
> ownership and permission 600
>
> When I change as root manually to: chown uucp:dialout /dev/ttyS0
> chmod 666 /dev/ttyS0
>
> after restart it goes back to previous setting: root:dialout 600
> H
After upgrade to "systemd" my /dev/ttyS0 shows up as: root:dialout ownership
and permission 600
When I change as root manually to: chown uucp:dialout /dev/ttyS0
chmod 666 /dev/ttyS0
after restart it goes back to previous setting: root:dialout 600
How to change it?
My VituralBox complain and wi
16 matches
Mail list logo