Re: dselect woes

1999-07-30 Thread Dean
Thanks David, worked great. The dselect manual for beginners should definitely have this information. For some reason the manual assumes dselect will handle any and all installing and configuing. I'll leave David's response for manual maintainer. Dean > Presumably you have a lot of .deb fil

Re: dselect woes

1999-07-30 Thread David Wright
Quoting Dean ([EMAIL PROTECTED]): > Since no one has responded will add a few more comments. I now see the > message > is md5sum. I was new installing using apt I downloaded a user profile. > It looked > like apt drew all files from stable main. Just got to the end of all the > downloading when

Re: dselect woes

1999-07-30 Thread Dean
Since no one has responded will add a few more comments. I now see the message is md5sum. I was new installing using apt I downloaded a user profile. It looked like apt drew all files from stable main. Just got to the end of all the downloading when dselect now shows the message md5sum. Have cke

Re: dselect woes

1999-06-01 Thread Ron Hale-Evans
> > I am currently trying to install some packages in Debian 2.0 (using the CD > Rom), using dselect. I can select them without any problem, however when I > choose the option to actually install them, I get the following error > message : > Any help appreciated !! Just a thought: try cleaning th

Re: dselect woes

1999-06-01 Thread shaleh
> > > I am currently trying to install some packages in Debian 2.0 (using the CD > Rom), using dselect. I can select them without any problem, however when I > choose the option to actually install them, I get the following error > message : > > "mount: wrong fs type, bad option, bad superblock

Re: dselect woes

1999-05-26 Thread Hartmut Figge
Kent West wrote: > > On Tue, 25 May 1999 [EMAIL PROTECTED] wrote: > > > > > Can it be! CAN IT BE!! > > > > Am I a complete idiot or is Deselect one of the most diabolical > > programs ever? > > > > > > > Donald MacDougall > > USC School of Medicine > > [EMAIL PROTECTED] > > AMEN! (for the re

Re: dselect woes

1999-05-25 Thread Kent West
On Tue, 25 May 1999 [EMAIL PROTECTED] wrote: > > Can it be! CAN IT BE!! > > Am I a complete idiot or is Deselect one of the most diabolical > programs ever? > > Donald MacDougall > USC School of Medicine > [EMAIL PROTECTED] AMEN! (for the reasons snipped and other similar issues) -- Ke

Re: dselect woes

1999-05-25 Thread Ed Cogburn
[EMAIL PROTECTED] wrote: > > Can it be! CAN IT BE!! > > Am I a complete idiot or is Deselect one of the most diabolical > > programs ever? > > It's so seductive. I've used it quite a number of times. Worked > > beautifully. Then I made a mistake. And each step to try to undo the > > mist

Re: dselect woes

1999-02-05 Thread Mike Schmitz
On Aug 19, Brandon Mitchell wrote > On Tue, 19 Aug 1997, Alfonso E. Urdaneta wrote: > > > I'm trying to use dselect to no avail. First I tried to tell dselect to > > read the cdrom. > > > > chose option a, saw the following > [ error sniped ] > > Is it recognized at boot up (try "more | dmesg"

Re: dselect Woes

1998-10-25 Thread Jim foltz
Hi Patrick, I suggest that you not change the package selections during the initial installation. You can always go back and add/remove packages later. Don't try to add/remove too many things at one time, the dependancies become difficult to sort out. On Sun, Oct 25, 1998 at 03:09:24PM -0500, Pa

Re: dselect Woes

1998-10-25 Thread Antti-Juhani Kaijanaho
On Sun, Oct 25, 1998 at 03:09:24PM -0500, Patrick Durusau wrote: > (I would think "all packages" would mean exactly that but it > apparently does not.) You cannot install everything. This is intentional: the distribution contains many packages which conflict, that is, which cannot coexist in a m

Re: dselect woes

1997-08-19 Thread Carl Fink
> I figure OK, the machine does not like my cdrom drive. Why not try the > insmod driver thing. > > So I type "insmod /dev/cdrom" Actually, insmod means "add a driver to the kernel". (Okay, it means "load a module", but let's not get technical.) For instance, to use my CD-ROM, I have to type

Re: dselect woes

1997-08-19 Thread Mike Schmitz
On Aug 19, Brandon Mitchell wrote > On Tue, 19 Aug 1997, Alfonso E. Urdaneta wrote: > > > I'm trying to use dselect to no avail. First I tried to tell dselect to > > read the cdrom. > > > > chose option a, saw the following > [ error sniped ] > > Is it recognized at boot up (try "more | dmesg"

Re: dselect woes

1997-08-19 Thread Brandon Mitchell
On Tue, 19 Aug 1997, Alfonso E. Urdaneta wrote: > I'm trying to use dselect to no avail. First I tried to tell dselect to > read the cdrom. > > chose option a, saw the following [ error sniped ] Is it recognized at boot up (try "more | dmesg" if you missed it)? If so, just mount it before goi

Re: dselect woes

1997-08-19 Thread Syrus Nemat-Nasser
On Tue, 19 Aug 1997, Alfonso E. Urdaneta wrote: > I'm trying to use dselect to no avail. First I tried to tell dselect to > read the cdrom. [snip] > So I type "insmod /dev/cdrom" > << > /dev/cdrom: /dev/cdrom: No such device > >> You should get your cdrom recognized. What kind of cdrom do you h