Roger Leigh rle...@codelibre.net writes:
On Wed, Nov 16, 2011 at 11:56:40AM +0100, Goswin von Brederlow wrote:
Roger Leigh rle...@codelibre.net writes:
As touched on in the bug report, I think that being able to store
1.2GiB on /tmp is an unrealistic expectation. To qualify, I mean
to
Chow Loong Jin hyper...@ubuntu.com writes:
On 16/11/2011 22:43, Salvo Tomaselli wrote:
Most netbooks and small laptops (such as Thinkpads) do not.
My thinkpad has it...
Mine doesn't. The smaller Thinkpads (less than 14?) don't.
This discussion is getting more and more weird, but for the
Salvo Tomaselli tipos...@tiscali.it writes:
I think the problems you describe are quite uncommon. Yes, there are use
cases where tmpfs for /tmp isn't the best solution but I think most
people do not place 1.2GB files in their /tmp and benefit greatly from
tmpfs.
I thought DVD burners were
Richard richard.b...@blueyonder.co.uk writes:
On Wed, 16 Nov 2011 13:21:47 +0100
Didier Raboud o...@debian.org wrote:
Salvo Tomaselli wrote:
I think the problems you describe are quite uncommon. Yes, there are use
cases where tmpfs for /tmp isn't the best solution but I think most
Chow Loong Jin hyper...@ubuntu.com writes:
On 16/11/2011 22:45, Salvo Tomaselli wrote:
Given that any burning software can (approximately) determine what size the
ISO file will be, it should really not start to write it in /tmp when the
/tmp size is not big enough (which the software can
Carlos Alberto Lopez Perez clo...@igalia.com writes:
On 16/11/11 11:37, Goswin von Brederlow wrote:
Assuming you have increased your SWAP by the size of the tmpfs to
compensate for /tmp now using RAM+SWAP you can only ever get that effect
in cases where the OOMKiller would have already been
Salvo Tomaselli tipos...@tiscali.it writes:
While amazon.com cloud may have small RAM and large disks, many
mainframes are opposite (ie, IBM big blue, japan's world simulator). And
many new PCs may become that way: no spin :) Maybe not!
I think we are focusing a bit too much on super
Russell Coker russ...@coker.com.au writes:
On Wed, 16 Nov 2011, Goswin von Brederlow goswin-...@web.de wrote:
With a filesystem it will write the dirty buffers to disk in the
background and then drop the clean pages from the cache quite
consistently. This leaves the code involved with moving
#1 Backup. Why is supporting optional kernel features injected at runlevel S
and not runlevel 3?
At runlevel 3, being optional, no one will care which is done. At runlevel S, before a login can
fix things, it's a problem.
/tmp is legacy. You don't write history or future for others. What
Ben Hutchings b...@decadent.org.uk writes:
On Sun, 2011-11-13 at 04:04 +0100, Carlos Alberto Lopez Perez wrote:
On 12/11/11 23:25, Josselin Mouette wrote:
Le samedi 12 novembre 2011 à 23:12 +0100, Samuel Thibault a écrit :
Adam Borowski, le Sat 12 Nov 2011 23:08:08 +0100, a écrit :
Roger Leigh rle...@codelibre.net writes:
On Sat, Nov 12, 2011 at 10:24:00PM +0100, Bastien ROUCARIES wrote:
Recently debian put /tmp under tmpfs.
Even if it increase reponsivness under desktop, it ruin completly
sciene and imaging software that do some off loading on /tmp.
For instance
On Wed, 16 Nov 2011, Goswin von Brederlow goswin-...@web.de wrote:
With a filesystem it will write the dirty buffers to disk in the
background and then drop the clean pages from the cache quite
consistently. This leaves the code involved with moving the mouse
pointer alone and functioning
I think the problems you describe are quite uncommon. Yes, there are use
cases where tmpfs for /tmp isn't the best solution but I think most
people do not place 1.2GB files in their /tmp and benefit greatly from
tmpfs.
I thought DVD burners were quite common... and almost every desktop or
On Wed, Nov 16, 2011 at 7:43 PM, Salvo Tomaselli wrote:
I thought DVD burners were quite common... and almost every desktop or laptop
has one.
Most netbooks and small laptops (such as Thinkpads) do not. I'm
personally looking forward to never having to deal with optical media
ever again.
--
Salvo Tomaselli wrote:
I think the problems you describe are quite uncommon. Yes, there are use
cases where tmpfs for /tmp isn't the best solution but I think most
people do not place 1.2GB files in their /tmp and benefit greatly from
tmpfs.
I thought DVD burners were quite common... and
On Wed, 16 Nov 2011 13:21:47 +0100
Didier Raboud o...@debian.org wrote:
Salvo Tomaselli wrote:
I think the problems you describe are quite uncommon. Yes, there are use
cases where tmpfs for /tmp isn't the best solution but I think most
people do not place 1.2GB files in their /tmp and
I find it hard to believe the origional bug is #630615 based on people's
comments! That's Funny!
1) rc.boot is for booting not for demanding / depends on kernel Options so and
so opted in (ie,
tmpfs). (is that why I had to hack mknod ptys in rc.local on one pc? wtf?)
Please do extras at
Given that any burning software can (approximately) determine what size the
ISO file will be, it should really not start to write it in /tmp when the
/tmp size is not big enough (which the software can also check). Prompting
a user with I will not be able to write ${file} in /tmp, please
While amazon.com cloud may have small RAM and large disks, many
mainframes are opposite (ie, IBM big blue, japan's world simulator). And
many new PCs may become that way: no spin :) Maybe not!
I think we are focusing a bit too much on super expensive computers here.
Of course on a computer
Most netbooks and small laptops (such as Thinkpads) do not.
My thinkpad has it...
--
Salvo Tomaselli
signature.asc
Description: This is a digitally signed message part.
On 16/11/2011 22:43, Salvo Tomaselli wrote:
Most netbooks and small laptops (such as Thinkpads) do not.
My thinkpad has it...
Mine doesn't. The smaller Thinkpads (less than 14?) don't.
--
Kind regards,
Loong Jin
signature.asc
Description: OpenPGP digital signature
On 16/11/2011 22:45, Salvo Tomaselli wrote:
Given that any burning software can (approximately) determine what size the
ISO file will be, it should really not start to write it in /tmp when the
/tmp size is not big enough (which the software can also check). Prompting
a user with I will not
On Wed, Nov 16, 2011 at 05:55, John D. Hendrickson and Sara Darnell
johnandsa...@cox.net wrote:
3) Whether 1.2G is or is not in a directory is a mute Question and argument.
it is a moot question, not mute
Cheers,
Kelly Clowers
--
To UNSUBSCRIBE, email to
Doesn't tmpfs default to 50% of your memory? Unless you have 8GB of memory,
you shouldn't be seeing 4GB worth of data getting into /tmp by mistake.
I am afraid of seeing 2GB paged out too, it is still a big amount of memory.
Well then if it will be decided to use tmpfs for /tmp, the installer
On Thu, Nov 17, 2011 at 12:14:26AM +0800, Chow Loong Jin wrote:
Doesn't tmpfs default to 50% of your memory? Unless you have 8GB
of memory, you shouldn't be seeing 4GB worth of data getting into
/tmp by mistake.
As mentioned elsewhere in the thread, it defaults to 20% core for /tmp.
--
On Wed, Nov 16, 2011 at 11:56:40AM +0100, Goswin von Brederlow wrote:
Roger Leigh rle...@codelibre.net writes:
As touched on in the bug report, I think that being able to store
1.2GiB on /tmp is an unrealistic expectation. To qualify, I mean
to expect that to work *by default*. If you
On 16/11/11 11:37, Goswin von Brederlow wrote:
Assuming you have increased your SWAP by the size of the tmpfs to
compensate for /tmp now using RAM+SWAP you can only ever get that effect
in cases where the OOMKiller would have already been triggered with /tmp
on disk.
We are talking about the
On Tue, 15 Nov 2011 07:41:54 +0100
Andrew Shadura bugzi...@tut.by wrote:
Hello,
On Mon, 14 Nov 2011 00:14:18 +0100
Josselin Mouette j...@debian.org wrote:
No it does not work like you said. We know the matrix structure, not
the kernel. We map and unmap manually. Doing as you said is
On Tue, Nov 15, 2011 at 07:41:54AM +0100, Andrew Shadura wrote:
On Mon, 14 Nov 2011 00:14:18 +0100
Josselin Mouette j...@debian.org wrote:
This is getting insane. Please learn how to use madvise and
posix_fadvise and let the kernel deal with paging. The kernel knows
everything about the
On 15 November 2011 08:17, Neil Williams codeh...@debian.org wrote:
On Tue, 15 Nov 2011 07:41:54 +0100
Andrew Shadura bugzi...@tut.by wrote:
Hello,
On Mon, 14 Nov 2011 00:14:18 +0100
Josselin Mouette j...@debian.org wrote:
No it does not work like you said. We know the matrix structure,
On Tue, 15 Nov 2011 12:34:03 +, Aneurin Price aneurin.pr...@gmail.com
wrote:
...
I think this discussion needs a sanity check.
Please remember, the topic of conversation is whether an application
can reasonably make the assumption that the system defined tmp
directory is a suitable
On Tue, 15 Nov 2011, Aneurin Price wrote:
I think this discussion needs a sanity check.
Please remember, the topic of conversation is whether an application
can reasonably make the assumption that the system defined tmp
directory is a suitable place to store temporary data.
/tmp in RAM has
Le Monday 14 November 2011 00:14:18, Josselin Mouette a écrit :
Le dimanche 13 novembre 2011 à 23:20 +0100, Bastien ROUCARIES a écrit :
No it does not work like you said. We know the matrix structure, not
the kernel. We map and unmap manually. Doing as you said is
inneficient and trash a
I still think that is disagreeing with thought using /tmp is a bad idea is a good idea and agree
with the people who are against.
debian-devel@lists.debian.orgAneurin Price wrote:
On 15 November 2011 08:17, Neil Williams codeh...@debian.org wrote:
Do not cripple all platforms with the sins
]] Roger Leigh
Hi,
| But we can certainly deprecate /etc/default/tmpfs and rely solely upon
| the hardcoded defaults in /lib/init/tmpfs.sh.
Yes, please and thanks. :-)
(Maybe consider doing a one-time migration to /etc/fstab and then drop
support for the settings in /etc/default a bit further
Timo Juhani Lindfors writes (Re: /tmp as tmpfs and consequence for imaging
software):
That does not seem to be so easy:
http://www.gnu.org/ghm/2011/paris/slides/jim-meyering-goodbye-world.pdf
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=28251
bug in libc which libc maintainers don't want
I would like to agree with Roger in his response.
simple well knowns, non-obstructing, no-new-bugsy, non-kernel-hack dep., If linux allows a
single project need to break softwares already prepared and working it is not survivable to
maintain and ignores justice in legacy.
(from
Ian Jackson wrote:
Timo Juhani Lindfors writes (Re: /tmp as tmpfs and consequence for imaging
software):
That does not seem to be so easy:
http://www.gnu.org/ghm/2011/paris/slides/jim-meyering-goodbye-world.pdf
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=28251
bug in libc which
Joey Hess writes (Re: /tmp as tmpfs and consequence for imaging software):
Which is a pity. Has it ever been sent to glibc upstream?
I didn't fancy fighting glibc upstream. However we have a new
upstream since we are now using eglibc so I should perhaps actually
try that.
With that said, it's
Ian Jackson ijack...@chiark.greenend.org.uk (14/11/2011):
I didn't fancy fighting glibc upstream. However we have a new
upstream since we are now using eglibc so I should perhaps actually
try that.
From http://www.eglibc.org/contributing:
| Applicability
|
| EGLIBC is focused on support for
Cyril Brulebois writes (Re: /tmp as tmpfs and consequence for imaging
software):
From http://www.eglibc.org/contributing:
| Applicability
|
| EGLIBC is focused on support for embedded systems. Therefore, if your
| change is of general utility, or is likely to be of more benefit to
|
On Mon, Nov 14, 2011 at 05:04:28PM +, Ian Jackson wrote:
Cyril Brulebois writes (Re: /tmp as tmpfs and consequence for imaging
software):
From http://www.eglibc.org/contributing:
| Applicability
|
| EGLIBC is focused on support for embedded systems. Therefore, if your
| change is
Hello,
On Sun, 13 Nov 2011 15:39:51 +0100
Salvo Tomaselli tipos...@tiscali.it wrote:
$HOME is not really nice but it could work. I have a tmp dir under
my home directry and some script to clean up at every log on.
$HOME seems like a very bad idea to me. At least if used by default...
Hello,
On Mon, 14 Nov 2011 00:14:18 +0100
Josselin Mouette j...@debian.org wrote:
No it does not work like you said. We know the matrix structure, not
the kernel. We map and unmap manually. Doing as you said is
inneficient and trash a lot cache and so on.
This is getting insane. Please
On Sat, Nov 12, 2011 at 11:12 PM, Samuel Thibault sthiba...@debian.org wrote:
Adam Borowski, le Sat 12 Nov 2011 23:08:08 +0100, a écrit :
You need to increase the swap size by the amount you'd use for /tmp.
Well, the idea of such case is precisely to *not* use swap, but real
disks. Such
Le dimanche 13 novembre 2011 à 09:40 +0100, Bastien ROUCARIES a écrit :
No it is not true. Science and imaging software are better to use true
disk baked file. For instance, if I want ot invert a big matrix they
are pretty good algorithm that force only some part of the file to be
keep on
On Sat, Nov 12, 2011 at 11:25 PM, Josselin Mouette j...@debian.org wrote:
Le samedi 12 novembre 2011 à 23:12 +0100, Samuel Thibault a écrit :
Adam Borowski, le Sat 12 Nov 2011 23:08:08 +0100, a écrit :
You need to increase the swap size by the amount you'd use for /tmp.
Well, the idea of
On Sat, Nov 12, 2011 at 11:35 PM, Ben Hutchings b...@decadent.org.uk wrote:
On Sat, 2011-11-12 at 22:24 +0100, Bastien ROUCARIES wrote:
Hello,
Recently debian put /tmp under tmpfs.
Even if it increase reponsivness under desktop, it ruin completly
sciene and imaging software that do some off
I agree with samuel here. Science software know how to use disk baked
file. And are better than general software. I will open rcbug to use
/var/tmp instead of /tmp in this case. But it is a pitty.
/var/tmp has a little problem: is not cleared upon reboot.
In fact one time i couldn't do a
On Sun, Nov 13, 2011 at 9:50 AM, Josselin Mouette j...@debian.org wrote:
Le dimanche 13 novembre 2011 à 09:40 +0100, Bastien ROUCARIES a écrit :
No it is not true. Science and imaging software are better to use true
disk baked file. For instance, if I want ot invert a big matrix they
are
Am Sonntag, 13. November 2011, 10:02:24 schrieb Salvo Tomaselli:
I agree with samuel here. Science software know how to use disk baked
file. And are better than general software. I will open rcbug to use
/var/tmp instead of /tmp in this case. But it is a pitty.
/var/tmp has a little
On Sun, Nov 13, 2011 at 09:44:15AM +0100, Bastien ROUCARIES wrote:
Yes I agree. But wich $TMPDIR should we use ? /var/tmp does not fit
because it is not cleaned at boot. And the problem is the default have
changed. I do not excuse sloppy programmer. but we need something like
a standard tmp
On Sun, 13 Nov 2011, Bastien ROUCARIES roucaries.bast...@gmail.com wrote:
Ok could we made some policy about /tmp use ? Like do not create file
above 10M ? And fill RC bug if the apps do this ?
10M is small by today's standards.
On Sun, 13 Nov 2011, Bastien ROUCARIES
On 11/13/2011 05:57 PM, Russell Coker wrote:
On Sun, 13 Nov 2011, Bastien ROUCARIES roucaries.bast...@gmail.com wrote:
Ok could we made some policy about /tmp use ? Like do not create file
above 10M ? And fill RC bug if the apps do this ?
10M is small by today's standards.
On Sun, Nov 13, 2011 at 06:30:27PM +0800, Thomas Goirand wrote:
Agreed. Anyway, I'd be happy to have, by policy, some hard limits
We can discuss of a tolerable size, like 100M? Anyway, anything
bigger than 512 MB is obviously abusing /tmp, IMHO. But if we're
to have /tmp using tmpfs by
also sprach Lars Wirzenius l...@liw.fi [2011.11.13.1204 +0100]:
A fixed policy is going to interact badly with real systems and
per-site decisions about, say, disk partitioning and provisioining
of RAM for various purposes.
The proper policy, IMHO, is that a) all software that uses temporary
Lars Wirzenius l...@liw.fi writes:
and b) all software must deal with out-of-disk-space errors in a
sensible way (where the exact details may depend on the software).
That does not seem to be so easy:
http://www.gnu.org/ghm/2011/paris/slides/jim-meyering-goodbye-world.pdf
--
To
On 11/13/2011 07:31 PM, martin f krafft wrote:
also sprach Lars Wirzenius l...@liw.fi [2011.11.13.1204 +0100]:
A fixed policy is going to interact badly with real systems and
per-site decisions about, say, disk partitioning and provisioining
of RAM for various purposes.
The proper
On Sun, Nov 13, 2011 at 11:04:55AM +, Lars Wirzenius wrote:
On Sun, Nov 13, 2011 at 06:30:27PM +0800, Thomas Goirand wrote:
Agreed. Anyway, I'd be happy to have, by policy, some hard limits
We can discuss of a tolerable size, like 100M? Anyway, anything
bigger than 512 MB is obviously
On Sun, Nov 13, 2011 at 12:04 PM, Lars Wirzenius l...@liw.fi wrote:
On Sun, Nov 13, 2011 at 06:30:27PM +0800, Thomas Goirand wrote:
Agreed. Anyway, I'd be happy to have, by policy, some hard limits
We can discuss of a tolerable size, like 100M? Anyway, anything
bigger than 512 MB is obviously
$HOME is not really nice but it could work. I have a tmp dir under my
home directry and some script to clean up at every log on.
$HOME seems like a very bad idea to me. At least if used by default...
Many universities (and i guess other places too) keep the homes on a file
server and the rest
Le dimanche 13 novembre 2011 à 15:39 +0100, Salvo Tomaselli a écrit :
$HOME is not really nice but it could work. I have a tmp dir under my
home directry and some script to clean up at every log on.
$HOME seems like a very bad idea to me. At least if used by default...
On the contrary, it
]] Bastien ROUCARIES
Hi,
| No it is not true. Science and imaging software are better to use true
| disk baked file. For instance, if I want ot invert a big matrix they
| are pretty good algorithm that force only some part of the file to be
| keep on disk. They known better than kernel when to
]] Roger Leigh
Hi,
somewhat of a tangent, so sorry for hijacking the thread:
| Currently, the size limits for /tmp and other temporary filesystems
| are set in /etc/default/tmpfs.
Can we please stop doing things like that? It makes things harder for
alternative init systems that sysvinit
On Sun, Nov 13, 2011 at 04:29:14PM +0100, Tollef Fog Heen wrote:
]] Roger Leigh
Hi,
somewhat of a tangent, so sorry for hijacking the thread:
| Currently, the size limits for /tmp and other temporary filesystems
| are set in /etc/default/tmpfs.
Can we please stop doing things like
Le Sunday 13 November 2011 16:24:18, Tollef Fog Heen a écrit :
]] Bastien ROUCARIES
Hi,
| No it is not true. Science and imaging software are better to use true
| disk baked file. For instance, if I want ot invert a big matrix they
| are pretty good algorithm that force only some part of
Bastien ROUCARIES:
Hello,
Recently debian put /tmp under tmpfs.
My /tmp does not have 50% the size of my RAM.
In my /etc/default/rcS:
RAMRUN=yex
RAMLOCK=yes
in /etc/fstab:
tmpfs /tmp tmpfs noatime 0 0
results in df -h on a 3GB RAM machine:
FilesystemSize Used Avail Use%
]] bastien ROUCARIES
Hi,
please don't cc me on mailing list posts. It's rude and against Debian
list policy, even more so when I've set mail-followup-to.
| Le Sunday 13 November 2011 16:24:18, Tollef Fog Heen a écrit :
| ]] Bastien ROUCARIES
|
| Hi,
|
| | No it is not true. Science and
]] Roger Leigh
| I may have given an incomplete picture here. While we set the defaults
| there, any entry in /etc/fstab will override those defaults.
Can you please not set the default in a file in /etc then, since then
people expect to be able to change them and bugs file bugs on systemd
On Sun, Nov 13, 2011 at 10:06 PM, Tollef Fog Heen tfh...@err.no wrote:
]] bastien ROUCARIES
Hi,
please don't cc me on mailing list posts. It's rude and against Debian
list policy, even more so when I've set mail-followup-to.
| Le Sunday 13 November 2011 16:24:18, Tollef Fog Heen a écrit :
Le dimanche 13 novembre 2011 à 23:20 +0100, Bastien ROUCARIES a écrit :
No it does not work like you said. We know the matrix structure, not
the kernel. We map and unmap manually. Doing as you said is
inneficient and trash a lot cache and so on.
This is getting insane. Please learn how to use
On Sun, Nov 13, 2011 at 09:16:55PM +0100, Thomas Koch wrote:
Bastien ROUCARIES:
Hello,
Recently debian put /tmp under tmpfs.
My /tmp does not have 50% the size of my RAM.
In my /etc/default/rcS:
RAMRUN=yex
RAMLOCK=yes
in /etc/fstab:
tmpfs /tmp tmpfs noatime 0 0
results in df
On Sun, Nov 13, 2011 at 10:09:16PM +0100, Tollef Fog Heen wrote:
]] Roger Leigh
| I may have given an incomplete picture here. While we set the defaults
| there, any entry in /etc/fstab will override those defaults.
Can you please not set the default in a file in /etc then, since then
On Sun, Nov 13, 2011 at 09:40:42AM +0100, Bastien ROUCARIES wrote:
On Sat, Nov 12, 2011 at 11:25 PM, Josselin Mouette j...@debian.org wrote:
Le samedi 12 novembre 2011 à 23:12 +0100, Samuel Thibault a écrit :
Adam Borowski, le Sat 12 Nov 2011 23:08:08 +0100, a écrit :
You need to increase
In data Sunday 13 November 2011 15:59:12, Josselin Mouette ha scritto:
Le dimanche 13 novembre 2011 à 15:39 +0100, Salvo Tomaselli a écrit :
$HOME is not really nice but it could work. I have a tmp dir under my
home directry and some script to clean up at every log on.
$HOME seems like
On Sun, 2011-11-13 at 13:36 +0100, Bastien ROUCARIES wrote:
In my uni sysadmin said: we use distribution default by default, if
you want to change default fill a complain. It take about 3 month to
get some simple change from default like activing transparent hugpage
for hpc. I know it is
On Mon, 14 Nov 2011, David McBride d...@doc.ic.ac.uk wrote:
But as with most things, being a systems administrator is often harder
than it looks.
In a more generic form, doing almost anything is harder than it looks.
If developing a Linux distribution for use by hundreds of millions of people
Hello,
Recently debian put /tmp under tmpfs.
Even if it increase reponsivness under desktop, it ruin completly
sciene and imaging software that do some off loading on /tmp.
For instance using gscan2pdf on 60pages document create more than 1.2G
of image file under /tmp and crash du to missing
On Sat, Nov 12, 2011 at 10:24:00PM +0100, Bastien ROUCARIES wrote:
Hello,
Recently debian put /tmp under tmpfs.
Even if it increase reponsivness under desktop, it ruin completly
sciene and imaging software that do some off loading on /tmp.
For instance using gscan2pdf on 60pages
Adam Borowski, le Sat 12 Nov 2011 23:08:08 +0100, a écrit :
You need to increase the swap size by the amount you'd use for /tmp.
Well, the idea of such case is precisely to *not* use swap, but real
disks. Such software already know how to manage its memory and
disk-backed memory (thusly stored
Le samedi 12 novembre 2011 à 23:12 +0100, Samuel Thibault a écrit :
Adam Borowski, le Sat 12 Nov 2011 23:08:08 +0100, a écrit :
You need to increase the swap size by the amount you'd use for /tmp.
Well, the idea of such case is precisely to *not* use swap, but real
disks. Such software
On Sat, 2011-11-12 at 22:24 +0100, Bastien ROUCARIES wrote:
Hello,
Recently debian put /tmp under tmpfs.
Even if it increase reponsivness under desktop, it ruin completly
sciene and imaging software that do some off loading on /tmp.
For instance using gscan2pdf on 60pages document
On Sat, 12 Nov 2011, Bastien ROUCARIES wrote:
Hello,
Recently debian put /tmp under tmpfs.
Even if it increase reponsivness under desktop, it ruin completly
sciene and imaging software that do some off loading on /tmp.
For instance using gscan2pdf on 60pages document create more than 1.2G
of
On Sat, Nov 12, 2011 at 10:24:00PM +0100, Bastien ROUCARIES wrote:
Recently debian put /tmp under tmpfs.
Even if it increase reponsivness under desktop, it ruin completly
sciene and imaging software that do some off loading on /tmp.
For instance using gscan2pdf on 60pages document create
On Sat, Nov 12, 2011 at 11:25:12PM +0100, Josselin Mouette wrote:
Le samedi 12 novembre 2011 à 23:12 +0100, Samuel Thibault a écrit :
Adam Borowski, le Sat 12 Nov 2011 23:08:08 +0100, a écrit :
You need to increase the swap size by the amount you'd use for /tmp.
Well, the idea of such
On 12/11/11 23:25, Josselin Mouette wrote:
Le samedi 12 novembre 2011 à 23:12 +0100, Samuel Thibault a écrit :
Adam Borowski, le Sat 12 Nov 2011 23:08:08 +0100, a écrit :
You need to increase the swap size by the amount you'd use for /tmp.
Well, the idea of such case is precisely to *not*
On Sun, 2011-11-13 at 04:04 +0100, Carlos Alberto Lopez Perez wrote:
On 12/11/11 23:25, Josselin Mouette wrote:
Le samedi 12 novembre 2011 à 23:12 +0100, Samuel Thibault a écrit :
Adam Borowski, le Sat 12 Nov 2011 23:08:08 +0100, a écrit :
You need to increase the swap size by the amount
87 matches
Mail list logo
