On Sat, Mar 29, 2014 at 12:53 PM, Patrick O'Callaghan wrote:
> On Sat, 2014-03-29 at 12:43 +0100, Henrik Frisk wrote:
> > Hi,
> >
> > I have a MBP with a ssd that hosts Fedora 20 and OSx Mavericks in a dual
> > boot setup. In the laptop I also have a 500GB internal drive on which I
> > currently
On Sat, 2014-03-29 at 12:43 +0100, Henrik Frisk wrote:
> Hi,
>
> I have a MBP with a ssd that hosts Fedora 20 and OSx Mavericks in a dual
> boot setup. In the laptop I also have a 500GB internal drive on which I
> currently have my OSX Home directory. I have this drive (HFS+) mounted r/w
> in Linu
On 23/09/13 17:14, inode0 wrote:
It is informative, it tells you what sort of "file" you are looking
at. No different than
# ls -ld /usr/bin
dr-xr-xr-x. 2 root root 69632 Sep 23 09:20 /usr/bin
which begins with a 'd' telling you that /usr/bin is a directory.
>Is there a mknod command to rem
On 23/09/13 15:13, Paul W. Frields wrote:
>[root@box10 bobg]# ll /dev/sdb*
>brw-rw. 1 root disk 8, 16 Sep 23 14:36 /dev/sdb
>brw-rw. 1 root disk 8, 17 Sep 23 14:36 /dev/sdb1
It means the file is a block device node. Typically control of that
file/device is through a device driver. In
On Mon, Sep 23, 2013 at 3:58 PM, Bob Goodwin ~ Zuni, Virginia, USA
wrote:
> Are you saying that the "b" is merely to control the color in a listing? I
> view everything in black and white.
>
> Does it have any other effect?
It is informative, it tells you what sort of "file" you are looking
at. N
, etc...
Why are you worried about these?
>
> From: "Bob Goodwin ~ Zuni, Virginia, USA"
>To: users@lists.fedoraproject.org
>Sent: Monday, September 23, 2013 4:58 PM
>Subject: Re: permissions -
>
>
>
>
>On 23/09/13 16:07
On 23/09/13 16:07, poma wrote:
http://en.wikipedia.org/wiki/Ls;)
File types
$ ll --color /dev/sdb*
$ file /dev/sdb*
# file --special-files /dev/sdb*
poma
Are you saying that the "b" is merely to control the color in a listing?
I view everything in black and white.
Does it have any othe
On 09/23/2013 01:13 PM, Bob Goodwin ~ Zuni, Virginia, USA issued this
missive:
On 23/09/13 15:05, Bob Goodwin ~ Zuni, Virginia, USA wrote:
I spent the last half hour googling with no success. What does the "b"
mean and how is it controlled?
[root@box10 bobg]# ll /dev/sdb*
brw-rw. 1 root
09/23/2013 01:13 PM, Bob Goodwin ~ Zuni, Virginia, USA wrote:
On 23/09/13 15:05, Bob Goodwin ~ Zuni, Virginia, USA wrote:
I spent the last half hour googling with no success. What does the "b"
mean and how is it controlled?
[root@box10 bobg]# ll /dev/sdb*
brw-rw. 1 root disk 8, 16 Sep 23
On 23/09/13 15:05, Bob Goodwin ~ Zuni, Virginia, USA wrote:
I spent the last half hour googling with no success. What does the "b"
mean and how is it controlled?
[root@box10 bobg]# ll /dev/sdb*
brw-rw. 1 root disk 8, 16 Sep 23 14:36 /dev/sdb
brw-rw. 1 root disk 8, 17 Sep 23 14:36 /d
On 23.09.2013 21:05, Bob Goodwin ~ Zuni, Virginia, USA wrote:
>
> I spent the last half hour googling with no success. What does the "b"
> mean and how is it controlled?
>
> [root@box10 bobg]# ll /dev/sdb*
> brw-rw. 1 root disk 8, 16 Sep 23 14:36 /dev/sdb
> brw-rw. 1 root disk 8, 17 Sep
On Mon, Sep 23, 2013 at 12:08:57PM -0700, Joe Wulf wrote:
> "b" stands for block device; just like "c" will represent a character device.
>
> I looked all over the place for that kind of information years ago...
> strangely, I found in when scanning the man page for 'find'.
This may be helpful,
On Mon, Sep 23, 2013 at 03:05:45PM -0400, Bob Goodwin ~ Zuni, Virginia, USA
wrote:
>
> I spent the last half hour googling with no success. What does the
> "b" mean and how is it controlled?
>
> [root@box10 bobg]# ll /dev/sdb*
> brw-rw. 1 root disk 8, 16 Sep 23 14:36 /dev/sdb
> brw-rw. 1
On Mon, Sep 23, 2013 at 2:05 PM, Bob Goodwin ~ Zuni, Virginia, USA
wrote:
>
> I spent the last half hour googling with no success. What does the "b" mean
> and how is it controlled?
>
> [root@box10 bobg]# ll /dev/sdb*
> brw-rw. 1 root disk 8, 16 Sep 23 14:36 /dev/sdb
> brw-rw. 1 root disk
> I spent the last half hour googling with no success. What does the "b"
> mean and how is it controlled?
>
> [root@box10 bobg]# ll /dev/sdb*
> brw-rw. 1 root disk 8, 16 Sep 23 14:36 /dev/sdb brw-rw. 1 root
> disk 8, 17 Sep 23 14:36 /dev/sdb1
>
> Bob
The first character is the file type.
"b" stands for block device; just like "c" will represent a character device.
I looked all over the place for that kind of information years ago...
strangely, I found in when scanning the man page for 'find'.
>
> From: "Bob Goodwin ~ Zuni, Virginia, USA"
>To:
On Wed, Jul 17, 2013 at 06:59:06PM -0700, T.C. Hollingsworth wrote:
> What gotchas, out of curiosity?
> I've always done this with `usermod -aG group user`. Would that also
> be affected?
That's fine too. -a didn't aways exist, which made it painful, because you
had to get the current list and re
On Wed, Jul 17, 2013 at 6:54 PM, Matthew Miller
wrote:
> system-config-users seems to be still available. It's moderately
> user-friendly. From the command line, I think 'gpasswd groupname -a
> username' is the easiest. (You can use groupmod, but it's got some gotchas
> with behavior where gpasswd
On Thu, Jul 18, 2013 at 11:07:13AM +0930, Tim wrote:
> Allegedly, on or about 17 July 2013, Matthew Miller sent:
> > Type "groups" without your username to show your _current_ groups --
> > remember that adding yourself to a group doesn't take effect until you
> > start a new session. (E.g. by logg
Allegedly, on or about 17 July 2013, Matthew Miller sent:
> Type "groups" without your username to show your _current_ groups --
> remember that adding yourself to a group doesn't take effect until you
> start a new session. (E.g. by logging out and in again.)
Or opening a new terminal?
Darned i
Am 17.07.2013 21:15, schrieb Joe Zeff:
> On 07/17/2013 11:18 AM, Reindl Harald wrote:
>> i did: "otherwise my /var/log/maillog on my workstation would not have 644"
>> this is "logrotaded" - logrotate keeps the permissions/owner/group if
>> not specified like below (which is my own config-piece)
On Wed, 2013-07-17 at 23:04 +0200, Suvayu Ali wrote:
> PS: I guess I'm not thinking straight today. This thread has plenty
> of evidence to that. :-/
"Even Homer nods" (no, not *that* Homer :-)
poc
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription option
On Wed, Jul 17, 2013 at 09:59:00PM +0100, Patrick O'Callaghan wrote:
> On Wed, 2013-07-17 at 16:18 +0200, Suvayu Ali wrote:
> > On Wed, Jul 17, 2013 at 03:59:35PM +0200, Timothy Murphy wrote:
> > > I'm tired of saying "sudo less /var/log/maillog" or "messages".
> >
> > For /var/log/messages you co
On Wed, 2013-07-17 at 16:18 +0200, Suvayu Ali wrote:
> On Wed, Jul 17, 2013 at 03:59:35PM +0200, Timothy Murphy wrote:
> > I'm tired of saying "sudo less /var/log/maillog" or "messages".
>
> For /var/log/messages you could use `dmesg -T | less +G' instead.
>
> Hope this helps,
That's not quite t
On Wed, Jul 17, 2013 at 12:57:02PM -0400, Matthew Miller wrote:
> On Wed, Jul 17, 2013 at 06:02:47PM +0200, Suvayu Ali wrote:
> > > Note that if you're using the systemd journal (and you are, in recent
> > > Fedora, including persistent logging to disk with F19), adding yourself to
> > > the 'syste
On 07/17/2013 12:24 PM, Reindl Harald wrote:
Am 17.07.2013 21:15, schrieb Joe Zeff:
I'm the only person who ever uses my laptop. If I wanted, then, I could use
this to make /var/log/messages world
readable for convenience. No, I'm not going to do it because unless I do it to
all of my ma
On 07/17/2013 11:18 AM, Reindl Harald wrote:
i did: "otherwise my /var/log/maillog on my workstation would not have 644"
this is "logrotaded" - logrotate keeps the permissions/owner/group if
not specified like below (which is my own config-piece)
/var/log/scriptlog {
missingok
notifemp
On 07/17/2013 10:29 AM, Chris Adams wrote:
Once upon a time, Timothy Murphy said:
Will it cause any problems if I change the permissions on these files?
Nope, been doing it for years.
so have I. Never been a surprise or problem
--
Roger Wells, P.E.
SAIC
221 Third St
Newport, RI 02840
401-84
Am 17.07.2013 20:08, schrieb Rick Stevens:
> On 07/17/2013 08:36 AM, Reindl Harald issued this missive:
>> *no they are not*
>> otherwise my /var/log/maillog on my workstation would not have 644
>
> The correct thing to say is "if syslog(whatever) has to CREATE the file,
> it will not have world
On 07/17/2013 08:36 AM, Reindl Harald issued this missive:
Am 17.07.2013 16:46, schrieb Suvayu Ali:
On Wed, Jul 17, 2013 at 10:35:46PM +0800, Ed Greshko wrote:
On 07/17/13 22:27, Timothy Murphy wrote:
Ed Greshko wrote:
Heck, you could always make your sudo password less and you could always
Am 17.07.2013 15:59, schrieb Timothy Murphy:
> I'm tired of saying "sudo less /var/log/maillog" or "messages".
> Is there any non-paranoiac reason for not making /var/log/ files
> readable say by wheel?
chown/chgrp/chmod exists
[harry@rh:~]$ ls /var/log/maillog
-rw-r--r-- 1 root root 7,1K 2013-
Am 17.07.2013 16:46, schrieb Suvayu Ali:
> On Wed, Jul 17, 2013 at 10:35:46PM +0800, Ed Greshko wrote:
>> On 07/17/13 22:27, Timothy Murphy wrote:
>>> Ed Greshko wrote:
Heck, you could always make your sudo password less and you could always
assign the frequently used commands aliases.
On 07/17/2013 09:57 AM, Matthew Miller issued this missive:
On Wed, Jul 17, 2013 at 09:44:41AM -0700, Rick Stevens wrote:
The reason the files are, by default, NOT world-readable is simply one
of security. Many programs (if using verbose logging) may expose
security-related items in plaintext in
On Wed, Jul 17, 2013 at 09:44:41AM -0700, Rick Stevens wrote:
> The reason the files are, by default, NOT world-readable is simply one
> of security. Many programs (if using verbose logging) may expose
> security-related items in plaintext in the log files (usernames,
> passwords, GPG keys, etc.).
On Wed, Jul 17, 2013 at 06:02:47PM +0200, Suvayu Ali wrote:
> > Note that if you're using the systemd journal (and you are, in recent
> > Fedora, including persistent logging to disk with F19), adding yourself to
> > the 'systemd-journal' group will allow you to see system logs with
> > 'journalctl
On 07/17/2013 06:59 AM, Timothy Murphy issued this missive:
I'm tired of saying "sudo less /var/log/maillog" or "messages".
Is there any non-paranoiac reason for not making /var/log/ files
readable say by wheel?
The consensus seems to be that it's OK to change the permissions and I
agree. Makin
On Wed, Jul 17, 2013 at 11:21:20AM -0400, Matthew Miller wrote:
>
> Note that if you're using the systemd journal (and you are, in recent
> Fedora, including persistent logging to disk with F19), adding yourself to
> the 'systemd-journal' group will allow you to see system logs with
> 'journalctl'
On 07/17/2013 09:47 AM, Suvayu Ali wrote:
> On Wed, Jul 17, 2013 at 09:29:04AM -0500, Chris Adams wrote:
>> Once upon a time, Timothy Murphy said:
>>> Will it cause any problems if I change the permissions on these files?
>>
>> Nope, been doing it for years.
>
> I thought changing the permission
Once upon a time, Bryn M. Reeves said:
> I'm trying to help Suvayu understand what he's getting confused over.
> Conflicts between logrotate and manual changes are certainly more likely
> than "something bad happened to syslog".
There are only a few logrotate.d config files that set permissions a
On Wed, Jul 17, 2013 at 03:59:35PM +0200, Timothy Murphy wrote:
> I'm tired of saying "sudo less /var/log/maillog" or "messages".
> Is there any non-paranoiac reason for not making /var/log/ files
> readable say by wheel?
I think it's reasonable for /var/log/secure to require an extra level of
aut
On Wed, Jul 17, 2013 at 10:01:59AM -0500, Chris Adams wrote:
> Once upon a time, Bryn M. Reeves said:
> > On 07/17/2013 03:47 PM, Suvayu Ali wrote:
> > > I thought changing the permission on /var/log/messages will cause
> > > problems with syslog, no?
> >
> > Maybe you are thinking of logrotate?
On 07/17/2013 04:01 PM, Chris Adams wrote:
> Again, nope, at least for common log files. logrotate copies the
> current ownership/permissions to the new files, unless otherwise
> configured (and only a few files have that set in the default config;
> they probably shouldn't either).
*if the conf
Once upon a time, Bryn M. Reeves said:
> On 07/17/2013 03:47 PM, Suvayu Ali wrote:
> > I thought changing the permission on /var/log/messages will cause
> > problems with syslog, no?
>
> Maybe you are thinking of logrotate? If you make changes by hand these
> will be undone when the logs are rota
Once upon a time, Suvayu Ali said:
> Your permission changes will be overwritten the moment a daemon sends a
> message to syslog.
No, they won't. Where did you get that idea? The syslog/rsyslog daemon
runs as root and can write to the file, no matter the permissions. It
doesn't ever change per
On 07/17/2013 03:47 PM, Suvayu Ali wrote:
> On Wed, Jul 17, 2013 at 09:29:04AM -0500, Chris Adams wrote:
>> Once upon a time, Timothy Murphy said:
>>> Will it cause any problems if I change the permissions on these files?
>>
>> Nope, been doing it for years.
>
> I thought changing the permission
Once upon a time, Suvayu Ali said:
> On Wed, Jul 17, 2013 at 09:29:04AM -0500, Chris Adams wrote:
> > Once upon a time, Timothy Murphy said:
> > > Will it cause any problems if I change the permissions on these files?
> >
> > Nope, been doing it for years.
>
> I thought changing the permission
Hi Timothy,
On Wed, Jul 17, 2013 at 10:35:46PM +0800, Ed Greshko wrote:
> On 07/17/13 22:27, Timothy Murphy wrote:
> > Ed Greshko wrote:
> >
> >> Heck, you could always make your sudo password less and you could always
> >> assign the frequently used commands aliases.
> > I guess my question shoul
On Wed, Jul 17, 2013 at 09:29:04AM -0500, Chris Adams wrote:
> Once upon a time, Timothy Murphy said:
> > Will it cause any problems if I change the permissions on these files?
>
> Nope, been doing it for years.
I thought changing the permission on /var/log/messages will cause
problems with sysl
On 07/17/13 22:27, Timothy Murphy wrote:
> Ed Greshko wrote:
>
>> Heck, you could always make your sudo password less and you could always
>> assign the frequently used commands aliases.
> I guess my question should have been:
> Will it cause any problems if I change the permissions on these files?
Once upon a time, Timothy Murphy said:
> Will it cause any problems if I change the permissions on these files?
Nope, been doing it for years.
--
Chris Adams
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailm
Ed Greshko wrote:
> Heck, you could always make your sudo password less and you could always
> assign the frequently used commands aliases.
I guess my question should have been:
Will it cause any problems if I change the permissions on these files?
Is there any program that won't work if you do t
On Wed, Jul 17, 2013 at 03:59:35PM +0200, Timothy Murphy wrote:
> I'm tired of saying "sudo less /var/log/maillog" or "messages".
For /var/log/messages you could use `dmesg -T | less +G' instead.
Hope this helps,
--
Suvayu
Open source is the future. It sets us free.
--
users mailing list
user
On 07/17/13 21:59, Timothy Murphy wrote:
> I'm tired of saying "sudo less /var/log/maillog" or "messages".
> Is there any non-paranoiac reason for not making /var/log/ files
> readable say by wheel?
>
>
Heck, you could always make your sudo password less and you could always assign
the frequently
On 29/02/2012, Tim wrote:
>
> Though reading any info file is like trying to read ten pages of
> documentation spread into various different paragraphs spread across a
> hundred pages in a book. You can go around in circles, not quite
> finding the part that you need to read.
Yeah, there is a lo
On Wed, 2012-02-29 at 02:38 -0500, Bob Goodwin wrote:
> Now I have to learn to navigate through that!
Hint: Using the pinfo program is easier to read than using info. For
one thing, it has coloured highlighting of the interactive parts of the
page.
Though reading any info file is like trying to
On 28/02/12 23:06, David wrote:
At the bottom of 'man ls' here it says: "The full documentation for ls
is maintained as a Texinfo manual. If the info and ls programs are
properly installed at your site, the command info coreutils 'ls
invocation' should give you access to the complete manual.
On 29/02/2012, Bob Goodwin wrote:
> Would someone explain the meaning of the permissions in the last
> line below, especially the "+" ?
>
> [root@box6 bobg]# ll /dev/bus/usb/001
> total 0
> crw-rw-r--. 1 root root 189, 0 Feb 28 03:08 001
>
On 28/02/12 10:24, Tony Placilla wrote:
-Original Message-
From: users-boun...@lists.fedoraproject.org
[mailto:users-boun...@lists.fedoraproject.org] On Behalf Of Bob Goodwin
Sent: Tuesday, February 28, 2012 10:12 AM
To: Fedora List
Subject: Permissions, F-16 -
Would someone
-Original Message-
From: users-boun...@lists.fedoraproject.org
[mailto:users-boun...@lists.fedoraproject.org] On Behalf Of Bob Goodwin
Sent: Tuesday, February 28, 2012 10:12 AM
To: Fedora List
Subject: Permissions, F-16 -
Would someone explain the meaning of the permissions in
59 matches
Mail list logo
