Pages

Search

problems installing any linux distro - Forums Linux

problems installing any linux distro - Forums Linux

problems installing any linux distro

Posted: 05 Mar 2008 05:42 AM PST

On Wed, 05 Mar 2008 05:42:17 -0800, giaino wrote:
 

You should have seen the error. Either disable APIC in your BIOS or boot
the install kernel with the "noapic" argument.

Does kernel 2.6 include an NSA backdoor?

Posted: 04 Mar 2008 04:19 PM PST

In comp.os.linux.advocacy, Chris Mattern
<gwu.edu>
wrote
on Wed, 05 Mar 2008 16:30:30 -0000
<gwu.edu>: 

Linux does have a protocol -- an implied one.
Communications with the Linux kernel are done using a
callgate/trap mechanism; the mechanisms vary between
processors but Linux is clearly creating a protocol, at
least at the call/return level. For example, to open a
file one has to go through the callgate with the parameters
of filename, open mode, and creation mode. (Most app
developers use higher levels which eventually go through
libc's open() call.)

Depending on the callgate mechanism parameters are in
the registers or on the stack, and additional parameters
may be needed either in registers or on the stack; for
example, in Linux/x86 one has to pass a call identifier
(__NR_open, or the constant 5; these are defined in
/usr/src/linux/asm-i386/unistd.h and correlate with a
dispatch table deep in the kernel) in %EAX. The actual
callgate is INT 80H (or int $0x80 in gas syntax).

There are some issues in binary compatibility which I'd
have to look up but at one point Linux was able to run
old SCO Unix binaries.

Parts of this protocol have been standardized, at
the libc level; for example, POSIX.1-2001 specifies
what open() shall be required to do.

X also has a protocol; one big difference between Linux
and X is that X goes a little deeper, specifying the
actual packets. Since the Linux callgate doesn't bother
with packets to do the actual call, no one's gone to that
detail, although in the case of Linux one can specify
packets of variable size (because of pointers), if need be.

It is far from clear how one would infiltrate the Linux
protocol, though an alternate entrance is available,
namely network packet processing. At this point (AFAIK)
the only leveraging (FSVO) was to crash a running kernel
using the teardrop attack.

This Linux protocol can and has been leveraged; the most
obvious application was UML, which could be construed as
"a linux executable emulating a linux system running a
linux kernel". (QEMU and VmWare run at a lower level,
as I understand it. Note that UML also means "universal
modeling language", which can get a bit confusing.)

--
#191, net
Linux. Because it's there and it works.
Windows. It's there, but does it work?

--
Posted via a free Usenet account from http://www.teranews.com

Torvalds Was Wrong (was: Problem with vim)

Posted: 03 Mar 2008 08:58 PM PST

Tom Newton wrote:
 

By the above two paragraphs you seem to be defining yourself as "An
Irritating Troll" "Some merely post drivel, or tirades against
netnannies and netcops, often at a BI of over 20. In general they
cause little real damage to newsgroups." Vide: Subject: 3.2 and
Subject: 4.2 http://www.hyphenologist.co.uk/killfile/anti_troll_faq.htm

You don't really expect us to believe that you haven't read every word
of all the responses to you, do you?
 
 

This is you having "something on the ball?

--
Two Ravens
"Tom Newton, surely the William Topaz McGonagall of
alt.os.linux.slackware, and now, seemingly, comp.os.linux.setup
and comp.os.linux.misc. as well!"

ODE -- The Other Desktop Environment

Posted: 02 Mar 2008 10:12 AM PST

+-------------+
| DO NOT FEED |
| THE TROLL |
+-------------+
|
|
|
_______L______

Debian Etch new install - no DVDROM.

Posted: 01 Mar 2008 08:23 AM PST

On Sun, 02 Mar 2008 22:07:24 +0000, araminska wrote:
 

You can't. It was a crude way to verify that the hard drive was a SATA
drive and that you know the difference. (You'd be surprised how many
people get confused: SATA? SCSI? IDE?)

Okay. one SATA hard drive: sda. Why do you have your IDE DVD drive set
as a Slave? If you have no other IDE drives/devices, it should be a
Master, and, if it's a Master on the Primary IDE controller, it should be
hda.

Make the change, if it is the only IDE drive and edit its listing in
fstab to reflect this. Verify that it is hda. And make a symbolic link
from /dev/cdrom --> hda, if there is a /dev/cdrom device. Reboot and see
if it works.

Stef