public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Sascha Kilian <sascha@sakisoft.de>
To: development@lists.ipfire.org
Subject: Re: fireinfo Bug for Kernel Informations and Root Disk Size
Date: Mon, 24 Feb 2014 17:08:39 +0100	[thread overview]
Message-ID: <1393258119.24982.13.camel@localhost> (raw)
In-Reply-To: <1393256502.24982.9.camel@localhost>

[-- Attachment #1: Type: text/plain, Size: 3038 bytes --]

okay, i have checked the real sended profile, there is ok, but for what
are the fireinfo/system.py, if the system this dont use? 


sendprofile -d (param found in Source Code) shows me the right values,
the root size too, but shows only 1 drive. My System has 2x 500GB first
drive is sdb (root) and second drive is mounted on /var/data (Various
files).

is it not better to use "df" to find out how many space the system
has ? 

Sascha


Am Montag, den 24.02.2014, 16:41 +0100 schrieb Sascha Kilian:
> oke i updated my local files, 
> 
> i now have 2.1.9, first look in the system.py seems not that the problem
> is changed. I can build this update and check the result file(s).
> 
> Best regards
> 
> Sascha
> 
> Am Montag, den 24.02.2014, 16:29 +0100 schrieb Arne Fitzenreiter:
> > current fireinfo version is 2.1.9
> > 
> > 
> > checkout the next branch of the ipfire source (master is the "released" 
> > branch):
> > 
> > git checkout next
> > 
> > I know about the discsize bug. The kernel is new for me but my beta2 
> > systems are showed correctly on the
> > fireinfo website.
> > 
> > Arne
> > 
> > On 2014-02-24 16:17, Sascha Kilian wrote:
> > > I checked it on Git-repository,
> > > 
> > > i updated my repository and have runned make.sh downloadsrc.
> > > It told me i have Fireinfo Version 2.1.7
> > > 
> > > in the Archive file fireinfo/system.py on line 445
> > > "print s.kernel"
> > > 
> > > on line 106 is defined s.kernel_release
> > > 
> > > 
> > > Am Montag, den 24.02.2014, 13:33 +0100 schrieb Sascha Kilian:
> > >> Hi there,
> > >> 
> > >> it is my first post on this list. If i make some misstakes, please 
> > >> tell
> > >> me.
> > >> 
> > >> If trying to figure out why the Diskspace is not shown in my Profile.
> > >> i figured out that some bugs in fireinfo "system.py" exist.
> > >> 
> > >> in line 450 "print s.kernel" -> "s.kernel_release"
> > >> 
> > >> The root_size is null, i have patched some in the system.py and make 
> > >> the
> > >> path in line 388 Static to "/sys/block/sda/size" then he got the right
> > >> size. I think it needs to be other identification, sda is the MBR not
> > >> the right partition (sda3). My Python expirience is too low to make 
> > >> this
> > >> right.
> > >> 
> > >> Best regards from Germany
> > >> 
> > >> Sascha Kilian
> > >> 
> > >> 
> > >> _______________________________________________
> > >> Development mailing list
> > >> Development(a)lists.ipfire.org
> > >> http://lists.ipfire.org/mailman/listinfo/development
> > > 
> > > 
> > > _______________________________________________
> > > Development mailing list
> > > Development(a)lists.ipfire.org
> > > http://lists.ipfire.org/mailman/listinfo/development
> > _______________________________________________
> > Development mailing list
> > Development(a)lists.ipfire.org
> > http://lists.ipfire.org/mailman/listinfo/development
> 
> 
> _______________________________________________
> Development mailing list
> Development(a)lists.ipfire.org
> http://lists.ipfire.org/mailman/listinfo/development



      reply	other threads:[~2014-02-24 16:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-24 12:33 Sascha Kilian
2014-02-24 14:13 ` Arne Fitzenreiter
2014-02-24 15:17 ` Sascha Kilian
2014-02-24 15:29   ` Arne Fitzenreiter
2014-02-24 15:41     ` Sascha Kilian
2014-02-24 16:08       ` Sascha Kilian [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1393258119.24982.13.camel@localhost \
    --to=sascha@sakisoft.de \
    --cc=development@lists.ipfire.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox