Penedo wrote:
[...]
BTW - speaking of which - the new Xen packages documentation in Debian
Etch
seem to assume that the user already knows which package he should use.
Could someone please tell me "yes/no" on weather "
linux-image-2.6.18-3-xen-k7" is the right package to use to run a Xen
machin
> Is there an Ubuntu Live CD image that does a network based install, rather
> than a media based (CD or DVD) install?
(Just go up the path if you want to find mini.iso for other releases... This
is also where you'll find PXE network install bits.)
http://archive.ubuntu.com/ubuntu/dists/edgy/ma
On Thu, 2006-12-14 at 00:01 +1100, Jeff Waugh wrote:
>
>
> > And why doesn't the Ubuntu installer do it automagically?
>
> The installer
> has all the smarts it needs to install the preferred kernel package if it's
> available though.
Oh... maybe I'm asking the wrong question...
Is there an Ub
> a. "on the install media" ONLY,
> b. even in the case where the install has access - at install time - to
> an Ubuntu repository over the Internet,
> c. even in the case where immediately post-install there is access to an
> Ubuntu repository over the Internet.
>
> i.e. for very very small val
On Thu, 2006-12-14 at 00:01 +1100, Jeff Waugh wrote:
> has all the smarts it needs to install the preferred kernel package if it's
> available
So by "available" you mean
a. "on the install media" ONLY,
b. even in the case where the install has access - at install time - to
an Ubuntu repository
Erik,
> Solaris needed that because Solaris' /proc/ file system contains
mostly (all?) binary data.
From what I can see, Solaris' /proc file system is a filesystem to
describe PROCcesses. That it became useful to describe other things is
history I don't quite know about...it's one of the di
On 14/12/06, Peter Miller <[EMAIL PROTECTED]> wrote:
By implication, I don't know what Ubuntu considers "686" when building a
kernel image. I'm guessing that it uses gcc definitions, but that is no
help, since I don't know gcc's mapping, either.
I've just found that "config.guess" exists in
On Thursday 14 December 2006 10:00, [EMAIL PROTECTED] wrote:
> > U cat /proc/cpuinfo
> > do what you like
>
> Hmm, I think this misses the point.
>
> (1) I, personally, do not know all of the things that can be present
> in /proc/cpuinfo
> (2) I, personally, do not know all of the CPUs which gc
On Thu, 2006-12-14 at 08:52 +0900, [EMAIL PROTECTED] wrote:
> U cat /proc/cpuinfo
> do what you like
Hmm, I think this misses the point.
(1) I, personally, do not know all of the things that can be present
in /proc/cpuinfo
(2) I, personally, do not know all of the CPUs which gcc supports, le
On Thursday 14 December 2006 08:50, [EMAIL PROTECTED] wrote:
> > Since dapper, the Ubuntu kernels have automagically handled SMP/UP where
> > appropriate, too. :-)
>
> And still - is there a good way to find out the exact cpu information in a
> useful way for a script? Something a-la the script use
On 14/12/06, Erik de Castro Lopo <[EMAIL PROTECTED]> wrote:
Penedo wrote:
> And still - is there a good way to find out the exact cpu information in
a
> useful way for a script? Something a-la the script used by gcc's source
code
> to automatically decide which architecture it should build for?
> And still - is there a good way to find out the exact cpu information in a
> useful way for a script?
uname -m -p is a good start. Depends how much info you need to know. You can
always use /proc/cpuinfo (family, model, stepping, name, features, bugs) or
you could use dmidecode for ever more i
Penedo wrote:
> And still - is there a good way to find out the exact cpu information in a
> useful way for a script? Something a-la the script used by gcc's source code
> to automatically decide which architecture it should build for? (it's been
> ages since I last built GCC so maybe it's differe
On 14/12/06, Jeff Waugh <[EMAIL PROTECTED]> wrote:
Since dapper, the Ubuntu kernels have automagically handled SMP/UP where
appropriate, too. :-)
And still - is there a good way to find out the exact cpu information in a
useful way for a script? Something a-la the script used by gcc's source
> And why doesn't the Ubuntu installer do it automagically?
In pre-edgy releases, there were -386 and -686 kernel packages. -386 was
installed by default because it was only kernel package that could fit on
the CD (considering priorities), and is maximally compatible. The installer
has all the s
Is there a script which takes the output of /proc/cpuinfo and tells me
weather or not I can use a 686 kernel on a machine?
And why doesn't the Ubuntu installer do it automagically?
(For that matter, mplayer needs this, too.)
--
Regards
Peter Miller <[EMAIL PROTECTED]>
/\/\*http://www.ca
16 matches
Mail list logo
