Mountie Light und Mountie für Enigma2

  • Na ja, nachdem Ihr Schlange steht um zu testen habe ich Euch halt das Mountie Light am Anfang des Threads gepostet.


    BITTE probiert aus ob damit gelabelte devices (etx3 kann man damit labeln, FAT muss man am PC machen und NTFS labels kann ich momentan nooch nicht lesen - muss erst suchen wo dort der label steht und wie er codiert ist) wie beim normalen Mountie gelesen und gemountet werden können.


    Weil das binary ist winzig, und eigentlich auch nur so gross weil ich noch das tune2fs zum labeln reingepackt habe


    Es ginge auch mit python den label schreiben nachdem ich durch mühsames forschen rausgefunden habe wo diese stehen, aber ich bin faul und jetzt schaun wir erstmal ob das label lesen wirklich so einfach geht.


    Bitte aber nicht im Gemini 4.2 mit deren udev probieren, dafür gibt ers weiterhin erstmals nur das Mountie4GP2 - wenn es in anderen Images geht kann ich dafür auch gerne ein Mountie4GP2 Light machen.


    LG
    gutemine

    Edited 6 times, last by gutemine ().

  • OK, nachdem die 1.0 in CVS Images zu funktioneren scheint (hat sich keiner beschwert) ist auf der ersten Seite des threads jetzt eine 1.1 vom Mountie Light die auch im GP 4.2 funktionieren sollte damit mehr Leute testen kann ob das Labeln von ext3 und lesen des labels von ext3 udn FAT USB devices auch funktioniert mit der Light Variante


    Viel Spass beim Testen !


    PS: Ich bastle in der Zwischenzeit am NTFS Label support weiter, das problem ist nur das dort der label in unicode LE encodiert zu sein scheint wenn ich den ntfslabel.c code richtig verstehe und ich mit python string encoding/deconding auf Kriegsfuss stehe - aber man gönnt sich ja sonst nichts.


    LG
    gutemine

    Edited 3 times, last by gutemine ().

  • OK, ich komme im Moment mit dem NTFS nicht weiter, also probieren wir mal das label schreiben mit python aus, weil das lesen des labels scheint ja erstaunlicherweise zu funktionieren - nachdem keiner sich bis jetzt beklagt hat über Mountie Light !


    Die Version 1.2 von Mountie Light am Anfang des Threads is jetzt noch kleiner, weil auch das tune2fs binary rausgeflogen ist und alles NUR mit python gemacht wird, dafür sollte der kit jetzt sogar aber wieder ext3, FAT16 und FAT32 auf der Dreambox labeln können !


    Bitte testet das label schreiben nur mit USB sticks und USB disken aus wo nichts wichtiges drauf ist, weil solange es nicht ausgiebig getestet ist wissen wir NICHT ob Mountie beim labeln nicht das filesystem kaputt machen kann - schließlich schreibe ich da in den Partitionsheader ohne zu wissen was ich eigentlich tue (aber keine Angst es geht nur um die usb devices, eure IDE/SATA Harddisk ist sicher).


    Aber wenn nicht mutige Leute es ausprobieren werden wir es nie erfahren ob es funktioniert.


    Und mehr als das man den USB stick neu formatieren muss kann eigentlich auch wieder nicht passieren.


    Also BITTE testet das ausgiebig und berichtet - bin schon gespannt !


    Mir und Mountie liegt viel daran das zum Laufen zu kriegen und dafür brauche ich eben Eure Hilfe !


    PS: Und der kit ist jetzt nur mehr reiner python code und kann daher auch in enigma2 images auf den PowerPC boxen getestet und benutzt werden !


    LG
    gutemine

    Edited 8 times, last by gutemine ().

  • salü!


    version 1.2 läuft bis jetz tadeolls mit gp4.1 auf meiner 800er. fat32 wie ext3 label werden erkannt und richtig gemountet (und glücklicherweise bleib das filesystem intakt^^).


    eine frage: könntest du die automatische erkennung/aktivierung des swaps einbauen?


    mfg, el_sasasa

  • Hmm


    Where as Mountie worked perfectly for me Mountie Light doesn't work well for me at all.


    Wether labeled or not cf and usb just don't mount, I just see a on screen message saying


    mounted device /dev/scsi/host3/bus0/target0/lun0/part1 at /media/no name with label no name and this is a continuous loop


    As it happens an SD card mounts ok


    8k with oozoon.


  • Na ja das label lesen macht mir auch weniger Sorgen, das schreiben des labels mit dem python code ist das was recht mutig ist und wo Ihr erst rausfinden müsst ob es funktioniert.


    Und ja das kann ich Euch einbauen das wenn nach dem mounten ein swapfile drauf gefunden wird er dieses auch gleich benutzt.


    LG
    gutemine


  • What filesystem do you have on this CF card/USB stick and have you tried formatting them with FAT and a device label on PC (the securest way until we know if it works in the Plugin) ?


    Label Reading is amazingly easy if you know how and where to look for them (look at the read_label.py code).


    Could you please use the attached standalone read_label.py to read your label in telnet and post me the output of the device which is making troubles (labeled and unlabeled):


    Usage is easy:


    FTP it to /tmp on you Dreambox. then type

    chmod 755 /tmp/read_label.py


    and then type:


    cd /tmp
    ./read_label.py /dev/...../part1


    Instead of /dev/..../part1 use your problematic devicepath (you can find it out with find /dev/scsi | grep part1)


    Then post me the output.


    Ciao
    gutemine

  • Think we only need to deal with 1 device as they both induce the same error


    Both devices were correctly recognised and mounted with Mountie


    this a CF labled as cf


    root@dm8000:/tmp# read_label.py /dev/scsi/host0/bus0/target0/lun1/part1
    FAT32 Header: NO NAME

  • OK, this means where it normally thinks the label should be it finds only the string NO NAME - strange, but my code is VERY dirty.


    Could you do it once more with the attached write_label.py which outputs the full starting string at teh header of the partition - maybe the label cf is somewhere else - and be aware cf in small capital is NOT a valid FAT name, only capital letters are allowed, which could cause the confusion.


    Mountie Light tries to convert your inputs in case of FAT, but maybe this is not working yet.


    Try labeling with CF instead of cf - should be still mounted at /media/cf :)


    It could be das if a non-DOS compliant label ist used it is stored somewhere else and the NO NMAME is used instead at the FAT location.


    For the moment I will simply put code into it that it will remove the blank, then it is a valid directory and this should prevent the recursive loop mounting till it crashes that you experienced - something I should have thought about before - that people could place blanks in their labels


    Ciao
    gutemine

  • OK, please try out the Version 1.3 of Mountie Light if at least the endless re-mounts stop when using it !


    And then please post the output of the second read_label.py so that we find out where the cf label is hidden on your device.


    Ciao
    gutemine

  • LOL


    wtf


    root@dm8000:/tmp# read_label.py /dev/scsi/host0/bus0/target0/lun1/part1
    ¸NO NAME FAT32 3ÉѼô{ÁÙ½|NV@´A»ªUÍrûUªu
    öÁtþFë-V@Ís¹ÿñf¶Æ@f¶Ñâ?÷âÍÀíAf·Éf÷áfFø~u8~*w2fFfÀ
    »¹è+é, ú}´}ð¬
    Àt< ´»Íëî û}ëå ù}ëàÍÍf`~
    fjfPSfh´BV@ôÍfXfXfXfXë3f;Førùë*f3Òf·Nf÷ñþ ÂÊfÐfÁê÷vÖV@èÀä
    ̸ÍfauÃf@IuÃBOOTMGR
    Remove disks or other media.
    Disk error
    Press any key to restart
    ¬ËØUªRRaArrAaÚUª
    FAT32 Header: NO NAME


    The CF is now mounted as /media/noname without a space [no name]

  • If you put the CF (or better the stick if you don't have a reader) on the PC and format it there with label CF - same problem when punt into the dreambox ?


    How big is your device (I tested with a 256MB stick and a 8GB one to cover most possible size ranges), but you never know.


    PS: yes, I simply removed the blank to make it mountable at this strange non-label.


    PPS: The partition header is not really an ascii string, but I read it in my code as text string - and because FAT/ext3 uses ansi encoding the bytes which are really text (= the label) and some other infos like bootmanager and Fielsystem text descriptor are readable text - then you just find out if the location of these strings is fixed - and voiala - you got the basics of the Mountie Light code to get rid of all text labeling binaries doing more or less the same but in compiled C code !


    BUT it took me quite some time to figure out this dirty trick to get the label for FAT16/32 and ext2/ext3 - and believe me coding it so that you can write the labels was also fun :)


    If you see the result you might say 'easy' but it was really sweat & tears & fun to make it work - even when it is not perfect yet.


    But it is a good example how I like to solve a problem :)


    Ciao
    gutemine

    Edited 8 times, last by gutemine ().

  • It's exactly the same 256MB Compact Flash that mounts ok with Mountie which was formated by the pc and labeled CF, nothing has changed !


    root@dm8000:/tmp# tune2fs /dev/scsi/host0/bus0/target0/lun1/part1
    tune2fs 1.40-WIP (14-Nov-2006)
    Usage: tune2fs [-c max_mounts_count] [-e errors_behavior] [-g group]
    [-i interval[d|m|w]] [-j] [-J journal_options]
    [-l] [-s sparse_flag] [-m reserved_blocks_percent]
    [-o [^]mount_options[,...]] [-r reserved_blocks_count]
    [-u user] [-C mount_count] [-L volume_label] [-M last_mounted_dir]
    [-O [^]feature[,...]] [-T last_check_time] [-U UUID] device


    Somethings amiss here I think, btw I just extracted the tune2fs from the ipk and ran it from tmp, that ok ?

  • sorry. I forgot that tune2fs is for labeling only not for showing the label - getting old :)


    Then better simply install the full mount binary from here and let's see after a reboot what mount -l shows as device label for the /media/nolabel mountpoint.


    mounten in der fstab via device label


    PS: Which formats were you using when formatting on the PC (FAT or FAT32, extended FAT,..) - currently only FAT16 and FAT32 are supprted as you see from the code ?


    Ciao
    gutemine

    Edited 4 times, last by gutemine ().

  • Cool, but remaining question is what Filesystem was it before, because it had a FAT32 label - maybe extended ?


    Is this a very old/small stick which became FAT12 or something else by choosing FAT ?


    Anyway, thanks for testing - now if you are still motivated you can try labeling it with the Plugin and check if the PC still likes and mounts it with the new label :)


    PS: you can enter the label string with small letters in the plugin, Mountie will convert them to capital ones to prevent incompatibilities with the labels FAT allows on the PC - and for mounting the label is lowered by Mountie in case of FAT.


    Ciao
    gutemine

    Edited 6 times, last by gutemine ().

  • No problem but I think you don't understand


    This CF was formatted fat32 and has NOT been re-formatted since, it still contains my picons and don't forget same problem exist with a stick I have.


    So was working perfect since first install of Mountie, then uninstalled Mountie, then installed Mountie Light, not formatted, you know the problem, removed Mountie light, installed Mountie for the second time, NOT re-formatted works perfect.


    So the question we must ask is if it works perfectly with Mountie then why not with Light ?


    :)

  • Mountie uses well known and tested binaries for doing the device labeling - but it needs 3 different ones (one for FAT, one for ext3 and one for NTFS) and also lots of libs to make them work. Which makes the classic Mountie kit pretty bigh and not easy for example to be installed in Flash.


    Making this approach standard in all images would be impossible due to this patchwork and sheer size of kit - but the main goal of Mountie was not ro provide good code (too many os.system and os.popen in the code to be proud off), the Goal was only to show how I would like to have my Mounting done !


    Mountie Light has a different goal - it should proove that it is possible to get rid of all these extra labeling binaries and do all the work with only a little python code - no need for complex things like automount, udev, /dev/discs links, etc.


    And it was a personall challenge for me if I would be able to achieve this goal without any real knowledge about device partitions, filesystem headers, etc....


    BUT such an approach is a little bit heretic, and during my research I have not found something comperable, especially simple and completely in python - so I created one myself - the original read_label.py I posted for standalone testing which then simply was planted into the standard Mountie code als labeling binaries replacement


    This simplicity has off course the tradeoff that I DO NOT KNOW if the filesystemlabels of the supprted filesystems (FAT/FAT32 and ext2/3) are really that simple


    BUT if enough people like you give it a try and find out the cases which do not (yet) work we maybe could even make this approach fully working and usable for our dreamboxes.


    My vision is pretty simple - add the code to label a device during initialization already to enigma2 and make Mountie a simple configurable enigma2 option (mount labeled devices with label) and you have a solution which could be checked into CVS and become standard in all images with less then 1 page of code total.


    Maybe this is just a Dream - BUT I like to create visions and at the same time to proove that they are achievable - which is the reason why I started the whole project.


    Actually I don't like creating plugins at all, I like to proove and/or invent things - if somebody needs to code it to achive this goal - I simply don't wait until this guy shows up :)


    PS: and to answer your question - I don't know why he disliked the label you had before and after re-labeling accepted it - but we can investigate and research and have fun by doing so - and I like to share my fun with others.


    Ciao
    gutemine

    Edited 3 times, last by gutemine ().

  • Hi !


    Habe noch schnell einen Mountie Light Kit 1.5 gepostet wo wenn auf dem von Mountie gemounteten device ein swapfile (genau mit diesem Namen) gefunden wird dies auch automatisch beswapped wird. Und eine CD/DVD wird in der 8000 jetzt hoffentlich auch automatisch auf /media/cd gemountet.


    PS: Wenn sonst alles mit den USB devices funktioniert wäre nur mehr die Frage ob man Mountie Light auch auf die IDE/SATA devices wie Harddisk und CF Karte in der 7025 loslassen sollte - weil hotplugable sind die eh nicht, aber dann wäre Mountie Light auch ein vollständiger udev/autofs Ersatz und man müsste diese devices nicht mehr in die fstab tun.


    PS: Und die os.system calls gehören dann auch raus für das absetzen der mount/umount Befehle.


    Viel Spass beim Testen !


    LG
    gutemine

    Edited 2 times, last by gutemine ().

  • GuteMine


    Thanks for the explanation. I for one very much appreciate your contribution to the Dreambox community.


    I use several of your plugins which enhances greatly my Dreambox experience, long may you continue with your visions and enthusiasm.


    I for one am truly greatfull to you and your peers.


    best regards