Re: [arch-general] tmpfs 100% /tmp - No space left on device

2013-08-18 Thread Tom Gundersen
On Thu, Aug 15, 2013 at 8:59 PM, Leonid Isaev lis...@umail.iu.edu wrote:
 Notice, though, that if /tmp is getting full and is about the same size as 
 RAM,
 the system will start swapping well before /tmp is filled, so you'll get no
 performance gain from building in /tmp because effectively you'll be
 compiling in the swap partition.

Well, in principle it should be faster to build in swap than on a
regular fs as tmpfs will only write to the backing swap when it runs
out of space, whereas regular filesystems will write out more
frequently (and also try to make guarantees about consistency in case
of unclean shutdowns, which tmpfs+swap doesn't need to care about).

-t


Re: [arch-general] tmpfs 100% /tmp - No space left on device

2013-08-18 Thread BlissSam
On 2013-8-15,19:55,Damjan gdam...@gmail.com wrote:
 On 13.08.2013 18:43, Ralf Mardorf wrote:
 Hi :)
 
 when I try to build current linux-rt I get No space left on device,
 resp. df shows tmpfs 100% /tmp.
 
 
 setup yaourt to not build in /tmp ?
 

Use the --tmp option as you can see in the man page,
for example, yaourt -S linux-rt --tmp /var/tmp

It will cost you about 3GiB or more disk space, so make sure to have enough 
space.

Re: [arch-general] tmpfs 100% /tmp - No space left on device

2013-08-17 Thread Nowaker

when I try to build current linux-rt I get No space left on device,
resp. df shows tmpfs 100% /tmp.

What can I do?
Add tmpfs   /tmp tmpfs   nodev,nosuid,size=3G  0  0
to /etc/fstab?
What should somebody do, assumed there are only 2 GB available by RAM?


That's not a problem. tmpfs will just use swap (if you have it) so set 
as much as you like. This will slow down your build but it won't fail.


--
Damian Nowak
www.AtlasHost.eu


Re: [arch-general] tmpfs 100% /tmp - No space left on device

2013-08-17 Thread Ralf Mardorf
On Thu, 2013-08-15 at 08:59 -0400, Leonid Isaev wrote:
 On Tue, 13 Aug 2013 18:43:29 +0200
 Ralf Mardorf ralf.mard...@alice-dsl.net wrote:
 
  Hi :)
  
  when I try to build current linux-rt I get No space left on device,
  resp. df shows tmpfs 100% /tmp.
  
  What can I do?
  Add tmpfs   /tmp tmpfs   nodev,nosuid,size=3G  0  0
  to /etc/fstab?
  What should somebody do, assumed there are only 2 GB available by RAM?
 
 So, your /tmp is larger than RAM size?

[rocketmouse@archlinux ~]$ df -h
Filesystem  Size  Used Avail Use% Mounted on
/dev/sda935G   24G  9.3G  72% /
dev 1.8G 0  1.8G   0% /dev
run 1.9G 1012K  1.9G   1% /run
tmpfs   1.9G 0  1.9G   0% /dev/shm
tmpfs   1.9G 0  1.9G   0% /sys/fs/cgroup
tmpfs   3.0G  7.2M  3.0G   1% /tmp
/dev/sdb12   48G  9.9G   35G  22% /home/music
/dev/sda11   57G   23G   32G  43% /mnt/music
[rocketmouse@archlinux ~]$ hwinfo --memory
  Memory Size: 3 GB + 512 MB

Yes, the memory is  4 GiB and /tmp does not have it's own mount point,
IOW it's size is 9.3G.

 If you were successfull building a kernel completely in RAM before, I'd say
 quit all unnecessary applications like KDE, firefox, etc. to free up as much
 memory as possible...

This didn't help and usually I want to use the computer when building a
kernel-rt.

 Notice, though, that if /tmp is getting full and is about the same size as 
 RAM,
 the system will start swapping well before /tmp is filled, so you'll get no
 performance gain from building in /tmp because effectively you'll be
 compiling in the swap partition.

That's what I expected instead of an error. So it would work, if I would
give /tmp it's own mountpoint on a partition, that is smaller or equal
to the size of the memory?

