Page 2 of 2 FirstFirst 12
Results 11 to 13 of 13

Thread: openSUSE and new hardware ? ( uefi, secure boot, gpt, ssd)

  1. #11
    Join Date
    Feb 2009
    Location
    Spain
    Posts
    25,547

    Default Re: openSUSE and new hardware ? ( uefi, secure boot, gpt, ssd)

    On 2014-01-02 03:56, F Sauce wrote:
    > It is also recommended to mount/tmp/ to RAM, some also suggest to mount
    > /var/spool, /var/tmp and even /var/log to RAM.


    If you do, in case of problems and crash you have no clue to read. No logs.

    --
    Cheers / Saludos,

    Carlos E. R.
    (from 13.1 x86_64 "Bottle" (Elessar))

  2. #12
    Join Date
    Jun 2008
    Location
    Sogndal, Noreg
    Posts
    1,103

    Default Re: openSUSE and new hardware ? ( uefi, secure boot, gpt, ssd)

    Quote Originally Posted by robin_listas View Post
    On 2014-01-02 03:56, F Sauce wrote:
    > It is also recommended to mount/tmp/ to RAM, some also suggest to mount
    > /var/spool, /var/tmp and even /var/log to RAM.


    If you do, in case of problems and crash you have no clue to read. No logs.

    --
    Cheers / Saludos,

    Carlos E. R.
    (from 13.1 x86_64 "Bottle" (Elessar))
    The priority for those who advocate putting /var/log to RAM is, I suppose, to limit disk write and thus increase the lifespan of the drive.
    I don't do this myself though.
    OpenSuSE 13.1, KDE 4.11.5, 64bit
    Gigabyte 990FXA-UD3, AMD FX8350, MSI GeForce GTX 760, RME HDSP9632, 16GB HyperX Kingston DDR3, Samsung 840-Pro SSD 128GB, WD Desktop Black 1TB, Hitachi Deskstar 7K1000 750GB

  3. #13
    Join Date
    Feb 2009
    Location
    Spain
    Posts
    25,547

    Default Re: openSUSE and new hardware ? ( uefi, secure boot, gpt, ssd)

    On 2014-01-02 07:16, F Sauce wrote:

    >> If you do, in case of problems and crash you have no clue to read. No
    >> logs.


    > The priority for those who advocate putting /var/log to RAM is, I
    > suppose, to limit disk write and thus increase the lifespan of the
    > drive.
    > I don't do this myself though.


    I know, but I think it is misplaced, with current hardware. Better would be adjusting kernel to
    delay and group writes (the customizations in laptop mode tools do it).

    --
    Cheers / Saludos,

    Carlos E. R.
    (from 13.1 x86_64 "Bottle" (Elessar))

Page 2 of 2 FirstFirst 12

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •