Active Topics
vi_ |
2011-11-21
, 13:23
|
|
Posts: 1,680 |
Thanked: 3,685 times |
Joined on Jan 2011
|
#141
|
Originally Posted by don_falcone
Aaah, so other persons have experienced this too? Well that is a start.
__________________
N900: One of God's own prototypes. A high-powered mutant of some kind never even considered for mass production. Too weird to live, and too rare to die.
| The Following User Says Thank You to vi_ For This Useful Post: | ||
|
|
2011-11-21
, 14:11
|
|
Posts: 1,808 |
Thanked: 4,272 times |
Joined on Feb 2011
@ Germany
|
#142
|
Me too 
It was the only time I tried backupmenu. In view of this and the fact that the backupmenu.item entry for bootmenu is behaving in an "unfriendly" manner, so to speak, I was planning to remove backupmenu (at least for now), and, now that Pali's recovery console is working fine, one could implement backupmenu's functionality (or a subset thereof) in a couple of scripts safely stored under /root (or even /).
After all, it's mostly tar/untar and mount/umount, so it would be "more or less" easy to implement by hand.
Of course still better would be to figure out the problem with Backupmenu and/or Busybox-Power
It was the only time I tried backupmenu. In view of this and the fact that the backupmenu.item entry for bootmenu is behaving in an "unfriendly" manner, so to speak, I was planning to remove backupmenu (at least for now), and, now that Pali's recovery console is working fine, one could implement backupmenu's functionality (or a subset thereof) in a couple of scripts safely stored under /root (or even /).
After all, it's mostly tar/untar and mount/umount, so it would be "more or less" easy to implement by hand.
Of course still better would be to figure out the problem with Backupmenu and/or Busybox-Power
|
|
2011-11-21
, 15:53
|
|
Posts: 1,680 |
Thanked: 3,685 times |
Joined on Jan 2011
|
#143
|
The more I think about it the more i think this implies there is something with BB-P 'getty' applet.
iDont, how is BB-P installed these days? Is the original binary still there? Can I change my 'getty' symlink to point to the old binary to test this?
MOAR!
The more I look, the more I see getty has been changed from v1.15->v1.19.
Looking at the source they both #include the exact same files so potentially getty.c v1.15 could be substituted for getty.c v1.19. While it may work it doesn't explain why there is an issue (assuming it is even getty that is the problem) after all, all the changes to getty.c have been simple bug fixes right? RIGHT??
Last edited by vi_; 2011-11-21 at 16:49.
iDont, how is BB-P installed these days? Is the original binary still there? Can I change my 'getty' symlink to point to the old binary to test this?
MOAR!
The more I look, the more I see getty has been changed from v1.15->v1.19.
Looking at the source they both #include the exact same files so potentially getty.c v1.15 could be substituted for getty.c v1.19. While it may work it doesn't explain why there is an issue (assuming it is even getty that is the problem) after all, all the changes to getty.c have been simple bug fixes right? RIGHT??
__________________
N900: One of God's own prototypes. A high-powered mutant of some kind never even considered for mass production. Too weird to live, and too rare to die.
Last edited by vi_; 2011-11-21 at 16:49.
| The Following 3 Users Say Thank You to vi_ For This Useful Post: | ||
|
|
2011-11-21
, 19:13
|
|
Posts: 268 |
Thanked: 1,053 times |
Joined on May 2010
@ The Netherlands
|
#144
|
Originally Posted by vi_
Thanks for reporting, I've just verified the bug on my device.
I have found a bug in BB-P. In the last version of BackupMenu Robbie was kind enough to add a framebuffer console. This allows you to access the console through BM. One problem...
Without BB-P it works fine.
With BB-P it gets as far as asking for your username then crashes back to the BM main menu when you press return (to enter your username). It gives the error: "applet not found". This is the BB error for when a BB applet has been called but does not exist. Useually the name of the erroneously called applet is given in the error (foobar: applet not found). With BB-P installed there is no name supplied.
I can confirm it is the BB-P package as if I remove it (apt-get uninstall) then try root console again it works, re-install, it fails.
What surprises me is that you're the first one to report this, while the latest BackupMenu has been released in back in July.
Originally Posted by vi_
Yep, the login applet seems to be the culprit. BackupMenu assumes that all utilities are provided by /bin/busybox. This is true for the default busybox setup, but not for busybox-power. Coincidentally, the very same 'issue' as described one page back in this thread is happening, only now with the login applet instead of ping: login is an applet that requires the SUID bit to be set to work for non-root users. Therefore, the login applet has been split to /bin/busybox_root.
The last line in BM when console is selected is:
I assume BB then has to run 'login' or 'logon' or whatever and it is somehow failing. I don't really know my understanding of how a new shell is spawned is a bit...uh...thin.Code:busybox getty 115200 tty1 sh
Originally Posted by vi_
Eager to see this bug fixed no? Assuming the missing login applet indeed is the issue, then the solution is simple, either:
The more I think about it the more i think this implies there is something with BB-P 'getty' applet.
iDont, how is BB-P installed these days? Is the original binary still there? Can I change my 'getty' symlink to point to the old binary to test this?
MOAR!
The more I look, the more I see getty has been changed from v1.15->v1.19.
Looking at the source they both #include the exact same files so potentially getty.c v1.15 could be substituted for getty.c v1.19. While it may work it doesn't explain why there is an issue (assuming it is even getty that is the problem) after all, all the changes to getty.c have been simple bug fixes right? RIGHT??
a) Pull login (and all other "SUID applets") back into busybox from busybox_root, or
b) Change BackupMenu's logic to symlink busybox' utilities in its own root like how they're symlinked in the default filesystem (which happens to be to two different binaries when using busybox-power -> busybox and busybox_root)
I think it's best to go with solution A since this reduces maintenance and makes things less confusing for users. The only downside is that when we set the SUID bit on /bin/busybox, well, a lot of utilities (i.e. cp) effectively have the SUID bit set. However, BusyBox can be configured to automatically drop privileges for applets that do not require the SUID bit to be set. As stated in a previous post: there were some issues with this feature in the past, but it seems to work as expected nowadays.
If anyone has a problem with the above solution, please let me know. Otherwise expect busybox-power 1.19.3power2 to hit the repositories tomorrow's evening.
P.s. RE how busybox-power is installed these days: have a look in /opt/busybox-power I would say. The deb installs its content to that location, after which install-binary.sh takes over to symlink etcetera. Be sure not to mess anything up in that folder though, for obvious reasons
|
|
2011-11-21
, 20:42
|
|
Posts: 1,680 |
Thanked: 3,685 times |
Joined on Jan 2011
|
#145
|
iDont, you are king of the bros.
__________________
N900: One of God's own prototypes. A high-powered mutant of some kind never even considered for mass production. Too weird to live, and too rare to die.
| The Following 5 Users Say Thank You to vi_ For This Useful Post: | ||
 |