Regards,
Ralf



Re: [arch-general] tmpfs 100% /tmp - No space left on device

2013-08-17 Thread Ralf Mardorf
On Thu, 2013-08-15 at 13:55 +0200, Damjan wrote:
 setup yaourt to not build in /tmp ?

Thank you,

good to know assumed I should experience this issue on a machine with
less RAM.

Building the kernel worked, after adding a line to fstab.
$ grep tmpfs  /etc/fstab
tmpfs   /tmp tmpfs   nodev,nosuid,size=3G  0  0

I didn't notice the variable TMPDIR.
$ grep TMPDIR /etc/yaourtrc
#TMPDIR=/tmp

Regards,
Ralf





Re: [arch-general] tmpfs 100% /tmp - No space left on device

2013-08-17 Thread WorMzy Tykashi
On 13 August 2013 17:43, Ralf Mardorf ralf.mard...@alice-dsl.net wrote:

 Hi :)

 when I try to build current linux-rt I get No space left on device,
 resp. df shows tmpfs 100% /tmp.

 What can I do?
 Add tmpfs   /tmp tmpfs   nodev,nosuid,size=3G  0  0
 to /etc/fstab?
 What should somebody do, assumed there are only 2 GB available by RAM?

 I could build the kernel-rt before this one,
 [rocketmouse@archlinux ~]$ uname -rm
 3.8.13-rt14-1-rt x86_64

 Some information:

 [root@archlinux rocketmouse]# df -h
 Filesystem  Size  Used Avail Use% Mounted on
 /dev/sda935G   24G  9.6G  71% /
 dev 1.8G 0  1.8G   0% /dev
 run 1.9G 1008K  1.9G   1% /run
 tmpfs   1.9G 0  1.9G   0% /dev/shm
 tmpfs   1.9G 0  1.9G   0% /sys/fs/cgroup
 tmpfs   1.9G  1.9G 0 100% /tmp
 /dev/sdb12   48G  9.9G   35G  22% /home/music
 /dev/sda11   57G   23G   32G  43% /mnt/music
 /dev/sdb820G  7.3G   12G  40% /mnt/maverick

 [rocketmouse@archlinux ~]$ hwinfo --memory
 01: None 00.0: 10102 Main Memory
   [Created at memory.66]
   Unique ID: rdCR.CxwsZFjVASF
   Hardware Class: memory
   Model: Main Memory
   Memory Range: 0x-0xe78c6fff (rw)
   Memory Size: 3 GB + 512 MB
   Config Status: cfg=new, avail=yes, need=no, active=unknown

 [root@archlinux rocketmouse]# cat /etc/fstab
 #
 # /etc/fstab: static file system information
 #
 # file system dir   type  options   dump  pass
 # UUID=f386221b-fc9c-434b-b4e7-b3b1b97be8aa LABEL=archlinux
 /dev/sda9   /   ext3
  rw,relatime,data=ordered0 1

 # UUID=3e19b702-30ed-4574-91d7-1594fad71842
 /dev/sdb7   noneswapdefaults0 0

 # UUID=4b65ccbf-2219-4734-98fa-16c58d4f60fa
 /dev/sda10  noneswapdefaults,pri=-2 0 0

 /dev/sda11/mnt/music  ext3
  noatime,defaults  0 2
 /dev/sdb12/home/music ext4
  noatime,defaults  0 2

 The available rest output of the terminal, when building linux-rt:

 cp: failed to extend
 ‘/tmp/yaourt-tmp-rocketmouse/aur-linux-rt/pkg/linux-rt/lib/modules/3.10.6-rt3-1-rt/kernel/sound/usb/snd-usbmidi-lib.ko’:
 No space left on device
   INSTALL sound/usb/usx2y/snd-usb-us122l.ko
   INSTALL sound/usb/usx2y/snd-usb-usx2y.ko
 cp: error writing
 ‘/tmp/yaourt-tmp-rocketmouse/aur-linux-rt/pkg/linux-rt/lib/modules/3.10.6-rt3-1-rt/kernel/sound/usb/usx2y/snd-usb-us122l.ko’:
 No space left on device
 cp: failed to extend
 ‘/tmp/yaourt-tmp-rocketmouse/aur-linux-rt/pkg/linux-rt/lib/modules/3.10.6-rt3-1-rt/kernel/sound/usb/usx2y/snd-usb-us122l.ko’:
 No space left on device
 cp: error writing
 ‘/tmp/yaourt-tmp-rocketmouse/aur-linux-rt/pkg/linux-rt/lib/modules/3.10.6-rt3-1-rt/kernel/sound/usb/usx2y/snd-usb-usx2y.ko’:
 No space left on device
 cp: failed to extend
 ‘/tmp/yaourt-tmp-rocketmouse/aur-linux-rt/pkg/linux-rt/lib/modules/3.10.6-rt3-1-rt/kernel/sound/usb/usx2y/snd-usb-usx2y.ko’:
 No space left on device
   MKDIR
 /tmp/yaourt-tmp-rocketmouse/aur-linux-rt/pkg/linux-rt/lib/firmware/acenic/
   MKDIR
 /tmp/yaourt-tmp-rocketmouse/aur-linux-rt/pkg/linux-rt/lib/firmware/adaptec/
   INSTALL
 /tmp/yaourt-tmp-rocketmouse/aur-linux-rt/pkg/linux-rt/lib/firmware/atmsar11.fw
   MKDIR
 /tmp/yaourt-tmp-rocketmouse/aur-linux-rt/pkg/linux-rt/lib/firmware/bnx2x/
 install: error writing
 ‘/tmp/yaourt-tmp-rocketmouse/aur-linux-rt/pkg/linux-rt/lib/firmware/atmsar11.fw’:
 No space left on device
 install: failed to extend
 ‘/tmp/yaourt-tmp-rocketmouse/aur-linux-rt/pkg/linux-rt/lib/firmware/atmsar11.fw’:
 No space left on device
 make[1]: ***
 [/tmp/yaourt-tmp-rocketmouse/aur-linux-rt/pkg/linux-rt/lib/firmware/atmsar11.fw]
 Error 1
 make[1]: *** Waiting for unfinished jobs
   MKDIR
 /tmp/yaourt-tmp-rocketmouse/aur-linux-rt/pkg/linux-rt/lib/firmware/bnx2/
 make: *** [_modinst_post] Error 2
 == ERROR: A failure occurred in package_linux-rt().
 Aborting...
 == ERROR: Makepkg was unable to build linux-rt.
 == Restart building linux-rt ? [y/N]
 == -
 ==

 Regards,
 Ralf

 Build the package outside of /tmp. You have plenty of space on /


