MandrivaThis Forum is for the discussion of Mandriva (Mandrake) 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.
Hi I need to unzip a .gz file for the driver for my modem, but lack some details. I know the command is 'gz xxx filename', but what are the letters i need to put after the gz please.
The .tar.gz is the file extension. The v isn't strictly necessary, it just gives a verbose output. Handy if you want to see what's happening as the file untars.
But brookes didn't say anything about tar. And it's not the distro that doesn't require the dash, but the GNU tar command, itself, on any distro. Where'd he go anyway? Did he ever get the damn thing extracted?
Tchah, takes the best minutes of our lives, sets us to mildly disagreeing and then disappears without a 'by your leave'. The youth of today, in my day blah blah blah
Hi,
OK heres a brief run down on the output:
you should not include /usr/include{linux,asm}/header files directly for the compilation of kernel.
glibc now uses kernel header files from a working kernel. These files are glibc internal and may not match currently running kernel. They should only be included via other system header files.When compiling make sure to use the compiler option to use the correct include files.-I/lib/modules/'uname-r'/build/include instead of /usr/include/linux.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.