#103771 - Darkflame - Sun Sep 24, 2006 2:48 pm
| OOPMan wrote: |
| Mr. Picklesworth wrote: | Of course, the other solution which works beautifully and actually does multi task is DSLinux, which now beats Opera DS hands down with the following:
Listening to music using madplay while browsing the web via Links and using nxview (in Nano-X) in order to view various images.
All at the same time.
It works beautifully, and I still have over 25 MB of RAM to spare! :) |
Hehehe, yeah, I'll bet DSLinux does beat Opera DS hands down when it comes to playing music and using nxview while browsing :-)
As for those people who complained that (DS)Linux is too hard to use...learn. Really, Linux is not actually that hard. If you can compile DS homebrew then you can sure as hell learn how to use Linux ;-) |
Its not a question of "learning" is a question of convience.
Its not as quick to run a linux app because you are still stuck typeing stuff in.
Or has that changed this last time I looked?
My main problem with it is only its a keyboard based interface for a machine without a keyboard.
I have no problem with linux as such, in fact, the machine next to me has been nicely set up with few flavours, includeing the very flashy and supprisingly good XGL interface.
_________________
Darkflames Reviews --
Make your own at;
Rateoholic:Reviews for anything, by anyone.
#103808 - tepples - Sun Sep 24, 2006 7:32 pm
| OOPMan wrote: |
| As for those people who complained that (DS)Linux is too hard to use...learn. Really, Linux is not actually that hard. If you can compile DS homebrew then you can sure as hell learn how to use Linux ;-) |
I have found a few big hassles that have discouraged me from keeping DSLinux on my memory card longer than necessary: - No physical keyboard for entering commands. My PC, on which I compile homebrew, has a keyboard.
- The requirement of entering a name/pass on an on-screen keyboard every time I start DSLinux. When I want to develop homebrew, I can enter the password much more quickly on my PC's physical keyboard.
- The requirement of closing all apps and shutting down the OS before the adapter becomes dislodged or the battery runs down. Computers, on the other hand, have internal drives (which don't stick out) and an easy "Shut down" option on the main system menu.
- The difficulty of learning how to use or even close some full-screen apps such as retawq. A source code editor on a desktop computer, on the other hand, has a nice friendly close button in the upper-right (on Windows) or upper left (on Mac) corner.
_________________
-- Where is he?
-- Who?
-- You know, the human.
-- I think he moved to Tilwick.
#103821 - OOPMan - Sun Sep 24, 2006 8:19 pm
The keyboard is a pain and will always be, I suspect, as Linux is really a command-line OS, no matter what those X.org monkeys try and tell you ;-)
The login can be circumvented, there is a thread on the DSLinux forums detailing how...
The closing all apps and shutting down OS thing is mainly a part of Linux itself. It's always been good Linux usage policy to issue a system halt command before powering off so as to ensure that all I/O buffers are emptied and all file-systems are cleanly dismounted. Which doesn't mean that just switching off will corrupt stuff all the time, but it does increase the odds.
Also, you don't need to close all the apps. The poweroff command will do this for you, as it issues a kill signal to all running processes.
The difficulty curve is just part of command line linux usage. Admittedly, having to use an on-screen keyboard doesn't help, but in other respects it's mostly the same thing...
All things said, I don't actually use DSLinux much myself, although I do keep track of its developments...
_________________
"My boot, your face..." - Attributed to OOPMan, Emperor of Eroticon VI
You can find my NDS homebrew projects here...
#103835 - tepples - Sun Sep 24, 2006 9:54 pm
| OOPMan wrote: |
| The login can be circumvented, there is a thread on the DSLinux forums detailing how... |
Why isn't this done by default?
| Quote: |
| The closing all apps and shutting down OS thing is mainly a part of Linux itself. It's always been good Linux usage policy to issue a system halt command before powering off so as to ensure that all I/O buffers are emptied and all file-systems are cleanly dismounted. |
Isn't there a SysRq that syncs the file system in this manner? And is there a reason why it can't display a red light next to the keyboard when file system buffers are waiting to be emptied, similar to the red light on the disk drives of 8-bit micros, and then have it sync automatically after a half second?
| Quote: |
| Also, you don't need to close all the apps. The poweroff command will do this for you, as it issues a kill signal to all running processes. |
How can I run the poweroff command if I'm inside an app that is taking all my keystrokes? If there were a little picture of a power switch on the keyboard that I could slide downward with the stylus, it wouldn't be so hard.
| Quote: |
| The difficulty curve is just part of command line linux usage. Admittedly, having to use an on-screen keyboard doesn't help, but in other respects it's mostly the same thing... |
MS-DOS on a PC, with programs that follow the keyboard shortcuts used by Microsoft apps such as QBasic, appears friendlier than Linux on a DS.
| Quote: |
| All things said, I don't actually use DSLinux much myself, although I do keep track of its developments... |
And I think this digression deserves to be split.
_________________
-- Where is he?
-- Who?
-- You know, the human.
-- I think he moved to Tilwick.
#103844 - Mr. Picklesworth - Sun Sep 24, 2006 11:07 pm
| Quote: |
| And is there a reason why it can't display a red light next to the keyboard when file system buffers are waiting to be emptied, similar to the red light on the disk drives of 8-bit micros, and then have it sync automatically after a half second? |
There is absolutely no reason not to do that.
With the extra RAM builds (or another build with many virtual terminals), typing poweroff in another the terminal while running userspace applications is quite useful, but even with the regular builds when you're viewing the terminal and typing poweroff there are a few applications running. (The terminal and poweroff, for example).
Annoyingly, you must type your username / password for each virtual terminal, but it's well worth it in the end.
Most applications can be closed with Ctrl-C. (In fact, is that actually the OS's own doing or is it still the application's choice?)
The little X on the corner is a recent addition to modern operating systems. In the olden days before windowed GUIs were used, people suffered the same thing.
It's surprising, I know, that I am not still struggling to close Keen 4 to this day...
For the most part I agree that it is a bit of a difficult thing to figure out, but it is an operating system so it takes a while.
You'll be happy to know that I have successfully run Links within a terminal in NanoX, which I then closed by clicking an X in the corner :)
(It didn't seem to like me pressing b, though).
_________________
Thanks!
MKDS Friend Code: 511165-679586
MP:H Friend Code: 2105 2377 6896
#103847 - TJ - Sun Sep 24, 2006 11:28 pm
| Quote: |
Why isn't this done by default?
...
Isn't there a SysRq that syncs the file system in this manner? And is there a reason why it can't display a red light next to the keyboard when file system buffers are waiting to be emptied, similar to the red light on the disk drives of 8-bit micros, and then have it sync automatically after a half second?
|
The problems you have are not faults in DSLinux, that is the way Linux works.
Having the system automatically log in as a user is very insecure, automatically logging in as root is just idiotic. No Linux distribution would ever dare do that by default (or else get laughed out of existence; I.E. Lindows), game console or not.
As for powering off, Linux simply can'y do this safely as a matter of design. Even if you put the system into synchronous write mode rather than Unix's normal asynchronous manner, you still couldn't turn the machine off any time you wanted. There are many files that need to be updated and closed out when the system goes down, or else there will be considerable confusion when it boots back up. This can be minimized by the system by putting those sorts of files back to sane defaults in the boot scripts, but this only complicates system initialization.
I think the "problem" here is that DSLinux is aiming to be a standard Linux system that just happens to be running on the DS, and not a system that is built to cater to people who just want to pop it open and run a telnet client.
Those people would be better of staying in the homebrew arena, since DSLinux is never going to become that. Adding a GUI isn't even a priority for the core development, that is being left up to the community if they want to do it.
#103873 - tepples - Mon Sep 25, 2006 2:56 am
| TJ wrote: |
| Having the system automatically log in as a user is very insecure |
If you are holding the DS, you are already root, as you can just yank the CF card and stick it in any random PC.
_________________
-- Where is he?
-- Who?
-- You know, the human.
-- I think he moved to Tilwick.
#103874 - Mr. Picklesworth - Mon Sep 25, 2006 3:03 am
This is true :p
I agree, there are some places like that where DSLinux tries a bit too hard to be like a desktop OS.
_________________
Thanks!
MKDS Friend Code: 511165-679586
MP:H Friend Code: 2105 2377 6896
#103877 - Darkflame - Mon Sep 25, 2006 3:44 am
| Quote: |
There are many files that need to be updated and closed out when the system goes down, or else there will be considerable confusion when it boots back up.
|
woaaaaa...there...wait...
You saying Linux is moveing/changeing files about on the CF as a mater of fact each time it boots up and closes down? O_o
Didnt people almost universaly agree swap files were a bad idea due to limited writes? This dosnt sound far off that at all.
For a bit of hardware like the DS, a shutdown should be as simple as making sure nothing is currently being written too. The DS hardware dosnt care if the power is cut. Its harmless whatever state it is in.
(ok, short of a firmware rewrite)
| Quote: |
and not a system that is built to cater to people who just want to pop it open and run a telnet client.
|
Something that is actualy practical to use in any form would be nice though.
DSLinux seems to being made purely as a nice tech-demostration, or as a challenge.
All Id like too see is it become practical for actual use regularly,or portably.
As others have pointed it, it does multitasking...something no other area of homebrew is doing. The potential to have something actualy incredibly cool and usefull is there.
Somehow though, its viewed as being "not a priority" too have a system that takes less then 5 minutes each time you want too run something.
| Quote: |
| Having the system automatically log in as a user is very insecure, automatically logging in as root is just idiotic. No Linux distribution would ever dare do that by default (or else get laughed out of existence; I.E. Lindows), game console or not. |
This sums up the problem indeed.
Very stuck mindset of what Linux "should" be, rather then what it would actualy be usefull as.
No one is going to use a portable system they are going to log into any time.
People are not using DSLinux because not its hard, or because they have to learn, they arnt using it because it simply isnt practical.
Of course, if DSLinux was only ever concieved too be a nice tech demo,then fair enough.
(because as we all know the saying "you can even port Linux to a dead hamster" :p)
_________________
Darkflames Reviews --
Make your own at;
Rateoholic:Reviews for anything, by anyone.
#103883 - TJ - Mon Sep 25, 2006 4:09 am
| Quote: |
If you are holding the DS, you are already root, as you can just yank the CF card and stick it in any random PC.
|
The same could be said for a desktop PC. If it is in your home, you are the "administrator"; and yet, no desktop distribution runs the user as root by default. Insecurity like that is a feature of Microsoft products.
It would be trivial to write a script or application that would wipe the contents of a person's media device if they were to run it as root. As DSLinux and DS homebrew in general increases in popularity, it only becomes more likely someone will attempt it. Do we forget the DS bricker so quickly?
| Quote: |
You saying Linux is moveing/changeing files about on the CF as a mater of fact each time it boots up and closes down? O_o
Didnt people almost universaly agree swap files were a bad idea due to limited writes? This dosnt sound far off that at all. |
At this point in time, many (most, even) of the files are located in the initrd that is in the system's RAM, but as the system advances and support gets better with media I/O, more files will begin pivoting onto flash to preserve settings beyond a reboot. With this expansion in mind, the system has to obey the normal startup and shutdown routines. Ironically, if DSLinux is ever to expand into more generally useful fields, this behavior is only going to become more important.
Even with configuration and dynamic files on the card, you still aren't looking at R/W cycles like you would if you actually tried to swap to it. It is the difference between writing a change to a file every few minutes or at every shutdown, to reading and writing multiple times a second if the system was swapping hard.
The issue is pointless to debate here. The DSLinux developers have no interest in building an OS that is simply a engine to drive user-applications. Their goal is to port a complete OS to a console, as has been the goal with XBox Linux, GCLinux, PS2 Linux, etc. There is rarely a "point" to it, no, but that is just how it is.
Of course, the system is obviously open source, and the developers would have no problems with a group forking development of it into something that would be useful for the average person. If any of you wants to create an off-shoot of the normal DSLinux system that automatically boots up into Links, then you could easily do that.
This is not dissimilar to the "real" Linux distributions. There are distributions that are only the core components of an OS and take nothing for granted (Slackware, Arch, etc), and then there are distributions that attempt as much hand-holding as possible (Ubuntu, Linspire, SuSE, etc). They are both made up of the exact same software, the only thing different is the intent of the group behind it's development.
If there is a group out there that wants to take the "Slackware" DSLinux and turn it into a Ubuntu, then more power to them. But it will certainly have to be an outside group, as the developers of DSLinux have made it very clear that they have no interest in such a project.
#103884 - Darkflame - Mon Sep 25, 2006 4:13 am
Right, so it is made as a tech-demo, fair enough.
_________________
Darkflames Reviews --
Make your own at;
Rateoholic:Reviews for anything, by anyone.
#103929 - MiL0 - Mon Sep 25, 2006 2:54 pm
that's a shame but respect to the dslinux boys for getting this far.
#103947 - OOPMan - Mon Sep 25, 2006 4:32 pm
Hmmmm, seems like some people just don't get "The Path of Linux" :-)
Each to his own...
Me, I like playing around with my OS and hence I like Linux :-)
I have fond memories of doing something like 30 or 40 Redhat installs over the course of a weekend, back when I fist got Linux. This was Redhat 3.0.3, mind you. Back in the day :-)
DS Linux is not a "tech demo" It's a port of a high-grade operating system to a portable platform. It'll take time to reach the level a lot of people want it at, but reach that level it may well do, as like many Linux projects it has a dedicated following of skilled programmers who like nothing more than a challenge...
Needless to say, there'll always be space on my mSD card for DSLinux, even if I only boot it up every now and then...
_________________
"My boot, your face..." - Attributed to OOPMan, Emperor of Eroticon VI
You can find my NDS homebrew projects here...
#104048 - octopusfluff - Tue Sep 26, 2006 4:32 am
On file buffers: Linux' standard behavior on most filesystems is to avoid committing writes for as long as possible. The general purpose behind this is performance; if you've made changes to a file once, probability in most cases is that you'll make changes again, and it's faster to do that while it's still in ram. In the case of write-limited media, the other purpose is to harm the storage device as little as possible. Synching to disk too often will increase the degradation rate of the media unnecessarily without ensuring validity of the filesystem any more than normal; if you're powering off arbitrarily, you can easily power off during a flush. The only precaution here is some form of journaling, but that is a Bad Idea(tm) on limited-write media, for the same reason swapfiles are a Bad Idea(tm).
On security: did you forget that this is a machine with wireless networking? Running as root means that if there's a security hole in a networking app that allows remote exploit, then they gain root. This may be a limited device in what they can accomplish, but since we've already established it's networking capable, there's quite a bit of mischief a sufficiently creative intruder can achieve with root priveliges.
I agree that a traditional typing login-prompt doesn't help with this, but it's still critical to not be running as root default on *ANY* full stacked OS. DSLinux may not be user-friendly in its present state, but it's still capable of quite a bit through shell scripting.
#104127 - tepples - Tue Sep 26, 2006 6:31 pm
| octopusfluff wrote: |
| On file buffers: Linux' standard behavior on most filesystems is to avoid committing writes for as long as possible. |
I understand that. It wouldn't be so bad if someone were to put a sync button or power switch on the touch screen, but having to open another console, type the name, type the password blind (especially with the troublesome touch screen code) and type "poweroff", is a pain in the glutes.
| Quote: |
| On security: did you forget that this is a machine with wireless networking? Running as root means that if there's a security hole in a networking app that allows remote exploit, then they gain root. |
Only if something is listen()ing on a port. The best firewall is not turning on any services that listen() in the first place until you're securely behind your home access point's firewall.
| Quote: |
| I agree that a traditional typing login-prompt doesn't help with this, but it's still critical to not be running as root default on *ANY* full stacked OS. |
Either you are local or you are remote. If you are local, you can remove the CF card. But why would you need a remote login on a handheld, especially when the handheld is more likely to be powered off than on?
| Quote: |
| DSLinux may not be user-friendly in its present state, but it's still capable of quite a bit through shell scripting. |
Then I suggest that people who promote the use of DSLinux as more than a tech demo should contribute such scripts.
_________________
-- Where is he?
-- Who?
-- You know, the human.
-- I think he moved to Tilwick.
#104130 - TJ - Tue Sep 26, 2006 6:36 pm
| Quote: |
| Then I suggest that people who promote the use of DSLinux as more than a tech demo should contribute such scripts. |
The people that are happy with the current functionality should contribute scripts to make the system easier to use for the people complaining about it?
Sure, that makes sense.
#104135 - tepples - Tue Sep 26, 2006 6:49 pm
People who develop applications for DSLinux and who want the general DS homebrew public to use their applications will want the general DS homebrew public not to find DSLinux itself a barrier.
_________________
-- Where is he?
-- Who?
-- You know, the human.
-- I think he moved to Tilwick.
#104169 - MaHe - Tue Sep 26, 2006 10:00 pm
I'm fascinated by the bare fact that the general homebrew and the DSLinux communities are so far away from each other. I mean; there are still people on these boards who think DSLinux is only a tech demo, useful for nothing. And on the contrary, some people on DSLinux forums are still claiming playing video on DS is impossible.
To tell the truth, I absolutely love DSLinux and almost don't use anything else anymore (well, I DO read Garfield comics I download through 'links' in DSOrganize :P). It's a complete operating system and feels and act like it.
I maybe dislike using Linux on a desktop workstation, but for a portable console, it's absolutely a killer-app.
Some facts:
- it was the first homebrew with file management (and still is, except for DSOrganize, which is easy to use but not that advanced, of course);
- it was the first homebrew with completed and perfect WiFi drivers - sgstair's lib still has some issues;
- it was the first homebrew to connect with IRC networks and therefore any IM protocol through bitlbee;
- it was the first homebrew to feature an internet browser (and still is);
- it is the only homebrew to feature multitasking (except for the M3 shell);
- it is the only homebrew making use of SuperCard's/M3's 32 MBs of RAM;
- (that's merely the start of the list, but I'll stop here)
Seriously, it features just everything I need. And to tell the truth, I prefer terminal over the GUI, but that's just me (hey, after all it's easier to type mv /music/*myband*.mp3 /home/music/myband/, than to scr*w with the interface all the time - and the keyboard in DSLinux is among the fastest homebrew virtual keyboards too). tepples: As far as I know, nobody in the DSLinux does develop their own applications - they only port them - it's fairly easy and also serves a PC-like functionality. And nobody is complaining over the user-friendlyness; after all, there's a wiki with all the needed documentation.
_________________
[ Crimson and Black Nintendo DS Lite | CycloDS Evolution | EZ-Flash 3-in-1 | 1 GB Transcend microSD ]
#104176 - TJ - Tue Sep 26, 2006 10:59 pm
As MaHe said, I don't know of any application that was written (beyond some scripts) specifically for DSLinux. They are all ported PC apps. Nobody cares if the general public finds them useful, they are included because they didn't take much system resources or require much modification to run.
If a developer wants to create a simple to use and mass-market friendly application, then they are going to write that on the bare-metal; and aren't going to do it as a terminal-only program packed in with DSLinux.
So again: if you are looking for simple to start, simple to use, idiot-proof software, then stay away from DSLinux. That isn't what it is about, and probably never will be. If you don't understand it (or the concept behind it) then don't use it, and definately don't complain because the developers didn't go out of their way to add in hand-holding.
This isn't a hard concept here.
#104181 - Mr. Picklesworth - Tue Sep 26, 2006 11:32 pm
But the most important point here to learn is: DSLinux is not difficult! It's just not a windowed GUI :)
_________________
Thanks!
MKDS Friend Code: 511165-679586
MP:H Friend Code: 2105 2377 6896
#104184 - kevinc - Tue Sep 26, 2006 11:59 pm
My personal pet peeve with DS Linux, and something that kept me away from the beginning. But seeing that many people seem to be using it, I assume it must be. So...
Are tab completion and command history already implemented?
_________________
http://akzeac.blogspot.com
#104197 - Mr. Picklesworth - Wed Sep 27, 2006 2:50 am
Yes, the new terminal has tab completion and command history. It's better implemented than Windows's terminal, too.
I understand completely anyone who doesn't like a CLI, but it really is not too different from a GUI.
With a windowed GUI you get used to some standards such as that tooltips are handy, Enter generally submits things, Alt-F4 closes windows with most window managers, minimizing puts a window somewhere, Alt-Tab in windows is a wonderful tool, and all those other little hotkeys that we look like stumbling old grannies if we don't use :b
The same is with a CLI; people look like stumbling old grannies at first because they may not be totally used to the idea that commands and programs are the exact same thing, --help after a program name almost always outputs command line options and maybe even a program's purpose in a readable way, multiple virtual terminals are sometimes the only way to run many programs at once (as opposed to multiple windows or virtual desktops), Ctrl-C almost always exits, Esc often opens some kind command mode or menu, and colour is a wonderful thing rarely used without reason.
(Hm... I've just had a thought that could make DSLinux more welcoming! An application launcher using that flashy menu code that somebody ported...)
_________________
Thanks!
MKDS Friend Code: 511165-679586
MP:H Friend Code: 2105 2377 6896
#104198 - tepples - Wed Sep 27, 2006 3:28 am
I'm comfortable with the CLI on my Windows PC because I have a nice full-size Logitech keyboard. (It's a step down from the Model M keyboard that I used to use until a few keys stopped working a month or two ago, but the Logitech still feels OK.) But a CLI is crap without a good way of inputting commands. Try using the Windows on-screen keyboard (in Windows 2000, start > programs > accessories > accessibility > on-screen keyboard) to navigate cmd.exe and you'll feel my pain. Is there any way to enter commands on the DS that can match the 80+ WPM that I routinely pull on a PC?
My suggestions: - Automatically log in when local
- Describe clearly how to create a virtual tty, and/or put dedicated buttons on the on-screen keyboard
- Dedicated poweroff switch on the on-screen keyboard
_________________
-- Where is he?
-- Who?
-- You know, the human.
-- I think he moved to Tilwick.
#104216 - HyperHacker - Wed Sep 27, 2006 6:03 am
There's little point in having a password for root on DSLinux anyway because every user is essentially root. Since DS has no memory protection or virtual memory any random program can write to firmware or kernel memory, power off or reboot in GBA mode without running the necessary commands first, etc. If a remote exploit is found in a web browser and someone really wants to they can have the exploit code write junk to the firmware regardless of what user you're logged in as, or modify the kernel in memory to do whatever they want.
_________________
I'm a PSP hacker now, but I still <3 DS.
#104247 - MaHe - Wed Sep 27, 2006 12:50 pm
| tepples wrote: |
- Automatically log in when local
- Describe clearly how to create a virtual tty, and/or put dedicated buttons on the on-screen keyboard
- Dedicated poweroff switch on the on-screen keyboard
|
- Browse through the DSLinux forums to find out how to do that
- Unfortunately, you must already compile the build with more VTs enabled. Though the precompiled RAM one already has this function.
- Hey, after all, DSLinux is open-source and everyone is welcome to contribute! :P
HyperHacker: DSLinux can't write to the firmware.
_________________
[ Crimson and Black Nintendo DS Lite | CycloDS Evolution | EZ-Flash 3-in-1 | 1 GB Transcend microSD ]
#104269 - OOPMan - Wed Sep 27, 2006 4:19 pm
Mahe made a very interesting point. The doesn't really seem to be much inter-mingling between the bare-metal homebrew scene and the DS Linux scene.
I think, to some extent, this is effect a little exagerated, as it's always the newest community members that tend to post questions and opinions with respect to various things being possible or not possible.
However, I do see a few of the DSLinux.org regulars on these forums as well (Mahe, HyperHacker and a few others). It's a pity Amadeus doesn't hang out here, since I think he could contribute a lot of info...
Some of DS Linux facts he points out are interesting, although he's not entirely correct on the multi-tasking point (Multi-threading has been pursued before and is being pursued again [With a good degree of success this time...]).
Anyay, I wish more of the DSLinux brains and GBADev brains would bash heads more often, since I'm sure it would be productive :-)
_________________
"My boot, your face..." - Attributed to OOPMan, Emperor of Eroticon VI
You can find my NDS homebrew projects here...
#104280 - pepsiman - Wed Sep 27, 2006 6:06 pm
| tepples wrote: |
| Automatically log in when local |
Amadeus has added this to the RAM build.
| tepples wrote: |
| Describe clearly how to create a virtual tty, and/or put dedicated buttons on the on-screen keyboard |
The RAM build has 3 ttys, press Alt+F1, Alt+F2 or Alt+F3 to switch.
Anyone want more than 3?
| tepples wrote: |
| Dedicated poweroff switch on the on-screen keyboard |
Making a button that types p o w e r o f f \n for you is possible, but it won't work when running a program.
#104285 - MaHe - Wed Sep 27, 2006 7:26 pm
| pepsiman wrote: |
| Making a button that types p o w e r o f f \n for you is possible, but it won't work when running a program. |
Unless you make a hidden virtual tty, but that's complete nonsense ... :|
_________________
[ Crimson and Black Nintendo DS Lite | CycloDS Evolution | EZ-Flash 3-in-1 | 1 GB Transcend microSD ]
#104295 - tepples - Wed Sep 27, 2006 9:01 pm
| MaHe wrote: |
| pepsiman wrote: | | Making a button that types p o w e r o f f \n for you is possible, but it won't work when running a program. |
Unless you make a hidden virtual tty, but that's complete nonsense ... :| |
It's not as nonsense as you might think. For instance, an xterm or an SSH server makes such a pty. But what about something more like the SysRq+RSEIUB method?
_________________
-- Where is he?
-- Who?
-- You know, the human.
-- I think he moved to Tilwick.
#104309 - HyperHacker - Wed Sep 27, 2006 11:20 pm
| MaHe wrote: |
| HyperHacker: DSLinux can't write to the firmware. |
No, but the point is with no memory protection any random program could just do it manually the same way it would without Linux.
_________________
I'm a PSP hacker now, but I still <3 DS.
#104378 - pepsiman - Thu Sep 28, 2006 2:19 pm
| HyperHacker wrote: |
| MaHe wrote: | | HyperHacker: DSLinux can't write to the firmware. |
No, but the point is with no memory protection any random program could just do it manually the same way it would without Linux. |
Well, the program would be running on the arm9, the firmware can only be written from the arm7. The arm9 cannot write to arm7 memory.
So I don't see how such an exploit would work.