[arch-general] tmpfs 100% /tmp - No space left on device

2013-08-15 Thread Ralf Mardorf
Hi :)

when I try to build current linux-rt I get No space left on device,
resp. df shows tmpfs 100% /tmp.

What can I do?
Add tmpfs   /tmp tmpfs   nodev,nosuid,size=3G  0  0
to /etc/fstab?
What should somebody do, assumed there are only 2 GB available by RAM?

I could build the kernel-rt before this one,
[rocketmouse@archlinux ~]$ uname -rm
3.8.13-rt14-1-rt x86_64

Some information:

[root@archlinux rocketmouse]# df -h
Filesystem  Size  Used Avail Use% Mounted on
/dev/sda935G   24G  9.6G  71% /
dev 1.8G 0  1.8G   0% /dev
run 1.9G 1008K  1.9G   1% /run
tmpfs   1.9G 0  1.9G   0% /dev/shm
tmpfs   1.9G 0  1.9G   0% /sys/fs/cgroup
tmpfs   1.9G  1.9G 0 100% /tmp
/dev/sdb12   48G  9.9G   35G  22% /home/music
/dev/sda11   57G   23G   32G  43% /mnt/music
/dev/sdb820G  7.3G   12G  40% /mnt/maverick

[rocketmouse@archlinux ~]$ hwinfo --memory
01: None 00.0: 10102 Main Memory
  [Created at memory.66]
  Unique ID: rdCR.CxwsZFjVASF
  Hardware Class: memory
  Model: Main Memory
  Memory Range: 0x-0xe78c6fff (rw)
  Memory Size: 3 GB + 512 MB
  Config Status: cfg=new, avail=yes, need=no, active=unknown

[root@archlinux rocketmouse]# cat /etc/fstab
# 
# /etc/fstab: static file system information
#
# file system dir   type  options   dump  pass
# UUID=f386221b-fc9c-434b-b4e7-b3b1b97be8aa LABEL=archlinux
/dev/sda9   /   ext3
rw,relatime,data=ordered0 1

# UUID=3e19b702-30ed-4574-91d7-1594fad71842
/dev/sdb7   noneswapdefaults0 0

# UUID=4b65ccbf-2219-4734-98fa-16c58d4f60fa
/dev/sda10  noneswapdefaults,pri=-2 0 0

/dev/sda11/mnt/music  ext3
noatime,defaults  0 2
/dev/sdb12/home/music ext4
noatime,defaults  0 2

The available rest output of the terminal, when building linux-rt:

cp: failed to extend 
‘/tmp/yaourt-tmp-rocketmouse/aur-linux-rt/pkg/linux-rt/lib/modules/3.10.6-rt3-1-rt/kernel/sound/usb/snd-usbmidi-lib.ko’:
 No space left on device
  INSTALL sound/usb/usx2y/snd-usb-us122l.ko
  INSTALL sound/usb/usx2y/snd-usb-usx2y.ko
cp: error writing 
‘/tmp/yaourt-tmp-rocketmouse/aur-linux-rt/pkg/linux-rt/lib/modules/3.10.6-rt3-1-rt/kernel/sound/usb/usx2y/snd-usb-us122l.ko’:
 No space left on device
cp: failed to extend 
‘/tmp/yaourt-tmp-rocketmouse/aur-linux-rt/pkg/linux-rt/lib/modules/3.10.6-rt3-1-rt/kernel/sound/usb/usx2y/snd-usb-us122l.ko’:
 No space left on device
cp: error writing 
‘/tmp/yaourt-tmp-rocketmouse/aur-linux-rt/pkg/linux-rt/lib/modules/3.10.6-rt3-1-rt/kernel/sound/usb/usx2y/snd-usb-usx2y.ko’:
 No space left on device
cp: failed to extend 
‘/tmp/yaourt-tmp-rocketmouse/aur-linux-rt/pkg/linux-rt/lib/modules/3.10.6-rt3-1-rt/kernel/sound/usb/usx2y/snd-usb-usx2y.ko’:
 No space left on device
  MKDIR   
/tmp/yaourt-tmp-rocketmouse/aur-linux-rt/pkg/linux-rt/lib/firmware/acenic/
  MKDIR   
/tmp/yaourt-tmp-rocketmouse/aur-linux-rt/pkg/linux-rt/lib/firmware/adaptec/
  INSTALL 
/tmp/yaourt-tmp-rocketmouse/aur-linux-rt/pkg/linux-rt/lib/firmware/atmsar11.fw
  MKDIR   
/tmp/yaourt-tmp-rocketmouse/aur-linux-rt/pkg/linux-rt/lib/firmware/bnx2x/
install: error writing 
‘/tmp/yaourt-tmp-rocketmouse/aur-linux-rt/pkg/linux-rt/lib/firmware/atmsar11.fw’:
 No space left on device
install: failed to extend 
‘/tmp/yaourt-tmp-rocketmouse/aur-linux-rt/pkg/linux-rt/lib/firmware/atmsar11.fw’:
 No space left on device
make[1]: *** 
[/tmp/yaourt-tmp-rocketmouse/aur-linux-rt/pkg/linux-rt/lib/firmware/atmsar11.fw]
 Error 1
make[1]: *** Waiting for unfinished jobs
  MKDIR   
/tmp/yaourt-tmp-rocketmouse/aur-linux-rt/pkg/linux-rt/lib/firmware/bnx2/
make: *** [_modinst_post] Error 2
== ERROR: A failure occurred in package_linux-rt().
Aborting...
== ERROR: Makepkg was unable to build linux-rt.
== Restart building linux-rt ? [y/N]
== -
==

Regards,
Ralf



Re: [arch-general] tmpfs 100% /tmp - No space left on device

