December 2002 - WLUG - wlug.mailman3.com

kernel saga continues

by avedis＠rcn.com

I managed to get my online connection working again. Just had to change "ippp0" to "ppp0" in my firewall config file. I was also able to make a lilo boot floppy from command line, and it worked, exept for my initial menu. I rebooted back and forth a few times between the two floppies, and they both seemed to be working, and then when I went into x-session, I had no mouse. WTF??? Why did I lose kernel support for other stuff when all I messed with was "sound"? Then I made the mistake of going into XF86Setup. Now, I can't get into x at all. Questions 1. Can anyone tell me where the problem is? (other than "user") 2. Is there someplace in make xconfig or make menuconfig to provide support for xfree? At one point, I got an error message about not being able to load a module when trying to get into x. 3. Would it make sense to go back to the distribution disks, remove and re-insall xfree? Thanks. Greg

Dec. 22, 2002

kernel - Help!

by avedis＠rcn.com

I'm in windows right now, which is where I automatically boot to if I don't use the floppy. I only get a choice of boots with floppy. Tried recompiling the kernel with sound, added the lbn32(?) line to /etc/lilo and the cylinder error went away, but somehow I lost support for ipchains and lost the suse firewall. Also lost support for vfat. I went back into make xconfig and started messing around with ppp support, vfat and dos support. Got my vfat back ok. Also had to go in and re-edit /etc/rc.config and /etc/rc.config.d/firewall- somethingorother.config. I think I need to review my selections in those files. At first, I could dialup and as soon as it would connect, it would disconnect, and pppd would give error message 4, no support for ppp in kernel. I went back in and selected netfilter with ipchains support, and ppp with async support. Now it will connect and stay connected, but I can't send or receive anything (mail or web). Oh, and I removed the sound support from the kernel, but I'm still getting error messages about trying to load the sound modules. Let me know if I did something obvious. Meanwhile, I'll review what I did. Thanks, Greg

Dec. 22, 2002

Re: [Wlug] "LN" question

by Bill Mills-Curran

On Sat, 21 Dec 2002, Michael LaPointe wrote: > My original site had all of the images in an images directory. To > avoid copying all of the images to each new sub domain/directory I > created an images directory for each sub directory and ran ln *.* > /path/to/sub/images from within the real images directory. > > This worked great but is it only a one shot deal? I.E. if I add > another image to the main directory do I need to run ln again? Michael, What you have created in each directory is an images directory populated with links. As you supposed, each time you add something to the "real" images directory, you have to add links to it everywhere. Here's a more efficient approach. 1) get rid of all these directories of links and 2) in each site directory, make single link to the "real" images directory (not to the images themselves). For example, cd <site_directory> ln -s <path_to_images_directory> images That's it. You won't have to worry about maintaining links to the individual files. Hope this helps. Bill

Dec. 21, 2002

[Off-Topic] Free Software Consortium in search of Consultants and Agents in your area.

by Consorcio Software Libre

We would like to invite you to be a founding members of the FSC either as a Consultant and/or an Agent. http://www.fsconsortium.com On the main page you will find links to subscribe as consultant and/or agent. Free Software Consortium is a multinational consortium established to link the companies and the independent consultants that use and promote free software. One of the bigger obstacles to the development of the free software services market is the fear of many companies to establish contracts with independent consultants who do not have support of a well known Company, Corporation or Consortium. Questioning quality, support, experience and capability to successfully complete a project are the companies manager's main concerns when considering the option of migrating their systems to free software. Like you, we know the excellent quality that Free Software offers. We have complete confidence that Free Software is going to be the platform of the future. That is why it's so important to work and consolidate together to solve the problem mentioned above. Free Software Consortium intends to fill this void joining the best free software companies and consultants at the national and international level. By joining to Free Software Consortium you or your company will have the following benefits: 1. Possibility of being hired by other Consortium members. 2. Possibility of hiring other Consortium members. 3. Use of the Consortium image and name with your clients. 4. Use of the Consortium's resources like Publicity Brochures, Business Cards, Banners for presentations and events, financial presentations, publicity articles for the press and magazines, support via mailing list and forums with the Consortium's members, marketing and communication assistance, CD's and manuals from the Consortium, site and mail hosting (yourarea.fsc.cc) and other future services. 5. Representation of the FS Consortium in your area to share administrative, legal and marketing resources between the Consultant members in your area. Free Software Consortium will establish a contract with an Agent company which will have exclusive representation in it's area, in charge of organizing the consultants in the area. This Agent company will provide the administrative services, marketing and sales with the local customers.

