Perl CPAN Catch-22 + ADHD (was: How's ...)
* Weaver [22-07/04=Mo 00:43 -0700]: >>> ... your day going? * Will Mengarini [22-07/04=Mo 07:50 -0700]: >> Hairier than Gene Heskett's nostrils, because "up"grading Perl >> from 5.8.8 to 5.34.1 [caused a kind of failure normally fixed >> using the Perl module CPAN, but this time the failure caused >> CPAN itself to fail early enough that it can't fix *itself*.] * Dan Ritter [22-07/04=Mo 11:34 -0400]: > Bullseye comes with 5.32.x; is there a reason that won't work for you? This is a 32-bit frankenlinux that's so old that even the 5.8.8 I was upgrading *from* wasn't available in any compatible package repository; I had to build *that* from source 9 years ago. At least back then I was able to apt-get source perl-suid; this time, I used the vanilla 5.34.1 tarball, and only after I'd built it did I realize how heavily the Debian source for 5.8.8 had been patched with new directories on @INC. At first I thought I could fix that by hacking /etc/profile and /etc/X11/Xsession, but as I kept studying the startup process I realized that even /usr/bin/screen is in /etc/shells, along with /bin/sash and /bin/es (which is actually interesting), so I had to say to hell with it, wait out the heat wave, and build the whole thing *again* just to get a Debian-compatible @INC. Only *then* did I find out about broken CPAN. Bullseye's package repository is as far out of reach as Tau Ceti. * Dan Ritter [22-07/04=Mo 11:34 -0400]: > CPAN is a repository for Perl modules [...] but in general > using the Debian dh-make-perl package to pull a CPAN > module and convert it into a .deb will make you happiest. That fails because of the same Catch-22: dh-make-perl *depends* on CPAN, and CPAN *itself* is broken. All dh-make-perl does is wrap CPAN to integrate it with the Debian package system. But CPAN itself can't update any modules including itself. Any CPAN wrapper, such as dh-make-perl, will be unable to run, because CPAN itself can't run: it die()s (a fatal internal failure) during its initial configuration, because it depends on installed compiled modules that are no longer compatible with 5.34.1, but that can't be recompiled because recompiling them is CPAN's job. At <https://metacpan.org/dist/DhMakePerl/view/dh-make-perl> is the enormous list of compiled modules on which dh-make-perl depends (including CPAN), cheerfully ending with "and possibly others". The whole thing is based on Perl modules, and the only Perl that actually *works* now is the core executable! S, I could theoretically reimplement CPAN purely in core Perl; but that's risky, because there's always a possibility that what I think is core Perl on which I can rely is actually also broken. It makes more sense to use another language completely. Ruby? Tcl? Sure ... but the best choice is actually the one we *know* will *always* be available to anybody in the same predicament on a frankendebian: Bash. * Will Mengarini [22-07/04=Mo 07:50 -0700]: >> Somebody needs to reimplement CPAN in Bash just so we can bootstrap a >> totally broken Perl without needing to run out and buy a new computer. At first it sounds crazy, because, well ... Bash?! But think broadly about what BedPAN needs to do for each broken module: (1) wget the source code from some mirror; (2) compile it by running the same command that CPAN would've run (to find which I can RTFS); (3) test it (again, RTFS); and, if it passed, (4) install it. * Will Mengarini [22-07/04=Mo 07:50 -0700]: >> I mean, how hard can it be (assuming you grok what CPAN >> actually *does*, which I don't yet, and know Bash, which >> I know just enough of to make Greg Wooledge hate me)? Steps 1 & 2 are each extremely complex processes, but each is completely encapsulated in a standard POSIX utility that does not depend on Perl and that is available on practically every non-embedded GNU/Linux system. Invoking utilities like that is what shell code is *for*. Step 3 invokes the output of step 2. Step 4 uses commands like mv, parameterized with shell variables set inside the BedPAN script where the user can easily edit them. Assuming I have to code BedPAN myself, I'll probably just use sudo and not bother to support su, unless somebody complains. Those 4 steps would themselves be wrapped in a monadic function defined in BedPAN; its argument would be the name of the module to install. A different monadic function would have run first, checking whether the module *needed* to be upgraded. (I'm not sure the best way to do that is by checking a mirror for the latest version; maybe it'd be better to run a local test, and accept the module in its older version if it passes its own test. I don't know yet.) Those 2 monadic functions would have been invoked from an outer loop that iterated through an array of modules that might need recompilation. The list needs to include every module that CPAN depends o
Re: installation catch 22
On Sat, Nov 20, 2021, 7:47 AM wrote: > I am able ro login in safe mode which has few commands and I am a new user > so I don't know enough. > See reply below (so messages are read in order). > -Original Message- > From: Kent West > To: debian-user@lists.debian.org > Cc: jasheb...@aol.com > Sent: Fri, Nov 19, 2021 11:10 am > Subject: Re: installation catch 22 > > > > On Fri, Nov 19, 2021 at 9:36 AM wrote: > > > The installation runs through to completion but the system does not boot > up. > I have tried several times with the same result. > > I am able to log in and look at the log file where it informs me that some > firmware > needs to be updated. (red warnings) I have a CD with the firmware but how > do I > install it if the system will not boot? > > > You say the system does not boot up, and yet then you say you're able to > log in. > > Perhaps what you mean is that the system does not boot up into a graphical > system, but that you are getting to a login prompt? > > If so, after logging in, what happens if you run "startx"? > > -- > Kent West<")))>< > Westing Peacefully - http://kentwest.blogspot.com > Hi jashebert! I would encourage you to reply to the debian-user list as a whole, so that others may be able to chime in. When you say "safe mode", I assume you mean that you're choosing the "Safe Mode" option from the first GRUB boot screen menu? If you let the machine boot normally, do you get to a login prompt at all? If so, is it on a text-only screen, or a graphical screen? If so, what happens when you type in your username and password? -- Kent >
Re: installation catch 22
jasheb...@aol.com wrote: > I have been trying to install Debian on an older computer using the CD1 > install. > The installation runs through to completion but the system does not boot up.I > have tried several times with the same result. > I am able to log in and look at the log file where it informs me that some > firmwareneeds to be updated. (red warnings) I have a CD with the firmware > but how do I install it if the system will not boot? > It seems to me that if the system can install it should be able to run as all > of the peripheralsneeded are available. Then I can install the updates. There are install CDs with non-free firmware included. During install, you can choose to add firmware from another disk or USB stick Can you describe "does not boot up" more thoroughly? Where does it stop? -dsr-
Re: installation catch 22
On Fri, Nov 19, 2021 at 9:36 AM wrote: > > The installation runs through to completion but the system does not boot > up. > I have tried several times with the same result. > > I am able to log in and look at the log file where it informs me that some > firmware > needs to be updated. (red warnings) I have a CD with the firmware but how > do I > install it if the system will not boot? > > You say the system does not boot up, and yet then you say you're able to log in. Perhaps what you mean is that the system does not boot up into a graphical system, but that you are getting to a login prompt? If so, after logging in, what happens if you run "startx"? -- Kent West<")))>< Westing Peacefully - http://kentwest.blogspot.com
installation catch 22
I have been trying to install Debian on an older computer using the CD1 install. The installation runs through to completion but the system does not boot up.I have tried several times with the same result. I am able to log in and look at the log file where it informs me that some firmwareneeds to be updated. (red warnings) I have a CD with the firmware but how do I install it if the system will not boot? It seems to me that if the system can install it should be able to run as all of the peripheralsneeded are available. Then I can install the updates.
Re: Systemic Debian bug -- was [Re: BUSTER install - CATCH-22]
On 2019-04-03, Richard Owlett wrote: > > I was going to document here the work-a-round I successfully used > yesterday to install desired additional packages. There's a bug report concerning this from 2014. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=745381 In that thread our very own Brian P. states: It would appear that on Wheezy it is necessary for '--no-auto-detect' to be added to the apt-cdrom command to get sources.list written to. On Jessie 'sudo apt-cdrom -d /media/usb0 add' works with or without this option. I guess the above holds true for Stretch and Buster, buster (but it's only a guess)? > Before doing so, I attempted to duplicate the steps performed yesterday. > I received a strange error message. I suspect I know the source of the > problem(s). It will take at least a day to document. > > > -- “Let us again pretend that life is a solid substance, shaped like a globe, which we turn about in our fingers. Let us pretend that we can make out a plain and logical story, so that when one matter is despatched--love for instance-- we go on, in an orderly manner, to the next.” - Virginia Woolf, The Waves
Re: Systemic Debian bug -- was [Re: BUSTER install - CATCH-22]
Richard Owlett writes: > At this point, the same cognoscenti who bemoan Linux lacking market > penetration tell him to go read some techie manuals and perform arcane > incantations. As true ostriches they insist the problem is "operator > error". This is a good way to not get any help. -- John Hasler jhas...@newsguy.com Elmwood, WI USA
Re: Systemic Debian bug -- was [Re: BUSTER install - CATCH-22]
On Wed, Apr 3, 2019, 8:26 AM Richard Owlett wrote: > > At this point, the same cognoscenti who bemoan Linux lacking market > penetration tell him to go read some techie manuals and perform arcane > incantations. As true ostriches they insist the problem is "operator > error". > This is a misperception. Linux rules the data center, not the desktop. Therefore the vast bulk of Linux installs are not done this way. Instead, entirely by network. I haven't heard anyone else complain about the mount message I don't believe. Now I think that the specific volume information displayed is just the text in sources.list. So perhaps you could replace it with your desired text. I was going to document here the work-a-round I successfully used > yesterday to install desired additional packages. > > Before doing so, I attempted to duplicate the steps performed yesterday. > I received a strange error message. I suspect I know the source of the > problem(s). It will take at least a day to document. > > >
Systemic Debian bug -- was [Re: BUSTER install - CATCH-22]
Rather than quote my original post, I'll restate the underlying problem. In the beginning, Joe Average would obtain Debian on a set of physical installation CDs. He boots from it. The installer does it's thing. Later, desiring additional software, he inserts the same CD and allows Synaptic to do it's thing. Time passes. Joe obtains a USB flash drive whose content is an image of the installation CD/DVD. It came with instructions on how to boot from it. The installer does it's thing. Later, wanting additional software, he inserts the flash drive. Synaptic tells him to insert a non-existent CD/DVD in a possibly non-existent drive. At this point, the same cognoscenti who bemoan Linux lacking market penetration tell him to go read some techie manuals and perform arcane incantations. As true ostriches they insist the problem is "operator error". I was going to document here the work-a-round I successfully used yesterday to install desired additional packages. Before doing so, I attempted to duplicate the steps performed yesterday. I received a strange error message. I suspect I know the source of the problem(s). It will take at least a day to document.
Re: BUSTER install - CATCH-22
On Tue, Apr 02, 2019 at 05:33:05AM -0500, Richard Owlett wrote: [...] > I was wondering about that. I've never had a clear understanding of > when to use 1 slash and when to use 3. I assumed that in this case 1 > was acceptable because how Synaptic's error message was phrased when > attempting Edit --> Reload Package Information. Wikipedia [1] is your friend. The short version: in the three-slashes variant, there's a little space between the two last, where you could put a hostname (you see it now, when you squint?). If that host name is empty, 'localhost' is assumed. But in the case of localhost, you can leave out the two leading slashes altogether. So file:///foo/bar and file:/foo/bar are equivalent and both mean file://localhost/foo/bar. Whether your strange desktop software (sorry, I couldn't resist) implements that correctly or not is quite another story, though. Cheers [1] https://en.wikipedia.org/wiki/File_URI_scheme#How_many_slashes? -- t signature.asc Description: Digital signature
Re: BUSTER install - CATCH-22
On 04/01/2019 06:11 PM, Jason wrote: On Mon, Apr 01, 2019 at 07:23:49AM -0500, Richard Owlett wrote: On 03/31/2019 08:55 AM, bw wrote: In-Reply-To: The installation, having put the DVD1 ISO on a flash drive, encountered no problems *HOWEVER* I need several packages [gparted, tcl, tk] which are in the DVD image. Synaptic is unable to install them: 1. sources.list refers to a non-existent physical DVD. 2. the default installation has no way of informing Synaptic that it should look for an alternate iso image. 3. modifying sources.list was unsuccessful I added the line deb "file:/media/richard/Debian testing amd64 1/debian" buster contrib main Looking at one of my sources.list files, I wonder if it shouldn't be deb "file:///media/ ... (3 slashes instead of 1) ?? I was wondering about that. I've never had a clear understanding of when to use 1 slash and when to use 3. I assumed that in this case 1 was acceptable because how Synaptic's error message was phrased when attempting Edit --> Reload Package Information. The line left by the installer usually looks something like: deb cdrom:[Name of CD/DVD - The word Official and the Date]/ buster main Yes, but ... By default automount of flash drives is enabled and /media/richard/Debian testing amd64 1/debian is how the system identifies the mounted flash drive. [And I've forgotten how to disable automount] My experience with automounters is that if you unmount / eject manually, it won't auto remount until you unplug and replug the drive. So from the file manager, select the mount point and from the right click menu select 'unmount', 'eject', 'safely remove', or whatever your file manager calls it, and then you should be able to mount it manually (from a terminal) wherever you want it. $ sudo mount /dev/$DEVICE /media/cdrom That's not so clear cut. MATE's Caja offers 2 choices ["Eject" and "Safely Remove Drive"]. Both remove it from MATE's Places menu. Using a subsequent mount command will mount it "read only". Have not checked for other ramifications. and if you mount either the usb or the .iso to /media/cdrom then apt can find it and you can continue installing pkgs from it after first boot. Can't do that as it is already mounted. Tried another workaround and crashed the system. Doing a re-install now. As I've work to do, I'll install manually install the needed packages before closing the installer. Haven't people warned you that apt or apt-get is preferred over synaptic? Opinions differ ;/ Do it the easy way. That's why I use Synaptic. Besides I suspect a typical user will use a GUI when possible. I have found a problem and believe I should document it. Besides, before retirement, I was an inspector. Concern for "minor" details is my nature. Thank you. I believe synaptic lets you configure the sources without manually editing sources.list. See Settings > Repositories . I found that after I posted. Didn't have time to fully investigate. I didn't act as I expected. Need to pursue documentation.
Re: BUSTER install - CATCH-22
On Mon, Apr 01, 2019 at 07:23:49AM -0500, Richard Owlett wrote: > On 03/31/2019 08:55 AM, bw wrote: > >In-Reply-To: > > > > > >>The installation, having put the DVD1 ISO on a flash drive, encountered > >>no problems > >> > >> > >>*HOWEVER* I need several packages [gparted, tcl, tk] which are in the DVD > >>image. > >> > >> > >>Synaptic is unable to install them: > >> 1. sources.list refers to a non-existent physical DVD. > >> 2. the default installation has no way of informing Synaptic > >> that it should look for an alternate iso image. > >> 3. modifying sources.list was unsuccessful > >> > >>I added the line > >> > >>deb "file:/media/richard/Debian testing amd64 1/debian" buster contrib > >> main Looking at one of my sources.list files, I wonder if it shouldn't be deb "file:///media/ ... (3 slashes instead of 1) ?? > > > > > >The line left by the installer usually looks something like: > >deb cdrom:[Name of CD/DVD - The word Official and the Date]/ buster main > > Yes, but ... > By default automount of flash drives is enabled and >/media/richard/Debian testing amd64 1/debian > is how the system identifies the mounted flash drive. > [And I've forgotten how to disable automount] > My experience with automounters is that if you unmount / eject manually, it won't auto remount until you unplug and replug the drive. So from the file manager, select the mount point and from the right click menu select 'unmount', 'eject', 'safely remove', or whatever your file manager calls it, and then you should be able to mount it manually (from a terminal) wherever you want it. $ sudo mount /dev/$DEVICE /media/cdrom > > > > >and if you mount either the usb or the .iso to /media/cdrom then apt can > >find it and you can continue installing pkgs from it after first boot. > > Can't do that as it is already mounted. Tried another workaround and crashed > the system. Doing a re-install now. As I've work to do, I'll install > manually install the needed packages before closing the installer. > > > > >Haven't people warned you that apt or apt-get is preferred over synaptic? > > Opinions differ ;/ > > >Do it the easy way. > > That's why I use Synaptic. > Besides I suspect a typical user will use a GUI when possible. > I have found a problem and believe I should document it. Besides, before > retirement, I was an inspector. Concern for "minor" details is my nature. > > Thank you. I believe synaptic lets you configure the sources without manually editing sources.list. See Settings > Repositories . > > > > > > -- Jason
Re: BUSTER install - CATCH-22
On 04/01/2019 02:51 AM, didier gaumet wrote: Le 31/03/2019 à 15:28, Richard Owlett a écrit : [...] I added the line deb "file:/media/richard/Debian testing amd64 1/debian" buster contrib main to the beginning of sources.list . [...] This is unacceptable when installation via an iso image on a flash drive is becoming more and more common. What package(s) to file bug(s) against? [...] This is unacceptable not to read the apt-cdrom manpage ;-) No indication it refers to anything but mechanical drive. The package to file a bug against is CTK ;-)
Re: BUSTER install - CATCH-22
On 03/31/2019 08:55 AM, bw wrote: In-Reply-To: The installation, having put the DVD1 ISO on a flash drive, encountered no problems *HOWEVER* I need several packages [gparted, tcl, tk] which are in the DVD image. Synaptic is unable to install them: 1. sources.list refers to a non-existent physical DVD. 2. the default installation has no way of informing Synaptic that it should look for an alternate iso image. 3. modifying sources.list was unsuccessful I added the line deb "file:/media/richard/Debian testing amd64 1/debian" buster contrib main The line left by the installer usually looks something like: deb cdrom:[Name of CD/DVD - The word Official and the Date]/ buster main Yes, but ... By default automount of flash drives is enabled and /media/richard/Debian testing amd64 1/debian is how the system identifies the mounted flash drive. [And I've forgotten how to disable automount] and if you mount either the usb or the .iso to /media/cdrom then apt can find it and you can continue installing pkgs from it after first boot. Can't do that as it is already mounted. Tried another workaround and crashed the system. Doing a re-install now. As I've work to do, I'll install manually install the needed packages before closing the installer. Haven't people warned you that apt or apt-get is preferred over synaptic? Opinions differ ;/ Do it the easy way. That's why I use Synaptic. Besides I suspect a typical user will use a GUI when possible. I have found a problem and believe I should document it. Besides, before retirement, I was an inspector. Concern for "minor" details is my nature. Thank you.
Re: BUSTER install - CATCH-22
Le 31/03/2019 à 15:28, Richard Owlett a écrit : [...] > I added the line >> deb "file:/media/richard/Debian testing amd64 1/debian" buster contrib >> main > > to the beginning of sources.list . [...] > This is unacceptable when installation via an iso image on a flash drive > is becoming more and more common. > > What package(s) to file bug(s) against? [...] This is unacceptable not to read the apt-cdrom manpage ;-) The package to file a bug against is CTK ;-)
BUSTER install - CATCH-22
I wish to install Buster on a machine with essentially *NO* internet connectivity. I downloaded the DVD1 ISO on my primary machine [creates secondary problem of being up against data cap]. The installation, having put the DVD1 ISO on a flash drive, encountered no problems *HOWEVER* I need several packages [gparted, tcl, tk] which are in the DVD image. Synaptic is unable to install them: 1. sources.list refers to a non-existent physical DVD. 2. the default installation has no way of informing Synaptic that it should look for an alternate iso image. 3. modifying sources.list was unsuccessful I added the line deb "file:/media/richard/Debian testing amd64 1/debian" buster contrib main to the beginning of sources.list . The Synaptic error message when attempting Edit --> Reload Package Information was > Download is performed unsandboxed as root as file '/media/richard/Debian testing amd64 1/debian/dists/buster/InRelease' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied)The repository 'cdrom://[Debian GNU/Linux testing _Buster_ - Official Snapshot amd64 DVD Binary-1 20190327-09:46] buster Release' does not have a Release file.Updating from such a repository can't be done securely, and is therefore disabled by default.See apt-secure(8) manpage for repository creation and user configuration details.The repository 'file:/media/richard/Debian testing amd64 1/debian buster Release' is not signed. This is unacceptable when installation via an iso image on a flash drive is becoming more and more common. What package(s) to file bug(s) against? Was the syntax of the line added to sources.list correct? How to work around the permission issues in the error message? Ran into something similar when Squeeze was current. I haven't found my correspondence from that time to see if it covers current situation. TIA
Re: How to get around ntpd catch-22?
Good to know. I was going to suggest that maybe your Internet connection was failing, but I did not do so because you checked it with another machine. On 17/08/17 11:04, Kynn Jones wrote: > It appears that the problem was a network misconfiguration (outside of my > control), and it is now resolved. > > Sorry for the confusing query. signature.asc Description: OpenPGP digital signature
Re: How to get around ntpd catch-22?
Dear sir, unfortunately I do not have a solution to your problem, but I want to note that in “Failed to start ntpd.service: Unit nptd.service not found.” the name of ntpd was spelled “nptd”; maybe that is the source of the problem. It does not appear to me that ntp is preventing the network from restarting, because I see a line “-- The start-up result is done.”. Though I can easily be wrong, as I am no expert in systemd. However, if the ntp package is really causing a problem, and reinstalling is not possible, the obvious solution would be to remove it, and install it again if required after Internet connection is established. I use chrony instead of ntp. It appears to be better documented, designed and maintained. Regards. On 17/08/17 09:51, Kynn Jones wrote: > I installed Debian on a (legacy) Optiplex 9010 desktop, using a minimal USB > installation image, and netinst. IOW, most of the contents of this > installation came in through the network (which rules out the most serious > hardware issues). > > One day later, the network connection suddenly stopped working, at all. > For example, the response to `ping 8.8.8.8` is now `connect: Network is > unreachable`. > > The problem is with the computer not with the jack, because if I plug a > different computer to the same jack the connection works fine. > > I did not touch any network-related config files, so I can't begin to guess > what could have caused this sudden failure. > > If I run `/etc/init.d/networking restart`, the output just says `Restarting > networking (via systemctl): networking.service`. At the end of this > message I post the relevant lines from the output I get if I then run > `journalctl -xe` immediately after. > > One can see that the restart of the network is failing due to an ntpd > problem. > > If I attempt to restart ntpd, I get the error "Failed to start > ntpd.service: Unit nptd.service not found." > > This makes no sense to me: ntpd was clearly available and working for > several hours before this sudden failure. The package is definitely > installed, and the error above persists even after I run `dpkg-reconfigure > -p low ntp` (which requires no input from me). > > The only fix I can think of at this point would be to reinstall ntp > altogether, but I can't do this without an internet connection, so I have a > Catch-22 situation. > > How can I fix this problem without having an internet connection? > > --- > > Aug 17 10:00:42 myhost ntpd[757]: error resolving pool 3.debian.pool.ntp.org: > Temporary failure in name resolution (-3) > Aug 17 10:00:45 myhost systemd[1]: Stopping Raise network interfaces... > -- Subject: Unit networking.service has begun shutting down > -- Defined-By: systemd > -- Support: https://www.debian.org/support > signature.asc Description: OpenPGP digital signature
Re: How to get around ntpd catch-22?
settings for this are in /etc/systemd/timesyncd.conf. On Thu, 17 Aug 2017, Kynn Jones wrote: Date: Thu, 17 Aug 2017 10:51:15 From: Kynn Jones <kyn...@gmail.com> To: Debian User <debian-user@lists.debian.org> Subject: How to get around ntpd catch-22? Resent-Date: Thu, 17 Aug 2017 14:51:44 + (UTC) Resent-From: debian-user@lists.debian.org I installed Debian on a (legacy) Optiplex 9010 desktop, using a minimal USB installation image, and netinst. IOW, most of the contents of this installation came in through the network (which rules out the most serious hardware issues). One day later, the network connection suddenly stopped working, at all. For example, the response to `ping 8.8.8.8` is now `connect: Network is unreachable`. The problem is with the computer not with the jack, because if I plug a different computer to the same jack the connection works fine. I did not touch any network-related config files, so I can't begin to guess what could have caused this sudden failure. If I run `/etc/init.d/networking restart`, the output just says `Restarting networking (via systemctl): networking.service`. At the end of this message I post the relevant lines from the output I get if I then run `journalctl -xe` immediately after. One can see that the restart of the network is failing due to an ntpd problem. If I attempt to restart ntpd, I get the error "Failed to start ntpd.service: Unit nptd.service not found." This makes no sense to me: ntpd was clearly available and working for several hours before this sudden failure. The package is definitely installed, and the error above persists even after I run `dpkg-reconfigure -p low ntp` (which requires no input from me). The only fix I can think of at this point would be to reinstall ntp altogether, but I can't do this without an internet connection, so I have a Catch-22 situation. How can I fix this problem without having an internet connection? --- Aug 17 10:00:42 myhost ntpd[757]: error resolving pool 3.debian.pool.ntp.org: Temporary failure in name resolution (-3) Aug 17 10:00:45 myhost systemd[1]: Stopping Raise network interfaces... -- Subject: Unit networking.service has begun shutting down -- Defined-By: systemd -- Support: https://www.debian.org/support --
Re: How to get around ntpd catch-22?
Have you tried: sudo -H systemd-timesyncd.service sudo -H timedatectl set-ntp true timedatectl or journalctl -f -u systemd-timesyncd.service to monitor the service? On Thu, 17 Aug 2017, Kynn Jones wrote: Date: Thu, 17 Aug 2017 10:51:15 From: Kynn Jones <kyn...@gmail.com> To: Debian User <debian-user@lists.debian.org> Subject: How to get around ntpd catch-22? Resent-Date: Thu, 17 Aug 2017 14:51:44 + (UTC) Resent-From: debian-user@lists.debian.org I installed Debian on a (legacy) Optiplex 9010 desktop, using a minimal USB installation image, and netinst. IOW, most of the contents of this installation came in through the network (which rules out the most serious hardware issues). One day later, the network connection suddenly stopped working, at all. For example, the response to `ping 8.8.8.8` is now `connect: Network is unreachable`. The problem is with the computer not with the jack, because if I plug a different computer to the same jack the connection works fine. I did not touch any network-related config files, so I can't begin to guess what could have caused this sudden failure. If I run `/etc/init.d/networking restart`, the output just says `Restarting networking (via systemctl): networking.service`. At the end of this message I post the relevant lines from the output I get if I then run `journalctl -xe` immediately after. One can see that the restart of the network is failing due to an ntpd problem. If I attempt to restart ntpd, I get the error "Failed to start ntpd.service: Unit nptd.service not found." This makes no sense to me: ntpd was clearly available and working for several hours before this sudden failure. The package is definitely installed, and the error above persists even after I run `dpkg-reconfigure -p low ntp` (which requires no input from me). The only fix I can think of at this point would be to reinstall ntp altogether, but I can't do this without an internet connection, so I have a Catch-22 situation. How can I fix this problem without having an internet connection? --- Aug 17 10:00:42 myhost ntpd[757]: error resolving pool 3.debian.pool.ntp.org: Temporary failure in name resolution (-3) Aug 17 10:00:45 myhost systemd[1]: Stopping Raise network interfaces... -- Subject: Unit networking.service has begun shutting down -- Defined-By: systemd -- Support: https://www.debian.org/support --
Re: How to get around ntpd catch-22?
It appears that the problem was a network misconfiguration (outside of my control), and it is now resolved. Sorry for the confusing query.
Re: How to get around ntpd catch-22?
On Thu, Aug 17, 2017 at 10:00:48AM -0500, Mario Castelán Castro wrote: > Dear sir, unfortunately I do not have a solution to your problem, but I > want to note that in “Failed to start ntpd.service: Unit nptd.service > not found.” the name of ntpd was spelled “nptd”; maybe that is the > source of the problem. In fact, they are both wrong, at least in stretch. wooledg:~$ LC_ALL=C systemctl status ntp * ntp.service - LSB: Start NTP daemon Loaded: loaded (/etc/init.d/ntp; generated; vendor preset: enabled) Active: active (running) since Mon 2017-08-07 08:07:33 EDT; 1 weeks 3 days ag Docs: man:systemd-sysv-generator(8) Process: 580 ExecStart=/etc/init.d/ntp start (code=exited, status=0/SUCCESS) Tasks: 2 (limit: 4915) CGroup: /system.slice/ntp.service `-606 /usr/sbin/ntpd -p /var/run/ntpd.pid -g -u 109:113 The service is spelled "ntp.service". There is not currently a systemd unit file for it; it's using the init.d script named "ntp" instead. Beyond that, I have no idea what caused the OP's problem.
How to get around ntpd catch-22?
I installed Debian on a (legacy) Optiplex 9010 desktop, using a minimal USB installation image, and netinst. IOW, most of the contents of this installation came in through the network (which rules out the most serious hardware issues). One day later, the network connection suddenly stopped working, at all. For example, the response to `ping 8.8.8.8` is now `connect: Network is unreachable`. The problem is with the computer not with the jack, because if I plug a different computer to the same jack the connection works fine. I did not touch any network-related config files, so I can't begin to guess what could have caused this sudden failure. If I run `/etc/init.d/networking restart`, the output just says `Restarting networking (via systemctl): networking.service`. At the end of this message I post the relevant lines from the output I get if I then run `journalctl -xe` immediately after. One can see that the restart of the network is failing due to an ntpd problem. If I attempt to restart ntpd, I get the error "Failed to start ntpd.service: Unit nptd.service not found." This makes no sense to me: ntpd was clearly available and working for several hours before this sudden failure. The package is definitely installed, and the error above persists even after I run `dpkg-reconfigure -p low ntp` (which requires no input from me). The only fix I can think of at this point would be to reinstall ntp altogether, but I can't do this without an internet connection, so I have a Catch-22 situation. How can I fix this problem without having an internet connection? --- Aug 17 10:00:42 myhost ntpd[757]: error resolving pool 3.debian.pool.ntp.org: Temporary failure in name resolution (-3) Aug 17 10:00:45 myhost systemd[1]: Stopping Raise network interfaces... -- Subject: Unit networking.service has begun shutting down -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- Unit networking.service has begun shutting down. Aug 17 10:00:46 myhost systemd[1]: Stopped Raise network interfaces. -- Subject: Unit networking.service has finished shutting down -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- Unit networking.service has finished shutting down. Aug 17 10:00:46 myhost systemd[1]: Starting Raise network interfaces... -- Subject: Unit networking.service has begun start-up -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- Unit networking.service has begun starting up. Aug 17 10:00:46 myhost systemd[1]: Started Raise network interfaces. -- Subject: Unit networking.service has finished start-up -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- Unit networking.service has finished starting up. -- -- The start-up result is done. Aug 17 10:00:48 myhost ntpd[757]: error resolving pool 2.debian.pool.ntp.org: Temporary failure in name resolution (-3) Aug 17 10:00:49 myhost ntpd[757]: error resolving pool 1.debian.pool.ntp.org: Temporary failure in name resolution (-3)
Re: catch-22 upgrade (FYI)
Mark Grieveson wrote: Hello. Just some info for those considering upgrading from Sarge to Etch (or Sid). I just upgraded my system from Debian Sarge, to Debian Sid. I initially set out to upgrade to Etch, but circumstances drove me to Sid. I changed the repositories in my sources.list from sarge to etch, and proceded. After a while it gave an error reading, claiming that to upgrade udev, the kernel image had to be greater than 2.6.12 (I was using 2.6.8). When trying to install the 2.6.15 kernel image, it complained that a newer version of udev was required. The xserver protested, committing hare-kare, and I was left using Lynx, and Pico (not the cutting edge software I had been anticipating, needless to say.) Running apt-get -f install did nothing. I then altered the sources from Etch, to Sid, and, giving me hope, various changes occurred. However, it left me with the same message, that the new udev was required. I rebooted using the 2.4.27 kernel image, and ran apt-get -f install, and, strangely enough, it worked. The new kernel installed, udev installed, the xserver came back to life, and I ended up in an XFCE desktop, with my home directory in tact. An unexpected surprise, to be sure, though I'm quite happy to have salvaged my system. I'm hoping one day that I'll be samrt and actually make a back-up of my system before trying stuff like upgrading again. My OpenOffice.org 2.0 (converted from alien) seems to have vanished. I think my gnome desktop environment is a casualty as well, but at least my home directory still exists. The solution to this is to uninstall the initrd-tools package and to install yaird and then install the new kernel. Uhg! I had it working reasonably well, and then THIS EMAIL CAME, and buggered everything up once again! I am going to sentence myself to write, a thousand times over, If it ain't broke, don't fix it. Anyway, after removing initrd-tools, installing yaird, and reinstalling the new kernel image, it broke. Thankfully, I've got my system half working again by reinstalling initrd-tools. My web-server is still not working however, and there's still oodles of errors. Yikes. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: catch-22 upgrade (FYI)
Mark Grieveson wrote: Hello. Just some info for those considering upgrading from Sarge to Etch (or Sid). I just upgraded my system from Debian Sarge, to Debian Sid. I initially set out to upgrade to Etch, but circumstances drove me to Sid. I changed the repositories in my sources.list from sarge to etch, and proceded. After a while it gave an error reading, claiming that to upgrade udev, the kernel image had to be greater than 2.6.12 (I was using 2.6.8). When trying to install the 2.6.15 kernel image, it complained that a newer version of udev was required. The xserver protested, committing hare-kare, and I was left using Lynx, and Pico (not the cutting edge software I had been anticipating, needless to say.) Running apt-get -f install did nothing. I then altered the sources from Etch, to Sid, and, giving me hope, various changes occurred. However, it left me with the same message, that the new udev was required. I rebooted using the 2.4.27 kernel image, and ran apt-get -f install, and, strangely enough, it worked. The new kernel installed, udev installed, the xserver came back to life, and I ended up in an XFCE desktop, with my home directory in tact. An unexpected surprise, to be sure, though I'm quite happy to have salvaged my system. I'm hoping one day that I'll be samrt and actually make a back-up of my system before trying stuff like upgrading again. My OpenOffice.org 2.0 (converted from alien) seems to have vanished. I think my gnome desktop environment is a casualty as well, but at least my home directory still exists. The solution to this is to uninstall the initrd-tools package and to install yaird and then install the new kernel. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
catch-22 upgrade (FYI)
Hello. Just some info for those considering upgrading from Sarge to Etch (or Sid). I just upgraded my system from Debian Sarge, to Debian Sid. I initially set out to upgrade to Etch, but circumstances drove me to Sid. I changed the repositories in my sources.list from sarge to etch, and proceded. After a while it gave an error reading, claiming that to upgrade udev, the kernel image had to be greater than 2.6.12 (I was using 2.6.8). When trying to install the 2.6.15 kernel image, it complained that a newer version of udev was required. The xserver protested, committing hare-kare, and I was left using Lynx, and Pico (not the cutting edge software I had been anticipating, needless to say.) Running apt-get -f install did nothing. I then altered the sources from Etch, to Sid, and, giving me hope, various changes occurred. However, it left me with the same message, that the new udev was required. I rebooted using the 2.4.27 kernel image, and ran apt-get -f install, and, strangely enough, it worked. The new kernel installed, udev installed, the xserver came back to life, and I ended up in an XFCE desktop, with my home directory in tact. An unexpected surprise, to be sure, though I'm quite happy to have salvaged my system. I'm hoping one day that I'll be samrt and actually make a back-up of my system before trying stuff like upgrading again. My OpenOffice.org 2.0 (converted from alien) seems to have vanished. I think my gnome desktop environment is a casualty as well, but at least my home directory still exists. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: catch-22 upgrade (FYI)
Mark Grieveson wrote: I'm hoping one day that I'll be samrt and actually make a back-up of my system before trying stuff like upgrading again. You should always have backups. If you are running unstable, you should make the backups NOW. You never know what is going to happen in the next upgrade. Better be paranoid and have backups ready than loosing months/years of work. My OpenOffice.org 2.0 (converted from alien) seems to have vanished. Why not just install them from unstable repositories (instead of alien)? It is as simple as running apt-get install openoffice.org Unstable currently has openoffice 2.0.1-2 . Also before upgrading from stable to testing or unstable, I think it is a good idea to check http://wiki.debian.org/StatusOfTesting http://wiki.debian.org/StatusOfUnstable hth raju -- Kamaraju S Kusumanchi http://www.people.cornell.edu/pages/kk288/ http://malayamaarutham.blogspot.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: catch-22 upgrade (FYI)
I'm hoping one day that I'll be samrt and actually make a back-up of my system before trying stuff like upgrading again. You should always have backups. If you are running unstable, you should make the backups NOW. You never know what is going to happen in the next upgrade. Better be paranoid and have backups ready than loosing months/years of work. My OpenOffice.org 2.0 (converted from alien) seems to have vanished. Why not just install them from unstable repositories (instead of alien)? It is as simple as running apt-get install openoffice.org Unstable currently has openoffice 2.0.1-2 . Also before upgrading from stable to testing or unstable, I think it is a good idea to check http://wiki.debian.org/StatusOfTesting http://wiki.debian.org/StatusOfUnstable hth raju Thanks for the tips. I did install OpenOffice.org 2.0, and it works well. My main point was how irritating the udev/kernel image catch-22 was. I know others have dealt with this quandary too. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: catch-22 upgrade (FYI)
Sunday, 12 February 2006 12:21, Mark Grieveson wrote: Thanks for the tips. I did install OpenOffice.org 2.0, and it works well. My main point was how irritating the udev/kernel image catch-22 was. I know others have dealt with this quandary too. In my experience, aptitude is quite, eh, apt at resolving that sort of situation, much more so than apt-get. Sometimes, it also helps the resolver in situations like this if you tell it to install both packages at the same time, rather than one after the other. -- Alex Nordstrom http://lx.n3.net/ Please do not CC me in followups; I am subscribed to debian-user. pgpgZMGubxoFP.pgp Description: PGP signature
Re: Display Catch-22
On Mon, May 24, 2004 at 04:09:51PM -0400, Thomas H. George wrote: On Mon, May 24, 2004 at 10:57:52AM -0600, Bob Proulx wrote: Thomas H. George wrote: My Belkin UPS probably saved my computer from the power surge but its internal programming is probably fried. I reinstalled the software from the Linux tarball changing all the ownerships to root:tom and all the permissions to 770. Please be specific. What software did you reinstall? Did you reinstall Debian? Sorry, I took it for granted that I was reinstalling the Belkin Bulldog software for linux which came with the UPS. It is the internal programming in the Belkin UPS that is probably fried. The computer and the Debian kernel and software were unscathed. This allows me to display the monitor but I cannot change the setup. When I originally installed the UPS I did all this as root and was able to change the setup. This is no longer possible as security changes do not allow me to open a display as root. What software are you talking about here? Belkin UPS monitoring software? From Debian or from elsewhere? The Belkin Bulldog software. Is there a good Debian alternative? Maybe. Some Belkin UPS appear to be supported by the nut package, which has both linux and windows versions. I have not used this but you might look into it. If you are using a Belkin universal UPS, you might need to look into the latest version, nut 2.x which has not yet made it into the Debian archives, but the source is available from their homepage. Note that the stable tree appears to have a quite old nut package (I don't know if it supports Belkin UPS), the one in Sarge/testing supports some Belkin UPS, the 2.x version supports more. I don't know if there are other packages that support Belkin. If you have to buy another UPS, you may want to check out which ones are well supported by some UPS packages first (it seems a lot of APC ones are supported). The only thing to change is the com port which I was certain I had right in the first place. To be sure I uninstalled the programs and reinstalled them changing from /dev/ttyS0 to /dev/ttyS1. Neither works though /dev/ttyS0 retrieved some information but in either case the installed software generates periodic messages that the UPS device is unreachable. This is what makes me believe the UPS internal software is fried. Before replacing it I would like to be sure that the display problem is resolved. I have searched the X11, xdm and icewm setup files trying to remove the restriction preventing opening a display as root. My plan would be to take the computer offline (The connection is wireless so ifdown wlan0 does this) during the time the root prohibition is overwridden. I usually use 'ssh -l root -X localhost' to log into the machine as root and tunnel the display back. But other suggest other options. I haven't studied ssh and will do so. I did try entering the command exactly as given above and got connection refused. I'll work on this. You probably don't have a sshd running? If I understand correctly, you are talking about a local X display, but you are (correctly) prevented from logging into X as root? You can log in as your normal user, open an xterm, su to root and then run the Belkin software (as root). It sounds like this is what you are wanting. You can also look into sudo for allowing users to execute some commands with root privileges. -- Chris Harris [EMAIL PROTECTED] --- GNU/Linux --- The best things in life are free. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Display Catch-22
If this is a re-posting, my apologies. The original was reported Mail Delivery Failed and did not appear in the list I downloaded. In another case I re-posted a message after receiving the Mail Delivery Failed notice, the re-posting did appear when I downloaded the list and there was a response to the re-posting telling me that the original was posted to the list. I have reconfigured exim and hope this solves the problem. My Belkin UPS probably saved my computer from the power surge but its internal programming is probably fried. I reinstalled the software from the Linux tarball changing all the ownerships to root:tom and all the permissions to 770. This allows me to display the monitor but I cannot change the setup. When I originally installed the UPS I did all this as root and was able to change the setup. This is no longer possible as security changes do not allow me to open a display as root. The only thing to change is the com port which I was certain I had right in the first place. To be sure I uninstalled the programs and reinstalled them changing from /dev/ttyS0 to /dev/ttyS1. Neither works though /dev/ttyS0 retrieved some information but in either case the installed software generates periodic messages that the UPS device is unreachable. This is what makes me believe the UPS internal software is fried. Before replacing it I would like to be sure that the display problem is resolved. I have searched the X11, xdm and icewm setup files trying to remove the restriction preventing opening a display as root. My plan would be to take the computer offline (The connection is wireless so ifdown wlan0 does this) during the time the root prohibition is overwridden. Any suggestions? Tom George -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Display Catch-22
Thomas H. George wrote: My Belkin UPS probably saved my computer from the power surge but its internal programming is probably fried. I reinstalled the software from the Linux tarball changing all the ownerships to root:tom and all the permissions to 770. Please be specific. What software did you reinstall? Did you reinstall Debian? This allows me to display the monitor but I cannot change the setup. When I originally installed the UPS I did all this as root and was able to change the setup. This is no longer possible as security changes do not allow me to open a display as root. What software are you talking about here? Belkin UPS monitoring software? From Debian or from elsewhere? The only thing to change is the com port which I was certain I had right in the first place. To be sure I uninstalled the programs and reinstalled them changing from /dev/ttyS0 to /dev/ttyS1. Neither works though /dev/ttyS0 retrieved some information but in either case the installed software generates periodic messages that the UPS device is unreachable. This is what makes me believe the UPS internal software is fried. Before replacing it I would like to be sure that the display problem is resolved. I have searched the X11, xdm and icewm setup files trying to remove the restriction preventing opening a display as root. My plan would be to take the computer offline (The connection is wireless so ifdown wlan0 does this) during the time the root prohibition is overwridden. I usually use 'ssh -l root -X localhost' to log into the machine as root and tunnel the display back. But other suggest other options. Any suggestions? Please spend some time reading the following: http://catb.org/~esr/faqs/smart-questions.html Bob pgpGfDzpAa08j.pgp Description: PGP signature
Re: Display Catch-22
On Mon, May 24, 2004 at 10:57:52AM -0600, Bob Proulx wrote: Thomas H. George wrote: My Belkin UPS probably saved my computer from the power surge but its internal programming is probably fried. I reinstalled the software from the Linux tarball changing all the ownerships to root:tom and all the permissions to 770. Please be specific. What software did you reinstall? Did you reinstall Debian? Sorry, I took it for granted that I was reinstalling the Belkin Bulldog software for linux which came with the UPS. It is the internal programming in the Belkin UPS that is probably fried. The computer and the Debian kernel and software were unscathed. This allows me to display the monitor but I cannot change the setup. When I originally installed the UPS I did all this as root and was able to change the setup. This is no longer possible as security changes do not allow me to open a display as root. What software are you talking about here? Belkin UPS monitoring software? From Debian or from elsewhere? The Belkin Bulldog software. Is there a good Debian alternative? The only thing to change is the com port which I was certain I had right in the first place. To be sure I uninstalled the programs and reinstalled them changing from /dev/ttyS0 to /dev/ttyS1. Neither works though /dev/ttyS0 retrieved some information but in either case the installed software generates periodic messages that the UPS device is unreachable. This is what makes me believe the UPS internal software is fried. Before replacing it I would like to be sure that the display problem is resolved. I have searched the X11, xdm and icewm setup files trying to remove the restriction preventing opening a display as root. My plan would be to take the computer offline (The connection is wireless so ifdown wlan0 does this) during the time the root prohibition is overwridden. I usually use 'ssh -l root -X localhost' to log into the machine as root and tunnel the display back. But other suggest other options. I haven't studied ssh and will do so. I did try entering the command exactly as given above and got connection refused. I'll work on this. Any suggestions? Please spend some time reading the following: http://catb.org/~esr/faqs/smart-questions.html Bob Thanks for you assistance. Tom -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Display Catch-22
My Belkin UPS probably saved my computer from the power surge but its internal programming is probably fried. I reinstalled the software from the Linux tarball changing all the ownerships to root:tom and all the permissions to 770. This allows me to display the monitor but I cannot change the setup. When I originally installed the UPS I did all this as root and was able to change the setup. This is no longer possible as security changes do not allow me to open a display as root. The only thing to change is the com port which I was certain I had right in the first place. To be sure I uninstalled the programs and reinstalled them changing from /dev/ttyS0 to /dev/ttyS1. Neither works though /dev/ttyS0 retrieved some information but in either case the installed software generates periodic messages that the UPS device is unreachable. This is what makes me believe the UPS internal software is fried. Before replacing it I would like to be sure that the display problem is resolved. I have searched the X11, xdm and icewm setup files trying to remove the restriction preventing opening a display as root. My plan would be to take the computer offline (The connection is wireless so ifdown wlan0 does this) during the time the root prohibition is overwridden. Any suggestions? Tom George -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Catch 22 ~ base-config console-data
Can someone please help me ~ I am getting error message that
my base-config is not OK because console-data is not configured
{ which I have tried to do in KDE control center}
1) when I try dpkg --configure console-data I get error that
base-config is not completed.
2) when I try dpkg --configure base-config I get error that
console-data is not completed
How can I cut out from this circle, and Fix matters ?
thanks
--
If you are not the intended recipient of this e-mail please alert
someone in authority and destroy it. Reading unauthorised e-mail
during working hours is an offense. Do not condone crime in the office -
just say no. This e-mail indemnifies the sender from all
provision of festive drinks, gratuities, seasonal goodwill or other non
tax deductible expenses.
Re: Catch 22 ~ base-config console-data
On Tuesday, 04. Dec. 2001 at 20:49:11, tabanna wrote:
Can someone please help me ~ I am getting error message that
my base-config is not OK because console-data is not configured
{ which I have tried to do in KDE control center}
1) when I try dpkg --configure console-data I get error that
base-config is not completed.
2) when I try dpkg --configure base-config I get error that
console-data is not completed
Hello tabanna,
try first /usr/sbin/base-config and then dpkg-reconfigure console-data.
Hth Michael
--
Real programmers don't write in Fortran. Fortran is for pipe stress
freaks and crystallography weenies.
Re: Catch 22 ~ base-config console-data
on Tue, Dec 04, 2001 at 08:49:11PM +, tabanna ([EMAIL PROTECTED]) wrote:
Can someone please help me ~ I am getting error message that
my base-config is not OK because console-data is not configured
{ which I have tried to do in KDE control center}
1) when I try dpkg --configure console-data I get error that
base-config is not completed.
2) when I try dpkg --configure base-config I get error that
console-data is not completed
How can I cut out from this circle, and Fix matters ?
Do 'em both at once:
$ dpkg --configure console-data base-config
Peace.
--
Karsten M. Self kmself@ix.netcom.com http://kmself.home.netcom.com/
What part of Gestalt don't you understand? Home of the brave
http://gestalt-system.sourceforge.net/ Land of the free
Free Dmitry! Boycott Adobe! Repeal the DMCA! http://www.freesklyarov.org
Geek for Hire http://kmself.home.netcom.com/resume.html
pgpmot93caD2v.pgp
Description: PGP signature
Re: Catch 22 ~ base-config console-data
On Tue, Dec 04, 2001 at 08:49:11PM +, tabanna wrote: 1) when I try dpkg --configure console-data I get error that base-config is not completed. 2) when I try dpkg --configure base-config I get error that console-data is not completed So 'dpkg --configure base-config console-data'. -- Colin Watson [EMAIL PROTECTED]
Re: Catch 22 ~ base-config console-data
On Tue, 4 Dec 2001, tabanna wrote: How can I cut out from this circle, and Fix matters ? Try: dpkg -i console-data* base-config* Oki
Upgrade Catch-22
Argh. I have a Woody machine that attempted to go through an upgrade last night and is now in dpkg jail. ppp tries to upgrade but bails with: Unpacking replacement ppp ... depmod: Unexpected value (20) in '/lib/modules/2.4.9-686/kern el/drivers/ieee1394/sbp2.o' for ieee1394_device_size It is likely that the kernel structure has changed, if so then you probably need a new version of modutils to handle this kernel. Check linux/Documentation/Changes. dpkg: warning - old post-removal script returned error exit status 255 dpkg - trying script from the new package instead ... [ same depmod err as above] dpkg: error processing /var/cache/apt/archives/ppp_2.4.1.uus-1_i3 86.deb (--unpack): subprocess new post-removal script returned error exit status 255 [ same depmod err as above] dpkg: error while cleaning up: subprocess post-removal script returned error exit status 255 Errors were encountered while processing: /var/cache/apt/archives/ppp_2.4.1.uus-1_i386.deb E: Sub-process /usr/bin/dpkg returned an error code (1) But trying to remove ppp balks with: dpkg: error processing ppp (--remove): Package is in a very bad inconsistent state - you should reinstall it before attempting a removal. Errors were encountered while processing: ppp E: Sub-process /usr/bin/dpkg returned an error code (1) So I can neither go forward nor back. Upgrading modutils directly claims I have the most recent version. I am using the 2.4.9-686 kernel image from the Woody distribution. I don't have a firewire device, nor is the module listed in my module config. I don't even need ppp on this machine. I could ignore this error but it is holding up the upgrade of ~50 other packages. Any nudges in the right direction are greatly appreciated. Thanks, -=greg BTW, I broke up some of the quoted lines above so they don't exceed normal term width. Is there a convention for reporting long-line output in email?
Re: Upgrade Catch-22
I am not in front of my linux box right now. So this from memory. When did this modutils 2.4.10-3 crap make it into testing? It sounds like you are going to have to use method 2. edit /var/lib/dpkg/status to trick dpkg into thinking modutils are not installed. Get a hold of modutils 2.4.8.1 from somewhere. Install this manually with dpkg -i When you use aptitude select modutils place a hold on it. Becareful you must place a hold before every get. Let me know how this works out. By the way this is the back door hack aproach. -Tim -- Original Message -- From: Greg Wiley [EMAIL PROTECTED] Date: Tue, 16 Oct 2001 13:36:45 -0700 Hi Tim- Thanks for your suggestions. I do not use unstable on any machine so I think the problem is that modutils 2.4.10-3 made it into testing. Unfortunately, aptitude isn't going to let me fix it since initrd requires =2.3.13 modutils and the only version (besides 2.4.10-3) available is 2.3.11-13.1 via aptitude (unless there is some option that I'm missing). I think I'm going to have to remove kernel 2.4.9 until modutils is fixed. I have two machines running testing and the second one just did the same thing. Thanks again for your help. At least some learning will come of this. :) -=greg - Original Message - From: Timothy Webster [EMAIL PROTECTED] To: Greg Wiley [EMAIL PROTECTED] Sent: Tuesday, October 16, 2001 12:15 PM Subject: Re: Upgrade Catch-22 This is an easy one to fix. You have 2 choices. 1) use aptitude and select modutiles then select 2.4.8.1 to reinstall (hope I remember the release correctly) anyway just select the release just prior to this one you are having a problem with. 2) edit /etc/apt/sources.list remove all references to unstable using references to testing 3) edit /var/lib/dpkg/status find Package: modutiles edit this package back to non-installed (hope I remember the code correctly) use apt-get or dselect to reinstall the testing version of modutiles This should fix your problem. Aptitude is the simpliest and best solution. -Tim. -- Original Message -- From: Greg Wiley [EMAIL PROTECTED] Date: Tue, 16 Oct 2001 09:50:34 -0700 Argh. I have a Woody machine that attempted to go through an upgrade last night and is now in dpkg jail. ppp tries to upgrade but bails with: Unpacking replacement ppp ... depmod: Unexpected value (20) in '/lib/modules/2.4.9-686/kern el/drivers/ieee1394/sbp2.o' for ieee1394_device_size It is likely that the kernel structure has changed, if so then you probably need a new version of modutils to handle this kernel. Check linux/Documentation/Changes. dpkg: warning - old post-removal script returned error exit status 255 dpkg - trying script from the new package instead ... [ same depmod err as above] dpkg: error processing /var/cache/apt/archives/ppp_2.4.1.uus-1_i3 86.deb (--unpack): subprocess new post-removal script returned error exit status 255 [ same depmod err as above] dpkg: error while cleaning up: subprocess post-removal script returned error exit status 255 Errors were encountered while processing: /var/cache/apt/archives/ppp_2.4.1.uus-1_i386.deb E: Sub-process /usr/bin/dpkg returned an error code (1) But trying to remove ppp balks with: dpkg: error processing ppp (--remove): Package is in a very bad inconsistent state - you should reinstall it before attempting a removal. Errors were encountered while processing: ppp E: Sub-process /usr/bin/dpkg returned an error code (1) So I can neither go forward nor back. Upgrading modutils directly claims I have the most recent version. I am using the 2.4.9-686 kernel image from the Woody distribution. I don't have a firewire device, nor is the module listed in my module config. I don't even need ppp on this machine. I could ignore this error but it is holding up the upgrade of ~50 other packages. Any nudges in the right direction are greatly appreciated. Thanks, -=greg BTW, I broke up some of the quoted lines above so they don't exceed normal term width. Is there a convention for reporting long-line output in email? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Upgrade Catch-22
On Tuesday, October 16, 2001 2:20 PM, [EMAIL PROTECTED] wrote: It sounds like you are going to have to use method 2. edit /var/lib/dpkg/status to trick dpkg into thinking modutils are not installed. Get a hold of modutils 2.4.8.1 from somewhere. Install this manually with dpkg -i When you use aptitude select modutils place a hold on it. Becareful you must place a hold before every get. I just finished a firewire-free kernel compile and the problem is now solved. It looks like there is another thread re: this problem and that it can also be solved by simply removing the offending ( sbp2.o ) module from the tree. doh. Thanks again, -=greg
removal catch-22
I have been plagued by this for a long time, decided to do something about it and messed up. Who has kind words of advice? I'm running Potato 2.2r1 on a P200 desktop. For some reason (honestly, I didn't do it consciously) irda-common-0.9.5-2 was installed, but never wanted to get configured (and I don't even have ir hardware installed). It also wouldn't let itself be removed, claiming that it needed to get re-installed before being able to be removed. Re-install didn't help, so I build a newer deb-version from testing sources. That didn't help either. Installed the older version again, but now things have gone really bad: dselect shows this package as RC**, it says it's in a very bad inconsistent state and should be re-installed before being removed. To make things worse than that, other packages can't be installed now either, because the configuration error of irda-common blocks their configuration. How to get out of this? Thanks for the help. --Hans
Re: removal catch-22
On Thu, May 03, 2001 at 12:18:40PM +0200, Hans wrote: I'm running Potato 2.2r1 on a P200 desktop. For some reason (honestly, I didn't do it consciously) irda-common-0.9.5-2 was installed, but never wanted to get configured (and I don't even have ir hardware installed). It also wouldn't let itself be removed, claiming that it needed to get re-installed before being able to be removed. Re-install didn't help, so I build a newer deb-version from testing sources. That didn't help either. Installed the older version again, but now things have gone really bad: dselect shows this package as RC**, it says it's in a very bad inconsistent state and should be re-installed before being removed. To make things worse than that, other packages can't be installed now either, because the configuration error of irda-common blocks their configuration. How to get out of this? Thanks for the help. --Hans dpkg --force-reinstreq --purge irda-common See dpkg(8) and dpkg --force-help for details. Be warned that this has the potentiol to break your system. Realistically, it's probably ok for this package, especially since you've never actually installed it properly. -- Andrew Suffield [EMAIL PROTECTED] pgp0zZ47qYmwa.pgp Description: PGP signature
Re: removal catch-22
dpkg --force-reinstreq --purge irda-common See dpkg(8) and dpkg --force-help for details. Be warned that this has the potentiol to break your system. Realistically, it's probably ok for this package, especially since you've never actually installed it properly. I think you meant dpkg --force-remove-reinstreq --purge irda-common, but that returned.. Removing irda-common ... Stopping IrDA Manager: dpkg: error processing irda-common (--purge): subprocess post-removal script returned error exit status 1 Stopping irmanager... Stopping IrDA Manager: dpkg: error while cleaning up: subprocess post-installation script returned error exit status 1 Errors were encountered while processing: irda-common Now I just checked the boot messages and saw this... Starting IrDA Manager: sh: /proc/sys/net/irda/devname: No such file or directory irmanager. irmanager is installed, but there isn't an entry in /proc/sys/net for irda. Could this be the reason? --Hans
Re: removal catch-22
On Thu, 3 May 2001, Hans wrote:
dpkg --force-reinstreq --purge irda-common
See dpkg(8) and dpkg --force-help for details. Be warned that this has the
potentiol to break your system. Realistically, it's probably ok for this
package, especially since you've never actually installed it properly.
I think you meant dpkg --force-remove-reinstreq --purge irda-common, but
that returned..
Removing irda-common ...
Stopping IrDA Manager: dpkg: error processing irda-common (--purge):
subprocess post-removal script returned error exit status 1
Stopping irmanager...
Stopping IrDA Manager: dpkg: error while cleaning up:
subprocess post-installation script returned error exit status 1
Errors were encountered while processing:
irda-common
When all else fails, do it manually.
You can edit the entry for the package out of /var/lib/dpkg/status,
then use the info in /var/lib/dpkg/info/package-name.list to rm the
files in the package. You'll also want to check for anything done by
the {pre,post}{inst,rm} scripts in the info dir. Best to keep this
method as a last resort.
Now I just checked the boot messages and saw this...
Starting IrDA Manager: sh: /proc/sys/net/irda/devname: No such file or
directory
irmanager.
irmanager is installed, but there isn't an entry in /proc/sys/net for irda.
Could this be the reason? --Hans
shrug It sounds like you don't have IR stuff for your kernel, I
would expect that to result in warnings when booting, not a broken pkg
DB. Once you get rid of the breakage you should be able to purge
any other IR related packages that were installed, without jumping
through any hoops.
- Bruce
Re: removal catch-22
On Thu, May 03, 2001 at 02:55:56PM +0200, Hans wrote: dpkg --force-reinstreq --purge irda-common See dpkg(8) and dpkg --force-help for details. Be warned that this has the potentiol to break your system. Realistically, it's probably ok for this package, especially since you've never actually installed it properly. I think you meant dpkg --force-remove-reinstreq --purge irda-common, but that returned.. Whoops. Brain fart. Removing irda-common ... Stopping IrDA Manager: dpkg: error processing irda-common (--purge): subprocess post-removal script returned error exit status 1 Stopping irmanager... Stopping IrDA Manager: dpkg: error while cleaning up: subprocess post-installation script returned error exit status 1 Errors were encountered while processing: irda-common The post-removal script will be /var/lib/dpkg/info/irda-common.postrm Edit to taste, removing anything that it looks like you can do without (or take a risk and stick exit 0 at the top). Then try again. (Need I remind you to back the file up first, just in case?) -- Andrew Suffield [EMAIL PROTECTED] pgp18BLSWS5oY.pgp Description: PGP signature
Re: removal catch-22
When all else fails, do it manually.
You can edit the entry for the package out of /var/lib/dpkg/status,
then use the info in /var/lib/dpkg/info/package-name.list to rm the
files in the package. You'll also want to check for anything done by
the {pre,post}{inst,rm} scripts in the info dir. Best to keep this
method as a last resort.
And cautiously he went where he had never been before. There wasn't much
too it, but still
Your hint and common sense while editing the status file helped and all
seems to be right. I had to remove /etc/init.d/irmanager and do an
'update-rc.d irmanager remove'. The docs were already removed. Thanks for
the help. I understand and appreciate Debian GNU/Linux a little more now.
--Hans
?? Lilo, Win NT, MBR problems: a catch 22
At home I have a laptop where win98 and linux co-exist, with lilo offering to boot either one at startup. But at office, after linux installs lilo to MBR, NT won't boot. So, I went to boot floppy, ran fdisk /mbr; but now machine won't boot linux. Boot floppy won't work for linux either. Reinstalled NT from scratch,and it is now the default boot. Since can't boot linux from floppy, I am now reinstalling Potato. But, I get stuck at ? where to put lilo. The /boot thing doesn't work for me. I can boot with shift key down, but then computer hangs and won't accept a number like 2. Shouldn't complain, I guess, but I lost a lot of time today because of this problem. Newbie always appreciates help. TIA,,,dave
Re: ?? Lilo, Win NT, MBR problems: a catch 22
[EMAIL PROTECTED] wrote: At home I have a laptop where win98 and linux co-exist, with lilo offering to boot either one at startup. But at office, after linux installs lilo to MBR, NT won't boot. So, I went to boot floppy, ran fdisk /mbr; but now machine won't boot linux. Boot floppy won't work for linux either. Reinstalled NT from scratch,and it is now the default boot. Since can't boot linux from floppy, I am now reinstalling Potato. But, I get stuck at ? where to put lilo. The /boot thing doesn't work for me. I can boot with shift key down, but then computer hangs and won't accept a number like 2. Shouldn't complain, I guess, but I lost a lot of time today because of this problem. Newbie always appreciates help. TIA,,,dave - I use System Commander 2000 a commercial boot loader that will allow you to do what you want. it is cheap and works flawlessly. It did not work with Win2000 the last time I checked but that may be fixed now. Happy Holidays! John
Re: ?? Lilo, Win NT, MBR problems: a catch 22
Pending further investigation, we now allege that [EMAIL PROTECTED] wrote: At home I have a laptop where win98 and linux co-exist, with lilo offering to boot either one at startup. But at office, after linux installs lilo to MBR, NT won't boot. So, I went to boot floppy, ran fdisk /mbr; but now machine won't boot linux. Boot floppy won't work for linux either. Reinstalled NT from scratch,and it is now the default boot. Since can't boot linux from floppy, I am now reinstalling Potato. But, I get stuck at ? where to put lilo. The /boot thing doesn't work for me. I can boot with shift key down, but then computer hangs and won't accept a number like 2. Shouldn't complain, I guess, but I lost a lot of time today because of this problem. Newbie always appreciates help. TIA,,,dave NT can boot from lilo, just set it up exactly as you would win98. You can also boot linux from ntloader; there's a howto that explains how to do this.
Re: ?? Lilo, Win NT, MBR problems: a catch 22
On Tue, Dec 26, 2000 at 06:25:28PM -0500, [EMAIL PROTECTED] wrote: At home I have a laptop where win98 and linux co-exist, with lilo offering to boot either one at startup. But at office, after linux installs lilo to MBR, NT won't boot. So, I went to boot floppy, ran fdisk /mbr; but now machine won't boot linux. Boot floppy won't work for linux either. Reinstalled NT from scratch,and it is now the default boot. Since can't boot linux from floppy, I am now reinstalling Potato. But, I get stuck at ? where to put lilo. The /boot thing doesn't work for me. I can boot with shift key down, but then computer hangs and won't accept a number like 2. Shouldn't complain, I guess, but I lost a lot of time today because of this problem. Newbie always appreciates help. TIA,,,dave See the Linux+NT-Loader mini-HOWTO (included in the doc-linux-txt package).
Re: ?? Lilo, Win NT, MBR problems: a catch 22
i did this recently, and as a solution i just created a 15MB C: drive for the boot loader(primary partition) then Linux got a /boot partition and NT got it's own primary partition. then i load LILO to the MBR and tell it to boot to C: (which then loads NT's boot loader) to load NT or load linux off it's own partition for linux. ive worked with other ways to do this including copying the boot sectors to a file for nt's boot.ini but i didn't like how that worked. in my experience the above was a better solution. (or just put NT on a FAT partition ..depending on your needs and the size of the HDD ..) nate [EMAIL PROTECTED] wrote: At home I have a laptop where win98 and linux co-exist, with lilo offering to boot either one at startup. But at office, after linux installs lilo to MBR, NT won't boot. So, I went to boot floppy, ran fdisk /mbr; but now machine won't boot linux. Boot floppy won't work for linux either. Reinstalled NT from scratch,and it is now the default boot. Since can't boot linux from floppy, I am now reinstalling Potato. But, I get stuck at ? where to put lilo. The /boot thing doesn't work for me. I can boot with shift key down, but then computer hangs and won't accept a number like 2. Shouldn't complain, I guess, but I lost a lot of time today because of this problem. Newbie always appreciates help. TIA,,,dave -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- ::: ICQ: 75132336 http://www.aphroland.org/ http://www.linuxpowered.net/ [EMAIL PROTECTED]
Catch-22 with modules/backups
I did not install SCSI support during my debian-2.2.17pre6 installation, since I have no SCSI devices. I have one backup mechanism, a CD-Rewritable drive. The CD-Rewritable howto says I need SCSI support. (whoops!) I am eager to try making a debian kernel, to make sure only the drivers I need are there, but first I need to make a backup !!! The module I am missing is sr_mod, which I am told is loadable. dselect knows nothing about scsi or sr_mod, apt-get knows the same. www.google.com has no links to any sources that I can find. If you look for "sr_mod" in the debian packages area, you get nothing, becuase it treats the _ as a space. Two or three people have tried to give me help, but one said "good luck" and the other main one began "Start with a clean .config file" (um, what .config file?) I am using 2.2.17-pre6 and all I want to do is get and load a "loadable device driver". I know I could have gotten this module off of my installation CDs in the first place. Please help, thankfully, Joshua S Narins PS I don't want to install debian on my swap partition, and then try to move the sr_mod module, but I bet it might work.
Re: Catch-22 with modules/backups
Lo, on Saturday, December 23, [EMAIL PROTECTED] did write: I am eager to try making a debian kernel, to make sure only the drivers I need are there, but first I need to make a backup !!! While backups never hurt, a kernel rebuild shouldn't require backups. If you leave out some necessary drivers, you won't be able to boot, but all of your files will still be there and more or less intact. If you save a copy of your previous kernel (always a good idea), then reboot under that image and try another rebuild, including all of the necessary drivers. The module I am missing is sr_mod, which I am told is loadable. dselect knows nothing about scsi or sr_mod, apt-get knows the same. www.google.com has no links to any sources that I can find. If you look for sr_mod in the debian packages area, you get nothing, becuase it treats the _ as a space. Two or three people have tried to give me help, but one said good luck and the other main one began Start with a clean .config file (um, what .config file?) I am using 2.2.17-pre6 and all I want to do is get and load a loadable device driver. I know I could have gotten this module off of my installation CDs in the first place. Loadable modules (or ``loadable device drivers,'' as you call them) are not in separate debian packages; they're all part of the kernel and are thus contained in the kernel-image package, which (I think) should have been installed during your Debian install. Therefore, dselect, apt, and the Debian package list aren't going to know anything about them. The first step is to figure out exactly which drivers you need. Is your CD-RW an ATAPI or a SCSI device? See the table in section 2.1 of the CD-Writing HOWTO for a discussion of the drivers you'll need. Now, my understanding (i.e., educated guess) is that the necessary drivers were installed on your machine, but those modules weren't loaded by default. Type modprobe foo as root to load module foo and any dependencies. If that works, you're good to go. (If you use the ide-scsi module, you'll need to hide your CD-RW drive from the IDE driver. Run `cat /proc/modules'. If you see ``ide-cd'' in the first column, then you're cool. Become root, then create a file called /etc/modutils/local which contains this stuff from the HOWTO: options ide-cd ignore=hdb# tell the ide-cd module to ignore hdb alias scd0 sr_mod# load sr_mod upon access of scd0 pre-install sg modprobe ide-scsi # load ide-scsi before sg pre-install sr_mod modprobe ide-scsi # load ide-scsi before sr_mod pre-install ide-scsi modprobe ide-cd # load ide-cd before ide-scsi then run the commands update-modules # umount any CDs rmmod ide-cd modprobe ide-cd modprobe ide-scsi If, however, ``ide-cd'' is NOT in /proc/modules, then you'll have to adjust lilo.conf, as in the HOWTO, and reboot before you can load ide-scsi.) Otherwise, you'll need to rebuild your kernel, including support for the necessary drivers. See section 8.5 of the Debian installation manual for details on how to do this. (The .config file you refer to is your *kernel* compilation configuration file.) PS I don't want to install debian on my swap partition, and then try to move the sr_mod module, but I bet it might work. Unnecessary. I think the sr_mod module is installed on your system (somewhere under /lib/modules), just not loaded. Hope this helps, Richard
Re: Catch-22 with modules/backups
On Sat, 23 Dec 2000 15:32:34 EST, [EMAIL PROTECTED] said: I did not install SCSI support during my debian-2.2.17pre6 installation, since I have no SCSI devices. I have one backup mechanism, a CD-Rewritable drive. The CD-Rewritable howto says I need SCSI support. (whoops!) I am eager to try making a debian kernel, to make sure only the drivers I need are there, but first I need to make a backup !!! The module I am missing is sr_mod, which I am told is loadable. dselect knows nothing about scsi or sr_mod, apt-get knows the same. www.google.com has no links to any sources that I can find. If you look for sr_mod in the debian packages area, you get nothing, becuase it treats the _ as a space. Two or three people have tried to give me help, but one said good luck and the other main one began Start with a clean .config file (um, what .config file?) You can use your /boot/config-2.2.xx as a bootstrap for your kernel compile .config file. To get the 'sr_mod ' set CONFIG_BLK_DEV_SR=m in SCSI support type. To record on IDE/ATAPI drive you'll need SCSI emulation set for module 'ide-scsi' ; SCSI support for 'scsi-mod' module; SCSI generic for 'sg' module. Also set CONFIG_BLK_DEV_IDECD to N or M and not directly linked to the kernel. When you want to record a cd you'll have to activate the SCSI bus and drivers with modprobe ide-scsi and also run cdrecord -scanbus.
Re: Catch-22 with modules/backups
On 23 Dec 2000 16:27:02 EST, mikpolniak said: On Sat, 23 Dec 2000 15:32:34 EST, [EMAIL PROTECTED] said: I did not install SCSI support during my debian-2.2.17pre6 installation, since I have no SCSI devices. I have one backup mechanism, a CD-Rewritable drive. The CD-Rewritable howto says I need SCSI support. (whoops!) I am eager to try making a debian kernel, to make sure only the drivers I need are there, but first I need to make a backup !!! The module I am missing is sr_mod, which I am told is loadable. dselect knows nothing about scsi or sr_mod, apt-get knows the same. www.google.com has no links to any sources that I can find. If you look for sr_mod in the debian packages area, you get nothing, becuase it treats the _ as a space. Two or three people have tried to give me help, but one said good luck and the other main one began Start with a clean .config file (um, what .config file?) You can use your /boot/config-2.2.xx as a bootstrap for your kernel compile .config file. To get the 'sr_mod ' set CONFIG_BLK_DEV_SR=m in SCSI support type. To record on IDE/ATAPI drive you'll need SCSI emulation set for module 'ide-scsi' ; SCSI support for 'scsi-mod' module; SCSI generic for 'sg' module. Also set CONFIG_BLK_DEV_IDECD to N or M and not directly linked to the kernel. When you want to record a cd you'll have to activate the SCSI bus and drivers with modprobe ide-scsi and also run cdrecord -scanbus. I think this will clarify your situation. Look for the following in /lib/modules/scsi : ide-scsi.o scsi_mod.o sg.o sr_mod.o in /lib/modules/block: ide-cd.o These modules should allow you to use 'cdrecord' to make a recording on your IDE/ATAPI CD-RW. If some of these modules are not listed then they must be directly linked into the kernel, which you can see in your /boot/config-2.2.XX file. If ide-cd is directly linked then you will have to edit lilo.conf and add : append='hdx=ide-scsi' where x is your drive e.g. hdc. This is necessary so that ide-cd does not grab your CD-RW before the ide-scsi module. If you have to compile to get the required modules you can leave out ide-cd since with SCSI emulation you will reference your drive as scd0.
Catch 22 dpkg mystery
Can anyone explain to me how you can install g++ ? I checked debian.org to find that g++ depends on http://www.debian.org/Packages/stable/devel/g++.html thats great, so one of the dependencies is libstdc++2.10-dev But libstdc++2.10-dev depends on g++ http://www.debian.org/Packages/stable/devel/libstdc++2.10-dev.html ARGH !! its a catch22 star dot deb situation, can anyone help?thanks! Richard Jenniss [EMAIL PROTECTED] icq: 28262372
Re: Catch 22 dpkg mystery
Richard Jenniss [EMAIL PROTECTED] writes: Can anyone explain to me how you can install g++ ? I checked debian.org to find that g++ depends on http://www.debian.org/Packages/stable/devel/g++.html http://www.debian.org/Packages/stable/devel/g++.html thats great, so one of the dependencies is libstdc++2.10-dev But libstdc++2.10-dev depends on g++ http://www.debian.org/Packages/stable/devel/libstdc++2.10-dev.html http://www.debian.org/Packages/stable/devel/libstdc++2.10-dev.html ARGH !! its a catch22 star dot deb situation, can anyone help? thanks! Have you actually tried `apt-get install g++`? Circular dependencies are not a problem (unless it's a Pre-Depends one). It merely means that you need both g++ and libstdc++2.10-dev installed in order to _use_ either of them. It does not mean that one has to be installed already before you can install the other. Go ahead, `apt-get install g++` and ask again if that doesn't work (it should). -- Olaf Meeuwissen Epson Kowa Corporation, Research and Development
Re: SANE install catch-22
On Mon, 1 Jan 1996, Ted Llewellyn wrote: Well, this is very pretty.I'm running Debian 2.0 with the default SANE--the doc says v0.71 but I think it's v0.74. I was going to upgrade to version 1.0. To do that, I have to install the new libc6, and to do that I have to upgrade libstdc++2.8, and apparently to do THAT, dpkg has to unconfigure itself. Since I'm running dselect, how is this supposed to work? Here is the output from dselect: dpkg: considering removing libstdc++2.8 in favour of libc6 ... dpkg: no, dpkg is essential, will not deconfigure it in order to enable removal of libstdc++2.8. dpkg: regarding .../base/libc6_2.0.7u-7.1.deb containing libc6: libc6 conflicts with libstdc++2.8 ( 2.90.29-2) libstdc++2.8 (version 2.90.29-0.6) is installed. dpkg: error processing debian/dists/unstable/main/binary-i386/base/libc6_2.0.7u: conflicting packages - not installing libc6 Can you tell why you'd have to upgrade libc6? Quickly looking at the sane and libc6 packages that are currently in 'unstable' I don't see it. It looks like you are trying to install a new libc6 package which conflicts with old libstdc++2.8 packages. You could try to also upgrade the libstdc++2.8 package to a newer version, but I don't know if that would break other things. Remco
SANE install catch-22
Well, this is very pretty.I'm running Debian 2.0 with the default SANE--the doc says v0.71 but I think it's v0.74. I was going to upgrade to version 1.0. To do that, I have to install the new libc6, and to do that I have to upgrade libstdc++2.8, and apparently to do THAT, dpkg has to unconfigure itself. Since I'm running dselect, how is this supposed to work? Here is the output from dselect: dpkg: considering removing libstdc++2.8 in favour of libc6 ... dpkg: no, dpkg is essential, will not deconfigure it in order to enable removal of libstdc++2.8. dpkg: regarding .../base/libc6_2.0.7u-7.1.deb containing libc6: libc6 conflicts with libstdc++2.8 ( 2.90.29-2) libstdc++2.8 (version 2.90.29-0.6) is installed. dpkg: error processing debian/dists/unstable/main/binary-i386/base/libc6_2.0.7u: conflicting packages - not installing libc6 Thanks, Ted
Re: SANE install catch-22
On Mon, Jan 01, 1996 at 20:12:48 +, Ted Llewellyn wrote: Well, this is very pretty.I'm running Debian 2.0 with the default SANE--the doc says v0.71 but I think it's v0.74. I was going to upgrade to version 1.0. To do that, I have to install the new libc6, and to do that I have to upgrade libstdc++2.8, and apparently to do THAT, dpkg has to unconfigure itself. The last part is probably a result of how the dselect access method you use is implemented. There is nothing in libstdc++2.8 that requires dpkg to unconfigure itself. Since I'm running dselect, how is this supposed to work? I suspect this will work if you use apt as dselect's access method. In any case, you should be able to work things out in dselect after you've upgraded libstdc++2.8 through dpkg. Ray -- Tevens ben ik van mening dat Nederland overdekt dient te worden.
Re: SANE install catch-22
Hi Ship's Log, Lt. Ted Llewellyn, Stardate 010196.2012: Date: Mon, 01 Jan 1996 20:12:48 + WOW .. a 2 Year old Email ... :-) did this mail get lost or is your date set a bit wrong ? greetings -- Alexander N. Benner - The Seven Promises of a Promise Keeper: -7- A Promise Keeper is committed to influencing his world, being obedient to the Great Commandment (Mark 12:30f) and the Great Commission (Matt 28:19f).
Re: SANE install catch-22
Is the list catching up on OLD mail or has someone forgotten to set their clock up? Subject: SANE install catch-22 Date: Mon, Jan 01, 1996 at 08:12:48PM + In reply to:Ted Llewellyn Quoting Ted Llewellyn([EMAIL PROTECTED]): Well, this is very pretty.I'm running Debian 2.0 with the default SANE--the doc says v0.71 but I think it's v0.74. I was going to upgrade to version 1.0. To do that, I have to install the new libc6, and to do that I have to upgrade libstdc++2.8, and apparently to do THAT, dpkg has to unconfigure itself. Since I'm running dselect, how is this supposed to work? Here is the output from dselect: dpkg: considering removing libstdc++2.8 in favour of libc6 ... dpkg: no, dpkg is essential, will not deconfigure it in order to enable removal of libstdc++2.8. dpkg: regarding .../base/libc6_2.0.7u-7.1.deb containing libc6: libc6 conflicts with libstdc++2.8 ( 2.90.29-2) libstdc++2.8 (version 2.90.29-0.6) is installed. dpkg: error processing debian/dists/unstable/main/binary-i386/base/libc6_2.0.7u: conflicting packages - not installing libc6 Thanks, Ted -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null -- Windows95 (noun): 32 bit extensions and a graphical shell for a 16 bit patch to an 8 bit operating system originally coded for a 4 bit microprocessor, written by a 2 bit company, that can't stand 1 bit of competition. ___ Wayne T. Topa [EMAIL PROTECTED]
Re: SANE install Catch-22
Well, everyone has picked up on the date. Can anyone answer the question? _ () _-- __() Ted Llewellyn ) _-- / /_--/__--- (/ (/ On Fri, 11 Dec 1998 [EMAIL PROTECTED] wrote: BTW: Your clock has the wrong date (1.1.1996) Alex. On Mon, 1 Jan 1996, Ted Llewellyn wrote: Well, this is very pretty.I'm running Debian 2.0 with the default SANE--the doc says v0.71 but I think it's v0.74. I was going to upgrade to version 1.0. To do that, I have to install the new libc6, and to do that I have to upgrade libstdc++2.8, and apparently to do THAT, dpkg has to unconfigure itself. Since I'm running dselect, how is this supposed to work? Here is the output from dselect: dpkg: considering removing libstdc++2.8 in favour of libc6 ... dpkg: no, dpkg is essential, will not deconfigure it in order to enable removal of libstdc++2.8. dpkg: regarding .../base/libc6_2.0.7u-7.1.deb containing libc6: libc6 conflicts with libstdc++2.8 ( 2.90.29-2) libstdc++2.8 (version 2.90.29-0.6) is installed. dpkg: error processing debian/dists/unstable/main/binary-i386/base/libc6_2.0.7u: conflicting packages - not installing libc6 Thanks, Ted -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null -- Alexander Schwartz ([EMAIL PROTECTED]) http://ourworld.compuserve.com/homepages/alex_schwartz
Re: Catch-22 - Help!
Sergey wrote: The package route is still better, but you don't have to use dselect. There's no problem about using dselect. Tell it you don't have a Packages file, when it asks for the path to the main packages, give it the path you have and tell it to 'scan' for packages. Make all the other paths blank. The Update step will take a bit longer, because it has to open each deb file and look into it, but not ridiculously so. HTH Jiri [EMAIL PROTECTED]
Re: Catch-22 - Help!
First of all, thanks to everyone who responded. Using dpkg is just what I needed to do. However, I now have run into a new problem. I've installed the gcc, binutils, make and patch packages and their dependancies. I patched the 2.0.35 kernal. I followed the instructions at the kernal.org website. Ran make config, make dep, make clean. No obvious problems to this point. Then I ran make zImage (takes awhile!) and it aborted with the following error: as86 -0 -a -o bootsect.o bootsect.s make[1]: as86: Command not found ***[bootsect.o] Error 127 ***[zImage] Error 2 Peeking into the Makefiles, I found as86 defined so: as86=$(CROSS_COMPILE)as86 -0 -a but I was unable to find a def for CROSS_COMPILE. I ran find / *as86 and there were no files found. Is there another package I need to install? Thanks for the help, Jerry At 08:19 AM 10/29/98 +0100, Helge Hafting wrote: In [EMAIL PROTECTED], on 10/28/98 at 12:53 PM, Jerry E. McGoveran [EMAIL PROTECTED] said: I have a Debian installation in which the ethernet card driver is apparently not installed. There were some errors at this stage of the installation process, but the screen drew and reset to the inst. menu too fast to read anything. I finished the installation, and now I need to update the kernel and the drivers. I can't compile a kernel (downloaded 2.0.35 src) because I don't have gcc. I can't install the gcc package because I don't have network access in Linux - only under Win95. My Linux installation has a 2.0.32 kernel with 2.0.34 drivers, and this is probably why the drivers don't work. I'm using the 2.0.32 kernel because the 2.0.34 kernel wasn't working with my AHA2842 SCSI adapter. Questions: 1) Can I get there from here? Sure. 2) How do I install a package assuming I can get the .deb files onto a mounted filesystem? Dselect asks for a series of directory pathnames, and complains when it doesn't find various files and directories within them. Use dpkg. It is guaranteed to be installed, dselect itself use dpkg for installing packages. Use dpkg -i /mountpoint/directories/package_filename.deb This is the manual way for installing debian packages, and the advantage over installing tar-files is that the package management system is used. Dependencies are checked, installation scripts are run, and everything is set up correctly in the proper directories. gcc and lots of other software is available as debian packages from www.debian.org 3) Is there a direct way to update the kernel and/or drivers without having to compile a kernel or use dselect? Dselect is not necessary. It is an interface when dealing with the entire debian distribution. (You don't want to run ftp and dpkg for each of 50 packages you may want to install.) I suggest getting gcc, kernel sources and the other utilities needed for development (make and such) Then compile a 2.0.35 kernel with the drivers you need. You may use dselect for installing further packages when the network is up and running. You can update the kernel by compiling it - or by getting a compiled kernel from someone else. Compiling it yourself is easy though, and you can set it up for exactly the hardware you have. If you have cdrom consider getting the debian cd for about $2 from www.cheapbytes.com or similiar places. It may save you a lot of time. 4) Should I give up on Debian and go buy the RedHat CD and hope for better results? No need, but do as you wish. 5) Why did I want a Linux system in the first place? :/ It is certainly a good idea if you have a pc :-) Helge Hafting Certus Consulting Group | Specializing in Integrated Circuit Antioch, CA 94509 | Design and Verification, Logic (925)757-0685 | Synthesis, Fault Grading, and http://www.certus.com | Test Development
Re: Catch-22 - Help!
On Sat, 31 Oct 1998, Jerry E. McGoveran wrote: Then I ran make zImage (takes awhile!) and it aborted with the following error: as86 -0 -a -o bootsect.o bootsect.s make[1]: as86: Command not found ***[bootsect.o] Error 127 ***[zImage] Error 2 [EMAIL PROTECTED](pa):bhmit1$ dpkg -S as86 bin86: /usr/doc/bin86/examples/as86_encap bin86: /usr/man/man1/as86.1.gz bin86: /usr/bin/as86 So you need to install the bin86 package. Peeking into the Makefiles, I found as86 defined so: as86=$(CROSS_COMPILE)as86 -0 -a but I was unable to find a def for CROSS_COMPILE. I ran find / *as86 and there were no files found. You're cut and paste verifies that CROSS_COMPILE is undefined, otherwise, there would have been something before as86. HTH, Brandon +--- ---+ | Brandon Mitchell * [EMAIL PROTECTED] * http://bhmit1.home.ml.org/ | | Dijkstra probably hates me (Linus Torvalds, in kernel/sched.c) |
Re: Catch-22 - Help!
On Wed, 28 Oct 1998, Jerry E. McGoveran wrote: I have a Debian installation in which the ethernet card driver is apparently not installed. There were some errors at this stage of the installation process, but the screen drew and reset to the inst. menu too fast to read anything. I finished the installation, and now I need to update the kernel and the drivers. I can't compile a kernel (downloaded 2.0.35 src) because I don't have gcc. I can't install the gcc package because I don't have network access in Linux - only under Win95.A Gcc is available at sunsite.unc.edu and most of the mirrors. Download it w/ win95 and then use tar to unpack it. My Linux installation has a 2.0.32 kernel with 2.0.34 drivers, and this is probably why the drivers don't work. I'm using the 2.0.32 kernel because the 2.0.34 kernel wasn't working with my AHA2842 SCSI adapter. Questions: 1) Can I get there from here? Yes. 2) How do I install a package assuming I can get the .deb files onto a mounted filesystem? Dselect asks for a series of directory pathnames, and complains when it doesn't find various files and directories within them. Why not just use the tar.gz files? You do have tar/gz don't you? Also, these are available at sunsite.unc.edu. Use 'make' to configure the kernel. If you have X-Windows, then you can use a really nice GUI. Goto the directory /usr/src/linux and type 'make xconfig;make dep;make clean' _AFTER_ you have installed gcc. The kernel 2.0.35 has an okay version of aic7xxx, you may want to apply the patch. 3) Is there a direct way to update the kernel and/or drivers without having to compile a kernel or use dselect? Notice above. 4) Should I give up on Debian and go buy the RedHat CD and hope for better results? Jumping out of the pot into the fire w/ RedHat (my opinion). 5) Why did I want a Linux system in the first place? :/ Linux is a very powerful OS, if you can use UNIX. Your machine is completely under your control w/ most versions of Linux. RedHat is more a install/setup themselves kind of people. Some of the usual files are replaced w/ RedHat dependant stuff. Hope this info is (a) correct and (b) helpful. wuff, andy
Re: Catch-22 - Help!
At 06:37 PM 10/28/98 -0600, Andy Kennedy wrote: On Wed, 28 Oct 1998, Jerry E. McGoveran wrote: I have a Debian installation in which the ethernet card driver is apparently not installed. There were some errors at this stage of the installation process, but the screen drew and reset to the inst. menu too fast to read anything. I finished the installation, and now I need to update the kernel and the drivers. I can't compile a kernel (downloaded 2.0.35 src) because I don't have gcc. I can't install the gcc package because I don't have network access in Linux - only under Win95.A Gcc is available at sunsite.unc.edu and most of the mirrors. Download it w/ win95 and then use tar to unpack it. Oh. I had assumed that it had to be installed via the package route. Silly me. Thanks for the help! -Jerry Certus Consulting Group | Specializing in Integrated Circuit Antioch, CA 94509 | Design and Verification, Logic (925)757-0685 | Synthesis, Fault Grading, and http://www.certus.com | Test Development
Re: Catch-22 - Help!
On Wed, 28 Oct 1998, Jerry E. McGoveran wrote: At 06:37 PM 10/28/98 -0600, Andy Kennedy wrote: On Wed, 28 Oct 1998, Jerry E. McGoveran wrote: I have a Debian installation in which the ethernet card driver is apparently not installed. There were some errors at this stage of the installation process, but the screen drew and reset to the inst. menu too fast to read anything. I finished the installation, and now I need to update the kernel and the drivers. I can't compile a kernel (downloaded 2.0.35 src) because I don't have gcc. I can't install the gcc package because I don't have network access in Linux - only under Win95.A Gcc is available at sunsite.unc.edu and most of the mirrors. Download it w/ win95 and then use tar to unpack it. Oh. I had assumed that it had to be installed via the package route. Silly me. The package route is still better, but you don't have to use dselect. Download packages using Win95, then mount vfat partition from within linux and use dpkg -i pakcagename.deb to install it. Sergey.
Re: Catch-22 - Help!
In [EMAIL PROTECTED], on 10/28/98 at 12:53 PM, Jerry E. McGoveran [EMAIL PROTECTED] said: I have a Debian installation in which the ethernet card driver is apparently not installed. There were some errors at this stage of the installation process, but the screen drew and reset to the inst. menu too fast to read anything. I finished the installation, and now I need to update the kernel and the drivers. I can't compile a kernel (downloaded 2.0.35 src) because I don't have gcc. I can't install the gcc package because I don't have network access in Linux - only under Win95. My Linux installation has a 2.0.32 kernel with 2.0.34 drivers, and this is probably why the drivers don't work. I'm using the 2.0.32 kernel because the 2.0.34 kernel wasn't working with my AHA2842 SCSI adapter. Questions: 1) Can I get there from here? Sure. 2) How do I install a package assuming I can get the .deb files onto a mounted filesystem? Dselect asks for a series of directory pathnames, and complains when it doesn't find various files and directories within them. Use dpkg. It is guaranteed to be installed, dselect itself use dpkg for installing packages. Use dpkg -i /mountpoint/directories/package_filename.deb This is the manual way for installing debian packages, and the advantage over installing tar-files is that the package management system is used. Dependencies are checked, installation scripts are run, and everything is set up correctly in the proper directories. gcc and lots of other software is available as debian packages from www.debian.org 3) Is there a direct way to update the kernel and/or drivers without having to compile a kernel or use dselect? Dselect is not necessary. It is an interface when dealing with the entire debian distribution. (You don't want to run ftp and dpkg for each of 50 packages you may want to install.) I suggest getting gcc, kernel sources and the other utilities needed for development (make and such) Then compile a 2.0.35 kernel with the drivers you need. You may use dselect for installing further packages when the network is up and running. You can update the kernel by compiling it - or by getting a compiled kernel from someone else. Compiling it yourself is easy though, and you can set it up for exactly the hardware you have. If you have cdrom consider getting the debian cd for about $2 from www.cheapbytes.com or similiar places. It may save you a lot of time. 4) Should I give up on Debian and go buy the RedHat CD and hope for better results? No need, but do as you wish. 5) Why did I want a Linux system in the first place? :/ It is certainly a good idea if you have a pc :-) Helge Hafting
Re: Catch-22 - Help!
You can always (under win95) go to the debian ftp site and download any .deb package, then boot linux and mount the windows partition. Then cd to the directory with the .deb and do a dpkg -i filename.deb. My system has a windows partition, and I have that listed in my /etc/fstab so it is mounted at bootup (I called that directory mount point /C:). If I do a full backup under linux, I also back up windows! = Oh. I had assumed that it had to be installed via the package route. Silly me. _ DO YOU YAHOO!? Get your free @yahoo.com address at http://mail.yahoo.com
Re: Catch-22 - Help!
On Wed, 28 Oct 1998, Jerry E. McGoveran wrote: : At 06:37 PM 10/28/98 -0600, Andy Kennedy wrote: : On Wed, 28 Oct 1998, Jerry E. McGoveran wrote: : : I have a Debian installation in which the ethernet card driver is : apparently not installed. There were some errors at this stage of : the installation process, but the screen drew and reset to the inst. : menu too fast to read anything. I finished the installation, and : now I need to update the kernel and the drivers. I can't compile a : kernel (downloaded 2.0.35 src) because I don't have gcc. I can't install : the gcc package because I don't have network access in Linux - only under : Win95.A : : Gcc is available at sunsite.unc.edu and most of the mirrors. Download it : w/ win95 and then use tar to unpack it. : : Oh. I had assumed that it had to be installed via the package route. : Silly me. That would be wiser. Download the gcc deb via Win95 and use dpkg to install it (dpkg -i) -- Nathan Norman MidcoNet 410 South Phillips Avenue Sioux Falls, SD mailto:[EMAIL PROTECTED] http://www.midco.net finger [EMAIL PROTECTED] for PGP Key: (0xA33B86E9)
Catch-22 - Help!
I have a Debian installation in which the ethernet card driver is apparently not installed. There were some errors at this stage of the installation process, but the screen drew and reset to the inst. menu too fast to read anything. I finished the installation, and now I need to update the kernel and the drivers. I can't compile a kernel (downloaded 2.0.35 src) because I don't have gcc. I can't install the gcc package because I don't have network access in Linux - only under Win95. My Linux installation has a 2.0.32 kernel with 2.0.34 drivers, and this is probably why the drivers don't work. I'm using the 2.0.32 kernel because the 2.0.34 kernel wasn't working with my AHA2842 SCSI adapter. Questions: 1) Can I get there from here? 2) How do I install a package assuming I can get the .deb files onto a mounted filesystem? Dselect asks for a series of directory pathnames, and complains when it doesn't find various files and directories within them. 3) Is there a direct way to update the kernel and/or drivers without having to compile a kernel or use dselect? 4) Should I give up on Debian and go buy the RedHat CD and hope for better results? 5) Why did I want a Linux system in the first place? :/ Advance appreciation for any and all help offered! -Jerry Certus Consulting Group | Specializing in Integrated Circuit Antioch, CA 94509 | Design and Verification, Logic (925)757-0685 | Synthesis, Fault Grading, and http://www.certus.com | Test Development
catch 22
I hope you can help me find out the origin or how we got this catch 22 phrase? I would appreciate a respomse from you. I got to you page when I did a search on catch 22 Thank you in advance. Ofori Boateng -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: catch 22
I hope you can help me find out the origin or how we got this catch 22 phrase? I would appreciate a respomse from you. I got to you page when I did a search on catch 22 Thank you in advance. Ofori Boateng Searching for catch 22 brought you to the Debian pages because of this thread. That's the origin of the phrase. -- Pete Harlan [EMAIL PROTECTED] -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: Apache - catch 22?
At 09:01 22/08/96 -0400, you wrote: Hi Fun -- hi Su:) dpkg --info libgdbm1_1.7.3-11.deb yields: ... Depends: libc5 (=5.2.16-1) ... You quite right, but i have libgdbm1_1.7.3.8 ... thats my other problem, i cant find lib3-11 ... I even had a look at ftp.debian.org, i can find this version ... .. thanks ..:) Im out like bell bottom trousers, - mIcHaEl ///\ The Australian Internet Company c-00 ISP par Excellence \http://www.electric.rain.aic.net.au/(mine) |\_- http://www.aic.net.au/ (not mine) \ / . Skinhead is to Pinhead, as Tiny is to Weany -La Hahn
Apache - catch 22?
Hi i just grabbed the unstable apache package. I tried to install it and it wouldnt because it need libc5 and libdbgm1 (?). I grabbed these packages installed libc5 and then tried installing libdbgm1, guess what, libdbgm1 wont intsall because it wants version libc5-16 while i have libc5-18. Where can i get libc5-16 oir a newer version of libdbgm1? sheesh, sounds like im speaking in another language:) thanks
Re: Apache - catch 22?
Hi Fun -- You said: Hi i just grabbed the unstable apache package. I tried to install it and it wouldnt because it need libc5 and libdbgm1 (?). I grabbed these packages installed libc5 and then tried installing libdbgm1, guess what, libdbgm1 wont intsall because it wants version libc5-16 while i have libc5-18. dpkg --info libgdbm1_1.7.3-11.deb yields: ... Depends: libc5 (=5.2.16-1) ... The '=' sign means that libgdbm1 depends on version/revisions equal to or later than 5.2.16-1, so 5.2.18 should be fine. Good luck, Susan Kleinmann
Re: catch 22?
Thanks to all the Debian L'ers for the suggestions on how to deal with this problem, especially Dwarf, Guy, Jim and Heiko. I did manage to correctly get a fresh source and image installed by using Heiko's suggestion (or a very close version of it)! I changed the status file to read purge ok not-installed and that did fake out dpkg. Thanks guys! Appreciate all the help. But, now, another has shown up! You guys are gonna get tired of me stumbling around. Seems if I didn't have bad luck, I'd have none at all. My CD is on a SB16 card. I've told the new kernel NOT to load modules (N to kerneld) and somehow, what is now happening is SB driver loads during boot, and then later in the boot process I see loading modules, and you guessed it, it loads sbpcd as a module also! Only the module doesn't see the line passed to the kernel specifying the parameters for sbpcd, so it polls for every darn possible address and clone drive! Now my systems takes about ten minutes to boot! Almost as long as my Vax's at work! :-) Anyone tell me what question I answered wrong to cause this? Paul
Re: catch 22?
Hi Paul -- You said: My CD is on a SB16 card. I've told the new kernel NOT to load modules (N to kerneld) and somehow, what is now happening is SB driver loads during boot, and then later in the boot process I see loading modules, and you guessed it, it loads sbpcd as a module also! The modules listed in /etc/modules will be loaded during boot time whether or not kerneld has been enabled. Only the module doesn't see the line passed to the kernel specifying the parameters for sbpcd, so it polls for every darn possible address and clone drive! Now my systems takes about ten minutes to boot! From the documentation in /usr/doc/modules, I would infer you have to put a line like sbpcd irq=NNN io=NNN into /etc/conf.modules. Maybe you have to give sbpcd a number like sbpcd1; I don't know. I'm also not sure of which particular arguments are accepted by this module, but I'd guess they can be deduced from the kernel sources. HTH? Susan Kleinmann
Re: catch 22?
manually created the symlink Jim, THANKS! I'll give that a try.best suggestion I've heard today :-) Paul - Jim
RE: catch 22?
I've managed to get myself in a catch-22 kind of dilemma. In an effort to get a working 2.0.0 kernel with the proper options to support IP masquerading, somehow or other both my kernel-image and kernel-source packages have gotten to a state where I'm stuck fast! Before you try anything drastic, check the #!/... line of the post-install scripts for the kernel. Mine pointed to a non- existent perl. Either modify the script(s) or create a link to the correct Perl. Once I had created the link, the install went forward without a hitch. Good luck, Owen
RE: catch 22?
On 23:36:54 [EMAIL PROTECTED] wrote: masquerading, somehow or other both my kernel-image and kernel-source packages have gotten to a state where I'm stuck fast! Before you try anything drastic, check the #!/... line of the post-install scripts for the kernel. Mine pointed to a non- existent perl. Either modify the script(s) or create a link to the correct Perl. Once I had created the link, the install went forward without a hitch. Owen, Thanks for suggesting caution. Others have suggested the scripts having that error also. However, I have managed to resolve the dilemma. I tried Heiko's suggestion and edited my status file. I changed the kernel-source and image status to purge ok not-installed. Then ran dselect, since I wanted to install a few other packages as well. All went fine! Except that now the postinst script fails. This is not dibilatating however as the source is now intact and the original kernel image (and the compressed) are where they should be. I believe this same error occured on the initial install of the kernel stuff as well. Paul
Re: catch 22?
On 7 Aug 1996, Jim Pick wrote: I had the same problem with a virgin Debian 1.1 installation. I investigated and found that the kernel-image/kernel-source postinst and prerm scripts reference #! /bin/perl. However, on my virgin Debian 1.1 installation, there was no symlink from /bin/perl to /usr/bin/perl! I manually created the symlink and that fixed the problem. I've been meaning to report this as a bug - but I haven't figured out how to do that yet... You don't need to report it, it's a known bug. It's been fixed in Debian 1.1.something. Christian
Re: catch 22?
Jim Pick wrote on 08 Aug 1996 04:44:21 +1000: wb2oyc ... In an effort to get a working 2.0.0 kernel with the wb2oyc proper options ... results in errors during the prerem wb2oyc or postrem scripts for both the source and image package. Jim I had the same problem with a virgin Debian 1.1 installation. Jim I investigated and found that the kernel-image/kernel-source Jim postinst and prerm scripts reference #! /bin/perl. Jim However, on my virgin Debian 1.1 installation, there was no Jim symlink from /bin/perl to /usr/bin/perl! I manually created Jim the symlink and that fixed the problem. This is Bug#3951 I think. I had the same problem. Cheers, Graham
Re: catch 22?
On 14:19:59 Guy Maor wrote: On Tue, 6 Aug 1996 [EMAIL PROTECTED] wrote: Is there some way to force dpkg to reinstall (or remove) in spite of the error it encounters attempting to remove the older package first? Type `dpkg --force-help' for instructions on forcing options. I think you want --force-remove-reinstreq. Be forewarned that you can seriously damage your installation with some of these options. Guy Thanks for the try Guy, but no help there. Been there, done that. The remove (or forced install) doesn't work either, for the same reason. The prerem and/or the postrem script fails. Actually, I thought the force option would be the answer, but I haven't been successful with it yet. Paul
Re: catch 22?
On Tue, 6 Aug 1996 [EMAIL PROTECTED] wrote: Is there some way to force dpkg to reinstall (or remove) in spite of the error it encounters attempting to remove the older package first? Type `dpkg --force-help' for instructions on forcing options. I think you want --force-remove-reinstreq. Be forewarned that you can seriously damage your installation with some of these options. Guy
Re: catch 22?
On Wed, 7 Aug 1996 [EMAIL PROTECTED] wrote: Thanks for the try Guy, but no help there. Been there, done that. The remove (or forced install) doesn't work either, for the same reason. The prerem and/or the postrem script fails. Actually, I thought the force option would be the answer, but I haven't been successful with it yet. You'll have to examine the prerm or postrm in question to see why it fails. You'll then have to correct the problem so you can remove the package. Be sure and file a bug report explaining the problem. Guy
Re: catch 22?
In article [EMAIL PROTECTED], [EMAIL PROTECTED] writes: I've managed to get myself in a catch-22 kind of dilemma. In an effort to get a working 2.0.0 kernel with the proper options to support IP masquerading, somehow or other both my kernel-image and kernel-source packages have gotten to a state where I'm stuck fast! I cannot successfully build a kernel at this point, and I can't remove or reinstall either of the packages. Attempting to reinstall results in errors during the prerem or postrem scripts for both the source and image package. Attempting to remove, errors with a recommendation to reinstall (which fails of course!--hence the dilemma) before attempting to remove! I am stuck in that proverbial hard place. I had the same problem with a virgin Debian 1.1 installation. I investigated and found that the kernel-image/kernel-source postinst and prerm scripts reference #! /bin/perl. However, on my virgin Debian 1.1 installation, there was no symlink from /bin/perl to /usr/bin/perl! I manually created the symlink and that fixed the problem. I've been meaning to report this as a bug - but I haven't figured out how to do that yet... - Jim
catch 22?
Oh Debian L'ers, I've managed to get myself in a catch-22 kind of dilemma. In an effort to get a working 2.0.0 kernel with the proper options to support IP masquerading, somehow or other both my kernel-image and kernel-source packages have gotten to a state where I'm stuck fast! I cannot successfully build a kernel at this point, and I can't remove or reinstall either of the packages. Attempting to reinstall results in errors during the prerem or postrem scripts for both the source and image package. Attempting to remove, errors with a recommendation to reinstall (which fails of course!--hence the dilemma) before attempting to remove! I am stuck in that proverbial hard place. Is there some way to force dpkg to reinstall (or remove) in spite of the error it encounters attempting to remove the older package first? Or is there some reasonable way to fake it out by creating the .deb files in some magic place where the remove will work, for example, or even by copying them from the CD to an appropriate place (I do have the I-Connect CD cut on 6_16)? I haven't been successful attempting to use dpkg -i either, but that could be me not getting the syntax correct perhaps. Any suggestions would be appreciated. Thanks. Stuck fast Paul