2013-08-15 Thread Leonid Isaev
On Tue, 13 Aug 2013 18:43:29 +0200
Ralf Mardorf ralf.mard...@alice-dsl.net wrote:

 Hi :)
 
 when I try to build current linux-rt I get No space left on device,
 resp. df shows tmpfs 100% /tmp.
 
 What can I do?
 Add tmpfs   /tmp tmpfs   nodev,nosuid,size=3G  0  0
 to /etc/fstab?
 What should somebody do, assumed there are only 2 GB available by RAM?

So, your /tmp is larger than RAM size?

If you were successfull building a kernel completely in RAM before, I'd say
quit all unnecessary applications like KDE, firefox, etc. to free up as much
memory as possible...

Notice, though, that if /tmp is getting full and is about the same size as RAM,
the system will start swapping well before /tmp is filled, so you'll get no
performance gain from building in /tmp because effectively you'll be
compiling in the swap partition.

Cheers,
L.

 
 I could build the kernel-rt before this one,
 [rocketmouse@archlinux ~]$ uname -rm
 3.8.13-rt14-1-rt x86_64
 
 Some information:
 
 [root@archlinux rocketmouse]# df -h
 Filesystem  Size  Used Avail Use% Mounted on
 /dev/sda935G   24G  9.6G  71% /
 dev 1.8G 0  1.8G   0% /dev
 run 1.9G 1008K  1.9G   1% /run
 tmpfs   1.9G 0  1.9G   0% /dev/shm
 tmpfs   1.9G 0  1.9G   0% /sys/fs/cgroup
 tmpfs   1.9G  1.9G 0 100% /tmp
 /dev/sdb12   48G  9.9G   35G  22% /home/music
 /dev/sda11   57G   23G   32G  43% /mnt/music
 /dev/sdb820G  7.3G   12G  40% /mnt/maverick
 
 [rocketmouse@archlinux ~]$ hwinfo --memory
 01: None 00.0: 10102 Main Memory
   [Created at memory.66]
   Unique ID: rdCR.CxwsZFjVASF
   Hardware Class: memory
   Model: Main Memory
   Memory Range: 0x-0xe78c6fff (rw)
   Memory Size: 3 GB + 512 MB
   Config Status: cfg=new, avail=yes, need=no, active=unknown
 
 [root@archlinux rocketmouse]# cat /etc/fstab
 # 
 # /etc/fstab: static file system information
 #
 # file system   dir   type  options
 dumppass # UUID=f386221b-fc9c-434b-b4e7-b3b1b97be8aa
 LABEL=archlinux /dev/sda9 /   ext3
   rw,relatime,data=ordered0 1
 
 # UUID=3e19b702-30ed-4574-91d7-1594fad71842
 /dev/sdb7 noneswapdefaults
   0 0
 
 # UUID=4b65ccbf-2219-4734-98fa-16c58d4f60fa
 /dev/sda10noneswap
 defaults,pri=-2   0 0
 
 /dev/sda11  /mnt/music
 ext3noatime,defaults  0
 2 /dev/sdb12/home/music
 ext4noatime,defaults  0 2
 
 The available rest output of the terminal, when building linux-rt:
 
 cp: failed to extend
 ‘/tmp/yaourt-tmp-rocketmouse/aur-linux-rt/pkg/linux-rt/lib/modules/3.10.6-rt3-1-rt/kernel/sound/usb/snd-usbmidi-lib.ko’:
 No space left on device INSTALL sound/usb/usx2y/snd-usb-us122l.ko INSTALL
 sound/usb/usx2y/snd-usb-usx2y.ko cp: error writing
 ‘/tmp/yaourt-tmp-rocketmouse/aur-linux-rt/pkg/linux-rt/lib/modules/3.10.6-rt3-1-rt/kernel/sound/usb/usx2y/snd-usb-us122l.ko’:
 No space left on device cp: failed to extend
 ‘/tmp/yaourt-tmp-rocketmouse/aur-linux-rt/pkg/linux-rt/lib/modules/3.10.6-rt3-1-rt/kernel/sound/usb/usx2y/snd-usb-us122l.ko’:
 No space left on device cp: error writing
 ‘/tmp/yaourt-tmp-rocketmouse/aur-linux-rt/pkg/linux-rt/lib/modules/3.10.6-rt3-1-rt/kernel/sound/usb/usx2y/snd-usb-usx2y.ko’:
 No space left on device cp: failed to extend
 ‘/tmp/yaourt-tmp-rocketmouse/aur-linux-rt/pkg/linux-rt/lib/modules/3.10.6-rt3-1-rt/kernel/sound/usb/usx2y/snd-usb-usx2y.ko’:
 No space left on device
 MKDIR   
 /tmp/yaourt-tmp-rocketmouse/aur-linux-rt/pkg/linux-rt/lib/firmware/acenic/
 MKDIR   
 /tmp/yaourt-tmp-rocketmouse/aur-linux-rt/pkg/linux-rt/lib/firmware/adaptec/
 INSTALL 
 /tmp/yaourt-tmp-rocketmouse/aur-linux-rt/pkg/linux-rt/lib/firmware/atmsar11.fw
 MKDIR   
 /tmp/yaourt-tmp-rocketmouse/aur-linux-rt/pkg/linux-rt/lib/firmware/bnx2x/
 install: error writing
 ‘/tmp/yaourt-tmp-rocketmouse/aur-linux-rt/pkg/linux-rt/lib/firmware/atmsar11.fw’:
 No space left on device install: failed to extend
 ‘/tmp/yaourt-tmp-rocketmouse/aur-linux-rt/pkg/linux-rt/lib/firmware/atmsar11.fw’:
 No space left on device make[1]: ***
 [/tmp/yaourt-tmp-rocketmouse/aur-linux-rt/pkg/linux-rt/lib/firmware/atmsar11.fw]
 Error 1 make[1]: *** Waiting for unfinished jobs
 MKDIR   
 /tmp/yaourt-tmp-rocketmouse/aur-linux-rt/pkg/linux-rt/lib/firmware/bnx2/
 make: *** [_modinst_post] Error 2 == ERROR: A failure occurred in
 package_linux-rt(). Aborting... == ERROR: Makepkg was unable to build
 linux-rt. == Restart building linux-rt ? [y/N] ==
 - ==
 
 Regards,
 Ralf
 



