On Tue, May 17, 2016 3:37 pm, m.r...@5-cent.us wrote:
> Paul Heinlein wrote:
>> On Tue, 17 May 2016, m.r...@5-cent.us wrote:
>>
>>> I'm hoping *someone* here has worked a bit with bareos. I've tried
>>> posting to the google groups for it... and haven't even had one person
>>> view my post
>
On 05/19/2016 09:56 AM, Kay Schenk wrote:
Hello all --
Recently, I'm seeing DOS line ends, ^M, on my /var/log/boot.log file.
Honestly, I don't check this very often so I can't say exactly when this
occurred. Is this just MY experience or are others seeing this also.
Additionally, boot/log see
On May 20, 2016, at 8:17 AM, Jarosław Bober wrote:
>
> ldd gives me:
> ldd a.out
> linux-vdso.so.1 => (0x7fff6e5ff000)
> libstdc++.so.6 => /usr/lib64/libstdc++.so.6 (0x0039d840)
In that case, I don’t see how you can be making use of any C++11/14 features
that aren’t implemented by
Are you asking if the new libstdc++ is statically linked into your app only
for the new functions but your app remains dynamically linked to the old
one for the parts of C++ that have remained unchanged, the answer is “no”.
Your app is linked to the new library, period. You can use ldd(1) to prove
On 19.05.2016 18:56, Kay Schenk wrote:
Hello all --
Recently, I'm seeing DOS line ends, ^M, on my /var/log/boot.log file.
Honestly, I don't check this very often so I can't say exactly when this
occurred. Is this just MY experience or are others seeing this also.
this file shows ident content,
On 19/05/16 09:54, Fred Smith wrote:
>I've used gparted live cd a number of times, but don't think I knew
that it handled lvm2 also.
Well, what you are doing with gparted has nothing to do with LVM; just
the drive (really, the image file) itself - similar to buying a bigger
hdd and then clon
6 matches
Mail list logo
