exim macro DEBCONFstringOK_config_ad [ David Baron <d_baron@012.net.il> ]
Re: Dual Boot With Win XP - Debian F [ "Russell L. Harris" <rlharris@oplin ]
Date: Wed, 27 Jun 2007 11:34:36 +0100
From: Jose Rodriguez <josec.rodriguez@gmail.com>
To: debian-user@lists.debian.org
Subject: Re: IPW3945 With Etch
Message-ID: <20070627113436.2fcfd49e.josec.rodriguez@gmail.com>
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
On Wed, 27 Jun 2007 10:10:08 +0200
Anthony Campbell <ac@acampbell.org.uk> wrote:
> On 27 Jun 2007, Jose Rodriguez wrote:
> >
> > > I was able to get it working but only after enabling SSID
> > > broadcasting on the AP. This is odd but it works. I wonder
> > > why this is?
> > >
> > > -Tom
> >
> > I don't know the technical reason whatsoever, just know it
> > happens out of my own experience. The point is: why on earth
> > would you want to hide the ssid? Certainly not as a security
> > measure. Even worse, depending on how crowded your area is,
> > you may end up with some of your neighbours dwelling in the
> > same channel as you are for they don't "see" you, interfering
> > your precious data.
> >
>
> Presumably to reduce the chance that people nearby will use up
> your bandwidth.
>
> From the online documentation for my Netgear DG834G:
>
> "The default SSID is Wireless, but NETGEAR strongly
> recommends that you change your networks Name (SSID) to a
> different value."
>
Changing and hiding the name of the station is not the
same thing. The security value of both things is, however, zero.
Broadcasting the ssid was never intended to be a security measure.
Have a look at the following:
"The six dumbiest ways to secure a wireless LAN":
http://blogs.zdnet.com/Ou/index.php?p=43
Funny video of somebody cracking a *WPA* protected network:
http://www.mirrors.wiretapped.net/security/vulnerability-assessment/aircrack/whax-aircrack-wpa/whax-aircrack-wpa.html
General information about wireless networking:
http://wireless.wikia.com/wiki/Wi-Fi#Wi-Fi_Security_Myths
Date: Wed, 27 Jun 2007 13:13:38 +0100
From: "Karl E. Jorgensen" <karl@jorgensen.org.uk>
To: debian-user@lists.debian.org
Subject: Re: Any ksh Raw binaries Out there that work for linux i386?
Message-ID: <20070627121338.GE8073@einstein.jorgensen.org.uk>
Content-Type: multipart/signed; micalg=pgp-sha1;
protocol="application/pgp-signature"; boundary="lkTb+7nhmha7W+c3"
Content-Disposition: inline
--lkTb+7nhmha7W+c3
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Tue, Jun 26, 2007 at 06:39:31PM -0400, Orestes leal wrote:
> Hi folks!
>=20
> I need ksh (The Korn Shell), but in binary form, what site you can recomm=
end me to download this binary version
> of ksh for linux i386, a web or ftp site with this file it's well accepte=
d.
>=20
> NOTE: I know that it's in the repository but I need the raw binary for 38=
6.
You can easily extract the raw binary out of the .deb file:
$ cd /tmp
$ wget http://http.us.debian.org/debian/pool/main/k/ksh/ksh_93r-1_i386.=
deb
# it's about 1.1 Mb
$ dpkg --extract ksh_93r-1_i386.deb /tmp/kshstuff
$ ls -l /tmp/kshstuff/bin/ksh93
Obviously you don't have to use the US mirror, there are others:
http://packages.debian.org/cgi-bin/download.pl?arch=3Di386&file=3Dpool%=
2Fmain%2Fk%2Fksh%2Fksh_93r-1_i386.deb&md5sum=3De25b1f0123cd96ced834e12cb1b4=
92f8&arch=3Di386&type=3Dmain
If you're doing it on a non-debian system, you can still extract it:
$ ar x ksh_93r-1_i386.deb
$ mkdir kshstuff
$ cd kshstuff
$ tar -xvf ../data.tar.gz
$ ls -l /tmp/kshstuff/bin/ksh93
Obviously, you will still need the shared libraries it depends on for it=20
to actually work. And possible other run-time support files. But most=20
Linux systems should have that available.
Hope this helps
--=20
Karl E. Jorgensen
karl(at)jorgensen.org.uk http://www.jorgensen.org.uk/
karl(at)jorgensen.com http://karl.jorgensen.com
=3D=3D=3D=3D Today's fortune:
Buy the negatives at any price.
--lkTb+7nhmha7W+c3
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFGglRyi+PVvwZpXJgRAhYeAKCAYlfx9zM4f0yoMuKhfFf0gFgZcACgg5+D
se1An0t/f9iA7T/ETHKhQkI=
=06fP
-----END PGP SIGNATURE-----
--lkTb+7nhmha7W+c3--
Date: Tue, 26 Jun 2007 15:39:27 -0400
From: Matthew K Poer <matthewpoer@gmail.com>
To: debian-user@lists.debian.org
Subject: Font issues when Printing to PDF with the KDE Psuedo-Printer
Message-Id: <200706261539.39804.matthewpoer@gmail.com>
Content-Type: multipart/signed;
boundary="nextPart14977864.WTqu5LD4Eg";
protocol="application/pgp-signature";
micalg=pgp-sha1
Content-Transfer-Encoding: 7bit
--nextPart14977864.WTqu5LD4Eg
Content-Type: text/plain;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
Everytime I print a PDF file from Kword, the font is jumbled up, and I do n=
ot=20
understand why. I have tried Arial, Times New Roman, and Bitsteam Vera Seri=
f.
What can I do to make these fonts appear correctly?
I have an example of a document pritned from the OpenOffice PDF printer and=
=20
the KDE (Kword) PDF printer, mentioned here:
http://matthewpoer.freehostia.com/wordpress/2007/06/15/win-and-loss-for-kde/
=2D-=20
Matthew K Poer <matthewpoer@gmail.com>
Location: GA, USA Web:
http://matthewpoer.freehostia.com
GnuPG Public Key: 4DD0A9A6 Keyserver: subkeys.pgp.net
--nextPart14977864.WTqu5LD4Eg
Content-Type: application/pgp-signature
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQBGgWt7kRdiiE3QqaYRAt+NAJ0Q4Jcq9XTxgIGflwHkZspoMK53ZgCfcaK8
8DA5yiz9dnAW608zGWFQpcY=
=nClS
-----END PGP SIGNATURE-----
--nextPart14977864.WTqu5LD4Eg--
Date: Wed, 27 Jun 2007 20:17:37 +0800
From: Bob <spam@homeurl.co.uk>
To: debian-user@lists.debian.org
Subject: Re: Dual Boot With Win XP - Debian First?
Message-ID: <46825561.7070901@homeurl.co.uk>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
russ421@aol.com wrote:
> I want to dual boot windows XP and Debian. I've seen the guides, but
> they all recommend that users have Windows XP installed first, and
> then install Debian. This allows you to set it up with the default
> Debian installation to use GRUB / etc. and dual boot.
>
> However, I won't have a copy of Win XP for my new machine for a month
> or two probably. I'd like to go ahead and install Debian, otherwise
> the new computer will be a paperweight.
>
> Is it possible to install Debian first and then Windows XP later on?
> Can you change the Debian configurations? Is it not too difficult?
> Impossible?
>
> I'm installing on two separate hard drives, so partitions shouldn't be
> a big problem I don't imagine. Debian on one, XP on the other.
There are a lot of ways to do this, the best one is to use something
like the approach suggested by Chris Lale, make sure you have an
alternative way of booting your debian install (you could even have
/boot on a USB pen drive) and a Knoppix CD handy.
It took me ages to get round to figuring out and trust dual booting,
(for a long while lilo or grub couldn't boot WinNT) since your using 2
physical drives you can setup linux on /hda and then when you set up Win
XP pull out the Linux drive and swap in the windows one, perform your
install as usual and then move the windows drive to hdb (actually better
hdc so you avoid 2 drives sharing a cable if you can) as windows doesn't
mind being moved after install (neither does linux with some care but
it's harder) then you can get Grub to boot windows for you, or use BIOS
to boot a different drive, independently.
Also while you have 2 drives you can stick a dedicated linux swap
partition on your windows drive and vice versa, effectively giving the
virtual memory for what ever OS you happen to be running a dedicated
spindle, for ease of moving things around leave your windows partition
as the first on the drive and get to know the ntfs tool on Knoppix, they
rock.
Good luck
--
Garrr, do your bit for global warming, become a pirate, you can "borrow" my copy of Windows 95 if you want.
Date: Wed, 27 Jun 2007 08:33:26 -0400
From: Orestes leal <orestesleal13022@cha.jovenclub.cu>
To: debian-user@lists.debian.org
Subject: Re: Any ksh Raw binaries Out there that work for linux i386?
Message-Id: <20070627083326.7b992163.orestesleal13022@cha.jovenclub.cu>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
On Tue, 26 Jun 2007 22:54:55 -0500
John Hasler <jhasler@debian.org> wrote:
> Ore writes:
> > I know that it's in the repository but I need the raw binary for 386.
>=20
> I don=B4t understand what you mean by =A8raw binary=A8. What=B4s wrong w=
ith the
> binary in the ksh package?
> --=20
> John Hasler
Well, I don't speak english to good, I meant a Ksh Binary that works in eve=
ry linux distro,
hope that makes clear the point.
Best,
Orestes
--=20
Orestes <orestesleal13022@cha.jovenclub.cu>
Date: Wed, 27 Jun 2007 06:58:09 -0500
From: Hugo Vanwoerkom <hvw59601@care2.com>
To: debian-user@lists.debian.org
Subject: Re: Pivot monitor with X.org
Message-ID: <f5tjcj$ruh$1@sea.gmane.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Masatran, R. Deepak wrote:
> I intend buying a pivot monitor (the wide-screen becomes a tall-screen). But
> how can I tell X.org to rotate the output image by a right angle? Also, can
> X.org handle tall resolutions like 900x1440 (instead of 1440x900)?
>
In my .fvwm2rc:
...
Key F9 A S Exec xrandr -o left
Key F10 A S Exec xrandr -o normal
...
then shift-F9 turns the screen to portrait.
But what good is that if VT-textmode does not turn also?
Hugo
Date: Wed, 27 Jun 2007 08:38:51 -0400
From: Douglas Allan Tutty <dtutty@porchlight.ca>
To: debian-user@lists.debian.org
Subject: Re: Migrate kernel 2.4 to 2.6
Message-ID: <20070627123851.GA7233@titan>
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
On Wed, Jun 27, 2007 at 07:50:45AM -0000, Qnick wrote:
> I have a box ((Fujitsu-Siemens PRIMERGY RX300 S3) within Debian 4.0
> "Etch" and 2.4.31 kernel .
> I very want upgrade it to kernel 2.6.21 but i don't know how do it.
How did you manage to install Etch without udev and with a 2.4 kernel?
For upgrading, the release notes say to upgrade the kernel to 2.6 first.
Doug.
Date: Wed, 27 Jun 2007 06:37:11 -0500
From: Hugo Vanwoerkom <hvw59601@care2.com>
To: debian-user@lists.debian.org
Subject: Re: how hot is my xeon?
Message-ID: <f5ti57$nlv$1@sea.gmane.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Paul Johnson wrote:
> Mike McCarty wrote in Article <467BFF0F.9040201@sbcglobal.net> posted to
> gmane.linux.debian.user:
>
>> michael wrote:
>>> I've tried unsuccessfully to monitor my dual Xeon box but lm-sensors
>>> doesn't seem to detect anything. I've a Intel Server Board SE7320SO2
>> Even if it did, unless you've calibrated the thing you won't know
>> the temp.
>>
>>> with two 3. GHz Xeon chips. Anybody know how to get mobo/chip/internal
>>> temps (and pref fan speeds)... my box gets noisy and I'm trying to see
>>> if it's temp related
>> What's wrong with simply sticking a thermometer in there? I'm talking
>> about a remote-reading one, like those intended to feed a wire through
>> your door or window and hang on the roofline or whatever. That will
>> give you a calibrated temp reading, not an arbitrary meaningless
>> number.
>
> What's wrong with the thermometer supplied by the motherboard, usually in
> contact with the underside of the die? So far, the ones I've come across
> have been in proper working, calibrated order when tested against one of
> those infrared thermometer gun deals.
>
??? my mobo supplied no thermometer
Hugo
Date: Wed, 27 Jun 2007 08:50:44 -0400
From: Douglas Allan Tutty <dtutty@porchlight.ca>
To: debian-user@lists.debian.org
Subject: Re: Any ksh Raw binaries Out there that work for linux i386?
Message-ID: <20070627125044.GB7233@titan>
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Wed, Jun 27, 2007 at 08:33:26AM -0400, Orestes leal wrote:
> On Tue, 26 Jun 2007 22:54:55 -0500
> John Hasler <jhasler@debian.org> wrote:
> > Ore writes:
> > > I know that it's in the repository but I need the raw binary for 38=
6.
> >=20
> > I don=B4t understand what you mean by =A8raw binary=A8. What=B4s wro=
ng with the
> > binary in the ksh package?
>=20
> Well, I don't speak english to good, I meant a Ksh Binary that works in=
every linux distro,
> hope that makes clear the point.
>=20
If you install ksh on your debian box you can then run ldd on it to see
what libraries it was compiled to require. You can then look at your
target linux (that doesn't include a ksh package?) and see if those same
libraries exist there. If so, just copy the binary from the debian
system; it may work.
However, it the libraries differ then they won't be binary compatible.
So, back up. What system are you trying to get ksh onto that doesn't
have it available? Does that target system not have gcc with which you
can compile ksh from source?
Doug.
Date: Wed, 27 Jun 2007 06:41:55 -0500
From: Hugo Vanwoerkom <hvw59601@care2.com>
To: debian-user@lists.debian.org
Subject: Re: stability problem; Asus M2N-MX mobo AMD 64; etch; is it hardware
or software? (apparently solved)
Message-ID: <f5tie4$nlv$2@sea.gmane.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Prismatic Plasma wrote:
> On Tuesday 26 June 2007 16:02, Prismatic Plasma wrote:
>> memtest86 tests 5 and 8 fail with consistency. They give several failures,
>> all in the range 770-880 MB range (1 GB stick). The exact addresses change
>> from pass to pass, but always remain in that range. The other tests reveal
>> no problems.
>>
>> At this point, it's definitely a hardware problem. Can I rule out a
>> configuration problem? What are the chances of it being mobo or cpu rather
>> than ram?
>
> Using the faster memory configuration (CS4-4-4-12), upped voltage to 2.0 V,
> and put memory in second slot seems to have solved the problem. memtest86
> finds no errors, and I was able to compile some large programs without any
> trouble. All 3 of these changes seem to be required. The first memory slot on
> the mobo appears to be bad.
>
Was there a userforum or user review from where you bought the board? I
usually only do mobo's that have a large number of reviews, to find
problems like this.
Hugo
Date: Wed, 27 Jun 2007 08:57:11 -0400
From: Orestes leal <orestesleal13022@cha.jovenclub.cu>
To: debian-user@lists.debian.org
Subject: Re: Any ksh Raw binaries Out there that work for linux i386?
Message-Id: <20070627085711.11521c15.orestesleal13022@cha.jovenclub.cu>
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
On Wed, 27 Jun 2007 13:13:38 +0100
"Karl E. Jorgensen" <karl@jorgensen.org.uk> wrote:
> On Tue, Jun 26, 2007 at 06:39:31PM -0400, Orestes leal wrote:
> > Hi folks!
> >
> > I need ksh (The Korn Shell), but in binary form, what site you can recommend me to download this binary version
> > of ksh for linux i386, a web or ftp site with this file it's well accepted.
> >
> > NOTE: I know that it's in the repository but I need the raw binary for 386.
>
> You can easily extract the raw binary out of the .deb file:
>
> $ cd /tmp
> $ wget http://http.us.debian.org/debian/pool/main/k/ksh/ksh_93r-1_i386.deb
> # it's about 1.1 Mb
> $ dpkg --extract ksh_93r-1_i386.deb /tmp/kshstuff
> $ ls -l /tmp/kshstuff/bin/ksh93
>
> Obviously you don't have to use the US mirror, there are others:
> http://packages.debian.org/cgi-bin/download.pl?arch=i386&file=pool%2Fmain%2Fk%2Fksh%2Fksh_93r-1_i386.deb&md5sum=e25b1f0123cd96ced834e12cb1b492f8&arch=i386&type=main
>
> If you're doing it on a non-debian system, you can still extract it:
> $ ar x ksh_93r-1_i386.deb
> $ mkdir kshstuff
> $ cd kshstuff
> $ tar -xvf ../data.tar.gz
> $ ls -l /tmp/kshstuff/bin/ksh93
>
> Obviously, you will still need the shared libraries it depends on for it
> to actually work. And possible other run-time support files. But most
> Linux systems should have that available.
>
> Hope this helps
yeah, thanks Karl, I did all the steps and passed the binary to my friend,
thanks to you friend.
Best,
Ore.
Date: Wed, 27 Jun 2007 14:03:36 +0100
From: Anthony Campbell <ac@acampbell.org.uk>
To: debian-user@lists.debian.org
Subject: Re: IPW3945 With Etch
Message-ID: <20070627130336.GC22079@acampbell.org.uk>
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
On 27 Jun 2007, Jose Rodriguez wrote:
> On Wed, 27 Jun 2007 10:10:08 +0200
[snip]
> > Presumably to reduce the chance that people nearby will use up
> > your bandwidth.
> >
> > From the online documentation for my Netgear DG834G:
> >
> > "The default SSID is Wireless, but NETGEAR strongly
> > recommends that you change your networks Name (SSID) to a
> > different value."
> >
>
> Changing and hiding the name of the station is not the
> same thing. The security value of both things is, however, zero.
> Broadcasting the ssid was never intended to be a security measure.
> Have a look at the following:
>
> "The six dumbiest ways to secure a wireless LAN":
>
> http://blogs.zdnet.com/Ou/index.php?p=43
[snip]
I take the point about changing and hiding the name are different
things. However, as some of the commenters on the blog cited by you
point out, the situation may be different for a home LAN from a larger
or commercial site. Neighbours may connect to a broadcast ESSID even
without meaning to; I've done this myself in the past and so have our
neighbours, who kindly advised me of the fact.
--
Anthony Campbell - ac@acampbell.org.uk
Microsoft-free zone - Using Linux Gnu-Debian
http://www.acampbell.org.uk (blog, book reviews,
on-line books and sceptical articles)
Date: Wed, 27 Jun 2007 14:18:46 +0200 (CEST)
From: fanen <afanen01@gmail.com>
To: debian-user@lists.debian.org
Subject: same issue
Message-Id: <listhandler=2&site=www.debianhelp.org&nid=8316&pid=&cid=29497&uid=4706&tid=79&ffb75277f319ab2cb52067bb96f6c255@www.debianhelp.org>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: quoted-printable
no devices listed in net admin tool, and users-admin isn't working either=
.
i also suspect it to be related to dbus. i'm using debian sid, and at the=
moment, i can only use my wireless with Network-Manager whenever i find =
access points with dhcp enabled
Date: Wed, 27 Jun 2007 09:03:41 -0400
From: Douglas Allan Tutty <dtutty@porchlight.ca>
To: debian-user@lists.debian.org
Subject: Re: Keyboard problem
Message-ID: <20070627130341.GC7233@titan>
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
On Wed, Jun 27, 2007 at 12:13:58PM +0200, ullrich.schicke@bluecarat.de wrote:
>
> Background:
> Evaluating linux kernels for a series of machines with 16,32 and 128Mb.
> On all machines with have tested a linux kernel 2.4.26 (Damm Small Linux
> 3.1) successfully (including X) with minor problems.
> Switching to linux kernel 2.6.18 (Debian stable Etch) shows the same
> positive result with the exception described below:
>
> The problem:
> Booting a kernel 2.6.18 (actually Debian etch) on the 16Mb machines results
> in a not functional keyboard. The following excerpt from the dmesg log shows
> that a keyboard is found.
Its at least encouraging that you somehow got etch installed on a 16 mb
machine. My 32MB 486 wouldn't upgrade so I transfered the drive to a
larger computer. I found etch significantly slower; text-only non-fb
scrolling and cursor movement jerky, loading mc or lynx slow, etc.
OTOH, it flies very well with either OpenBSD or NetBSD.
Good luck,
Doug.
Date: Wed, 27 Jun 2007 16:27:30 +0300
From: David Baron <d_baron@012.net.il>
To: "debian-user@lists.debian.org" <debian-user@lists.debian.org>
Subject: exim macro DEBCONFstringOK_config_adapted (repost)
Message-id: <200706271627.31222.d_baron@012.net.il>
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: 7BIT
Content-disposition: inline
I want to keep my config files for exim4 for now.
Where do I place this macro and how?
Just says to "do it" :-)
Date: Wed, 27 Jun 2007 08:53:58 -0500
From: "Russell L. Harris" <rlharris@oplink.net>
To: debian-user@lists.debian.org
Subject: Re: Dual Boot With Win XP - Debian First?
Message-ID: <20070627135358.GA22112@cromwell.tmiaf>
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
* Bob <spam@homeurl.co.uk> [070627 07:21]:
> russ421@aol.com wrote:
>> I want to dual boot windows XP and Debian. I've seen the guides, but
>> they all recommend that users have Windows XP installed first, and
>> then install Debian. This allows you to set it up with the default
>> Debian installation to use GRUB / etc. and dual boot.
>>
>> However, I won't have a copy of Win XP for my new machine for a month
>> or two probably. I'd like to go ahead and install Debian, otherwise
>> the new computer will be a paperweight.
>>
>> Is it possible to install Debian first and then Windows XP later on?
>> Can you change the Debian configurations? Is it not too difficult?
>> Impossible?
>>
>> I'm installing on two separate hard drives, so partitions shouldn't be
>> a big problem I don't imagine. Debian on one, XP on the other.
With two hard drives -- one for Debian and one for Window$ -- this is
trivial; I do it routinely.
The use of a separate cable for each drive is nice, but it is not
essential with modern motherboards. If I recall correctly, modern
motherboards incorporate an independent controller for each drive, so
that there is no performance penalty if two drives are attached to the
same cable.
I have no experience with XP, but with W2000 it doesn't matter whether
you install Debian first or Window$ first. However, if you do install
Debian first and wish to ensure that Window$ cannot mess up the
system, simply unplug the Debian drive before you install Window$.
You need not worry about Debian messing up the Window$ installation
(apart from the fact that GRUB is going to replace whatever boot
manager Window$ may install).
Partitioning in Window$ and partitioning in Debian are independent,
UNLESS you put both operating systems on the same drive. But
considering the pitfalls and the low price of drives, I think it
generally foolish to put both operating systems on the same drive.
If you install Window$ first and subsequently install Debian, GRUB
takes care of everything, automatically, and leaves you with a boot
menu which includes both Debian and Window$.
But if you install Debian first and then install Window$, Window$ may
install its own boot manager in place of GRUB. But that's not a
problem; all you need to do in that event is boot Debian and, from a
command line prompt within Debian, reinstall GRUB, whereupon
everything again is taken care of automatically. Of course, in this
event you need to use a GRUB boot CD to boot Debian. So once Debian
is running, make it a priority to burn yourself a GRUB boot CD.
To see how to burn a GRUB boot CD and how to reinstall GRUB, take a
look at the GRUB man page or the GRUB manual. Or just google a bit.
RLH
End of debian-user-digest Digest V2007 Issue #1854
**************************************************
Received on Wed Jun 27 11:20:57 2007