Once you run these two commands, it removes a link for each that allows the service to run at startup. So, once you run these two commands, reboot and you are done. Consider that if you have a mixed system, SSD and hard drive, you may not want to use these commands.
Also,
I strongly consider you look at the publication date for any article you read about optimizing SSD.
As I describe in the presentation I created a year ago, there have been plenty of changes in SSD manufacturing up to a year ago which largely standardized the quality of drives and obsoleted plenty of advice given before then.
I also skimmed the articles referenced in the SDB and don’t think too much of most of the articles. There is plenty of FUD and inaccurate information in several of them.
If you <really> want up to date advice, I highly recommend the Arch Linux Wiki on optimizing SSD. But even so, I feel that most of the new optimizations recommended since my presentation was created provide little incremental value. I would stick with the optimizations I implemented for openSUSE 12.2 and are still totally relevant through 12.3 and likely ffor 13.1
A few optimizations mentioned in the slide deck
Partitioning for rotational (HDD) and solid state (SSD) systems
Disabling journaling when not needed
Modifying I/O to account for flat data access because default accounts for disk geometry
Discusses TRIM and SSD writes accurately (unlike as described in some of the articles referenced by the SDB)
Recommended additions to monitor real time disk performance
I had not thought about that Jim and I think I see what you mean. Removing the links affects the HDD as well.
And you probably know that I am fretting about maybe milliseconds.
And I’ll be darned if I can see any difference.