[IMAGE]
¡La Ley de Educación lo dice bien claro!
"Sin perjuicio del tratamiento especÃfico en algunas de las materias de
la etapa, la comprensión lectora, la expresión oral y escrita... se
trabajaran en TODAS (las asignaturas)".
"La lectura constituye
Tisztelt Tag!
[IMAGE]ÃrtesÃtünk, hogy a SunaMustra.com oldalon Melani jelezte, szÃvesen
lefeküdne veled![IMAGE]
[IMAGE]
Melani adatlapja: http://sunamustra.com/pussy.php?id=36202032528
Amennyiben szeretnéd megtekinteni az adatlapját, vagy jóváhagyni a
szexuális felkérését, kattints
On Sun, Sep 02, 2012 at 08:36:57PM +0200, Otto Moerbeek wrote:
> On Sun, Sep 02, 2012 at 04:18:17PM +0200, rustyBSD wrote:
>
> > Le 02/09/2012 16:06, rustyBSD a ?crit :
> > > [demime 1.01d removed an attachment of type text/x-patch which had a name
> > > of scsi.c.diff]
> > Mmhhh...
> >
> > ---
On Mon, Sep 03, 2012 at 02:44, IMAP List Administration wrote:
> I haven't seen anything in /var/log/kern since it's been running (days).
>
> Is there some way to generate a test kernel message ala logger(1)? If
> not, how
> about a harmless way to get the kernel to report an error?
plug someth
On Sun, Sep 02, 2012 at 18:46, Jan Stary wrote:
> What could be the reason for that?
>
> The apparent difference between the two, USB-wise, is
> (amd64 box) uhub0 at usb0 "Intel EHCI root hub" rev 2.00/1.00 addr 1
> (i386 laptop) uhub0 at usb0 "VIA UHCI root hub" rev 1.00/1.00 addr 1
>
> i.e.
Hello,
I've replaced syslogd with syslog-ng. I have the following config for kernel
messages:
> source kernel {
> file("/dev/klog" program_override("kernel: "));
> };
>
> destination kern { file("/var/log/kern"); };
>
> log { source(kernel); destination(kern); };
Perhaps someone can com
Your ANZ online Banking has been temporary suspended.
To confirm your ANZ online account status please "LOGIN"
On Sun, Sep 02, 2012 at 09:18:02PM +0200, rustyBSD wrote:
> Le 02/09/2012 20:36, Otto Moerbeek a ?crit :
> > Confusing errno and exit code. Just use 1. Or err(1, NULL). The
> > default message is clear enough.
> I use errno because most of other calls to err() in this
> file use errno too.
Then t
Le 02/09/2012 20:36, Otto Moerbeek a écrit :
> Confusing errno and exit code. Just use 1. Or err(1, NULL). The
> default message is clear enough.
I use errno because most of other calls to err() in this
file use errno too.
On Sun, September 2, 2012 20:24, Andrew Fresh wrote:
> I got a nice G5 from work and would like to run OpenBSD macppc on it.
>
> However, when I attempt to install I get to what is described as step 4
> for i386 and amd64 in the FAQ:
> booting hd0a:/bsd 4464500+838332 [58+204240+181750]=0x56cfd0
>
On Sun, Sep 02, 2012 at 04:18:17PM +0200, rustyBSD wrote:
> Le 02/09/2012 16:06, rustyBSD a ?crit :
> > [demime 1.01d removed an attachment of type text/x-patch which had a name
> > of scsi.c.diff]
> Mmhhh...
>
> --- scsi.cSun Sep 2 15:47:45 2012
> +++ scsi.cSun Sep 2 16:00:42 2012
> @
Run dmesg from a shell on the Android. See what its side of the story is. I
think it uses eth0 and/or usb0 for tethering. Check ifconfig usb0/eth0 too.
My guess is that the phone doesn't do usb1. Can you mount the phone as a
storage device with the i386? If you can, you can pipe dmesg to a file in
With the diff below it resumes ok to X, but when I try to switch
to text console or do a shutdown, I get this panic:
/etc/rc.shutdown in progress...
/etc/rc.shutdown complete.
Stopped at cpu_idle_cycle+0xf: ret
ddb{1}> bt
No such command
ddb{1}> trace
cpu_idle_cycle(d406ac00) at cpu_idle_
On my amd64 workstation (see dmesg below), my android appears
as an urndis(4) device a can provide the box with a network conection.
urndis0 at uhub0 port 3 configuration 1 interface 0 "SAMSUNG Electronics Co.,
Ltd. Samsung Android USB Device" rev 2.00/4.00 addr 3
urndis0: address be:a1:fc:82:8f:
I got a nice G5 from work and would like to run OpenBSD macppc on it.
However, when I attempt to install I get to what is described as step 4
for i386 and amd64 in the FAQ:
booting hd0a:/bsd 4464500+838332 [58+204240+181750]=0x56cfd0
http://openbsd.org/faq/faq14.html#Boot386
Except that line does
The "moon" indicator is blinking, but screen stays black, so I connected
a serial cable. Here's what I got:
Script started on Sun Sep 2 19:52:24 2012
> sudo cu -l /dev/tty00
Connected
>> OpenBSD/i386 BOOT 3.18
boot> boot
booting hd0a:/bsd:
/-\|/8354720-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/
Le 02/09/2012 16:06, rustyBSD a écrit :
> [demime 1.01d removed an attachment of type text/x-patch which had a name of
> scsi.c.diff]
Mmhhh...
--- scsi.cSun Sep 2 15:47:45 2012
+++ scsi.cSun Sep 2 16:00:42 2012
@@ -223,6 +223,7 @@
case 'z':
{
char *p = mal
Le 02/09/2012 14:57, Alexander Hall a écrit :
> Whoever it is, I'm sure he or she appreciate diffs anyway!
Ok, here is one.
[demime 1.01d removed an attachment of type text/x-patch which had a name of
scsi.c.diff]
This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.
[demime 1.01d removed an attachment of type image/jpeg which had a name of
duyuru maÝl.jpg]
On 09/02/12 14:42, Kenneth R Westerback wrote:
On Sun, Sep 02, 2012 at 02:27:57PM +0200, rustyBSD wrote:
Le 01/09/2012 19:59, Kenneth R Westerback a ?crit :
On Sat, Sep 01, 2012 at 07:19:25PM +0200, rustyBSD wrote:
Hi,
in /usr/src/sbin/scsi/scsi.c line 225, why
is the malloc not checked ? ...
On Sun, Sep 02, 2012 at 02:27:57PM +0200, rustyBSD wrote:
> Le 01/09/2012 19:59, Kenneth R Westerback a ?crit :
> > On Sat, Sep 01, 2012 at 07:19:25PM +0200, rustyBSD wrote:
> >> Hi,
> >> in /usr/src/sbin/scsi/scsi.c line 225, why
> >> is the malloc not checked ? ... If it fails,
> >> it overflows,
Le 01/09/2012 19:59, Kenneth R Westerback a écrit :
> On Sat, Sep 01, 2012 at 07:19:25PM +0200, rustyBSD wrote:
>> Hi,
>> in /usr/src/sbin/scsi/scsi.c line 225, why
>> is the malloc not checked ? ... If it fails,
>> it overflows, no ?
>>
> Crufty old code. Feel free to submit an actual diff! Note t
22 matches
Mail list logo
