search for: aeb

With the release of the Nevada build 90 binaries, it is now possible to install SXCE directly onto a ZFS root filesystem, and also put ZFS swap onto a ZFS filesystem without worrying about having it deadlock. ZFS now also supports crash dumps! To install SXCE to a ZFS root, simply use the text-based installer, after choosing "Solaris Express" from the boot menu on the DVD. DVD download

...most 99% of the attacks are through SMTP/SASL attempts, using 'auth login'. Postfix is configured to use Dovecot for the authentication backend. NOTE: parens contain the base64 decoded values, this is not part of the data stream. C: auth login S: 334 VXNlcm5hbWU6 (334 Username:) C: YWVi (aeb) S: 334 UGFzc3dvcmQ6 (334 Password:) C: My4xNDE1OTI2 (3.1415926) S: 535 5.7.8 Error: authentication failed: UGFzc3dvcmQ6 (535 5.7.8 Error: authentication failed: Password:) Aug 22 11:00:31 host3 dovecot: auth-worker(19844): sql(aeb,120.198.9.221): unknown user How difficult would it be to add...

When I issue sudo tail -f/var/log/syslog in order to try and track down an external drive problem I get the following: Jan 11 07:56:00 kernel: [17179663.076000] atkbd.c: Unknown key released (translated set 2, code 0x81 on isa0060/serio0). Jan 11 07:56:00 kernel: [17179663.076000] atkbd.c: Use 'setkeycodes e001 <keycode>' to make it known. Jan 11 07:56:00 kernel: [17179663.084000]

Hello, Recently I realized that entering first 8 characters from my root password is enough to log in as root although I've enabled MD5 passwords in installation program. Also I've added two other users during installation. After looking through /etc/shadow it seems that root's password isn't md5 although passwords of other two users are md5. Is it correct behaviour? Eugene --

Hi, I don´t think that this is a ext3 Problem, since you have problems partitioning that disk. Perhaps a hdparm -i /dev/hdX could shine some light on this, also a fdisk -l /dev/hdX could be useful. For now - let me guess: <guess> To me, it seems, that the disk is clipped to 32GB, perhaps the mainboard bios can not cope with a disk >32GB - just a thought. Since the manufactorer

> > The appliance kernel couldn't find any partitions at all on the disk. > > Is it a raw format disk image, or some other format that qemu can > reasonably be expected to read? I used the "Advanced Options" of Macrium Reflect (on Windows 7) to do a raw byte copy. If it is, then yes I'd say the image is corrupted. However you'd > probably want to hexdump

...54 20 53 59 53 00 00 55 AA .WINBOOT SYS..Uª 00000200 F8 FF FF FF FF FF 04 00 FF FF 06 00 FF FF 08 00 øÿÿÿÿÿ..ÿÿ..ÿÿ.. So if that is where guestfish is looking for the partition table... I searched for other references. Found this one and it agreed with this 0x1BE value. http://www.win.tue.nl/~aeb/partitions/partition_types-2.html Any other locations that you know of?

...the wiki (which I already repeated here in this email). The result > of using font files with different characteristics than those that are > expected by Syslinux is unknown / undetermined. > > Regards, > Ady. seel also if you didn't came across it yet: https://www.win.tue.nl/~aeb/linux/kbd/font-formats-1.html especially the last paragraph. So both syslinux and the psf1 format were designed by hpa <smile> Best, Didier

Hello, would it be possible to update config.sub and config.guess to the latest versions (or at least version from automake-1.13.1) in order to support new architectures based on the ARM 64 bit CPU? Patch: http://plautrba.fedorapeople.org/openssh/openssh-latest-config.sub-config.guess.patch Related Fedora bug: https://bugzilla.redhat.com/show_bug.cgi?id=926284 Thanks, Petr

Hi. I was trying to make syslinux to display russian letters. This page https://wiki.syslinux.org/wiki/index.php?title=Directives/font says that for Cyrillic you need a CP855. Is that correct? All other guides in internet say that you need CP866. I finally got it working. My config file was encoded in ibm866 correctly, but the problem was the font file itself. I am on Arch Linux, so I run gunzip

I have continous oom&panic situation unresolved. I am not sure system fills up all the ram (36GB). Why this system triggered this oom situation? Is it about some other memory? highmem? lowmem? stack size? Best Regards, Kernel 3.10.24 Dec 27 09:19:05 2013 kernel: : [277622.359064] squid invoked oom-killer: gfp_mask=0x42d0, order=3, oom_score_adj=0 Dec 27 09:19:05 2013 kernel: :

...cwi.nl [192.16.201.185]) by hera.cwi.nl with ESMTP id LAA13535 for ; Sat, 5 Dec 1998 11:47:24 +0100 (MET) Received: by texel.cwi.nl id LAA103995; Sat, 5 Dec 1998 11:47:24 +0100 (MET) Date: Sat, 5 Dec 1998 11:47:24 +0100 (MET) From: Andries.Brouwer@cwi.nl Message-Id: <UTC199812051047.LAA103995.aeb@texel.cwi.nl> To: allbery@kf8nh.apk.net, linux-security@redhat.com Subject: [linux-security] Re: Red Hat 5.2's login doesn't do PAM session management correctly Cc: linux-afs@mit.edu X-moderate: yes > I have a temporary patch to util-login which restores the original behavior This w...