Re: WiFi borked after update

2008-10-08 Thread Marius Vollmer
ext Denis Dimick [EMAIL PROTECTED] writes: I agree that updating over a network should, and does work from a normal Linux distro, however, I'm not sure it's going to work on Maemo anytime soon; I'm guessing the small memory footprint prevents some of the applications from not killing off a

Fwd: WiFi borked after update

2008-10-08 Thread Andrew Flegg
at 12:59 PM Subject: Re: WiFi borked after update To: ext Dmitry S. Makovey [EMAIL PROTECTED] Cc: maemo users maemo-users@maemo.org ext Dmitry S. Makovey [EMAIL PROTECTED] writes: Marius Vollmer wrote: Yes. What about making red-pill mode non-persistent: on the next start of the AM, it would

Re: WiFi borked after update

2008-10-08 Thread hendrik
On Wed, Oct 08, 2008 at 01:48:24PM +0300, Marius Vollmer wrote: ext Denis Dimick [EMAIL PROTECTED] writes: I agree that updating over a network should, and does work from a normal Linux distro, however, I'm not sure it's going to work on Maemo anytime soon; I'm guessing the small memory

Re: WiFi borked after update

2008-10-08 Thread Marius Vollmer
ext Dmitry S. Makovey [EMAIL PROTECTED] writes: Marius Vollmer wrote: Yes. What about making red-pill mode non-persistent: on the next start of the AM, it would be back in blue-pill mode. I think this is a good middle-ground solution for the problem at hand. Ok, it's decided, then. Cool.

Re: Fwd: WiFi borked after update

2008-10-08 Thread Marius Vollmer
ext Andrew Flegg [EMAIL PROTECTED] writes: More information on the problem/use-case of the cross-domain package would be useful, I think. The package domains are an effort to simulate a sane distribution on the device: in a sane distribution, a given package is available only from one source.

Re: WiFi borked after update

2008-10-08 Thread Marius Vollmer
ext [EMAIL PROTECTED] [EMAIL PROTECTED] writes: Debian warns not to do an upgrade over X, because X will go down and up when it is reinstalled, [...] Never happened to me, and I would expect the X packagers to be better than that. The xserver-xorg.postinst is the mother of all maintainer

Re: WiFi borked after update

2008-10-08 Thread hendrik
On Wed, Oct 08, 2008 at 05:28:19PM +0300, Marius Vollmer wrote: ext [EMAIL PROTECTED] [EMAIL PROTECTED] writes: Debian warns not to do an upgrade over X, because X will go down and up when it is reinstalled, [...] Never happened to me, and I would expect the X packagers to be better

Re: WiFi borked after update

2008-10-08 Thread Marius Vollmer
ext [EMAIL PROTECTED] [EMAIL PROTECTED] writes: On Wed, Oct 08, 2008 at 05:28:19PM +0300, Marius Vollmer wrote: ext [EMAIL PROTECTED] [EMAIL PROTECTED] writes: Debian warns not to do an upgrade over X, because X will go down and up when it is reinstalled, [...] Never happened to me,

Re: WiFi borked after update

2008-10-07 Thread Andrew Flegg
Dmitry wrote:   Well I know about colors, but why do you need them at all - that is my question. I don't know of any other distro using similar concepts: Xandros on Eee, Ubuntu, Debian, OpenMoko, Gentoo, RedHat - none is using a concept of two separate modes for installs. I wonder how did it

Re: WiFi borked after update

2008-10-07 Thread Marius Vollmer
ext Dmitry S. Makovey [EMAIL PROTECTED] writes: Ryan Abel wrote: To anybody reading using Red Pill mode, please don't. If you aren't absolutely positive of what it's going to do, then you're just going to get yourself in trouble. You don't need it and you don't want it, so don't use it.

Re: WiFi borked after update

2008-10-07 Thread Marius Vollmer
ext Andrew Flegg [EMAIL PROTECTED] writes: This is the reason for the two modes - one gives you the sanitised view, one gives you everything. I fully agree with blue-pill mode for end-users; but I don't understand why red-pill's needed: if you're a power user, I can't imagine Hildon App Mgr

Re: WiFi borked after update

