Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Its resolution will be higher. Reduce its resolution and size will be reduced automatically.
You can use gimp or kolour paint to reduce the resolution & size.
It's a little bit hidden in the above example (if you are a newbie to commandline stuff), but the operative command you should investigate is "convert". Specifically "convert" with the "-resize" option. All that other "find" and "ionice" stuff is great if you understand what they are doing, but they have nothing to do with image resizing.
Generally people take images using 5 mega px, 10 mega px or higher mega pixel camera because of this image size is more than 2 MB.
Now when you see the dimension of the image, the width & height is more than 2000 pixels. If you reduce this dimension and make it in the range of 800, the image size is reduced as well as the image does not look stretched or pixelated for normal view (without zoom).
Ex-
if an image has 3457 x 2408(w x h)dimension and 2.2 MB image size, if you make it into 800 x 557 (a normal sufficient view to see an image without zoom), it's size becomes around 500kb.
These are not standard numbers.
This is a just an example.
I always set my point-n-shoots to lower than max resolution. I have a nice little Canon Elph that is 12.1 megapixels. Although it's a nice camera, it is nowhere near the quality required to make use of 12 megapixels. The lens isn't outstanding nor is it useful to put 12 megapixels onto a itty bitty sensor like these point-n-shoots have. High pixel counts are just marketing foolishness to make you think the cameras are better than they really are. Much more important is the size and quality of the sensor, not how many pixels they managed to cram onto the thing.
Reduce the image size before the camera takes the picture in the first place, and then you don't have to mess with ridiculously large photos on your computer. Of course, if you have a professional level camera that CAN make use of high pixel counts, the above advice doesn't apply.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.