-- 
Leonid Isaev
GnuPG key: 0x164B5A6D
Fingerprint: C0DF 20D0 C075 C3F1 E1BE  775A A7AE F6CB 164B 5A6D


signature.asc
Description: PGP signature


[arch-general] tmpfs

2010-03-25 Thread Juan Diego
Good day everyone,

I want to delete the next two lines from my fstab:

none /dev/pts devpts defaults 0 0
none /dev/shm tmpfs defaults 0 0

however I would like to know the secondary effects of doing such
thing, all the information I could get on the internet is that shm is
for POSIX shared memory support and that almost any program actually
use it, for devpts I couldn't find much information about it.

does anyone knows if it is safe to remove those lines from my fstab?

thank you.


Re: [arch-general] tmpfs

2010-03-25 Thread Jan de Groot
On Fri, 2010-03-26 at 00:53 +0900, Juan Diego wrote:
 Good day everyone,
 
 I want to delete the next two lines from my fstab:
 
 none /dev/pts devpts defaults 0 0
 none /dev/shm tmpfs defaults 0 0
 
 however I would like to know the secondary effects of doing such
 thing, all the information I could get on the internet is that shm is
 for POSIX shared memory support and that almost any program actually
 use it, for devpts I couldn't find much information about it.
 
 does anyone knows if it is safe to remove those lines from my fstab?
 
 thank you.

/dev/pts is required for virtual terminals like xterm, gnome-terminal
and others. Without that filesystem you can't start a virtual terminal.

/dev/shm is used for shared memory, it's a requirement for NPTL
semaphore functions. Now that /dev is also on tmpfs, I don't know if
it's harmful to remove. The main requirement is that this folder has
1777 permissions.



Re: [arch-general] tmpfs

2010-03-25 Thread Thomas Bächler
Am 25.03.2010 16:53, schrieb Juan Diego:
 Good day everyone,
 
 I want to delete the next two lines from my fstab:
 
 none /dev/pts devpts defaults 0 0
 none /dev/shm tmpfs defaults 0 0
 
 however I would like to know the secondary effects of doing such
 thing, all the information I could get on the internet is that shm is
 for POSIX shared memory support and that almost any program actually
 use it, for devpts I couldn't find much information about it.
 
 does anyone knows if it is safe to remove those lines from my fstab?

