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.
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 all,
Due to being on my summer holidays and being bored out of my brain i have decided to install gentoo due to the recommendations of its portage/packaging system ('emerge'), to find it is a splendid OS. Anyway, because it doesn't seem to work with the binaries that Alcatel provide i am trying to compile the mgmt.o module for the Alcatel SpeedTouch USB ADSL modem, however i am getting errors. But...i can't see the errors because they just whizz by me on the screen, i have installed all of the software it needed, like sarlib etc. What i would like tto do is find a way to be able to read all of the output including errors that is given when i call 'make'.
you could do either of the above suggestions [although I would suggest less rather than more - it enables you to scroll back]:
so
make | less
or
make > dummy-file
it depends whether you want to view the errors once or save them to refer to them. If you want to just see them once, then do the first, it just shows the output screen by screen. If, on the other hand, you want to refer to the errors later, redirect the ouput to a text file.
You do not have to create the file prior to "command > file.log" although i believe that "command >> file.log" actually appends to an already created file or creats one itself.
Anyone that wants an easy way round that works brilliantly for installing the speedtouch USB modem on thier system download the speedbundle from: http://sourceforge.net/project/showf...?group_id=3581 . It includes all the config files and binaies etc that you need.
P.S. i think when using commands like 'make' you need to include the 2 before > like so: "command 2> file.log" otherwise it just outputs the commands it used to the file.
Thanks mark rawson!! .... so for example when im installing i type ...
$make 2> makeErrors.log
??? and can i do that with any command or only certain types? and also in what runlevels? all.. thatd be cool , like....
$ init 6 2> reboot-MumboJumbo.log
To my knowledge this can be done with all commands but some may give different unexpected outputs than other. Regarding which runlevels i assume that you will be able to log part of runlevel 6 but not all due to the fact that it terminates all processes.
yeah goodpoint mark.. but umm... where does it save the log if you cd ../ up all the way to root directory ?? just wondering .. would it have.. no write permissions?..
the "command 2> file.log" has the same permissions as the user that executed it. So if you had not access to anything except your home directory then you would not be able to log anywhere but your home directory. You can obviously change the path that the file goes e.g. "command 2>/root/randomdir/debug.log
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.