hummm.. and why not building up TPG's tool
to an OMLx-Tool for technicals ? This was it what i had meant..
and this as an OMLx Technicals, own Created Bug hunting and
collectingtool + dmesg as helping hand,
for have all informations who be possible, if the User allow it .
and, if something not work, maybe in the prompt, as Ascii-surface who have
the user/bughunter/Administrator ans so on, an possible for calling
tc.bugreport and
they collecting all informations about the systems and for 100% also the
etc and /var/log
and all what need also and the user have an Acii-surface who it is
possible with the cursur-keys
navigating and an possible to typing an report, what's happens , and if
he finisch can he navigate
per tab/cursorkeys on "send" button and the whole "crap" *g* it is
sending as mail+attachment to
an [email protected] Mailinglist . who have the
QA the possibility for
building up an hardware-db and catching all bug's who have sended users,
who easy using the system,
but know, it is an possible in this distribution over tc.bughunter
without logging in, for create an bugreport
with the Systemogs and other whi be interresting and give all the
possible for helping with to catching all possible bugs ..
And get all the possible in the hand, for helping without active be an
Bughunter or an member or what ever ..
but they can fast as possible get an full report with .. if TPG's script
createt as program, who be maybe tc.bughunter
can you are have mutch more feedback, as only 3-6 peoples who try they
are best to find bugs, therewith be
mutch more in the possible to create fast an bugreport, if maybe
something not really works, and only this
peoples knows about this tool, who be more experience, so schold it
possible, to be not many kiddys and
not many inexperienced user,but more user who know that it is possible
to help with and
using these / TPG' tool wo maybe made more as program "robot" for
collecting all informations
about the system and get the user an possible for typing an human
report, what he has
does.. and what it is crashed .. an tc.bughunting - Tool/programm give
all/anyone the
possible for creating fast and easy an Bugreport for QA ..
so, good night :) (damn, i am thired.. ;) )
best regards
Blacky
Am 22.03.2014 08:36, schrieb Alexander Khryukin:
You forgot dmesg
22 ????? 2014 ?. 9:44 ???????????? "Blackcrack"
<[email protected] <mailto:[email protected]>> ???????:
Hi,
very niiice idea, should installed as default Application !
maybe later with graphical thing if anyone/anything crash, start
this script and ask the user
wi they want sending it in to the Cookers (edit it automatic on an
text field and let show
the users what be sending , under all, an button with
"cancel/send/save as txt /"
and over it an clean Textfield for writing the bugreport in Users
word's
(humanwriteable.. 2 textfiels, one with the collecting
informations, one for human writeable).
Maybe in the bash the possible with the command "tc.bugreport" or/
and "tc.hardwareinfo"
or something for have a possible to buildup an hardware-database
from all !
If exist an Gui/grafical tc.bugreport, want be possible for the
testers for easy testing on
an Hardware and can start the tc.bugreport and writing in what's
they are done ,
if the system work well and what's have be seen ..
therewith mus be of course, a functioning sendmail-system on it
and an well working network configuration, what it is now :)
so, only need an working sendmail-system and an gui for you script.
for have the possible behind the installation, on first login as
user XXXXX
make F2 and typing in "tc.bugreport"
you see ? and there can include all what's was on the installation
+ you logs and
things who you need or you are need as programmers,
maybe create an new mailinglist "om-bugreports"
showable by all poples ... to know, what's was see and reportet
and which engines running :)
this can collecting by db as harware-database and many other things ..
you scripts be an very nice start ! whant be crewl, if you makeing
it as programm
with graphical interface for all testers and users ! as
"tc.bugreport"
my 2cents :)
best regards
Blacky
Am 21.03.2014 22:55, schrieb Tomasz Pawe? Gajc:
I've created a simple shell script that will help in a bug fixing. It is
called omv-bug-report.
To install it please run:
urpmi omv-bug-report
This will install in /usr/bin/omv-bug-report.sh a simple shell script that
gathers informationf form:
1. various config files in /etc/*
2. various /proc entries
3. grub configuration
4. lspcidrake output
5. lsusb output
6. dmidecode output
7. systemd --failed
8. journalctl -b
9. rpm -qa
10. gcc version
and pack it into omv-bug-report.log.xz. This file should be attached to any
bugreport, just to speed up things and do not wait for a response of
bugreporter to provide more detailed information.
I've spec a few minutes on this and adapted nvidia-bug-report.sh to OMV
specific environment. Feel free to adjust it more.