2008-10-07 Thread Andrew Flegg
On Tue, Oct 7, 2008 at 2:59 PM, Marius Vollmer [EMAIL PROTECTED] wrote: However, sometimes the Application manager is the only tool you have: xterm might not be there, or you can not login as root. It would be frustrating to not be able to bootstrap yourself into a root shell just because the

Re: WiFi borked after update

2008-10-07 Thread Marius Vollmer
ext Andrew Flegg [EMAIL PROTECTED] writes: True. Perhaps we (as a community) should try pushing this message more: red-pill mode is intended as a rescue environment in the event of b0rkage; not for every day use (even by power users)? Yes. What about making red-pill mode non-persistent: on

Re: WiFi borked after update

2008-10-07 Thread kenneth marken
On Tuesday 07 October 2008 16:24:35 Marius Vollmer wrote: ext Andrew Flegg [EMAIL PROTECTED] writes: True. Perhaps we (as a community) should try pushing this message more: red-pill mode is intended as a rescue environment in the event of b0rkage; not for every day use (even by power

Re: WiFi borked after update

2008-10-07 Thread Andrew Flegg
On Tue, Oct 7, 2008 at 3:51 PM, kenneth marken [EMAIL PROTECTED] wrote: or mod so that there is a power user mode that shows more info about the packages, but do not show the system related ones that red pill is there to protect. What's the use case that that'd support, though? I consider

Re: WiFi borked after update

2008-10-07 Thread Marius Vollmer
ext Denis Dimick [EMAIL PROTECTED] writes: While I'm not sure I'm in Red Pill Mode, I did my update from the command line over SSH; a really STUPID ting to do. On a Maemo device, yes. In general, no. Updating while logged in over the network must work in any half-serious OS. (Red-pill mode

Re: WiFi borked after update

2008-10-07 Thread Denis Dimick
Marius, I agree that updating over a network should, and does work from a normal Linux distro, however, I'm not sure it's going to work on Maemo anytime soon; I'm guessing the small memory footprint prevents some of the applications from not killing off a SSH session when there's an upgrade. I'd

Re: WiFi borked after update

2008-10-07 Thread Eero Tamminen
Hi, ext Marius Vollmer wrote: True. Perhaps we (as a community) should try pushing this message more: red-pill mode is intended as a rescue environment in the event of b0rkage; not for every day use (even by power users)? Yes. What about making red-pill mode non-persistent: on the next

Re: WiFi borked after update

2008-10-07 Thread Andrew Flegg
On 10/7/08, Eero Tamminen [EMAIL PROTECTED] wrote: ext Marius Vollmer wrote: Yes. What about making red-pill mode non-persistent: on the next start of the AM, it would be back in blue-pill mode. Sounds good to me. Agreed. Sounds like the best way of balancing the features against the

Re: WiFi borked after update

2008-10-07 Thread Ryan Abel
On Oct 7, 2008, at 12:15 PM, Eero Tamminen wrote: Hi, ext Marius Vollmer wrote: True. Perhaps we (as a community) should try pushing this message more: red-pill mode is intended as a rescue environment in the event of b0rkage; not for every day use (even by power users)? Yes. What about

Re: WiFi borked after update

2008-10-07 Thread Dmitry S. Makovey
Marius Vollmer wrote: True. Perhaps we (as a community) should try pushing this message more: red-pill mode is intended as a rescue environment in the event of b0rkage; not for every day use (even by power users)? Yes. What about making red-pill mode non-persistent: on the next start

Re: WiFi borked after update

2008-10-06 Thread Marius Vollmer
ext Dmitry S. Makovey [EMAIL PROTECTED] writes: I distinctly remember seeing osso* packages in the listing and I caught a glimpse of screen when it was downloading separate packages. It never got to Feature Upgrade. I got to that much later, when I fixed my networking. Come to think of it I'm

Re: WiFi borked after update

2008-10-06 Thread Ryan Abel
On Oct 6, 2008, at 4:04 AM, Marius Vollmer wrote: I have already changed the defaults of red-pill mode to be 'safer': Show all packages and Show magic:sys are now off by default. Oh thank god! That makes my troubleshooting life so much easier. Three cheers for Marius! Ah, no, just stay out

Re: WiFi borked after update

2008-10-06 Thread Denis Dimick
While I'm not sure I'm in Red Pill Mode, I did my update from the command line over SSH; a really STUPID ting to do. I did reboot my system last night after doing the upgrade on Sat, and all of a sudden everything looks like it works. There where a number of 3rd party apps that needed to be

Re: WiFi borked after update

2008-10-06 Thread Dmitry S. Makovey
Marius Vollmer wrote: I know how frustrating it is to have very little details to resolve issues, but I was in a hurry, and I needed my N800 in somewhat working condition no matter what, so I just took as many shortcuts as I could at the time just to get going. Now that I've learned my lesson

Re: WiFi borked after update

2008-10-06 Thread Dmitry S. Makovey
Ryan Abel wrote: To anybody reading using Red Pill mode, please don't. If you aren't absolutely positive of what it's going to do, then you're just going to get yourself in trouble. You don't need it and you don't want it, so don't use it. Not trying to spin any flamewars or try to be

Re: WiFi borked after update

2008-10-06 Thread hendrik
On Mon, Oct 06, 2008 at 08:06:56PM -0600, Dmitry S. Makovey wrote: Ryan Abel wrote: To anybody reading using Red Pill mode, please don't. If you aren't absolutely positive of what it's going to do, then you're just going to get yourself in trouble. You don't need it and you don't want it,

Re: WiFi borked after update

2008-10-06 Thread Dmitry S. Makovey
[EMAIL PROTECTED] wrote: One colour pill is for ordinary users. They get packages that are safe to use. The other is for system hackers who know what they're doing. They also get packages that are not safe to use, in case they need them to do things the ordinary user wouldn't dream of.

Re: WiFi borked after update

2008-10-04 Thread Laurent GUERBY
On Thu, 2008-10-02 at 10:03 +0300, Patrik Flykt wrote: d I suspect that if I had tried with 'apt-get -f install' or 'apt-get upgrade' immediately I did apt-get -f install and didn't have to reflash indeed. Even if everything works, it looks like situation is not completely clean on my N810:

Re: WiFi borked after update

2008-10-04 Thread Denis Dimick
I just noticed, after I upgraded, that I seem to have the same problem, however, it's a icon issue, I can still use the wireless. For some reason it's looks like it's not working, but it is. HtH, Denis On Sat, Oct 4, 2008 at 4:00 AM, Laurent GUERBY [EMAIL PROTECTED] wrote: On Thu, 2008-10-02

Re: WiFi borked after update

2008-10-03 Thread Marius Vollmer
ext Dmitry S. Makovey [EMAIL PROTECTED] writes: On Tue, September 30, 2008 10:37, Marius Vollmer said: Hmm, the Application manager will first download all the needed packages, and only after that has happened will it start the update process. So you should have all the packages somewhere.

Re: WiFi borked after update

2008-10-03 Thread Ryan Abel
On Oct 3, 2008, at 7:20 AM, Marius Vollmer wrote: Hmm, a dependency error is not something that you can override. Any chance that you remember more details about this? More than a few people have mentioned overriding or ingoring dependency errors when installing this update. I can't

Re: WiFi borked after update

2008-10-03 Thread Marius Vollmer
Eero Tamminen [EMAIL PROTECTED] writes: Hi, ext Marius Vollmer wrote: Unlike apt-get, the AM tries to ignore broken packages so that, for example, a broken maemomapper installation does not prevent a OS upgrade. Um, wouldn't a broken package database be a good reason to refuse to do on

Re: WiFi borked after update

2008-10-03 Thread Eero Tamminen
Hi, Marius Vollmer wrote: Eero Tamminen [EMAIL PROTECTED] writes: Unlike apt-get, the AM tries to ignore broken packages so that, for example, a broken maemomapper installation does not prevent a OS upgrade. Um, wouldn't a broken package database be a good reason to refuse to do on OS

Re: WiFi borked after update

2008-10-03 Thread Dmitry S. Makovey
Marius Vollmer wrote: from what I've seen it was downloading packages one-by-one installing as it goes. :( No, that's impossible... The code just doesn't do it this way. Once the Installing OS2008 Feature Upgrade progress bar is shown, the network should no longer be needed. I

Re: WiFi borked after update

2008-10-02 Thread Patrik Flykt
Hi, Re-reading the original post seems to indicate that I encountered a totally different issue than what was described. For me the all the required packages were downloaded nicely, but the installation failed. No idea why it failed, but the good thing is that nobody else has been able

Re: WiFi borked after update

2008-10-02 Thread Tommy Persson
Patrik Flykt [EMAIL PROTECTED] writes: Hi, Re-reading the original post seems to indicate that I encountered a totally different issue than what was described. For me the all the required packages were downloaded nicely, but the installation failed. No idea why it failed, but the

Re: WiFi borked after update

2008-10-02 Thread Marius Vollmer
ext Tommy Persson [EMAIL PROTECTED] writes: I suspected I did not have enough space to install but I suppose the reason for the failure could have been something else. There is one stupid bug in the Application manager that I suspect might be to blame for some of the failures. If you have

Re: WiFi borked after update

2008-10-02 Thread Eero Tamminen
Hi, ext Marius Vollmer wrote: ext Tommy Persson [EMAIL PROTECTED] writes: I suspected I did not have enough space to install but I suppose the reason for the failure could have been something else. There is one stupid bug in the Application manager that I suspect might be to blame for

Re: WiFi borked after update

2008-10-01 Thread Laurent GUERBY
On Tue, 2008-09-30 at 23:37 -0600, Dmitry S. Makovey wrote: Andre Klapper wrote: This might be related to the problem: https://bugs.maemo.org/show_bug.cgi?id=3749 thanks. that was the exact problem. Poking around with autoconnection on my N800 made it to connect to nearest known AP,

Re: WiFi borked after update

2008-10-01 Thread Dmitry S. Makovey
Laurent GUERBY wrote: On Tue, 2008-09-30 at 23:37 -0600, Dmitry S. Makovey wrote: Andre Klapper wrote: This might be related to the problem: https://bugs.maemo.org/show_bug.cgi?id=3749 thanks. that was the exact problem. Poking around with autoconnection on my N800

WiFi borked after update

2008-09-30 Thread Dmitry S. Makovey
Today in the morning my N800 happily announced available updates. So I agreed to install them. At some point half way through WiFi connection was interrupted so I've been left with packages in inconsistent state (I assume) as my WiFi can't locate any access points anymore spinning into infinity.

Re: WiFi borked after update

2008-09-30 Thread Dmitry S. Makovey
As a follow-up, I've tried: # apt-get -qq --print-uris dist-upgrade uris with subsequent attempt to fetch listed uris on my desktop # awk '{print wget -O $2 $1}' uris wget-script # sh +x wget-script however all the nokia updates refuse to download in this fashion. Is it possible for

Re: WiFi borked after update

2008-09-30 Thread Marius Vollmer
ext Dmitry S. Makovey [EMAIL PROTECTED] writes: Today in the morning my N800 happily announced available updates. So I agreed to install them. At some point half way through WiFi connection was interrupted so I've been left with packages in inconsistent state (I assume) as my WiFi can't

Re: WiFi borked after update

2008-09-30 Thread Dmitry S. Makovey
On Tue, September 30, 2008 10:37, Marius Vollmer said: Hmm, the Application manager will first download all the needed packages, and only after that has happened will it start the update process. So you should have all the packages somewhere. from what I've seen it was downloading packages

Re: WiFi borked after update

2008-09-30 Thread Andre Klapper
Am Dienstag, den 30.09.2008, 09:13 -0600 schrieb Dmitry S. Makovey: Today in the morning my N800 happily announced available updates. So I agreed to install them. At some point half way through WiFi connection was interrupted so I've been left with packages in inconsistent state (I assume) as

Re: WiFi borked after update

2008-09-30 Thread Dmitry S. Makovey
Andre Klapper wrote: This might be related to the problem: https://bugs.maemo.org/show_bug.cgi?id=3749 thanks. that was the exact problem. Poking around with autoconnection on my N800 made it to connect to nearest known AP, from there I was able to continue in terminal. ugh. glad I didn't