Dec. 21, 2002

"LN" question

by Michael LaPointe

I just recently upgraded my hosting plan to include sub domains, shell access and a few other goodies. My original site had all of the images in an images directory. To avoid copying all of the images to each new sub domain/directory I created an images directory for each sub directory and ran ln *.* /path/to/sub/images from within the real images directory. This worked great but is it only a one shot deal? I.E. if I add another image to the main directory do I need to run ln again? Server is FreeBSD 4.7 with Apache/1.3.27 I didnt try hard linking the directories since my books say that you need to be root to do so but I think that is what I really needed. Thank you, ~ Michael LaPointe

Dec. 21, 2002

Re: [Wlug] kernel questions

by Charles R. Anderson

On Sat, Dec 21, 2002 at 11:52:21AM -0500, Gregory Avedissian wrote: avedis> 1. I get errors on this, because I'm above cylinder 1023 on my dual-boot avedis> drive. I boot linux from floppy with lilo. Error message suggests using avedis> lba32 option, but it doesn't say where or how to use it. How do I get avedis> around this? /etc/lilo.conf, put lba32 on a line by itself (like right below the boot = line). Remove any "linear" line you see at the same time. Then rerun "/sbin/lilo". Then you may be able to boot using lilo on the hard drive instead of using a floppy (if your BIOS is new enough). avedis> 2. Instructions say next to install the kernel. Is that done by typing avedis> make install? In addition to the make install that comes after make avedis> modules? (see below) make install does work with recent kernels, yes. It should put the kernel into /boot for you. You might or might not still need to create an initial ramdisk with the "mkinitrd" command... You also will probably have to add an entry to /etc/lilo.conf and rerun /sbin/lilo. -- Charles R. Anderson <cra(a)wpi.edu> / http://angus.ind.wpi.edu/~cra/ PGP Key ID: 49BB5886 Fingerprint: EBA3 A106 7C93 FA07 8E15 3AC2 C367 A0F9 49BB 5886

Dec. 21, 2002

RE: [Wlug] kernel questions

by Skip Gaede

Hi Greg, > -----Original Message----- > From: wlug-admin(a)mail.wlug.org [mailto:wlug-admin@mail.wlug.org]On > Behalf Of Gregory Avedissian > Sent: Saturday, December 21, 2002 11:52 AM > To: wlug(a)mail.wlug.org > Subject: [Wlug] kernel questions > > > I'm trying to get oss sound modules compiled into kernel. > make xconfig was easy enough to get through. > instructions say to then make dep and make bzImage or bzlilo. > 1. I get errors on this, because I'm above cylinder 1023 on > my dual-boot > drive. I boot linux from floppy with lilo. Error message > suggests using > lba32 option, but it doesn't say where or how to use it. How do I get > around this? The best option would be to shrink your primary partition by a few MB, leaving room to create a small primary partition for the Linux /boot partiition. You can easily do this with Partition Magic. ---------------------- Primary | ext2 | /boot ---------------------- Primary | FAT or NTFS or ??? ---------------------- Extended| swap ---------------------- Extended| ext2 or ext3 | / ---------------------- other partitions as desired... > > 2. Instructions say next to install the kernel. Is that done > by typing > make install? In addition to the make install that comes after make > modules? (see below) No, you need to copy the arch/i386/boot/bzImage --> /boot/<some unique name> and then add an entry to /etc/lilo.conf or /boot/grub/menu.lst. If you are using lilo, you then need to install the new boot sector by typing lilo. > > 3. I haven't been able to create a lilo boot disk for awhile. > I'm using > Yast2 to configure boot mode, and it keeps telling me that my > floppy is > write protected and it can't access the boot sector. I've tried this > with new floppies that have been formated with fdformat /dev/fd0. You shouldn't need to format it first, and the disk should not be mounted. Refer to help on www.tldp.org on how to make a boot disk. > > Thanks for any insight. > > Here are the instructions I'm looking at: > > 1. To make the kernel sound modules, cd to your /usr/src/linux > > directory (typically) and type make config, make menuconfig, > > or make xconfig (to start the command line, dialog, or x-based > > configuration tool). > > > > 2. Select the Sound option and a dialog will be displayed. > > > > 3. Select M (module) for "Sound card support". > > > > 4. Select your sound driver(s) as a module. For ProAudio, Sound > > Blaster, etc., select M (module) for OSS sound modules. > > [thanks to Marvin Stodolsky <stodolsk(a)erols.com>]A > > > > 5. Make the kernel (e.g., make dep ; make bzImage), and install > > the kernel. > > > > 6. Make the modules and install them (make modules; make > modules_install). > > > _______________________________________________ > Wlug mailing list > Wlug(a)mail.wlug.org > http://mail.wlug.org/mailman/listinfo/wlug >

Dec. 21, 2002

kernel questions

by Gregory Avedissian

I'm trying to get oss sound modules compiled into kernel. make xconfig was easy enough to get through. instructions say to then make dep and make bzImage or bzlilo. 1. I get errors on this, because I'm above cylinder 1023 on my dual-boot drive. I boot linux from floppy with lilo. Error message suggests using lba32 option, but it doesn't say where or how to use it. How do I get around this? 2. Instructions say next to install the kernel. Is that done by typing make install? In addition to the make install that comes after make modules? (see below) 3. I haven't been able to create a lilo boot disk for awhile. I'm using Yast2 to configure boot mode, and it keeps telling me that my floppy is write protected and it can't access the boot sector. I've tried this with new floppies that have been formated with fdformat /dev/fd0. Thanks for any insight. Here are the instructions I'm looking at: > 1. To make the kernel sound modules, cd to your /usr/src/linux > directory (typically) and type make config, make menuconfig, > or make xconfig (to start the command line, dialog, or x-based > configuration tool). > > 2. Select the Sound option and a dialog will be displayed. > > 3. Select M (module) for "Sound card support". > > 4. Select your sound driver(s) as a module. For ProAudio, Sound > Blaster, etc., select M (module) for OSS sound modules. > [thanks to Marvin Stodolsky <stodolsk(a)erols.com>]A > > 5. Make the kernel (e.g., make dep ; make bzImage), and install > the kernel. > > 6. Make the modules and install them (make modules; make modules_install).

Dec. 21, 2002

Re: [Wlug] The Package Chase

by Andy Stewart

On Friday 20 December 2002 9:25 pm, Gregory Avedissian wrote: > OK, I've been going along merrily with my SuSE 7.2 for about a year, and > I just now ran into a problem that a lot of you folks must know all too > well. Install a new program and it calls for a package you don't have. > You've all seen the lists, I'm sure. > > I'm trying to install ecawave and ALSA 0.9, and I've had to install some > gtk and gnome stuff, and I went to look at upgrading the whole gnome > package. There's a list of more than 50 things to compile, and they must > be done in the correct order. Do people actually do that? Is there any > advantage of doing that over upgrading the whole distribution? HI Greg, It might be easier to find a more recent SuSE CD and upgrade just the packages about which you care. You could probably download them, but that may be slow and cumbersome given the number of packages you describe. If its just one or two packages, I'll "do it the hard way" and download the package and upgrade it. On occasion, it turns into a rat's nest of dependencies, but typically not. Later, Andy -- Andy Stewart, Founder Worcester Linux Users' Group Worcester, MA USA http://www.wlug.org

Dec. 21, 2002

The Package Chase

by Gregory Avedissian

OK, I've been going along merrily with my SuSE 7.2 for about a year, and I just now ran into a problem that a lot of you folks must know all too well. Install a new program and it calls for a package you don't have. You've all seen the lists, I'm sure. I'm trying to install ecawave and ALSA 0.9, and I've had to install some gtk and gnome stuff, and I went to look at upgrading the whole gnome package. There's a list of more than 50 things to compile, and they must be done in the correct order. Do people actually do that? Is there any advantage of doing that over upgrading the whole distribution?

Dec. 21, 2002