On Thu, 8 Feb 2018 23:18:19 +, Wol's lists wrote:
> > More specifically, /var/tmp is traditionally supposed to be
> > non-volatile (across reboots).
> >
> > Comparatively the contents of /tmp can be volatile (across reboots).
> >
> > I would advise against mounting /var/tmp on tmpfs.
> >
2018-02-09 0:50 GMT+02:00 Tsukasa Mcp_Reznor :
> From: freemanr...@gmail.com on behalf of Rich
> Freeman
> Sent: Thursday, February 8, 2018 5:38 PM
> To: gentoo-user@lists.gentoo.org
> Subject: Re: [gentoo-user] Re: /var/tmp on tmpfs
>
> Just adding my 2 cents EMERGE_DEFAULT_OPTS="--fail-clean" h
On Friday, 9 February 2018 08:11:29 GMT Neil Bothwick wrote:
> On Thu, 8 Feb 2018 23:18:19 +, Wol's lists wrote:
> > > More specifically, /var/tmp is traditionally supposed to be
> > > non-volatile (across reboots).
> > >
> > > Comparatively the contents of /tmp can be volatile (across reboots
2018-02-09 10:11 GMT+02:00 Neil Bothwick :
> On Thu, 8 Feb 2018 23:18:19 +, Wol's lists wrote:
>
>> > More specifically, /var/tmp is traditionally supposed to be
>> > non-volatile (across reboots).
>> >
>> > Comparatively the contents of /tmp can be volatile (across reboots).
>> >
>> > I would
Am Sun, 04 Feb 2018 05:20:03 +0100 schrieb tuxic:
> after installing linux-4.15.1 (downloaded from kernel.org) I want to
> reinstall (beside others) nvidia drivers.
>
> Emerge told me:
> |>emerge nvidia-drivers
> |Calculating dependencies... done!
> |>>> Jobs: 0 of 0 complete
Am Fri, 09 Feb 2018 11:39:25 +0100 schrieb Kai Krakow:
> Am Sun, 04 Feb 2018 05:20:03 +0100 schrieb tuxic:
>
>> after installing linux-4.15.1 (downloaded from kernel.org) I want to
>> reinstall (beside others) nvidia drivers.
>>
>> Emerge told me:
>> |>emerge nvidia-drivers
>> |Calculati
2018-02-09 3:24 GMT+02:00 Dale :
>
> In my experience, once swap starts getting used, it gets slow, sometimes
> to the point that a response may take several seconds or more. When I
> compile without tmpfs at all, which means everything is on disk, it's
> rare that I can even tell it is using that
On Fri, 9 Feb 2018 12:30:21 +0200, gevisz wrote:
> > Why mess around with another tmpfs? Just set PORTAGE_TMPDIR="/tmp" in
> > make.conf. Job done!
>
> It is an interesting idea. But why it is not done by default then?
>
Because when the defaults were picked neither /tmp nor /var/tmp used
tmpf
On Fri, 09 Feb 2018 10:12:01 +, Peter Humphrey wrote:
> > Why mess around with another tmpfs? Just set PORTAGE_TMPDIR="/tmp" in
> > make.conf. Job done!
>
> Acting on the advice of various Gentoo guides, I have this:
>
> # grep tmp /etc/fstab
> tmpfs /var/tmp/portagetmpfs
On Fri, 9 Feb 2018 12:30:21 +0200 gevisz wrote about
Re: [gentoo-user] /var/tmp on tmpfs:
> > Why mess around with another tmpfs? Just set PORTAGE_TMPDIR="/tmp" in
> > make.conf. Job done!
>
> It is an interesting idea. But why it is not done by default then?
>
> Can somebody think of a situati
On Thu, 8 Feb 2018 22:50:58 +, Tsukasa Mcp_Reznor wrote:
> Just adding my 2 cents EMERGE_DEFAULT_OPTS="--fail-clean" helps a ton
> with tmpfs.
But it doesn't help much when your chromium build fails with 30 minutes to
go and a quick(ish) "ebuild path/to/ebuild merge" would have fixed it, as
h
2018-02-09 3:50 GMT+02:00 Dale :
> gevisz wrote:
>>
>> You probably will be surprised, but the main reason I am trying to use
>> tmpfs for /var/tmp/ is not because I want to make emerging chromium
>> faster (I have no hope about that because read somewhere that it will
>> make compilation only 10 p
2018-02-09 4:15 GMT+02:00 Ian Zimmerman :
> On 2018-02-09 01:15, Wol's lists wrote:
>
>> > Care to cite an example of such a program in the Gentoo repo? I
>> > certainly can't think of any, and I've been running with /var/tmp on
>> > tmpfs for over a decade.
>>
>> I don't know of any.
>
> vim?
>
>
I just noticed I can no longer use bluetooth with the 4.14.15 kernel. This
laptop has a shared bluetooth and WiFi mini card, which has never worked
properly (see attached hardware details).
Although MWindows has no problem, in Linux I have to disable WiFi when I need
to use bluetooth! O_o
An
Am Sonntag, 4. Februar 2018, 15:03:28 CET schrieb tu...@posteo.de:
> Hi,
>
> I still have the problem of failed builds due to an
> 'undefined reference to `__alloca''. I recompiled
> gcc/glibc and I am using linux-4.15.1 (from kernel.org)
> with linux-headers 4.15. .
>
> Affected are (at least) c
On 02/09/2018 03:30 AM, gevisz wrote:
May be, it is not a good idea to put /mnt on tmpfs at the time of Spector
and Meltdown?
I wouldn't put /mnt on tmpfs as I routinely create mount points there
in. As such they would be lost on reboot.
What difference does Spector or Meltdown (or the next
On 02/09 10:02, Andreas K. Huettel wrote:
> Am Sonntag, 4. Februar 2018, 15:03:28 CET schrieb tu...@posteo.de:
> > Hi,
> >
> > I still have the problem of failed builds due to an
> > 'undefined reference to `__alloca''. I recompiled
> > gcc/glibc and I am using linux-4.15.1 (from kernel.org)
> > w
17 matches
Mail list logo
