I normally grade PKAs as "completed", "incomplete" or "not handed in". If you use Moodle, you can propose new activities, let the students work on them, and after they're done, you just open the result PKA file to check their score.
Creating the initial and answer scenarios takes quite a bit, but it's definitely worth the effort. This makes life extraordinarily easier for the teacher. Students start off from 0% and get to 100% when they reach the answer network.
A lot of things can be graded: setting the correct netmask, using the right cable, issuing any IOS command, etc. Packet Tracer will figure out what changed between both scenarios and grade each of the steps required to move between one another. With Packet Tracer's "Activity Wizard", you can even automate the grading of these kind of exercises: you just create an answer network (the student's target) and an initial network (the faulty one). In fact, I'd only need to page my students at 3am to make it look like a real life problem :) These kind of activities put a lot of skills to the test: you need to understand the network, know which tools to use, emit a valid diagnostic and find a proper solution that doesn't break something else. One of my favorite activities consists of building a completely operational network, then causing a random fault somewhere and leaving students with the broken-down network to figure the problem out. Cuando tenga un rato lo miro e intento averiguar el problema. Al final el os dará un enlace por cada fichero, pues lo ponéis en los comentarios. Pero antes buscad en el modem.log la palabra "PIN" y si aparece vuestro PIN lo borráis, para que no aparezca publicado. Le dais con doble click a los dos ficheros de antes (nm.log y modem.blog) y se abrirán con el gedit. Luego os vais a Lugares > Carpeta personal. Pasados esos 3 minutos le dais a CONTROL-C en los dos terminales y los cerráis. Lo dejáis 2 ó 3 minutos para que se conecte. Sudo NM_PPP_DEBUG=1 NetworkManager -no-daemon >nm.log 2>&1Įnchufad el módem y le dais a conectar. Sudo modem-manager -debug >modem.log 2>&1 Luego abrís un terminal (Aplicaciones > Accesorios > Terminal) y ponéis: Ahora que tengo un poco de tiempo puedo mirarlo, pero necesito que me mandéis un par de logs. Viendo los comentarios parece que algunos tenéis problemas. Si todo ha ido bien, se habrá instalado el nuevo modemmanager que corrige este asunto. Por otro lado necesitamos que el paquete usb-modeswitch esté instalado: Sudo add-apt-repository ppa:jmartinj/x060-karmic Mientras tanto podéis bajaros la versión parcheada haciendo: Podéis ver los detalles aquí, esperemos que el autor los solucione. Segundo: ahora los problemas tienen que ver con el paquete "modemmanager", que es el que gestiona los módems 3G. Sudo dpkg -r usb-modeswitch-alcatelX060-dkms Los problemas son varios: en primer lugar el módem ya está soportado por el kernel y no hace falta parchear el módulo "option", así que el paquete usb-modeswitch-alcatelX060-dkms_1.0.2-4_b que utilizábamos en Jaunty ya no hace falta en Karmic y se puede desinstalar:
Los que venís de Jaunty probablemente estaríais utilizando estas instrucciones, que ahora ya no funcionan. I believe the Ubuntu team applied this very same concept to the bugfixing process, so that users are constantly eager for a new release.Įste post es para aquellos que tengáis el módem X060 que venía con la tarifa plana de Simyo y queráis utilizarlo con Ubuntu 9.10.
If you are a fan of the TV series LOST, you probably know that the addiction to it comes partly from the directors' mastery of solving a mistery while puzzling you with three more on each episode. I don't know what two metacities are good for, and last but not least, gnome-power-manager (yeah, the tiny little battery icon that also takes care of suspending, etc.) is munching on another 100 MB. We also excuse evince because it's dealing with some graphics. We also know that it's normal for Xorg to join the feast, but what are gdm-simple-slave and gdm-simple-greeter doing here, taking about as much as firefox altogether? Ok, we all know about Firefox's soft spot for memory when you have 30 tabs opened. the ones that have allocated over 100 MB of virtual memory. I'm just capturing the top hogging processes, ie. It shows the processes running on my computer after 5 days uptime. I just took this snapshot of the system monitor after seeing how my swap space is half full, trying to find a culprit. Looks like there are some memory leaks in the new Ubuntu 9.10 (Karmic):