|
2011-11-21
, 22:59
|
|
Posts: 5,028 |
Thanked: 8,613 times |
Joined on Mar 2011
|
#146
|
Originally Posted by iDont
To be honest, I've been fighting with this issue for some time, and reported it in backupmenu thread. Unfortunately, got no idea that busybox could cause it - it was just about limits in my knowledge/experience here, I suppose.
What surprises me is that you're the first one to report this, while the latest BackupMenu has been released in back in July.
/Estel
__________________
N900's aluminum backcover / body replacement
-
N900's HDMI-Out
-
Camera cover MOD
-
Measure battery's real capacity on-device
-
TrueCrypt 7.1 | ereswap | bnf
-
Hardware's mods research is costly. To support my work, please consider donating. Thank You!
N900's aluminum backcover / body replacement
-
N900's HDMI-Out
-
Camera cover MOD
-
Measure battery's real capacity on-device
-
TrueCrypt 7.1 | ereswap | bnf
-
Hardware's mods research is costly. To support my work, please consider donating. Thank You!
| The Following 2 Users Say Thank You to Estel For This Useful Post: | ||
|
|
2011-11-22
, 19:52
|
|
Posts: 268 |
Thanked: 1,053 times |
Joined on May 2010
@ The Netherlands
|
#147
|
Originally Posted by Estel
I might have oversimplified things a bit too much, the statement wasn't meant provocative (if you had read it that way). Anyway, thanks for getting back on this.
To be honest, I've been fighting with this issue for some time, and reported it in backupmenu thread. Unfortunately, got no idea that busybox could cause it - it was just about limits in my knowledge/experience here, I suppose.
--
On other news, busybox-power 1.19.3power2 should hit the repositories any minute now. All applets requiring the SUID bit to be set (to work properly as a non-root user) have been merged back into the standard busybox binary. And as expected, BackupMenu's shell option works again
.The package will be promoted to extras-testing soon.
Last edited by iDont; 2011-11-22 at 19:55.
| The Following 9 Users Say Thank You to iDont For This Useful Post: | ||
|
|
2011-11-23
, 16:14
|
|
Posts: 16 |
Thanked: 11 times |
Joined on Oct 2011
|
#149
|
hi))
In "ls" output russian characters shows as ????, how to fix it?
On default BusyBox all good
In "ls" output russian characters shows as ????, how to fix it?
On default BusyBox all good
| The Following 3 Users Say Thank You to SeT For This Useful Post: | ||
|
|
2011-11-23
, 17:39
|
|
Posts: 2,225 |
Thanked: 3,822 times |
Joined on Jun 2010
@ Florida
|
#150
|
Originally Posted by SeT
Confirmed with the following test:
hi))
In "ls" output russian characters shows as ????, how to fix it?
On default BusyBox all good
Code:
cd ~/MyDocs touch файл ls [file name came out as ????????] /opt/busybox-power/busybox.original ls ./ [file name came out as файл]