public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mick <michaelkintzios@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] udev-191 bit me. Insufficient ptys
Date: Mon, 11 Feb 2013 16:14:06 +0000	[thread overview]
Message-ID: <201302111622.36229.michaelkintzios@gmail.com> (raw)
In-Reply-To: <51191074.5030801@xunil.at>

[-- Attachment #1: Type: Text/Plain, Size: 1108 bytes --]

On Monday 11 Feb 2013 15:38:28 Stefan G. Weichinger wrote:
> Am 07.02.2013 22:38, schrieb Canek Peláez Valdés:
> > For what is worth, you also don't need to specify neither /dev nor
> > /proc in fstab with systemd. I'm not sure the init system has anything
> > to do with it, though; I believe is udev work, so with a recent
> > version of udev, no matter the init system (I think), /dev and /proc
> > are unnecessary (and perhaps even problematic) in /etc/fstab.
> 
> In my fstab there is the line(s):
> 
> # NOTE: The next line is critical for boot!
> proc                    /proc           proc            defaults        0 0
> 
> both outdated?
> 
> ;-)

I would think so.

This is the only line that I have in mine and the system boots fine:

# glibc 2.2 and above expects tmpfs to be mounted at /dev/shm for 
# POSIX shared memory (shm_open, shm_unlink).
# (tmpfs is a dynamically expandable/shrinkable ramdisk, and will
#  use almost no memory if not populated with files)
tmpfs           /dev/shm        tmpfs           nodev,nosuid,noexec     0 0

-- 
Regards,
Mick

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2013-02-11 16:23 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-31  3:35 [gentoo-user] udev-191 bit me. Insufficient ptys Michael Mol
2013-01-31  4:45 ` Canek Peláez Valdés
2013-01-31  4:48   ` Canek Peláez Valdés
2013-01-31 13:26     ` Michael Mol
2013-01-31 13:47       ` Michael Mol
2013-01-31 14:05         ` Michael Mol
2013-01-31 14:30           ` Peter Humphrey
2013-01-31 14:37             ` Michael Mol
2013-01-31 18:24               ` Mick
2013-01-31 18:29                 ` Michael Mol
2013-01-31 14:31           ` Michael Mol
2013-01-31 14:45             ` Peter Humphrey
2013-01-31 15:23 ` Alan McKinnon
2013-01-31 15:26   ` Michael Mol
2013-02-02 15:21 ` Alex Schuster
2013-02-02 19:17   ` Alan McKinnon
2013-02-02 20:31     ` Neil Bothwick
2013-02-02 20:47       ` Alan McKinnon
2013-02-02 20:53         ` Bruce Hill
2013-02-03 11:24         ` Neil Bothwick
2013-02-03 12:02           ` Alan McKinnon
2013-02-03 14:54             ` Neil Bothwick
2013-02-03 17:24               ` Alan McKinnon
2013-02-03 19:08                 ` Neil Bothwick
2013-02-03 19:23                 ` Michael Orlitzky
2013-02-02 21:06     ` Michael Mol
2013-02-03 17:51     ` Alex Schuster
2013-02-03 19:08       ` [gentoo-user] " »Q«
2013-02-07 17:40       ` [gentoo-user] " Tanstaafl
2013-02-07 17:53         ` Peter Humphrey
2013-02-07 20:53           ` Tanstaafl
2013-02-07 21:25             ` Paul Hartman
2013-02-07 21:37               ` Tanstaafl
2013-02-07 22:00                 ` Alecks Gates
2013-02-07 22:12                   ` [gentoo-user] " »Q«
2013-02-08  7:29                 ` [gentoo-user] " Alan McKinnon
2013-02-08 16:02                 ` Paul Hartman
2013-02-08 20:17                 ` Peter Humphrey
2013-02-11  1:40                 ` Stroller
2013-02-07 21:38               ` Canek Peláez Valdés
2013-02-11 15:38                 ` Stefan G. Weichinger
2013-02-11 16:14                   ` Mick [this message]
2013-02-11 17:36                     ` Dale
2013-02-11 19:41                       ` Stefan G. Weichinger

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=201302111622.36229.michaelkintzios@gmail.com \
    --to=michaelkintzios@gmail.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox