Re: configure dies with Permission denied error
CROSS-POSTED FROM DEBIAN-DEVEL Ken, debian-devel is for development of the Debian distribution (as the name would imply). debian-user is for user questions (as yours is). Please follow-up your question on debian-user. My solution to your problem: chmod +x configure. On Fri, Jan 09, 2004 at 03:05:22PM -0500, ken picha wrote: I have debian running from a very simple installation of the 3.0 rev1 woody disks. I downloaded and uncompressed the mm distribution on the machine, and I am having a problem running configure. This problem occurs no matter what I try to build, and so it is not particular to mm. Logged on to the console as root when I execute: ./configure I get the following error: bash: ./configure: /bin/sh: bad interpreter: Permission denied Of course, configure will run if you execute: sh configure but it dies as soon as it tries to fire off a submodule I have been working with solaris and other UNIX distributions for many years, so I should know the answer to this one, but I am getting old and can't remember anything anymore any ideas? -- Chad Walstrom [EMAIL PROTECTED] http://www.wookimus.net/ assert(expired(knowledge)); /* core dump */ signature.asc Description: Digital signature
Unbootable FastTrak TX2 100
[[[ Please Cc: me, as I'm not subscribed to the list. ]]] I admit it. I'm spoiled. I have come to expect Linux setups to just work, so when they don't I'm quite tenacious in trying to fix things. Currently, I'm trying to get an APPRO 1124i system (http://www.appro.com) to work using the Linux 2.4.18 native ataraid support. This PC Class server is using the Tyan Thunder K7 motherboard, dual AMD MP2400+ processors, 1GB DDRAM, and the Promise FastTrak TX2 100 PCI card. I have the 4 disk Array Configured in Security mode or Mirror/Stripe. I'm booting with LordSutch's Debian Woody 2.4.18-bf2.4 kernel, which has ataraid support compiled in (yes, I know this is a Red Hat list). The machine boots successfully off of CD and recognizes the ataraid device correctly. I've been able to partition and format the ataraid device with a working Debian install. What I cannot seem to accomplish is to boot the system off this raid device: /dev/ataraid/d0. Grub simply won't ackowledge the ataraid device as useable and instead just lists the four physical drives as being available. lilo 22.2-3 installs into the MBR, but fails with L 01 01 01 01 lilo 22.5.4 installs, but instead fails at boot time with L 99 99 99 99 99. Apparently something was fixed between 22.2 and 22.5 to allow lilo to see the device correctly, but now it doesn't seem to want to accept the detected geometry as correct. I've compared the geometry as reported by the Promise card at boot time with the geometry from the lilo diagnostic disk (compiled from 22.5.4 source), and they match perfectly. I have not touched the /dev/hd[e-h] devices as directed by the FAQ's, etc. I honestly don't know what else to do. I don't know if this problem is isolated to lilo or if it's influenced by what the initial kernel is reporting to lilo. Should I be upgrading the installation kernel to 2.4.20? 2.4.21-preX? Does the ataraid driver support the mirror/stripe configuration I'm using, or am I being naieve? Advice? Flames? Etc. -- Chad C. Walstrom [EMAIL PROTECTED] 247 Gortner Hall Asst. Coordinator of IT Help: 612-625-9284 CBS Computing Services, UMN Phone: 612-624-2918 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Setting up phpGroupWare w/Postgresql
I'm attempting to set up phpGroupWare from the woody distribution. I'm
using phpgroupware{,-calendar,-email,-core,-api,-setup,-admin},
php4{-pgsql,-imap}, apache 1.3, and postgresql 7.x.
The database server is on a separate woody box. I've set up a blank
database called phpgroupware with a user called phpgroupware. I've
changed the /etc/phpgroupware/header.inc.php to reflect this
information. I've confirmed that I can connect from the webhost to the
database host with said user account and password using the psql client.
I've confirmed that I can create and drop tables in the database.
As expected, when I visit http://localhost/phpgroupware/, the login.php
reports an error and I see the postgresql logs in the syslog of the DB
host. (can't find phpgw_config table). However, when I go to the
http://localhost/phpgroupware/setup/ URL, nothing happens. It simply
hangs.
Am I doing something wrong? I have php logging to syslog and the debug
level set up high.
I'm not sure it's a bug or not, so I'm posting here first.
WEB HOST
ii phpgroupware0.9.14-0.RC3.2
ii phpgroupware-admin 0.9.14-0.RC3.2
ii phpgroupware-api0.9.14-0.RC3.2
ii phpgroupware-core 0.9.14-0.RC3.2
ii phpgroupware-preferences0.9.14-0.RC3.2
ii phpgroupware-setup 0.9.14-0.RC3.2
ii apache 1.3.24-2.1
ii php44.1.2-4
ii php4-imap 4.1.2-4
ii php4-mcal 4.1.2-4
ii php4-mhash 4.1.2-4
ii php4-pgsql 4.1.2-4
DB HOST
ii postgresql 7.2.1-2
--
Chad Walstrom [EMAIL PROTECTED] | a.k.a. ^chewie
http://www.wookimus.net/| s.k.a. gunnarr
pgpF1s84jxvlG.pgp
Description: PGP signature
Re: GIMP and gif files
Jim Lynch wrote: Is it just Debian or is GIMP not supporting gif files any longer? apt-get install gimp1.2-nonfree Package: gimp1.2-nonfree Priority: optional Section: non-free/graphics Installed-Size: 57 Maintainer: Ben Gertzfield [EMAIL PROTECTED] Architecture: i386 Source: gimp1.2 Version: 1.2.3-2 Replaces: gimp1.1-nonfree Depends: libc6 (= 2.2.4-4), libgimp1.2 (= 1.2.0), libglib1.2 (= 1.2.0), libgtk1.2 (= 1.2.10-4), xlibs ( 4.1.0) Conflicts: gimp1.1-nonfree Filename: pool/non-free/g/gimp1.2/gimp1.2-nonfree_1.2.3-2_i386.deb Size: 23452 MD5sum: e397ad2ee228e1029d0ff183b2ffa456 Description: GIF support for the GNU Image Manipulation Program This package includes GIF support for The GNU Image Manipulation Program. These files are not freely available; their use is disallowed by the UNISYS patent on LZW compression. . Use at your own legal risk. Enhances: gimp1.2 -- Chad Walstrom [EMAIL PROTECTED] | a.k.a. ^chewie http://www.wookimus.net/| s.k.a. gunnarr pgp3b1gbLvEE9.pgp Description: PGP signature
XDCMP Problem w/GDM
I'm having a rather serious error today. I provide X desktops to thin clients on my network. They use gdm to log in and have been successful in doing so until very recently. Two days ago, I added a new harddrive to the system and moved files over to it using the 'find mounted source -mount -print | cpio -p -v mounted target' command. Everything seemed to work fine, so I left Georgia and went back home to Minnesota. The following day, everything seemed to work just fine. However, when I get into the office this morning, one of the users reported to me that she could not log in to her workstation. So, on to debugging... I tried to start a remote X desktop from the XDM server in question. It failed, miserably. I checked the logs (below) for any clues, but couldn't find any -- I'm fairly new to the details of XDMCP, etc. The only thing I can think about may be a possible permissions problem on the part of the file system (as I forgot to add the preserve ownership flag in the cpio string). I've tried uninstalling (and purging) the gdm package multiple times, but that does not fix the problem. (My reason for doing this would be to ensure that the permissions of the gdm files in the least would be correct.) So, my question to you is, Can you help me? The following is a log of what I felt may be important to you. This was generated using the debug flag enabled and connecting with a remote desktop from our VPN. PLEASE RESPOND via email TO ME as well as to the list. I receive this list in digest format and would prefer to have any responses immediately rather than waiting for the next volume. Thank you. Chad Start Log File Mar 2 10:27:05 gonzo gdm[5195]: gdm_xdmcp_display_dispose_check (chewie.rogers.ltiflex.com:1) Mar 2 10:27:05 gonzo gdm[5195]: gdm_display_dispose: Disposing chewie.rogers.ltiflex.com:1 Mar 2 10:27:05 gonzo gdm[5195]: gdm_auth_secure_display: Setting up access for chewie.rogers.ltiflex.com:1 Mar 2 10:27:32 gonzo gdm[5195]: gdm_auth_secure_display: Error getting hentry for chewie.rogers.ltiflex.com Mar 2 10:27:32 gonzo gdm[5195]: gdm_xdmcp_display_alloc: Error setting up cookies for chewie.rogers.ltiflex.com:1 Mar 2 10:27:32 gonzo gdm[5195]: gdm_xdmcp_display_alloc: display=chewie.rogers.ltiflex.com:1, session id=952010702, pending=4 Mar 2 10:27:32 gonzo gdm[5195]: gdm_xdmcp_send_accept: Sending ACCEPT to 192.168.1.50 with SessionID=952010702 Mar 2 10:27:32 gonzo gdm[5195]: gdm_xdmcp_decode: Received opcode MANAGE from client 192.168.1.50 Mar 2 10:27:32 gonzo gdm[5195]: gdm_xdmcp_manage: Got MANAGE from 192.168.1.50 Mar 2 10:27:32 gonzo gdm[5195]: gdm_xdmcp_manage: Got Display=1, SessionID=952010698 from 192.168.1.50 Mar 2 10:27:32 gonzo gdm[5195]: gdm_xdmcp_handle_manage: Failed to look up session id 952010698 Mar 2 10:27:32 gonzo gdm[5195]: gdm_xdmcp_send_refuse: Sending REFUSE to 952010698 -- Chad Walstrom, Systems Analyst LTI Flexible Products, Inc.P: 612-428-9119 21801 Industrial Blvd F: 612-428-9126 Rogers, MN 55374 http://www.ltiflex.com pgpCwo0LBQMgu.pgp Description: PGP signature
More on XDM and runlevels
Brad wrote: As has been mentioned before, this isn't the best solution either. Say you remove the link in runlevel 2. Fine, xdm doesn't start on boot. Then you change to level 3, and xdm is started. Again, good. But now you change back to level 2, where xdm shouldn't be running. What happens? xdm is still there, since you never told the system to kill it in runlevel 2. Simple solution. If you want xdm killed in run level 2, just add a symbolic link in rc2.d to xdm prefixed with a KNNxdm where K directs the computer to Kill the app and NN is the number sequence in which you want the app killed. Eric G . Miller wrote: Yes, but this begs the question, why? I don't know of any good reason to go around changing runlevels midstream. The only time that makes any sense to me, is when you want to do maintainence, and don't want anyone else using the system, and only the minimal services running. For that, using shutdown now brings you down to runlevel 1, then you log in as root, do whatever, and then bring the system back up. Am I missing something here? Well, I can't site any reason w/xdm other than possibly using something like kdm or gdm periodically. However, I do know run levels come in handy. Let's say, for example, you'd like to work on your web pages at home, perhaps running mysql and apache with php. Yet, you're only running a 486 which has limited resources. You've got no need to run Apache and MySQL all of the time, just when you need them. There's where run levels come into play. But to answer your question, yes, you are missing something. There is no reason to bring the system down to run level 1 when it's just as easy to type init num to change the function of the machine. Run levels are there to be used. They're there as a convenience and as a flexible tool. Use them! Experiment with them! Isn't that what Linux is for? ^chewie
Kernel Strategies
I've read and successfully followed the guidelines for creating new kernels using the the kernel-headers-2.0.34.deb, kernel-source-2.0.34.deb, and kernel-package.deb packages. I've read the manuals and some of the HOWTO's, but some things still elude me. I'd like to know some of the personal strategies used in the Debian environment for creating and using kernel packages for unstable kernel releases. No, I haven't R-all-TFM's out there, but I'm getting burnt out on 'em. So, I'd like to hear a little about what some of you do personally to keep track of things. What you like to do to back up old kernels, etc. (The next FM's I'll be looking at include the Debian package creation utilities, reviewing the Kernel stuff, modules, etc. Just give me a breather; I need a breather! *grin*) The reason I ask this is because I'm wary about moving or deleting the .deb-installed headers from the /usr/include directory.