This is definitely NOT SAFE!

If you don't have /dev/shm, POSIX shared memory will use the same tmpfs
filesystem as /dev, which is currently limited to 10MB - POSIX shared
memory blocks might be much larger.

As for removing /dev/pts, I was tempted to tell you to do it, as it's SO
funny what happens: No pseudo TTYs are available anymore. This will
effectively prevent ssh logins, screen, any X terminal and probably many
more applications from allocating a TTY, so the only way to get a shell
is to login via a real TTY (console).

I am curious, why would you want to remove these? I am glad thouh that
you asked BEFORE killing your system instead of after.



signature.asc
Description: OpenPGP digital signature


Re: [arch-general] tmpfs

2010-03-25 Thread Thomas Bächler
Am 25.03.2010 17:12, schrieb Xavier Chantry:
 On Thu, Mar 25, 2010 at 5:07 PM, Thomas Bächler tho...@archlinux.org wrote:

 This is definitely NOT SAFE!

 If you don't have /dev/shm, POSIX shared memory will use the same tmpfs
 filesystem as /dev, which is currently limited to 10MB - POSIX shared
 memory blocks might be much larger.

 As for removing /dev/pts, I was tempted to tell you to do it, as it's SO
 funny what happens: No pseudo TTYs are available anymore. This will
 effectively prevent ssh logins, screen, any X terminal and probably many
 more applications from allocating a TTY, so the only way to get a shell
 is to login via a real TTY (console).

 I am curious, why would you want to remove these? I am glad thouh that
 you asked BEFORE killing your system instead of after.


 
 Random suggestion : adding a one-line comment before these two entries
 describing what they are for (i.e. sumup of the above) :)

Patches welcome.

Personally, I don't think it's worth the time - anyone who is going to
mess with these entries is either expected to know what they are for or
fail miserably. However, as someone who has been messing with this stuff
for 10 years, I am probably not the right person to ask.



signature.asc
Description: OpenPGP digital signature


Re: [arch-general] tmpfs

2010-03-25 Thread Juan Diego
I wanted to remove them because I was cleaning my fstab of old entries
that I dont use anymore, so I found those two in the middle of the
way, I guess they will have to stay there

On Fri, Mar 26, 2010 at 1:22 AM, Thomas Bächler tho...@archlinux.org wrote:
 Am 25.03.2010 17:12, schrieb Xavier Chantry:
 On Thu, Mar 25, 2010 at 5:07 PM, Thomas Bächler tho...@archlinux.org wrote:

 This is definitely NOT SAFE!

 If you don't have /dev/shm, POSIX shared memory will use the same tmpfs
 filesystem as /dev, which is currently limited to 10MB - POSIX shared
 memory blocks might be much larger.

 As for removing /dev/pts, I was tempted to tell you to do it, as it's SO
 funny what happens: No pseudo TTYs are available anymore. This will
 effectively prevent ssh logins, screen, any X terminal and probably many
 more applications from allocating a TTY, so the only way to get a shell
 is to login via a real TTY (console).

 I am curious, why would you want to remove these? I am glad thouh that
 you asked BEFORE killing your system instead of after.



 Random suggestion : adding a one-line comment before these two entries
 describing what they are for (i.e. sumup of the above) :)

 Patches welcome.

 Personally, I don't think it's worth the time - anyone who is going to
 mess with these entries is either expected to know what they are for or
 fail miserably. However, as someone who has been messing with this stuff
 for 10 years, I am probably not the right person to ask.




Re: [arch-general] tmpfs

2010-03-25 Thread Ng Oon-Ee
On Fri, 2010-03-26 at 01:47 +0900, Juan Diego wrote:
 I wanted to remove them because I was cleaning my fstab of old entries
 that I dont use anymore, so I found those two in the middle of the
 way, I guess they will have to stay there

Bottom-posting, please...

And yes, I've wanted to remove them before. Thankfully google set me
right on that one.