SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Nah, that article is written by the one of the kernel memory management guys, so what does he know?
The conclusion btw...
Quote:
Swap is a useful tool to allow equality of reclamation of memory pages, but its purpose is frequently misunderstood, leading to its negative perception across the industry. If you use swap in the spirit intended, though – as a method of increasing equality of reclamation – you'll find that it's a useful tool instead of a hindrance.
Disabling swap does not prevent disk I/O from becoming a problem under memory contention, it simply shifts the disk I/O thrashing from anonymous pages to file pages. Not only may this be less efficient, as we have a smaller pool of pages to select from for reclaim, but it may also contribute to getting into this high contention state in the first place.
Swap can make a system slower to OOM kill, since it provides another, slower source of memory to thrash on in out of memory situations – the OOM killer is only used by the kernel as a last resort, after things have already become monumentally screwed. The solutions here depend on your system:
You can opportunistically change the system workload depending on cgroup-local or global memory pressure. This prevents getting into these situations in the first place, but solid memory pressure metrics are lacking throughout the history of Unix. Hopefully this should be better soon with the addition of refault detection.
You can bias reclaiming (and thus swapping) away from certain processes per-cgroup using memory.low, allowing you to protect critical daemons without disabling swap entirely.
Wait, so your reason to not use swap is because saves more power?
My English is probably not very clear...
But what I said (or wanted to say) is:
I use swap because I use hibernation.
And because of power saving, hibernation is not an option for me
I don't see any reason not to use swap anyway (cf. Jan K. post & link)
And because of power saving, hibernation is not an option for me
This sentence is basically saying what I asked about before. What this sentence comes across as is you can't use hibernation ("hibernation is not an option for me") because of power saving.
It doesn't seem like that is your intention behind the sentence...
This sentence is basically saying what I asked about before. What this sentence comes across as is you can't use hibernation ("hibernation is not an option for me") because of power saving.
It doesn't seem like that is your intention behind the sentence...
hmm, not really. At least, that's not what I wanted to say
"is not an option" means "is mandatory"
hmm, not really. At least, that's not what I wanted to say
"is not an option" means "is mandatory"
in any case, in French that's what it means
If you've ever seen Apollo 13 in English, you'll understand the differences with the phrase.
In the movie, Gene Kranz, the flight director in Houston states, "Failure is not an option." meaning, we can't fail or our people up there die. We definitely don't want "Failure is mandatory."
I know I'm new here, but I think that the occasional friendly English lesson in an effort to help each other understand and communicate better is not a Bad Thing. Much better than degenerating into a flame war because someone took something differently than intended.
I know I'm new here, but I think that the occasional friendly English lesson in an effort to help each other understand and communicate better is not a Bad Thing. Much better than degenerating into a flame war because someone took something differently than intended.
No flame war here
Mr. bassmadrigal knows very well that the meaning of a sentence can be different in two states of his own country, so with a different country, culture, etc. the different levels of understanding are logical
Quote:
Originally Posted by bassmadrigal
"Failure is not an option." meaning, we can't fail or our people up there die. We definitely don't want "Failure is mandatory."
And to conclude on this point:
to keep the negation (because failure is a "negative" word), and the meaning:
failure is not an option ==> no failure is mandatory
ditto for:
miss the target is not an option => hit the target is mandatory
Suspend/Resume is not an option because it consumes power even while sleeping.
Hibernate does not use power and is your best option.
If no other power management systems offer 0% power utilization and you require a power saving solution for your use case, then we can conclude that Hibernation is not optional.
The "failure is not an option" idiom does not apply to this situation and is generally used as a "call to arms" in competitive scenarios. E.g. Russia has more tanks, but failure is not an option!
[removed]
Quote:
Originally Posted by marav
No flame war here
Mr. bassmadrigal knows very well that the meaning of a sentence can be different in two states of his own country...
LOL that made my day. Spent the whole bus ride home chuckling to myself.
To continue with the language disambiguation, but also staying on topic...
Quote:
In summary, "Is it possible to install Slackware without swap?" Yes it is possible to install Slackware without a swap
The initial question asks about a possibility: can XXX be done (or not), which has a yes/no answer. Either it can, or it can't.
Reading between the lines, one might think that the actual question being asked is "Is it a good idea to install Slackware without swap?". This still leaves much ambiguity, because "good idea" is not an objective fact, it is an opinion. What might seem like a good idea to one person may seem like a bad idea to another - either due to simple preferences, or due to additional unknown differences is setup or use.
Adding more interpretation, you could answer the question "What are the advantages or disadvantages of installing Slackware without swap?", but this is only a useful question if the answer to the original question is "yes'. At this point, the question allows one to collect information, hopefully to be able to make up one's own mind about "is it a good idea?".
And when the original question leaves ambiguity, and people ask for more information so that they can help answer the correct version, the person that originally asked is best off to realize the ambiguity and clarify.
I think in this thread, we've seen the answers to "can you?", "Is it a good idea?", and "what are the advantages/disadvantages?". Constructive dialog.
As the original poster I was asking "Is it possible". Having installed slackware many times I am familiar with the stage of setting up swap and I wanted to know if it was possible to skip that swap stage entirely.
Having said that I did appreciate all the discussion about the wisdom of doing so and perhaps sub-consciously I had this question in mind as well.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.