Re: [gentoo-user] syslog-ng: how to read the log files
On 02/18/2015 12:13 AM, Peter Humphrey wrote: On Tuesday 17 February 2015 22:51:55 Peter Humphrey wrote: On Tuesday 17 February 2015 20:41:06 Matti Nykyri wrote: On Feb 17, 2015, at 20:26, lee l...@yagibdah.de wrote: how do you read the log files when using syslog-ng? The log file seem to be some sort of binary that doesn't display too well in less, and there doesn't seem to be any way to read them. This was discussed earlier on this list... Actually what syslog-ng produces is plain text. There seemed to be a bug that creates some binary (i.e. unreadable characters) and that causes less to consider files to be binary and show them incorrectly. Yes, that was me. I found that something had marked /var/log/messages as a binary file. There's nothing in it that can't be read, no mysterious characters or anything; it's just marked as binary. All you have to do is to move it, then cat it back into place. I did that with no ill effects. Actually, this is what I did, as I reported here on 26/12: 1.Boot rescue system and mount main system 2.# cd /mnt/main/var/log 3.# mv messages messages.bin 4.# strings messages.bin messages 5.# rm messages.bin 6.Reboot. When I had similar problem, I changed threaded(yes) to threaded(no) in syslog-ng.conf and the problem disappeared. Maybe it helps you too. -- Jan Sever
Re: [gentoo-user] syslog-ng: how to read the log files
On Tue, Feb 17, 2015 at 5:51 PM, Peter Humphrey pe...@prh.myzen.co.uk wrote: Yes, that was me. I found that something had marked /var/log/messages as a binary file. There's nothing in it that can't be read, no mysterious characters or anything; it's just marked as binary. All you have to do is to move it, then cat it back into place. I did that with no ill effects. Uh, of what binary mark are you speaking? Seems likely that however you processed the file stripped it of whatever was causing less to consider it as binary. I don't think cat alone would do anything to the file, but I'm not certain of that. -- Rich
Re: [gentoo-user] syslog-ng: how to read the log files
On Tuesday 17 February 2015 20:41:06 Matti Nykyri wrote: On Feb 17, 2015, at 20:26, lee l...@yagibdah.de wrote: how do you read the log files when using syslog-ng? The log file seem to be some sort of binary that doesn't display too well in less, and there doesn't seem to be any way to read them. This was discussed earlier on this list... Actually what syslog-ng produces is plain text. There seemed to be a bug that creates some binary (i.e. unreadable characters) and that causes less to consider files to be binary and show them incorrectly. Yes, that was me. I found that something had marked /var/log/messages as a binary file. There's nothing in it that can't be read, no mysterious characters or anything; it's just marked as binary. All you have to do is to move it, then cat it back into place. I did that with no ill effects. -- Rgds Peter.
Re: [gentoo-user] syslog-ng: how to read the log files
On Wednesday 18 February 2015 00:23:19 Jan Sever wrote: On 02/18/2015 12:13 AM, Peter Humphrey wrote: On Tuesday 17 February 2015 22:51:55 Peter Humphrey wrote: On Tuesday 17 February 2015 20:41:06 Matti Nykyri wrote: On Feb 17, 2015, at 20:26, lee l...@yagibdah.de wrote: how do you read the log files when using syslog-ng? The log file seem to be some sort of binary that doesn't display too well in less, and there doesn't seem to be any way to read them. This was discussed earlier on this list... Actually what syslog-ng produces is plain text. There seemed to be a bug that creates some binary (i.e. unreadable characters) and that causes less to consider files to be binary and show them incorrectly. Yes, that was me. I found that something had marked /var/log/messages as a binary file. There's nothing in it that can't be read, no mysterious characters or anything; it's just marked as binary. All you have to do is to move it, then cat it back into place. I did that with no ill effects. Actually, this is what I did, as I reported here on 26/12: 1.Boot rescue system and mount main system 2.# cd /mnt/main/var/log 3.# mv messages messages.bin 4.# strings messages.bin messages 5.# rm messages.bin 6.Reboot. When I had similar problem, I changed threaded(yes) to threaded(no) in syslog-ng.conf and the problem disappeared. Maybe it helps you too. Good idea. Sounds like a bug report is needed, unless it's already been superseded. -- Rgds Peter.
Re: [gentoo-user] syslog-ng: how to read the log files
On Tuesday 17 February 2015 18:52:07 Rich Freeman wrote: On Tue, Feb 17, 2015 at 5:51 PM, Peter Humphrey pe...@prh.myzen.co.uk wrote: Yes, that was me. I found that something had marked /var/log/messages as a binary file. There's nothing in it that can't be read, no mysterious characters or anything; it's just marked as binary. All you have to do is to move it, then cat it back into place. I did that with no ill effects. Uh, of what binary mark are you speaking? Seems likely that however you processed the file stripped it of whatever was causing less to consider it as binary. I don't think cat alone would do anything to the file, but I'm not certain of that. I don't know. Are we talking magic here? -- Rgds Peter.
Re: [gentoo-user] Package conflict while trying to emerge chromium
On Tue, Feb 17, 2015 at 11:09:43PM +0100, Marc Joliet wrote Am Tue, 17 Feb 2015 12:09:23 + schrieb Stroller strol...@stellar.eclipse.co.uk: On Sat, 14 February 2015, at 10:36 am, Marc Joliet mar...@gmx.de wrote: Personally, I don't like that way of doing things, because unless you you completely deactivate Flash, Youtube will stupidly never attempt to use HTML5 videos YouTube have recently switched to HTML5 as the default: http://www.theverge.com/2015/1/27/7926001/youtube-drops-flash-for-html5-video-default Excellent :-) ! One minor(!) problem though: that does not include the current Firefox 35 (they say they enabled HTML5 video for Firefox *betas*). But starting with Firefox 36 I'll try running without FlashDisable and see what it's like. I'm running the Seamonkey-2.32 variant of Firefox, and Seamonkey is nowhere near Firefox beta. It seems to work on Youtube in HTML5. A few oddities, which may or may not be specific to Seamonkey... - It has only 2 resolutions... 360p... and auto... which gives 360pG. This is the case even for 1080p demo videos. Mind you, the video quality looks (to me at least) a lot better than 360p on Flash looks. - There are 2 player sizes. Default is the standard size that you're used to in the upper left corner of the screen. Theater Mode expands to the full width of the browser. The vertical size scales to the proper height for the aspect ratio. However, it's not true fullscreen because you still see the browser frame/bars/etc, even if the browser is maximized. On some other HTML5 video demos, you can right click, and get a menu which includes a Fullscreen item that gives true fullscreen. But this does not appear on Youtube. - Last, but not least, the cpu load is a lot lower when playing HTML5 video than Flash video. This is important to me, because I'm trying to run my 7 and 1/2 year old Dell (Intel Core Duo) into the ground. It refuses to die. I have multiple Seamonkey profiles, dedicated to specific tasks (You can do this with Firefox, too). It's ironic that the first profile on which I can turn off Flash is my youtube profile. I still need Flash for NHL GameCentreLive, internet radio, etc. Your version of Firefox might HTML5 video now. Try it. -- Walter Dnes waltd...@waltdnes.org I don't run desktop environments; I run useful applications
[gentoo-user] mtp stops working after system re-install
I got around to upgrading my desktop from 32-bit to 64-bit. The only problem so far is that mtp connections to my tablet and smart phone no longer work. I've tried both mtpfs and simple-mtpfs. The results are similar with both programs on both devices... = [d531][root][~] /usr/bin/mtpfs /mnt/drive1 Device 0 (VID=0bb4 and PID=0ca8) is a HTC EVO 4G LTE/One V (ID2). Android device detected, assigning default bug flags fuse: device not found, try 'modprobe fuse' first [d531][root][~] modprobe fuse modprobe: FATAL: Module fuse not found. = They were working just before the re-install/upgrade from 32-bits to 64-bits. Any ideas? Could it be a kernel setting that I didn't set on the new kernel? -- Walter Dnes waltd...@waltdnes.org I don't run desktop environments; I run useful applications
Re: [gentoo-user] syslog-ng: how to read the log files
On Tuesday 17 February 2015 22:51:55 Peter Humphrey wrote: On Tuesday 17 February 2015 20:41:06 Matti Nykyri wrote: On Feb 17, 2015, at 20:26, lee l...@yagibdah.de wrote: how do you read the log files when using syslog-ng? The log file seem to be some sort of binary that doesn't display too well in less, and there doesn't seem to be any way to read them. This was discussed earlier on this list... Actually what syslog-ng produces is plain text. There seemed to be a bug that creates some binary (i.e. unreadable characters) and that causes less to consider files to be binary and show them incorrectly. Yes, that was me. I found that something had marked /var/log/messages as a binary file. There's nothing in it that can't be read, no mysterious characters or anything; it's just marked as binary. All you have to do is to move it, then cat it back into place. I did that with no ill effects. Actually, this is what I did, as I reported here on 26/12: 1.Boot rescue system and mount main system 2.# cd /mnt/main/var/log 3.# mv messages messages.bin 4.# strings messages.bin messages 5.# rm messages.bin 6.Reboot. -- Rgds Peter.
[gentoo-user] Re: [SOLVED] mtp stops working after system re-install
On Wed, Feb 18, 2015 at 04:11:06PM +1100, Adam Carter wrote They were working just before the re-install/upgrade from 32-bits to 64-bits. Any ideas? Could it be a kernel setting that I didn't set on the new kernel? Yes: grep -i fuse /usr/src/linux/.config CONFIG_FUSE_FS=m You can search the kernel config in 'make menuconfig' with / so just try / then fuse then enter Thank you very much. It works now. Actually, I sort of remembered that entry, having set up the kernel from scratch several days ago. This is what I get for trying to pare down the kernel. I went into... File systems --- * FUSE (Filesystem in Userspace) support I figured I may as well build it in. -- Walter Dnes waltd...@waltdnes.org I don't run desktop environments; I run useful applications
[gentoo-user] Open ansible UI (semaphore)
Hello, I just ran across this community Users Interface for Ansible: https://github.com/ansible-semaphore/semaphore The requirements toinstall are there too. I'd be curious if anyone has tested this already or other alternatives besides ansible-tower. James
Re: [gentoo-user] syslog-ng: how to read the log files
On Tuesday 17 Feb 2015 23:13:08 Peter Humphrey wrote: On Tuesday 17 February 2015 22:51:55 Peter Humphrey wrote: On Tuesday 17 February 2015 20:41:06 Matti Nykyri wrote: On Feb 17, 2015, at 20:26, lee l...@yagibdah.de wrote: how do you read the log files when using syslog-ng? The log file seem to be some sort of binary that doesn't display too well in less, and there doesn't seem to be any way to read them. This was discussed earlier on this list... Actually what syslog-ng produces is plain text. There seemed to be a bug that creates some binary (i.e. unreadable characters) and that causes less to consider files to be binary and show them incorrectly. Yes, that was me. I found that something had marked /var/log/messages as a binary file. There's nothing in it that can't be read, no mysterious characters or anything; it's just marked as binary. All you have to do is to move it, then cat it back into place. I did that with no ill effects. Actually, this is what I did, as I reported here on 26/12: 1.Boot rescue system and mount main system 2.# cd /mnt/main/var/log 3.# mv messages messages.bin 4.# strings messages.bin messages 5.# rm messages.bin 6.Reboot. How often do you have to do this? -- Regards, Mick signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] mtp stops working after system re-install
= [d531][root][~] /usr/bin/mtpfs /mnt/drive1 Device 0 (VID=0bb4 and PID=0ca8) is a HTC EVO 4G LTE/One V (ID2). Android device detected, assigning default bug flags fuse: device not found, try 'modprobe fuse' first [d531][root][~] modprobe fuse modprobe: FATAL: Module fuse not found. = They were working just before the re-install/upgrade from 32-bits to 64-bits. Any ideas? Could it be a kernel setting that I didn't set on the new kernel? Yes: grep -i fuse /usr/src/linux/.config CONFIG_FUSE_FS=m You can search the kernel config in 'make menuconfig' with / so just try / then fuse then enter
Re: [gentoo-user] perl-cleaner lerfovers
On Feb 16, 2015 11:26 PM, Neil Bothwick n...@digimed.co.uk wrote: On Mon, 16 Feb 2015 18:35:15 +0200, Alexander Kapshuk wrote: What I've done on two of my gentoo systems is, what had been suggested in one of the earlier replies to this thread. I ran emerge -C `grep -i libs /var/lib/portage/world`, followed by emerge @preserved-rebuild. That could have been dangerous, unmerging important libs just because they have found their way into @world. While on another one of my systems I tried emerge --deselect `grep -i libs /var/lib/portage/world`, followed by emerge --depclean. That is far more sensible. As a result, I no longer have any libs in my world set. Or you could have done sed -i /libs\//d /var/lib/portage/world emerge -ca -- Neil Bothwick All things being equal, fat people use more soap. Thanks a lot for your feedback. I'm learning as I go.
Re: [gentoo-user] syslog-ng: how to read the log files
On Tue, Feb 17, 2015 at 2:29 PM, cov...@ccs.covici.com wrote: Alexander Kapshuk alexander.kaps...@gmail.com wrote: On Tue, Feb 17, 2015 at 8:26 PM, lee l...@yagibdah.de wrote: Hi, how do you read the log files when using syslog-ng? The log file seem to be some sort of binary that doesn't display too well in less, and there doesn't seem to be any way to read them. -- Again we must be afraid of speaking of daemons for fear that daemons might swallow us. Finally, this fear has become reasonable. If you're talking about /var/log/messages, which is: messages: data I use cat(1). I wonder if the OP is using systemd and trying to read the journal files? Those live under /var/lib/journal (which you need to create; Gentoo doesn't do it by default last time I saw), in the directory named after the machine ID (cat /etc/machine-id). And there are several journal files, of the kind: system@1df50cd49c7f4a089c9414561f65aac7-0006f091-000507235df68768.journal I think it would be really difficult to mix up that with /var/log/messages. I think it's just that some part of /var/log/messages got corrupted (happens a lot of times), and therefore /usr/bin/less identifies it as a binary files since it contains non-printable characters. Regards. -- Canek Peláez Valdés Profesor de asignatura, Facultad de Ciencias Universidad Nacional Autónoma de México
Re: [gentoo-user] syslog-ng: how to read the log files
Hello, Lee. On Tue, Feb 17, 2015 at 07:26:05PM +0100, lee wrote: Hi, how do you read the log files when using syslog-ng? The log file seem to be some sort of binary that doesn't display too well in less, and there doesn't seem to be any way to read them. When I try less /var/log/messages, less gives me what is basically a hex dump of the file. I'm assuming you see the same. less searches part of the buffer (presumably the first few KB) and if it finds non-printable characters, uses an input filter first to convert to the hex dump. This same filter is what enables less to expand compressed files and man pages. What I do is to disable this input filter with # LESSOPEN= less /var/log/messages . It is evident that every now and then, syslog-ng writes a stream of several hundred null bytes to /var/log/messages. It seems to do this when logging the system startup messages. This is probably a bug. By the way, the LESSOPEN= trick can sometimes leave your display corrupted, displaying wierd glyphs on the screen when you type. To restore your screen, output ^o. To do this, type (blindly) # echo ctrl-vcrtl-oCR . -- Again we must be afraid of speaking of daemons for fear that daemons might swallow us. Finally, this fear has become reasonable. -- Alan Mackenzie (Nuremberg, Germany).
Re: [gentoo-user] syslog-ng: how to read the log files
On Tue, Feb 17, 2015 at 8:26 PM, lee l...@yagibdah.de wrote: Hi, how do you read the log files when using syslog-ng? The log file seem to be some sort of binary that doesn't display too well in less, and there doesn't seem to be any way to read them. -- Again we must be afraid of speaking of daemons for fear that daemons might swallow us. Finally, this fear has become reasonable. If you're talking about /var/log/messages, which is: messages: data I use cat(1).
[gentoo-user] Re: syslog-ng: how to read the log files
On 17/02/15 20:26, lee wrote: Hi, how do you read the log files when using syslog-ng? The log file seem to be some sort of binary that doesn't display too well in less, and there doesn't seem to be any way to read them. As others said, it's probably a bug and /var/log/messages is actually really a text file. FWIW, I'm on syslog-ng 3.6.2 and it seems to not have this bug.
Re: [gentoo-user] syslog-ng: how to read the log files
Alan Mackenzie a...@muc.de writes: Hello, Lee. On Tue, Feb 17, 2015 at 07:26:05PM +0100, lee wrote: Hi, how do you read the log files when using syslog-ng? The log file seem to be some sort of binary that doesn't display too well in less, and there doesn't seem to be any way to read them. When I try less /var/log/messages, less gives me what is basically a hex dump of the file. I'm assuming you see the same. Yes, that's what I was looking at. less searches part of the buffer (presumably the first few KB) and if it finds non-printable characters, uses an input filter first to convert to the hex dump. Is that a new feature of less? I've never had this problem with any other file. IIRC, unprintable characters, like null, used to be displayed like ^@, and less always did a great job in preventing the display from needing a reset without switching to an equivalent of hexl-mode. BTW, what happens when something writes to /var/log/messages? I noticed today that the default shorewall.conf that ships with gentoo has that set as logfile for shorewall. Shouldn't all messages going into /var/log/messages go to syslog-ng instead when syslog-ng is used, with nothing else writing to this file? -- Again we must be afraid of speaking of daemons for fear that daemons might swallow us. Finally, this fear has become reasonable.
Re: [gentoo-user] syslog-ng: how to read the log files
On Feb 17, 2015, at 20:26, lee l...@yagibdah.de wrote: Hi, how do you read the log files when using syslog-ng? The log file seem to be some sort of binary that doesn't display too well in less, and there doesn't seem to be any way to read them. This was discussed earlier on this list... Actually what syslog-ng produces is plain text. There seemed to be a bug that creates some binary (i.e. unreadable characters) and that causes less to consider files to be binary and show them incorrectly. To work around you can use -r flag with less, or replace/remove unreadable chars from log, or delete the log file. -- -Matti
[gentoo-user] syslog-ng: how to read the log files
Hi, how do you read the log files when using syslog-ng? The log file seem to be some sort of binary that doesn't display too well in less, and there doesn't seem to be any way to read them. -- Again we must be afraid of speaking of daemons for fear that daemons might swallow us. Finally, this fear has become reasonable.
Re: [gentoo-user] syslog-ng: how to read the log files
On Tue, Feb 17, 2015 at 1:26 PM, lee l...@yagibdah.de wrote: Hi, how do you read the log files when using syslog-ng? The log file seem to be some sort of binary that doesn't display too well in less, and there doesn't seem to be any way to read them. That's news to me. Are you sure you're not looking at wtmp or something like that (which isn't maintained by syslog)? -- Rich
Re: [gentoo-user] syslog-ng: how to read the log files
On Tue, Feb 17, 2015 at 8:38 PM, Alexander Kapshuk alexander.kaps...@gmail.com wrote: On Tue, Feb 17, 2015 at 8:26 PM, lee l...@yagibdah.de wrote: Hi, how do you read the log files when using syslog-ng? The log file seem to be some sort of binary that doesn't display too well in less, and there doesn't seem to be any way to read them. -- Again we must be afraid of speaking of daemons for fear that daemons might swallow us. Finally, this fear has become reasonable. If you're talking about /var/log/messages, which is: messages: data I use cat(1). Just tried 'sed p /var/log/messages', which seems to work as well.
Re: [gentoo-user] syslog-ng: how to read the log files
Alexander Kapshuk alexander.kaps...@gmail.com wrote: On Tue, Feb 17, 2015 at 8:26 PM, lee l...@yagibdah.de wrote: Hi, how do you read the log files when using syslog-ng? The log file seem to be some sort of binary that doesn't display too well in less, and there doesn't seem to be any way to read them. -- Again we must be afraid of speaking of daemons for fear that daemons might swallow us. Finally, this fear has become reasonable. If you're talking about /var/log/messages, which is: messages: data I use cat(1). I wonder if the OP is using systemd and trying to read the journal files? -- Your life is like a penny. You're going to lose it. The question is: How do you spend it? John Covici cov...@ccs.covici.com
Re: [gentoo-user] syslog-ng: how to read the log files
On Tuesday 17 Feb 2015 19:17:20 lee wrote: Alan Mackenzie a...@muc.de writes: Hello, Lee. On Tue, Feb 17, 2015 at 07:26:05PM +0100, lee wrote: Hi, how do you read the log files when using syslog-ng? The log file seem to be some sort of binary that doesn't display too well in less, and there doesn't seem to be any way to read them. When I try less /var/log/messages, less gives me what is basically a hex dump of the file. I'm assuming you see the same. Yes, that's what I was looking at. less searches part of the buffer (presumably the first few KB) and if it finds non-printable characters, uses an input filter first to convert to the hex dump. Is that a new feature of less? I've never had this problem with any other file. IIRC, unprintable characters, like null, used to be displayed like ^@, and less always did a great job in preventing the display from needing a reset without switching to an equivalent of hexl-mode. BTW, what happens when something writes to /var/log/messages? I noticed today that the default shorewall.conf that ships with gentoo has that set as logfile for shorewall. Shouldn't all messages going into /var/log/messages go to syslog-ng instead when syslog-ng is used, with nothing else writing to this file? It depends on what filters have been set in the configuration file of the application in question or syslog-ng. I use less -L /var/log/messages to see the content of the log files in plain text. At boot up I get a load of: Feb 16 07:54:04 ^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@ ^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@ ^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@ ^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@ ^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@ ^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@ ^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@ kernel: Initializing cgroup subsys cpuset Feb 16 07:54:04 ^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@ ^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@ being printed up. Perhaps I will disable cgroups in the kernel and see what gives. I don't use containers anyway. -- Regards, Mick signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] Package conflict while trying to emerge chromium
Am Tue, 17 Feb 2015 12:09:23 + schrieb Stroller strol...@stellar.eclipse.co.uk: On Sat, 14 February 2015, at 10:36 am, Marc Joliet mar...@gmx.de wrote: Personally, I don't like that way of doing things, because unless you completely deactivate Flash, Youtube will stupidly never attempt to use HTML5 videos YouTube have recently switched to HTML5 as the default: http://www.theverge.com/2015/1/27/7926001/youtube-drops-flash-for-html5-video-default Excellent :-) ! One minor(!) problem though: that does not include the current Firefox 35 (they say they enabled HTML5 video for Firefox *betas*). But starting with Firefox 36 I'll try running without FlashDisable and see what it's like. -- Marc Joliet -- People who think they know everything really annoy those of us who know we don't - Bjarne Stroustrup pgpd_e0BZ04V0.pgp Description: Digitale Signatur von OpenPGP
Re: [gentoo-user] syslog-ng: how to read the log files
Am Tue, 17 Feb 2015 13:45:38 -0600 schrieb Canek Peláez Valdés can...@gmail.com: On Tue, Feb 17, 2015 at 2:29 PM, cov...@ccs.covici.com wrote: Alexander Kapshuk alexander.kaps...@gmail.com wrote: On Tue, Feb 17, 2015 at 8:26 PM, lee l...@yagibdah.de wrote: Hi, how do you read the log files when using syslog-ng? The log file seem to be some sort of binary that doesn't display too well in less, and there doesn't seem to be any way to read them. -- Again we must be afraid of speaking of daemons for fear that daemons might swallow us. Finally, this fear has become reasonable. If you're talking about /var/log/messages, which is: messages: data I use cat(1). I wonder if the OP is using systemd and trying to read the journal files? Those live under /var/lib/journal (which you need to create; Gentoo doesn't do it by default last time I saw) [...] It did on my laptop after I migrated it to systemd over the weekend (on a whim, no less -- apparently I'm adventurous?). Or, to be more precise, I didn't have to create the directory myself. And wouldn't it be created at run-time, anyway? That's what I would expect, at least. [...] -- Marc Joliet -- People who think they know everything really annoy those of us who know we don't - Bjarne Stroustrup pgpATVahurywy.pgp Description: Digitale Signatur von OpenPGP
Re: [gentoo-user] Package conflict while trying to emerge chromium
On Sat, 14 February 2015, at 10:36 am, Marc Joliet mar...@gmx.de wrote: Personally, I don't like that way of doing things, because unless you completely deactivate Flash, Youtube will stupidly never attempt to use HTML5 videos YouTube have recently switched to HTML5 as the default: http://www.theverge.com/2015/1/27/7926001/youtube-drops-flash-for-html5-video-default
