This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Messages - squalyl
31
« on: January 07, 2011, 04:48:43 am »
Hello
That's great.
Is the URL alive for you all now?
32
« on: January 06, 2011, 04:18:28 pm »
Mrakoplaz: I understand how you feel about svn... until I lost 3 months worth of code, recovered half of it, then broke it once again, without the possibility to revert 3 days of (bad) work. However I'm not here to force anyone to do anything, so that's fine.
Just to say that I don't either use svn for shared projects, but the dumb way, as a cheap incremental backup with log messages. svn with more than 1 developer is a mess as soon as 2 people change the same file (half joke - but svn branches really sucks), and git seems nice but is too complicated for me. but the backup side of svn is nice. again, just my 2 cents, I totally respect your freedom.
33
« on: January 06, 2011, 10:59:14 am »
We're just waiting for DNS propagation, sorry  [edit: and a corrected DNS entry #sick# ] however the name tells everything. The page just mentions a contact address: [email protected] . This one is functional.
34
« on: January 06, 2011, 10:04:51 am »
Well, that could be interesting but I wonder how much time I will need to admin all of this if the number of projects grow too fast. My vision was a human-sized thing, not a sourceforge-bis.
35
« on: January 06, 2011, 06:10:10 am »
Would some people being interested by a domain where you can register an nspire related project? I could offer that: http://nspforge.unsads.com/ [edit: just waiting DNS propagation] The only non negotiable conditions are: respecting all required laws. This is obvious. make your releases available free of charge. serious projects only ("hai I want to make a nspire dreamcast emulator where do I download ndless and what is ARM lol?" -> KTHXBYE) Any other is negotiable. The code does not have to be open source. Projects would be manually approved for the moment, until I can automate the creation process. I can provide - trac -> follow issues, bugs, etc - svn -> record backup and control your source code - daily backup to a ftp space If someone helps me, git is also possible. I can also import existing svn repositories and discuss any requirement I did not talk about in this post. What do you think of this? Useful? already done by individual project owners? What more could make that thing interesting?
36
« on: January 06, 2011, 05:57:07 am »
Actually, for all the Nspire stuff, it would be ideal to have an svn host dedicated to hosting Nspire. Such as someone here setting up their webserver for that. What would you think of this? http://nspforge.unsads.com/(be patient, DNS propagation may not be complete yet, I just added the domain a few minutes ago)
37
« on: January 04, 2011, 04:55:20 pm »
Hello,
first: over 9000 congrats. That's awesome.
second: if you don't have a svn now, or need a svn, or want to host it on my server, i'd be happy to provide it. git is probably possible too, but I'm still a noob with it.
squalyl, hackspire's / nsptools hoster.
38
« on: December 02, 2010, 06:20:45 pm »
Hello,
unsads is back, including trac, svn and hackspire (with an updated - but still ugly - logo that matches the trac one \o/ ).
this was a followup of the previous failure. The disk remained weak, and today it totally died.
once in the recovery system, I only had /dev/sda and no more /dev/sda1 and others... frightening!
The whole server hardware has been replaced.
Thanks to the daily backups not a single bit was lost.
sorry for the inconvenience, I'm happy it was relatively short.
and congrats to critor for this awesome shell explorer.
39
« on: November 28, 2010, 06:08:27 pm »
yes it is marked as optional even if I require it, but I don't know how to change the trac template. So I added a warning on the wiki main page.
thanks.
40
« on: November 28, 2010, 04:43:40 pm »
Hello Levak,
please register with an email address. All accounts with no email address will be deleted once in a while.
squalyl
41
« on: October 03, 2010, 03:50:06 pm »
not quite. and solar flares are not cosmic rays: -cosmic rays are ultra high energy particles coming from the deep space (supernovas, black holes, etc) -solar flares are energetic protons and/or electrons IIRC. most cosmic rays are filtered by the atmosphere. that's why the Alpha magnetic spectrometer [1] is sent to the space station, and why satellite computers have to be radiation-hardened, but not ours  that was a kernel bug, not a hardware issue. oh, btw, is ti a linux contributor? Maybe they targeted my server using GnuStuxnet [1] http://www.esa.int/esaCP/SEMZE8BO3DG_index_0.html
42
« on: October 03, 2010, 06:33:21 am »
I think my cosmic ray was named firefox sync server that usually writes a lot of database entries, causing traffic and journalling operations. Couple that with a transient IO problem or a weird ext3 bug that triggers only on certain (race) conditions and you're done.
unfortunately it was in the same datafile as other databases.
this cause is now eradicated, my firefox sync server is now using sqlite.
the wiki database is now almost alone. And dumped daily to a backup server.
43
« on: October 02, 2010, 04:44:17 pm »
Yes the server is in utf-8 and putty was left in iso8859-1, but that's not really important.
the server's hardware is perfectly fine, that was confirmed by a complete check by the server's provider administrative interface.
the filesystem got somewhat totally destroyed, I don't know how it is even possible. e2fsck found so many corruptions that I thought the disk was filled with garbage, such as if some block (and all the following) was not properly aligned.
in the end, I formatted the disk, reinstalled debian, then restored the backup I did last night. I pray myself for having thought about that or I would have lost *anything*. I also thank debian for the sites-enabled concept that permitted a very fast restoration using symlinks to my individual config files.
svn is back
mysql is back
the wiki is back
In the process mediawiki was bumped from 1.13.2 to 1.16.0
(i'm struggling with firefox sync but that's another story.)
Now recent changes need to be fed in. The change made yesterday was lost in the process. You can import any new information that you found was lost.
The most important change is that I now have automatic daily backups (300MB.bz2 for web and svn, 1MB.bz2 for mysql)
44
« on: October 02, 2010, 06:43:44 am »
the ext3 filesystem is dead. Here is the beginning of the e2fsck log.
root@88-191-122-130:~# e2fsck -v /dev/sda2 -f -c
e2fsck 1.41.11 (14-Mar-2010)
Vérification des blocs défectueux (test en mode lecture seule) : complété
/: Updating bad block inode.
Passe 1 : vérification des i-noeuds, des blocs et des tailles
I-noeud 598304, i_blocs est 33607752, devrait être 33599560. Corriger<o>? oui
l'i-noeud 745906 a un(des) bloc(s) illégal(aux). Effacer<o>? oui
Illégal block #12 (4294967295) in i-noeud 745906. EFFACÃ.
Illégal block #13 (4294967295) in i-noeud 745906. EFFACÃ.
Illégal block #14 (4294967295) in i-noeud 745906. EFFACÃ.
Illégal block #15 (4294967295) in i-noeud 745906. EFFACÃ.
Illégal block #16 (4294967295) in i-noeud 745906. EFFACÃ.
Illégal block #17 (4294967295) in i-noeud 745906. EFFACÃ.
Illégal block #18 (4294967295) in i-noeud 745906. EFFACÃ.
Illégal block #19 (4294967295) in i-noeud 745906. EFFACÃ.
Illégal block #20 (4294967295) in i-noeud 745906. EFFACÃ.
Illégal block #21 (4294967295) in i-noeud 745906. EFFACÃ.
Illégal block #22 (4294967295) in i-noeud 745906. EFFACÃ.
Trop de blocs illégaux dans l'i-noeud 745906.
Effacer l'i-noeud<o>? oui
des i-noeuds qui faisaient partie d'une liste chaînée d'orphelins corrompue ont été repérés. Corriger<o>? oui
l'i-noeud 1954497 fait partie de la liste des i-noeuds orphelins. CORRIGÃ.
l'i-noeud 1954498 est utilisé, mais a un dtime. Corriger<o>? oui
l'i-noeud 1954498 a un drapeau imagic activé. Effacer<o>? oui
L'i-noeud spécial (périphérique/socket/fifo) 1954498 a une taille non nulle. Corriger<o>? oui
l'i-noeud 1954499 fait partie de la liste des i-noeuds orphelins. CORRIGÃ.
l'i-noeud effacé 1954500 a un dtime à zéro. Corriger<o>? oui
l'i-noeud 1954513 fait partie de la liste des i-noeuds orphelins. CORRIGÃ.
l'i-noeud 1954514 a le drapeau EXTENTS_FL activé sur le système de fichiers sans support des extents.
Effacer<o>? oui
l'i-noeud 1954515 fait partie de la liste des i-noeuds orphelins. CORRIGÃ.
l'i-noeud 1954516 fait partie de la liste des i-noeuds orphelins. CORRIGÃ.
l'i-noeud 1954529 est utilisé, mais a un dtime. Corriger<o>? oui
l'i-noeud 1954529 a un drapeau imagic activé. Effacer<o>? oui
l'i-noeud 1954530 fait partie de la liste des i-noeuds orphelins. CORRIGÃ.
l'i-noeud 1954531 fait partie de la liste des i-noeuds orphelins. CORRIGÃ.
l'i-noeud 1954532 fait partie de la liste des i-noeuds orphelins. CORRIGÃ.
l'i-noeud 1954533 est utilisé, mais a un dtime. Corriger<o>? oui
l'i-noeud 1954533 a un drapeau imagic activé. Effacer<o>? oui
l'i-noeud 1954533 a une taille extra (24430) qui est invalide
Corriger<o>? oui
l'i-noeud 1954534 fait partie de la liste des i-noeuds orphelins. CORRIGÃ.
l'i-noeud 1954535 fait partie de la liste des i-noeuds orphelins. CORRIGÃ.
l'i-noeud 1954536 fait partie de la liste des i-noeuds orphelins. CORRIGÃ.
l'i-noeud 1954537 fait partie de la liste des i-noeuds orphelins. CORRIGÃ.
l'i-noeud 1954545 fait partie de la liste des i-noeuds orphelins. CORRIGÃ.
l'i-noeud 1954546 a le drapeau EXTENTS_FL activé sur le système de fichiers sans support des extents.
Effacer<o>? oui
l'i-noeud 1954547 a le drapeau EXTENTS_FL activé sur le système de fichiers sans support des extents.
Effacer<o>? oui
l'i-noeud 1954548 est utilisé, mais a un dtime. Corriger<o>? oui
l'i-noeud 1954548 a une taille extra (51589) qui est invalide
Corriger<o>? oui
l'i-noeud 1954549 est utilisé, mais a un dtime. Corriger<o>? oui
l'i-noeud 1954549 a une taille extra (17547) qui est invalide
Corriger<o>? oui
l'i-noeud 1954550 a le drapeau EXTENTS_FL activé sur le système de fichiers sans support des extents.
Effacer<o>? oui
l'i-noeud 1954551 est utilisé, mais a un dtime. Corriger<o>? oui
l'i-noeud 1954551 a un drapeau imagic activé. Effacer<o>? oui
l'i-noeud 1954551 a une taille extra (9300) qui est invalide
Corriger<o>? oui
l'i-noeud 1954552 a le drapeau EXTENTS_FL activé sur le système de fichiers sans support des extents.
Effacer<o>?
this is french, and that says, lots of invalid inodes.
FORTUNATELY I backed up svn, trac, the web pages and the database yesterday.
45
« on: October 02, 2010, 05:35:12 am »
I just found I have a disk problem. The disk was remounted read only during the last hours.
I rebooted the server into recovery mode.
I Keep you up to date
|
Show Posts
