Re: grml can, why can't my Debian kernel do it?
Thomas H. George wrote: When I boot from a grml-0.9 cd my dvdrw and cdrw drives are found on hde and hdf. They are mountable and usable. The grml release info says it is based on Debian and uses a vanilla 2.6.18-3 kernel with patches and additional modules. I complied a kernel from Debian linux-source-2.6.18. On boot up the system fails to find the dvdrw and cdrw drives and does not add hde and hdf to the list of devices in /dev. Only entries hda and hdb for the two hard drives appear in /dev. grml can, why can't my Debian kernel do it? Tom George It can, and does. The reasons why it doesn't in your case can include your custom kernel not being properly configured to support ide-cdrom devices (CONFIG_BLK_DEV_IDECD=m|y) among many others. Are you running this kernel on a regular debian system (etch), or is this a live-cd or something like that? Tom -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: grml can, why can't my Debian kernel do it?
Thomas H. George wrote: When I boot from a grml-0.9 cd my dvdrw and cdrw drives are found on hde and hdf. They are mountable and usable. The grml release info says it is based on Debian and uses a vanilla 2.6.18-3 kernel with patches and additional modules. I complied a kernel from Debian linux-source-2.6.18. On boot up the system fails to find the dvdrw and cdrw drives and does not add hde and hdf to the list of devices in /dev. Only entries hda and hdb for the two hard drives appear in /dev. grml can, why can't my Debian kernel do it? Tom George It can, and does. The reasons why it doesn't in your case can include your custom kernel not being properly configured to support ide-cdrom devices (CONFIG_BLK_DEV_IDECD=m|y) among many others. Are you running this kernel on a regular debian system (etch), or are you trying to use this as a replacement kernel on the grml live-cd or something like that? Tom -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: grml can, why can't my Debian kernel do it?
Thomas H. George wrote: On Wed, Mar 07, 2007 at 12:55:52PM -0500, Tom Pfeifer wrote: Thomas H. George wrote: When I boot from a grml-0.9 cd my dvdrw and cdrw drives are found on hde and hdf. They are mountable and usable. The grml release info says it is based on Debian and uses a vanilla 2.6.18-3 kernel with patches and additional modules. I complied a kernel from Debian linux-source-2.6.18. On boot up the system fails to find the dvdrw and cdrw drives and does not add hde and hdf to the list of devices in /dev. Only entries hda and hdb for the two hard drives appear in /dev. grml can, why can't my Debian kernel do it? Tom George It can, and does. The reasons why it doesn't in your case can include your custom kernel not being properly configured to support ide-cdrom devices (CONFIG_BLK_DEV_IDECD=m|y) among many others. Just checked this and found CONFIG_BLK_DEV_IDECD=y Are you running this kernel on a regular debian system (etch), or are you trying to use this as a replacement kernel on the grml live-cd or something like that? The system is regular debian etch. I ran apt-get update and apt-get dist-upgrade earlier today. Tom The stock debian kernel that gets installed with etch will definitely support these devices. What went wrong from there with your custom kernel is hard to tell with the information given. A summary of the steps you took to configure, build, and install the kernel might help someone pick up on what the problem could be... Tom -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: New Etch install - IP address question
Andrei Popescu wrote: On Sat, 27 Jan 2007 00:46:50 -0500 Kevin Mark [EMAIL PROTECTED] wrote: Hi Andrei, it seems enough people do an install and have this problem that the answer has become know to the debian-user list. Now I know very little about zeroconf but it seems to me that it would be better to _not_ have it installed and allow those folks who need it to install it then to have newbies not have proper networking when they finish an install. Opinions? cheers, Kev avahi-daemon recommends libnss-mdns libnss-mdns recommends zeroconf The link is pretty weak, but it still gets installed on a lot of systems, because aptitude installs recommends by default. Maybe it (zeroconf) should be installed disabled? Regards, Andrei In my case it was dselect that pulled it in, since that also installs recommends by default. Installing it disabled would be OK, or changing it to suggestsI'm not sure how important zeroconf is for the overall user base. Tom -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
New Etch install - IP address question
Just installed Etch from the RC1 net install CD. Did standard install, updated everything to the latest etch packages from the Debian repository, and then installed xorg + kde. Everything *works fine*, but something is different about the network configuration that I don't understand, and hoping someone can explain what I'm seeing. I didn't change anything in the network configuration - just left it as set up by default. I have a simple LAN behind a router that assigns IP addresses with DHCP. I'm using 192.168.2.X as the local subnet, so normally a system on the LAN will get an IP address such as 192.168.2.155 or 192.168.2.156 etc. But on this new install of etch, when I run ifconfig I'm getting this: [EMAIL PROTECTED]:~$ /sbin/ifconfig eth0 Link encap:Ethernet HWaddr 00:13:20:F3:7A:03 inet addr:169.254.128.152 Bcast:169.254.255.255 Mask:255.255.0.0 inet6 addr: fe80::213:20ff:fef3:7a03/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:583 errors:0 dropped:0 overruns:0 frame:0 TX packets:433 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:276931 (270.4 KiB) TX bytes:46680 (45.5 KiB) Note the strange IP address. The leases file in /var/lib/dhcp3 does show that the IP address assigned is in the expected range (192.168.2.199), and I can ping that IP from other systems etc. Again, everything looks and works normally excecpt for the strange IP address. Just hoping someone can explain or provide a link to some information - thanks...(maybe this is related to IPv6 ?) Tom -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: New Etch install - IP address question
Andrei Popescu wrote: On Fri, 26 Jan 2007 11:08:45 -0500 Tom Pfeifer [EMAIL PROTECTED] wrote: Again, everything looks and works normally excecpt for the strange IP address. Just hoping someone can explain or provide a link to some information - thanks...(maybe this is related to IPv6 ?) These addresses are usually assigned by the zeroconf package. You can (should) purge that. Regards, Andrei Yes, that was it - thanks. zeroconf can also be disabled (as a test) in /etc/default/zeroconf The other symptom of this is the output of route. It will have a link-local entry - which will show as 169.254.0.0 with route -n Tom -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Promise card
FWIW, I have the same Promise card as you (Ultra 133 TX2). The module (driver) it needs is included in the 2.4 and 2.6 kernels (at least) and should show up as 'pdc202xx_new' when you run the 'lsmod' command - if it is, in fact, loaded and compiled as a module. It can also be compiled directly into the kernel. If you look at the kernel config, that option is: CONFIG_BLK_DEV_PDC202XX_NEW=y (or =m if compiled as a module) Tom David A. Parker wrote: Did you have to get any special drivers for your cards? I thought it might be a driver issue, but I was unable to locate any. Thanks, Dave uniqx wrote: I, too, am using a Western Digital 120 BG w/8 buffer. Also, an 80G WDdrive (both 7200). Both in one system. In another system (sarge also) I am using a 100 GB WD drive. The Promise cards are great! gere David A. Parker wrote: Thanks for your reply. It's probably not worth having you switch out your cards right now, but the offer is appreciated. What kind of drives do you have connected to your Ultra 100 cards? I should have mentioned before that this was a Western Digital 120 GB drive w/ 8 MB buffer, connected to the Ultra 133 as the primary master. It was recognized as /dev/hde when Debian booted, but it was really a game of chance as to whether or not it would be writable or even mountable. The filesystem was a single JFS partition (/dev/hde1), it's the data drive for MythTV. Thanks, Dave Parker uniqx wrote: I know you asked about the 133, but I am using the Promise Ultra 100 --on two debian systems -- and they work great. I can switch out the 133 from my windows box and try it if you would like. If you think I can help, let me know. gere harvey -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: problem using Canon SD400 on Debian Sarge
Sayantan Sur wrote: On 10/3/05, Henrique de Moraes Holschuh [EMAIL PROTECTED] wrote: On Mon, 03 Oct 2005, Sayantan Sur wrote: As soon as I plug the camera in, for a brief period it is reported by `lsusb' (from usbutils package). But after a few seconds, the device dissappears from lsusb!! However, it is always to be found in /proc/bus/usb/devices. Try lsusb as root. If it shows up, it is just braindamage happening, with a race condition on USB plugin just to make sure you know that whomever is responsible for it really needs to get his act together. Track down whatever is screwing up with /proc/bus/usb permissions and you will have the culprit. Thanks a lot! This worked. There is definitely brain damage happening ;-) Apparently, if I run lsusb as root, everything is just fine. However, as Tom else pointed out on the list, it is not accessible as a Mass Storage Device. Now, if I use gphoto2 as root, then everything is just hunky-dory. You may still have to add your user(s) to the camera groupand then that usually requires the user to log off and then on for the change to take affect. Tom -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: problem using Canon SD400 on Debian Sarge
Sayantan Sur wrote: Hello, I recently got a Canon SD400 camera. I have been trying to get it to work with my laptop which runs Debian Sarge but no luck yet :-( I am running kernel version 2.6.12-1-686. I have usb storage working fine. I can use USB hard disks and other kinds of memory sticks by mounting them onto /dev/sda1 ... Coming to the peculiar problem which I face with the camera ... As soon as I plug the camera in, for a brief period it is reported by `lsusb' (from usbutils package). But after a few seconds, the device dissappears from lsusb!! However, it is always to be found in /proc/bus/usb/devices. Any clue as to why this behavior? This camera works with SuSe (I think 10.someversion), but it should work on Debian too!! Thanks for all your help, Sayantan. = Debug information: 1. lsusb -v # For the very short period of time the camera is reported by lsusb Bus 001 Device 009: ID 04a9:310e Canon, Inc. Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize064 idVendor 0x04a9 Canon, Inc. idProduct 0x310e bcdDevice0.02 iManufacturer 1 iProduct2 iSerial 0 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 39 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xc0 Self Powered MaxPower2mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 0 bNumEndpoints 3 bInterfaceClass 6 Imaging bInterfaceSubClass 1 Still Image Capture bInterfaceProtocol 1 Picture Transfer Protocol (PIMA 15470) iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0040 1x 64 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x02 EP 2 OUT bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0040 1x 64 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x83 EP 3 IN bmAttributes3 Transfer TypeInterrupt Synch Type None Usage Type Data wMaxPacketSize 0x0008 1x 8 bytes bInterval 32 can't get device qualifier: Operation not permitted can't get debug descriptor: Operation not permitted 2. cat /proc/bus/usb/devices # Device info for the camera T: Bus=01 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 10 Spd=12 MxCh= 0 D: Ver= 2.00 Cls=00(ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1 P: Vendor=04a9 ProdID=310e Rev= 0.02 S: Manufacturer=Canon Inc. S: Product=Canon Digital Camera C:* #Ifs= 1 Cfg#= 1 Atr=c0 MxPwr= 2mA I: If#= 0 Alt= 0 #EPs= 3 Cls=06(still) Sub=01 Prot=01 Driver=(none) E: Ad=81(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms E: Ad=02(O) Atr=02(Bulk) MxPS= 64 Ivl=0ms E: Ad=83(I) Atr=03(Int.) MxPS= 8 Ivl=32ms 3. tail -f /var/log/messages # When camera is inserted and turned on Oct 3 21:50:39 localhost kernel: usb 1-1: new full speed USB device using uhci_hcd and address 10 Oct 3 21:50:40 localhost usb.agent[7405]: libgphoto2: loaded successfully It's possible that this camera doesn't support being mounted as a USB mass storage device. This web page lists the Canon SD500 as strictly PTP (pitcure transfer protocol: http://www.teaser.fr/~hfiguiere/linux/digicam.html If the SD400 is the same in that regard, then you would have to access the camera with gphoto2, and a front end for it like digikam. Tom -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: HELP- Grub problem, I can't load WInXP SOLVED
Andy wrote: On Tuesday 27 September 2005 12:42, Tom Pfeifer wrote: Since your WinXP on /dev/hda1 is a FAT32 partition, one thing that might work is to use the backup boot sector that is kept on FAT32 file systems to restore the WinXP boot sector on /dev/hda1. dd if=/dev/hda1 of=/dev/hda1 bs=512 count=1 skip=6 The above dd command will read the 7th sector (or sector 6) of the partition, and then write it to the 1st sector (or sector 0). The 7th sector is where the backup boot sector is stored on FAT32. The skip means it will skip over the first 6 sectors when reading from the partition - since you are interested in the 7th sector. GRUB should have only overwritten the 1st sector of the partition. Tom Tom, I cannot thank you enough! Your instructions worked flawlessly. I can't believe that your dd command managed to fix something that Microsoft's own fixboot and fixmbr commands could not. You have saved me a lot of time and money, thank you very much. Regards, Andy You're welcome, and glad to hear it. To be honest, I don't know if fixboot (or some other MS command) can restore a backup boot sector. NTFS also has a backup boot sector (the last sector of the partition), so you would think they would have a command than can restore it but... Tom -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: HELP- Grub problem, I can't load WInXP
Andy wrote: On Monday 26 September 2005 3:17, Dennis Stosberg wrote: Windows XP is on /dev/hda, which is (hd0,0) in GRUB's notation. So, if you install the GRUB boot sector into /dev/hda1, you overwrite Windows XP's boot sector in that partition. That means you won't be able to boot Windows XP at all, because GRUB will simply reload itself when it tries to chain-load from (hd0,0). Ah, didn't realise that, oops. What you probably wanted was to overwrite /dev/hda's MBR, which is (hd0) in GRUB's notation with the GRUB boot loader. So the BIOS would start grub at (hd0), which in turn can chain-load Windows XP from (hd0,0). Or other systems/kernels from other devices. Double oops. I'd suggest you to let the Windows XP setup restore the boot sector of /dev/hda1 again. After that you can reinstall GRUB to (hd0) and _not_ to (hd0,0). Well, I booted using the XP recovery console and have tried various fixmbr and fixboot commands but none of them brought windows back. So I've just installed grub again in hd0 to get an OS back. Since your WinXP on /dev/hda1 is a FAT32 partition, one thing that might work is to use the backup boot sector that is kept on FAT32 file systems to restore the WinXP boot sector on /dev/hda1. dd if=/dev/hda1 of=/dev/hda1 bs=512 count=1 skip=6 The above dd command will read the 7th sector (or sector 6) of the partition, and then write it to the 1st sector (or sector 0). The 7th sector is where the backup boot sector is stored on FAT32. The skip means it will skip over the first 6 sectors when reading from the partition - since you are interested in the 7th sector. GRUB should have only overwritten the 1st sector of the partition. Tom -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: new hard drive
Kudret Güler wrote: Hi all, yesterday I had only one hard drive. hda1 / #debian installation A hda5 /home Today this hard drive is hdb with the same structure. On hda there is grub installed pointing to debian installation A as well as other entries. When I try to load debian installation A, currently I am having kernel panic after an error: VFS can't find ext3 filesystem on dev hda1 Question: Which files should I edit to let linux know that it is on hdb now? I already edited fstab and mtab thank you Probably, just /boot/grub/menu.lst needs to be updated. Take a look at the kopt= and groot= entries in the Default Options section, and correct them to reflect your new drive configuration - but don't uncomment those lines as warned in the file. Then, as root, run 'update-grub', which will use the default values you just changed to update the boot menu entries further down in the menu.lst file. Tom -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: dist-upgrade failure
Steven Van Cleave wrote: On my Sarge (stable), 2.6.8-2-686, $ 'apt-get dist-upgrade' produces the following error text: ldconfig: Writing of cache data failed dpkg: error processing zlib1g (--configure): subprocess post-installation script returned error exit status 1 Errors were encountered while processing: zlib1g I've done a fairly thorough search of solution sources without success. Running df yields: FilesystemSize Used Avail Use% Mounted on /dev/hda1 250M 250M 0 100% / tmpfs 253M 0 253M 0% /dev/shm /dev/hda9 66G 15G 49G 23% /home /dev/hda8 361M 8.1M 334M 3% /tmp /dev/hda5 4.6G 4.1G 313M 93% /usr /dev/hda6 2.8G 470M 2.2G 18% /var tmpfs 10M 772K 9.3M 8% /dev This just started happening and I'm not sure why. Any helpful suggestions will be much appreciated. Thanks! Steve That's most likely because your root partition (/) is full, and it's trying to write to the /etc directory - which is included in your root partition. You could either delete something you don't need on the root partition to give yourelf some wiggle room (as previously mentioned), or you could consider adding some disk space to the root partition by resizing it. Looks like you have plenty of elbow room on the drive (especially in your /home partition) to do the resizing. You can get a better look at your overall partition layout by running 'fdisk -l /dev/hda' (as root), and you can get the output into a text file with 'fdisk -l /dev/hda filename' Tom -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: unsupported package in Sarge?
Bernhard Fastenrath wrote: update-grub is unsupported¹ but used in 3.1 r0a Sarge? How can a package that is used in the current release be unusupported and how can I submit a bug report? update-grub is not a package. It's part of the grub package. see 'dpkg -L grub' or 'dpkg -S /sbin/update-grub' You can file the bug report against grub. Tom -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Why Grub? Must I Switch?
Thomas H. George wrote: Setup a new computer from Sarge. Everything is perfect, but I liked and was comfortable with Lilo. Are there compelling reasons to switch to Grub or can I go back to Lilo without losing anything important? Tom George Sure, you can still use Lilo. Both work fine. FWIW, I now prefer Grub, mostly because of the interactive shell that's available at boot time - from which you can boot items not on the menu, or edit items that areor have no menu at all if that's what you wantetc. Tom -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bootloader for Sarge
Matthew Jackson wrote: I just downloaded the weekly build for Sarge and burnt the first iso. The install goes great but when asked to install GRUB, I decide not to install to the MBR so it asks me where to install it to. The reason is I have XP on one hard disk and Linux on the other hard disk. the linux hard disk comes up as 'hdc'. On it I have partitioned it into these: /boot 250mb /tmp 750mb /var 1gb / 10gb /usr 20gb swap 1gb /home remainder ~40gb in that order. I tell the debian installer to install GRUB into /dev/hdc1 meaning the /boot partition. I want to use the NTLDR so it does not mess with windows MBR. I then have installed bootpart onto my xp drive and added to boot.ini the 250mb (/boot) linux drive as read here: http://www.aboutdebian.com/dualboot.htm In bootpart my /boot is number 2. So is it the debiban installer not putting it where I want or is it bootpart not finding it? What are the contents of your boot.ini file? It's just a simple text file, so you could post it here. There needs to be an entry for Debian in there, and it has to refer to a file containing the contents of the /boot partition's boot sector (a 512 byte file). And of course, that boot sector file has to contain stage 1 of Grub - which it should if you told the Debian installer to install Grub to /dev/hdc1. What happens when you try to boot Debian? Is there an entry for Debian on the Windows boot menu? Tom -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: How to set up CUPS client
Tim Kelley wrote: On Thu, Sep 09, 2004 at 11:35:08AM -0400, Tom Pfeifer wrote: For the benefit of anyone else trying this, you don't have to touch anything on the client machine(s). Just the default install of the basic CUPS packages is needed on the client. The CUPS daemon running on the client will then automatically discover the printer(s) on the local network, and the printcap file for the remote printer will show up at /var/run/cups/printcap on the client. At that point, the remote printer will be available to your applications to print from. What's wrong with just putting the servers name in /etc/cups/client.conf? There's no need to be running another daemon ... all you need in debian to use cups on another server is cupsys-client and it's depends. Yes, someone else mentioned doing it that way also. Interesting, and I'll have to try it sometime, but right now I'm quite satisfied with how it's all working. Tom -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: How to set up CUPS client
John L Fjellstad wrote: Tom Pfeifer [EMAIL PROTECTED] writes: Thanks for the response, but it's not working. The docs don't help much. A simple example is needed there. Did you check the location entry in the /etc/cups/cupsd.conf? I have this as my location entry to allow systems on my network to print: Location / Order Deny,Allow Deny From All Allow From 127.0.0.1 Allow From 192.168.10.* /Location I think the 127.0.0.1 is the default statement, which would allow the local system to print I finally managed to get it working - and very nicely. Thanks for your help, and to the others who responded also. For the benefit of anyone else trying this, you don't have to touch anything on the client machine(s). Just the default install of the basic CUPS packages is needed on the client. The CUPS daemon running on the client will then automatically discover the printer(s) on the local network, and the printcap file for the remote printer will show up at /var/run/cups/printcap on the client. At that point, the remote printer will be available to your applications to print from. The only actual configuration needed to enable printing from a client is to edit the Location / section in /etc/cups/cupsd.conf on the server machine (the one the printer is connected to) similar to as shown above. This allows printing from a machine other than just the localhost. Of course, to begin with, the printer has to be properly configured on the server machine. This is covered very well in the CUPS documentation, but basically you just point your web browser to localhost:631, and the configuration is menu driven from there. Tom -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: How to set up CUPS client
John L Fjellstad wrote: Tom Pfeifer [EMAIL PROTECTED] writes: Thanks for the response, but it's not working. The docs don't help much. A simple example is needed there. Did you check the location entry in the /etc/cups/cupsd.conf? I have this as my location entry to allow systems on my network to print: Location / Order Deny,Allow Deny From All Allow From 127.0.0.1 Allow From 192.168.10.* /Location I think the 127.0.0.1 is the default statement, which would allow the local system to print Yes, I did try that at one point, but I think it was a case of when I did that, I had something else wrong. I won't go into all the things I tried, but they were all wrong :-) What I'm going to do when I get back to this problem is get the client machine back to a freshly installed state (as far as CUPS is concerned) and start over. I get the feeling this is rediculously easy once you know how to do it. That's always the trick Tom -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: How to set up CUPS client
Stephen Patterson wrote: On Tue, 07 Sep 2004 13:10:07 +0200, Tom Pfeifer wrote: I have 2 machines on a local network, both running Debian/Sarge. One has a printer (Epson SC 660) attached to it's parallel port, and I have that printer set up with CUPS so that I can print to it from that machine. That machine is a CUPS server and client, and it works fine. I used the CUPS web interface (port 631) to set it up. The simplest way is to install these packages on the client (not sure if cupsys-bsd is really needed) cupsys install cupsys-bsd install cupsys-client install libcupsimage2 install libcupsys2-gnutls10 install Cups has a (default enabled) browsing protocol which will let the cupsys server on your client pc discover printers which are configured on the cupsys other server[1]. This should simply work, though if either system has more than one IP or network card, you may need to configure BrowseAddress in /etc/cups/cupsd.conf. [1] OK, I'm simplifying things here. In a more diverse network, any one cupsys process can discover printers on any other cups server. AFAIK even windows can't beat that :) Yes, I have all those packages installed, along with the 2 gimpprint packages. I've gotten to the point now where I realize that the client machine 'discovers' the printer on the other machine without me doing anything - and that does in fact happen on the client. But like I said in my other post, I need to get back to a default CUPS install on the client to undo my other attempts/mistakesand go from there. Tom -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
How to set up CUPS client
Here's my situation: (which has to be a very common one) I have 2 machines on a local network, both running Debian/Sarge. One has a printer (Epson SC 660) attached to it's parallel port, and I have that printer set up with CUPS so that I can print to it from that machine. That machine is a CUPS server and client, and it works fine. I used the CUPS web interface (port 631) to set it up. The part where I'm going blank is how to set up the 2nd machine so that I can use (send jobs to) the printer on the 1st machine. The docs seem to gloss over this, not going into any kind of step by step (or example) as they do with configuring the local machine. In other words, what CUPS packages (if any) are needed on the client machine, and how do I go about accessing and selecting that printer over the network from applications such as Open Office, Mozilla, etc.? I'm sure this is fairly simple, but I just need some kind of a hint (or example) to get started with. This is the first time I've tried CUPS. Thanks Tom -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: How to set up CUPS client
Tom Pfeifer wrote: Here's my situation: (which has to be a very common one) I have 2 machines on a local network, both running Debian/Sarge. One has a printer (Epson SC 660) attached to it's parallel port, and I have that printer set up with CUPS so that I can print to it from that machine. That machine is a CUPS server and client, and it works fine. I used the CUPS web interface (port 631) to set it up. The part where I'm going blank is how to set up the 2nd machine so that I can use (send jobs to) the printer on the 1st machine. The docs seem to gloss over this, not going into any kind of step by step (or example) as they do with configuring the local machine. In other words, what CUPS packages (if any) are needed on the client machine, and how do I go about accessing and selecting that printer over the network from applications such as Open Office, Mozilla, etc.? I'm sure this is fairly simple, but I just need some kind of a hint (or example) to get started with. This is the first time I've tried CUPS. Thanks Tom Thanks for the response, but it's not working. The docs don't help much. A simple example is needed there. I've had enough of this for now. The config files are making my head spin. I'll dig back in again and do some more reading when I get to it, and post if I solve it. I'm just lacking in basic understanding of CUPS right now - and how all the packages fit together etc. Tom -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Real Debian LiveCD?
Preston Boyington wrote: I am involved with a project that is (currently) using Knoppix as a base for a LiveCD. The end result of the project is having a trial cdrom that can then be installed as a real Debian system. I know that there are projects like Morphix (which is what the Debian Non-Profit is based on) and that there are several tutorials on converting Knoppix/Morphix into a Debian system, but is there a better variant out there? Thanks, Preston Mepis (www.mepis.org) is another live CD that is based on Debian. I like it both as a live CD and as an installed system - and it's very straight forward to install to your hard drive. Tom -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Resize partitions urgent help
Carl Fink wrote: On Tue, Aug 03, 2004 at 11:34:29PM +0300, David Baron wrote: When I put in a second disk in my Windows box and could not get fdisk to work, I shelled out the money for ParitionMagic. Does the job--reparitioning is scarey, especially when there is already data on the disk. I used BOOT-IT, which is much cheaper and worked perfectly. You need a Windows system (not necessarily the one being partitioned) to use it, at least the downloaded version -- it's a Windows program that creates a boot diskette or CD-ROM. I haven't tried it under WINE. -- Carl Fink [EMAIL PROTECTED] Jabootu's Minister of Proofreading http://www.jabootu.com If you meant BootIt NG (BING), you don't actually need DOS or Windows to make the diskette. You can create the floppy disk by just copying the raw image (DISKIMG3.DAT) included in the downloaded zip file with a command such as 'cp DISKIMG3.DAT /dev/fd0' And making a bootable CD is just a matter of using that same file as the boot image while creating the ISO file with 'mkisofs', or of course you can also do that from xcdroast etc. Tom -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Installing Debian on second hard disk
Both Debian and Win2k will boot from a 2nd disk, but the difference is this: Debian can be installed to any drive, but if Debian is installed to hda and then you later move that drive to hdb, you'll need to change the /etc/fstab entry for the root partition from hda to hdb. BIOS swapping or remapping in Grub won't work because the kernel ignores these once it takes over on the boot. Win2k can't be installed (directly and completely) to any drive other than hda, but once you do that, that drive can then be moved to the hdb position and then Win2k will boot from that position if you swap the drives in the BIOS or with Grub. Tom Dhiraj wrote: Hello, Thanks for your reply. I now see some possibility that it might work. However, for the problem you are facing, that even when you setup the second(slave ?) HDD as the first one in BIOS, that drive ends up as hdb instead of hda. That I think is because, Linux ignores the BIOS and finds out info about the disks on its own, so it knows that hd0 is not the first hard disk but the second one. I think windows 2000 also functions like this. So, I need to know whether your hard disk was hda or hdb at the time of installation of Debian. If the disk name changes will debian still boot or will it refuse to boot ? I want a separate grub on both hard disks and I will load the second grub from the first one when I want to boot an OS on the second disk, I will remap hd0 and hd1 to fake the BIOS change. Hope I can fool them ! Why don't you too try this out instead of making changes in BIOS everytime you want to boot from the second hard disk. Just write map (hd0) (hd1) and map (hd1) (hd0). This should swap your HDD's without making changes to the BIOS everytime. Then you load the grub on the second disk using chainloader just like we load windows bootloader. thanks a lot Dhiraj Rosenstrauch, David wrote: If I add entries like (hd1,0) and (hd1,1), will the grub on my first disk be able to boot the win2K and Debian on the second HDD. I don't mind if it won't boot win2K but will atleast Debian 3.0r2 boot ? Short answer: yes. Grub on the first disk should be able to boot either of the 2 OS's on the second disk. I just went through this whole issue myself (trying to get 2 drives in my box both able to be booted) which is how I know. I set up my second drive as a fail-safe: I can always boot off that even if I mess up the first one. All I need to do now is go enter the Dell BIOS setup and switch the order of the drives listed and that switches the machine to boot off the second drive. In other words, each drive can function as a stand-alone. It's a complete bootable system complete with its own grub installation. In the above context, by the way, by boot I mean run grub off of. So you can config the 2 drives the way I have them. Or you could have grub only exist on 1 of the drives and always boot (run grub) off of that drive. From that point on grub completely takes over, and you can instruct it which drive and sector you want to load the kernel from (e.g., root (hd0,0) or root (hd1,0)), which drive and sector contain the root file system (e.g., vmlinuz root=/dev/hda1 or vmlinuz root=/dev/hdb1), etc. So bottom line is that grub is completely configurable that way. FYI - the only significant issue I had when setting it up my way is that when I switch the order of the drives in the BIOS, I was surprised to find that the drive that's first to boot winds up always being assigned (hd0) to grub, but when the kernel finally loads it may turn out that that drive is actually /dev/hdb. This confused me for a while till I figured out what was going on, as I assumed that grub's drive assignment should have matched the kernel's. Hope this helps. Email back if you need more clarification. DR -Original Message- From: Dhiraj [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 28, 2004 3:18 PM To: [EMAIL PROTECTED] Subject: Installing Debian on second hard disk Hello, My motherboard has two IDE channles. I have two optical drivers on one channel and my HDD on the second. I have win98SE and Red Hat 7.2 on my current HDD. I am planning to buy a second HDD and install win 2000 and Debian on it. When installing Debian 3.0r2 and win 2000, I would like to take out my first hard disk and put in the blank second one. This is because I am paranoid about something breaking the original hard disk(I spent a lot of time making many things work and installing stuff on my RHL). I fear that if not Debian, atleast win 2K will destroy my first hard disk somehow. Now, when I put in the second hard disk and the first is out, the second one will become /dev/hda but when I re-insert the first one as master, the second one will become /dev/hdb. I have grub as my loader on the first hard disk. If I add entries like (hd1,0) and (hd1,1), will the grub on my
Re: Grub doing strange things
Alan Chandler wrote: I've just switched over to grub. When I boot it seems to automagically include all the kernels installed in /boot in its list after the ones I put there. 1) How do they get there, and can you turn them off 2) Why do they always fail to work (seems they are missing an initrd clause) Just a guess (I use Grub, but not initrd), but it may have to do with how you have the initrd files named. The following is from the update-grub man page: It will also add initrd lines for ramdisk images found with the same version as kernels found. e.g. /boot/vmlinuz-2.4.5 and /boot/initrd-2.4.5 will cause a line of initrd=/boot/initrd-2.4.5 or simliar to be added for the kernel entry in the menu.lst. Tom -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Lilo menu?
Tim Bates wrote: Hi people. What's the go with LILO supplied with Debian 3.0? I cant get it to boot anything other than what it comes with. What's the trick? Where am I going wrong? I added the new kernel I made to /boot/ and the added a section for it to lilo.conf. I run lilo, it says it's added it, but when I reboot Im greeted with a LILO 22.2 message and then after the delay time is reached (tested by upping to 200) it boots the default option (havent tried changing default to see what happens). All I want to do is have the standard Boot: prompt or a simple menu. For the life of me, I cant find anything about what it's doing. Anyone know what to do with it? I need to test my kernel (since it's a scary bugger needing satellite and tv tuner drivers among other things). Thanks in advance Tim Bates You may need the prompt option in /etc/lilo.conf, and then I think the TAB key at the prompt will display the choices. But also read over the man page for lilo.conf, especially about the install= option which you can use to bring up a menu automatically. If in doubt, post the contents of your /etc/lilo.conf file Tom -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: minimal boot loader?
Jason Pepas wrote: hello, I have been reading through a bunch of howto's on creating floppy based linux systems. The process of creating the floppy images strikes me as being way too complicated. In short, is there a program which behaves like this? mkbootdisk --append=kernel boot parameters kernel.img rootfs.img I haven't been able to find anything which takes a kernel image, a root filesystem image, and a boot paramter string, and creates a 1 or 2 floppy set, all in one command. This seems like it would be such a nice thing to have, I just can't beleive no one has done this yet, so I though I'd ask here before I go off and write a script which accomplishes the same thing. thanks, jason pepas The Debian package of grub has something like that called 'mkbimage' (I haven't tried it). It uses grub as the bootloader, which you may or may not want to use Tom -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Where is parport.o ?
Dieter Schoppitsch wrote: Hi all! I try to setup a 2.0.34-Kernel on an older laptop. Unfortunately I'm not able to insmod parport (no module found). It seems that I have to compile a new kernel and new modules - but I didn't find the option Parallel Port Support (General Setup) in the kernel configuration (like it is with newer kernels 2.2). What did I miss? What do I have to do to get parport.o? Thanks for any help. Dieter In the 2.0.xx kernels, there is no parport.o module. You can enable parallel printer support (lp.o) under Character devices -- Parallel printer support. Tom -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: God answeres my prayers to get off this list, NO!, God says,Your pain must endure forever!!!
Glenn English wrote: On Fri, 2003-03-28 at 08:39, [EMAIL PROTECTED] wrote: But you're right -- why should I (or anyone else here) lower myself to eauclair's level. Did you notice his domain: optinsomething-or-other. Is it possible he was a one of those who spam the debian lists? No, it's optonline.net, the same as mine. It's a cable ISP in the northeast USA (NY/CT area). Tom -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: possible IDE hard disk problem
On Mon, Mar 24, 2003 at 10:29:04AM -0500, David Roundy wrote:
Hello all.
I am getting the following error messages on my thinkpad (along with
nasty crashes):
hda: dma_intr: Status=0x51 { DriveReady Seek Complete Error }
hda: dma_intr: Error=0x40 { Uncorrectable Error }, LBAsect=35053408,
sector=5184
end_request: I/O error, dev=03:09 (hda), sector 5184
My web search revealed a few people saying this meant someone's hard
drive was failing, so I've ordered a replacement hard drive and am
backing up the entire contents of my hard drive to another computer
(just in case...). The computer (and thus hard drive) is now one and a
half years old, which seems like a short lifetime for a hard drive,
except that I leave it on constantly, and have been using ext3, so it
hasn't been spinning down.
My kernel is 2.4.20, which I compiled just recently, so another
explanation would be that the new kernel is causing IDE problems.
Prior to this kernel I was on 2.4.17, I believe. For the moment I've
turned off my swap, thinking that that should make hard disk errors
less likely to simply freeze up the system. I just won't run X in my
unstable chroot...
Any suggestions, advice or wisdom?
David Roundy (hoping someone can tell me that when my new drive arrives
I can just save it for a rainy day)
As an aid in determining whether it's really a failing drive vs some
other problem, I'd suggest downloading the test utility from the drive
mauufacturer's web site (IBM's is called Drive Fitness Test), and
running the diagnostic test. It runs from it's own bootable floppy
and it's non destructive to existing data.
Tom
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: format partition
On Tue, Mar 18, 2003 at 03:18:10PM +0100, Goeman Stefan wrote: Hello All, Formatting under linux doesn't include checking the partition (Windoze does this everytime). For FAT32 the actual formatting takes about 2 Seconds. Maybe you _did_ format the partition but expected it to take several minutes. Did you try and mount the partition? mount -t vfat /dev/hdc8 /mnt if that works and the partition is empty it _was_ formatted. Yes indeed it takes only a few seconds. That surprised me. So, indeed i tried to mount it (it work) cp a file to it. Unmount and remount and the file is still there. So, I guess you are right. It is formatted. The problem is that when I reboot in WinNT, the partition is not recognized WinNT says E:\ is not accessible. The volume does not contain a recognized file system. Please make sure So what can I do to make WinNT to recognize the partition?? Greetings, Stefan For one thing, WinNT doesn't recognize FAT32 unless you get a third party driver for it Tom -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: GRUB configuration question
Joseph Monti wrote: Hi all, I am the project manager/developer for GrubConf [http://grubconf.sourceforge.net] (is in beta at the moment). GrubConf is a graphical GRUB configuration tool. I have a few questions for Debian users (I use Gentoo and dont have a system that I can load Debian to and dont know anyone with Debian that uses GRUB). Right now GrubConf thinks the GRUB configuration file is /boot/grub/grub.conf I am wondering, could this assumption fail on a Debian system? If so, what configuration would lead to this? Thanks! - Joe Debian's Grub package (at least as of 0.92) uses /boot/grub/menu.lst as the configuration file. That's also the name of the config file referred to in the Grub manual - see link below. http://www.gnu.org/manual/grub-0.92/html_mono/grub.html#Configuration The Debian package also includes a script called 'update-grub' which will generate /boot/grub/menu.lst the first time it's run, and then will update the file on subsequent runs if, for example, you upgrade your kernel or add another kernel etc. Tom -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: did lilo rewrite my boot sector?
Matt Price wrote: Hi, I was installing a new kernel and accidentally pressed return when asked if I wanted to have lilo rewrite the boot sector of my disk. The install failed, and I want to figure out whether the boot sector was ACTUALLY rewritten. I use GRUB, so I'd really rather not have to deal with setting up the boot loader all over again... Is there a way to look at the boot record and see when it was last modified, or what its contents are? thanks, matt One way to look at disk sectors is by using the hexedit program. Hexedit is a Debian package. It will help if you know where Grub is/was installed. If in the MBR, you could use the command 'hexedit -s /dev/hda' to look at the MBR sector. If installed in the boot sector of /dev/hda1, the command 'hexedit -s /dev/hda1' would show the boot sector for /dev/hda1 etc. Boot sectors installed by Lilo will have the LILO string visible on the first line like this FA EB 32 90 A4 01 4C 49 4C 4F 01 00 16 03 00 00 ..2...LILO.. Boot sectors installed by Grub will have the 'GRUB' string present on the 170h offset line like this: 7D E8 2A 00 EB FE 47 52 55 42 20 00 47 65 6F 6D }.*...GRUB .Geom Reinstalling Grub (if necessary) is pretty simple to do though. Check the man page for the 'grub-install' command. The 'update-grub' command is also good to know about. Tom -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Disk Corruption (was: Disk formatting)
Jonathan Brandmeyer wrote: dmesg shows this interesting entry: Partition check: hda: hda1 hdb: hdb1 hdb2 hdb3 hdb4 hdb5 and the view in cfdisk is: Size: 60040544256 bytes hdb1BootPrimaryLinux ext2509.97 hdb2PrimaryLinux swap1019.94 hdb3PrimaryLinux ext230721.43 hdb5LogicalLinux1998.75 LogicalFree Space25786.26 What if hdb4 is actually a primary partition that I cannot see? This would violate the partitioning rules, wouldn't it? That's just the result of the way cfdisk deals with extended partitions. It doesn't show them in the main partition listing for some unknown reason, but if you use the [ Print ] option, hdb4 will show up there as partition # 4. Tom -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Communicator removed from Testing?
Colin Watson wrote: Leaving it there with known security holes was worse ... If you want it back, there is really only one option: find a developer willing to maintain it properly. That's absolutely all it comes down to. Mark L. Kahnt wrote: As Colin notes in his reply, and was noted in the advisory that DWN noted, it was subject to serious bugs that weren't seeing any sign, in Debian, of getting any better. The source code not being available and not as many using it anymore, it was not showing signs of being fixed to be raised to meet Debian standards for security. The decision wasn't something commercial - it was in keeping with the Debian policies iiuc. OK guys, thanks for the clarifications and explanations. After reading more about this, it's clear that I jumped the gun a bit in being critical of Debian on this issue. Tom -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Communicator removed from Testing?
Mark L. Kahnt wrote: On Mon, 2003-01-27 at 23:58, Curt Howland wrote: Personal reply if possible, I cannot keep up with the traffic on user... Does anyone know why Netscape Communicator has been dropped from Testing? Does Mozilla email load the Communicator mail files ok? Chocolate or Vanilla? Curt- -- Wherever I go, everyone is a little bit safer because I am there. Wherever I am, anyone in need has a friend. Whenever I return home, everyone is happy I am there. ---The Warrior Creed, Robert L. Humphrey, USMC Debian Weekly News warned a while back that it would get the hook, as a) it is non-free, b) it is buggy and not getting noticeably better as Netscape is looking to retire it in favour of Netscape 7, and c) it wasn't even being kept up with the latest releases of that codebase from Netscape. Yes, and with all of that said, some of us still prefer to use it for various reasons. Mozilla is not a 100% replacement as of yet as it runs too slowly on older systems, and in addition, the Mozilla mail/news just isn't as good yet. I know there are other alternatives to look at, as well as other ways to install Communicator. My point is simply that removing the Communicator packages, as justified as it may seem to many, is still something of a disservice to a portion of the Debian community. Tom -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Hard Disk Partition Recovery
Jeetu Golani wrote: Hello guys, Someone I know recently got his partition table destroyed by misusing Norton's Rescue. Anyways, I was able to recreate his partition table using gpart and Fdisk and Debian's installable CD. The partitions are Win95 Fat32 (LBA) partitions. I've setup the Id's on the partitions to reflect these as Win95 Fat32 (LBA) partitions (extended where necessary) I can mount and access the data under Linux. I've even copied the data onto a backup hard disk. Now the mysterious thing is that I can't see these partitions under DOS :( I've used an MSDOS 6.22 disk to boot into the system since the boot loaders not running after fdisk wrote to the MBR and it can't see any of the partitions and pops up the message Invalid drive specification. FDisk shows one of the partitions as Non-Dos and the partition sizes are in negatives. I can't figure out that how I can see everything fine under Linux but not under DOS.how do I get things working correctly?? Any ideas would be appreciated. Thanks To start with, DOS 6.22 would not be able to recognize FAT32 partitions. You would need a Win95b or later MS boot disk to be able to recognize and read/write a FAT32 file system. You can download Win9X boot disks from www.bootdisk.com if you don't have any available. If that's not the entire problem, posting the partition table data here (from Linux fdisk, or gpart etc.) may help expose any problem(s) with it. Tom -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Linux partition question
This could be an issue if your motherboard was more than say 4 or 5 years old (pre 1998 or so) and/or if you were running an older release of Windows or Linux. Win98 can boot from anywhere on that drive and so can Debian stable and testing as long as the motherboard BIOS contains the INT13 extensions. INT13 are a set of BIOS routines that are used to access hard drives. The older version (without the extensions) could not access a drive beyond 1024 cylinders - which is (typically) 8 GB. Tom On Wed, Jan 22, 2003 at 02:51:35PM +, debian parisc wrote: Hello, although I've been reading this list for a few months now I haven't actually installed in on a i386 pc (although I have installed it on a HP Unix server - well smooth). I'm now read to install on my home PC, to ensure that my wife doesn't divorce me I need to make sure that I get it right. I'm going to resize my windows98 partition to free up 10GB on which I will put 2 logical partition of 5GB each (i'll probably run stable on one and testing on the other or maybe woody and mandrake). I'm going to use Partition Magic 7 to resize it. Having looked at the instructions on Powerquest's site it says this IMPORTANT! In most cases, the Windows partition and the Linux Ext2 partition must start below the 8 GB boundary to be bootable. However, if your system supports INT13 extensions, then Windows XP/2000, Windows Me, and some Linux distributions can boot beyond the 8 GB boundary. Check your system documentation to determine if your machine supports INT13 extensions. Does that mean that if my Linux partitions are first I can't boot windows98? or if I put Windows first (10GB) I won't be able to boot linux? and what is INT13? regards Leo It use to be said if your name is not on the LIST you can't come in. I say I'm on the LIST so DON'T CC me Leo... _ Express yourself with cool emoticons http://messenger.msn.co.uk -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Parition mangling tools
Hugh Saunders wrote: hello, standard storry... have xp installation taking up entire hard disk, want to add woody. Have tried the parition resize tool from zeleps.com but havent had any joy with that, any suggestions as to linux tools/alternative dos tools? [could just repartittion then reinstall XP and debian but have mucked about with the XP installation so dont really want to reinstall. Also i dont have the CD [the installation is legal as there is a XP-authenticity sticker on the underside [is laptop]]] [kinda irellevant:] I would just install debian but need windows for two purposes 1. to use the internal winmodem -occasional [usually use wifi but sometimes outta range] 2. to run a realtime audio analyser [for setting up graphic equalisers] thanks, hugh Bootit NG is an excellent disk management shareware program that can resize an NTFS partition non-destructively, among other things. It's also a boot manager (and a very good one), but if you just want to use it for partitioning, you can just download the zip file, make the floppy install disk, boot from it, cancel Setup, and then go into the Partition Work screen where the partitioning tools are available. http://www.bootitng.com Tom -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Boot Disks
Keith O'Connell wrote: Hi, I have clearly misunderstood the making of boot disks and would like some guidance. I made some for each machine here in case or emergency, and thought I would test them, and each one halted with a kernel panic. I assumed that a floppy in the drive of a working machine followed by the command mkboot as root would create a boot disk from the currently running kernel. The disk booted to a panic. I read over the rather small man page and tried the full complement of switches of mkboot -r /dev/hda3 -i /vmlinuz but still there is a panic I have 2.2.20 and 2.4.28 on each machine, and want to be able to use a floppy to boot one kernel and another floppy to boot another kernel. How do I make these disks? I have tried the man pages and the books on the shelf, but I am not getting it. What is the right way to create the floppy disks I want? Anyone? Keith -- There's several ways other than mkboot One very simple method is to just copy your kernel to the floppy disk (the raw device), and then set the kernel's root device. Insert the floppy, *don't* mount it, and then: cp /boot/your_kernel /dev/fd0 rdev /dev/fd0 /dev/your_root_partition To check the root device: rdev /dev/fd0 The kernel will bootstrap itself, mount the root partition and go from there. The disadvantage of that method is that it's slow on boot, and you need one disk for each kernel you might want to boot. It's slow because the kernel has to uncompress and load itself from the floppy disk. Another way is if you have Lilo installed, and already have a valid /etc/lilo/conf for booting off the hard drive. Take that /etc/lilo.conf and change the boot= parameter to boot=/dev/fd0. Then run 'lilo' with a floppy disk inserted in the drive. It will write the Lilo boot sector to the floppy disk. On boot, it will read just the one sector from the floppy, and do the rest from the hard drive - much faster. And you will have the same menu as when booting normally. If you use grub, you can do a similar thing, and can also just make a generic grub boot disk where you specify the kernel and root partition interactively from grub's shell. The command to make the generic grub disk is 'grub-floppy /dev/fd0'. If you like grub, it's not a bad idea to have one of those around. Tom -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: why boot using floppy is very slow?
debianlist wrote: I boot my DEbian 2.2R4 using floppy,but the process is very slow..at least much slower than other linux distr...how can i improve the speed based on boot by floopy...(there is no hardware problem) i have a 2.2r4 boot floppy,,can i boot 2.2r5? As was mentioned in the earlier response, how slow the floppy boot is has much more to do with what type of boot floppy it is, rather than what distro it was made from or what version of potato you're running. Most likely it is loading the kernel image from the floppy disk, which takes a while. You can configure Lilo (or Grub) to boot from floppy disk so that only the first sector is read from the floppy disk, and then everything else is loaded from the hard drive. That will be much faster. To do that, you'll have to configure Lilo to install it's boot sector on a floppy (boot=/dev/fd0). The man pages for lilo and lilo.conf, as well as the Lilo manual in /usr/share/doc/lilo/Manual.txt.gz, have the information you need. Tom
Re: Partitioning a working NTFS drive
Patrick Kirk wrote: Hi all, I want to install on a laptop that has one 7 Gig ntfs partition. I do not want to reinstall win2k or its apps. Can this be done? -- Best regards, Patrick Kirk As an alternative to buying Partition Magic, try Bootit NG. You can make the floppy disk, boot from it, cancel it's Setup, and then use the partitioning tools. It can resize NTFS. http://www.bootitng.com Tom
Re: Does anyone know a good X windows documentation
der der wrote: For example setting up the video card, monitor and the differences between the different window managers... would like to hear from someone. Another window manager to take a look at is icewm which I use, or the gnome compatible version of it icewm-gnome. I like it, some don't, but it's probably one of the easiest to use and configure. Also know that there are some companion packages for it such as a config program (icepref), a menu editor (iceme), and a themes package (icewm-themes). In woody there's also a lightweight version (icewm-lite), and a new experimental version (icewm-experimental). Tom
Re: Another off-topic -- EXT3 question
Hall Stevenson wrote: Is there some app that tells me what type my partitions are mounted as ?? I'm now running 2.4.16 with ext3 enabled after running a patched kernel for quite some time... Is it 'df -T' that you're looking for?
Re: vintage lilo interface
Recent versions of lilo have /boot/boot.b as a symlink to /boot/boot-menu.b, which gives you the color menu. To get the plain menu back, you can either use 'install=/boot/boot-text.b' in /etc/lilo.conf, or change the /boot/boot.b symlink to point to /boot/boot-text.b Tom Peter Jay Salzman wrote: hi there, awhile ago, lilo changed formats -- it was just black and white text, and now it shows a red menu that you can choose a kernel to boot. i'd like to get the old interface back. is this possible? pete
Re: OT: How long has your Linux system been up ?
Frank Zimmermann wrote: Just curious how long people have left their system running without reboot. I once left my server at a co-locate for over 3 months and it ran fine. In three years, I have never had to reboot because of crash. I have rebooted about once every 3 to 4 months (guessing average) after maintenance. This was voluntary, not necessary. I don't run X either (dedicated server mail/ftp/web). Anyone have any really long times for X and non-X systems? Paul As long as your talking about servers this uptime thing is ok, but when talking about workstaions it's redicolous, premature and an unjustifiable waste of natural resources. I sometimes think Linux users just do this to show their Windows using friends how cool they are. I shut down my machines at the end of the day. Frank I agree. It's not like this has to be proven any longer. Linux will basically run forever unless interrupted by power failure or hardware failure. Tom
Re: Debian-lilo
Windows rewrites the MBR on install and makes itself the default OS by setting it's own partition active. To fix this you can either: 1) Boot from a Linux boot disk (such as you hopefully made during the Debian install) and reinstall Lilo. 2) Boot from a DOS/Win9XX boot disk and run fdisk to set the Linux partition active. On reboot Linux should boot, then reinstall Lilo. For future use, it's also good to have a self contained Linux around, either on floppy or CD, from which you can boot and make these kinds of repairs. A good floppy disk is tomsrtbt, and if you can burn CDs, look into the LNX-BBC - it fits on a business card CD and has just about everything you could possibly need on it. Here's the links for those two: http://www.toms.net/rb/ http://www.lnx-bbc.org/ Tom Joop Stakenborg wrote: On Thu, 15 Nov 2001 13:41:02 + Graeme Orton [EMAIL PROTECTED] wrote: Hi i have my hard drive partisioned. One for Linux (debian) and the other for windows. I had lilo configured to load windows as default and to stop it i pressed 'shift' to boot debian. I recently installed windows-xp professional and lilo load has dissapereard and i cant get in linux. Does windows-xp pro allow the lilo config boot? If not is there a way around this problem? Do you have a boot floppy with debian on it? Thats should do it for the time being. I guess windows-xp uses it's own boat loader, like NT does. There are documents on the web that describe how to use the NT bootlader to use the linux kernel. You might think off a similar solution for XP, but I am guessing here Regards Graeme. Joop -- Joop Stakenborg FOM-instituut Rijnhuizen tel. 030-6096862
Re: old PCMCIA+2.4
This page has some information it, although you may have seen it already: http://pcmcia-cs.sourceforge.net/ftp/README-2.4 One of the key things on that page is that CONFIG_PCMCIA must be disabled in the 2.4 kernel config in order to compile the PCMCIA modules the old way. I haven't tried what you want to do for 2.4 (I'm using the 2.4 kernel drivers for PCMCIA). If you install the Debian pcmcia-source package, the README file in the debian directory of that source tree gives some build information also. Tom Osamu Aoki wrote: Hi, Does anyone know howto compile 2.4 kernel with PCMCIA driver from pcmcia-cs source. This is needed to get my old 486DX2 notebook used as my gateway moved to 2.4 and get transparent proxy enabled. I tried make-kpkg modules-image etc. But no success. 2.4 normally uses new PCMCIA support which only (I think) supports new cardbus interface since it uses yenta.c driver in kernel source. How can I replace this yenta driver with traditional 2.2 style PCMCIA module?
Re: Autodetect hardware...
To add to the previous message about needing the newer version of modutils with a 2.4.x kernel. If you're running potato (stable), you'll need to go here to find that deb package along with some others you'll need: http://www.fs.tum.de/~bunk/kernel-24.html As far as other software packages that need to be upgraded to run 2.4.x, the following excerpt is taken from the Changes file in the kernel's documentation: Current Minimal Requirements Upgrade to at *least* these software revisions before thinking you've encountered a bug! If you're unsure what version you're currently running, the suggested command should tell you. Again, keep in mind that this list assumes you are already functionally running a Linux 2.2 kernel. Also, not all tools are necessary on all systems; obviously, if you don't have any PCMCIA (PC Card) hardware, for example, you probably needn't concern yourself with pcmcia-cs. o Gnu C 2.91.66 # gcc --version o Gnu make 3.77# make --version o binutils 2.9.1.0.25 # ld -v o util-linux 2.10o # fdformat --version o modutils 2.4.2 # insmod -V o e2fsprogs 1.19# tune2fs o reiserfsprogs 3.x.0j # reiserfsck 21|grep reiserfsprogs o pcmcia-cs 3.1.21 # cardmgr -V o PPP2.4.0 # pppd --version o isdn4k-utils 3.1pre1 # isdnctrl 21|grep version Tom Erik Funkenbusch wrote: Recently, I upgrade my kernel to 2.4.8 from a 2.2 kernel. During the process, my modutils files got overwritten by clean copies, losing all my hardware configurations. I unwisely did not make a backup of /etc before doing this. My question is, is it possible to re-detect all my hardware and generate a new set of modutils files? Since the install program correctly identified my hardware, I must assume there is some way to generate this data. The reason I ask, is that the server is across town and I don't want to have to go over there to check what hardware is inside just to configure it. Any help would be appreciated. Thanks.
Re: Enlarging FAT Partition (in use)
Antonio Alberto Lobato wrote: Hello ! What must I to do to enlarge a FAT partition in use (preserving their datas) to all HD ? I desinstalled Linux from the machine of the my friend and I`d like to restore it HD partition configuration, Windows in all HD. Tom One way would be to download BootitNG (shareware, fully functional), make the install floppy disk, boot from it, and then cancel Setup. That will put you in Maintenance mode where you can access the partitioning tools by clicking on the Partition Work icon. From there you can use the Resize button to resize FAT16 and FAT32 partitions non-destructively. http://www.bootitng.com Tom
Re: apt-get question
Vishal Soni wrote: Does anyone know how I can specify a destination with apt-get? i.e. apt-get installs everything in /usr, but I want to get it to install in /usr/local/... Thanks in advance, v Also, where files get installed to is determined by the package, not by apt-get. Tom
Re: fsck and non-contiguous
To put it another way, that non-contiguous percentage is totally unrelated to whether your drive is failing or not. It's just telling you the degree of file system fragmentation. Tom [EMAIL PROTECTED] wrote: Hi all. You know how every so often while booting debian, fsck will run? well, last week I noticed that after it ran, it said .3% non contiguous. Today it ran and it said .6% non contiguous. My question is.. why diesn't fsck fix the non contiguous errors it finds? about a month ago my hard drive failed. before it failed it was dojng this same thing. when debian wouldn't boot any longer, I ran fsck manually and it didn't seem to work.. Not fsck's fault, the hard drive is completely bad. Could this be a sign of another hard drive failure? (it's a different drive, I tossed the old one) or should I just run fsck as root and fix the non contiguous errors? thanks! xucaen
Re: mformat, boot disks
One way to make a floppy boot disk that doesn't boot with Lilo... 1) copy your kernel to the (umounted) floppy disk using dd or cp: dd if=/boot/your_kernel of=/dev/fd0 cp /boot/your_kernel /dev/fd0 2) tell the kernel on the floppy disk where your root partition is: rdev /dev/fd0 /dev/your_root_partition The kernel on the floppy disk will boot itself, and then mount and run from the root partition on the hard drive. Tom [EMAIL PROTECTED] wrote: I'm running 2.2r3 i-386. 1. When I run 'superformat /dev/fd0' the disk is formatted. However, when superformat tries to run mformat to created an msdos file system, I get the error message 'sh: error:command not found' or something similar. When i simply type 'mformat' i get a similar error message. Should I worry about this? Even if it is not a problem, why am i getting this message? 2. I have successfully made a lilo boot disk using mkboot /boot/vmlinuz2.2.17pre19. But i have also tried copying the binary to the disk using 'cp' and 'dd'. However, these disks are recognized as system boot disks, but the do not successfully boot linux. When booting for these disks the monitor simply displays loading but does not successfully load. Am I copying the wrong file, or will this method simply not work with Debian? Regardless, how can I create a 'normal' boot disk? (one that doesn't use lilo)
Re: mkfs.vfat? where is it ??
Hi, mkfs.vfat is part of the dosfstools package. Disem wrote: I was unable to create an *windows* filesistem... mkfs -t vfat /dev/myharddrivepartition.. mkfs.vfat: no such file or directory is there a feature in the kernel config that I have to enable, or any kind of package that I need in order to mount/create a win partition ? :D edward
Re: Makeing telnet avalible
Assuming you have the telnetd package installed, the telnet server can be enabled/disabled using the 'update-inetd' command. For example: update-inetd --enable telnet update-inetd --disable telnet What it's doing is editing /etc/inetd.conf, which you can also do manually. See 'man update-inetd' for more information. Enabling or disabling root logins is done with the file /etc/securetty, which is part of the login package. Tom Hi It seems (to me) that deaufultly telnet server is disaabled in Debian. How can i set it up? 1. With the root user enabled? 2. Without the root user enabled? Thanks alot cheers, Raffaele -- Raffaele Sandrini [EMAIL PROTECTED] For encrypted Mail get my Public Key from search.keyserver.net ID is: 0xEC4950E9 Fingerprint: FFEA 3317 8624 4771 A05D 2AFA 46A2 A22B EC49 50E9
Re: channging partition sizes without data loss
To resize your root partition with parted, there is a boot disk available at the parted site here: http://www.ibiblio.org/pub/gnu/parted/ You need a boot disk for this since the partition being resized can't be mounted. Tom V.Suresh wrote: I want to shorten my 1 Gig root partition. To around 300-400 MB. Without losing data. I mean, just want to resize the partition. What software should I use? -V.Suresh. Sureshvatusersdotsourceforgedotnet Http://www16.brinkster.com/vsuresh
Re: staroffice package
Dave Sherohman wrote: On Thu, May 17, 2001 at 05:07:58PM -0500, Andrew D Dixon wrote: I just installed it today with out doing this. I just ran the installer from a directory that I created in my home directory. I've only tried the word processor out so far but it works great. What's going to be broken because I didn't do a network install? network install: 100 M[1] + 2 M/user standard install: 100 M/user It's functionally identical, but if you're going to have multiple users accessing SO (bloated stuck pig that it is), the network install saves lots of disk space. [1] I don't recall how much space SO actually takes up, but, given that the install binary it 97 M, it seems safe to assume that it demands at least 100 M to install. Your assumption is very safe. SO 5.2 takes up about 250 MB on my system. Tom
Re: Cloning your Debian system
There is a HOWTO written up on the general subject of copying a Linux installation, and that's what got me started. You can find it here: http://www.linuxdoc.org/HOWTO/mini/Hard-Disk-Upgrade/index.html Tom Viktor Lakics wrote: I got a crazy idea: if you want to make 100 % sure that you do not brake your production system, why don't you have an exact copy of that system before you do an upgrade (or just use that system for trying out things, which you cannot afford on your system). I got a spare 2 Gig partition on my system, and I want to give it a try. I just do not know how to start this? O.K. I could probably do it with hard disk image program, but then what configuration files do I have to edit (exept /etc/fstab) after my root partition moves from /dev/hda8 to /dev/hda7... Anyone have done it already? All comments and possible ways to do it are welcome! Thanks in advance. -- Viktor
Re: Debian box does not 'finish' booting...
That file is normally removed by the rmnologin script located at /etc/init.d/rmnologin. There should also be links to that script in the /etc/rc2.d through /etc/rc5.d directories. The rmnologin file is part of the sysvinit package, and the links to it are installed by the /var/lib/dpkg/info/sysvinit.postinst script during the package configuration. The relevant files are: /etc/init.d/rmnolgin /etc/rc2.d/S99rmnologin - ../init.d/rmnologin /etc/rc3.d/S99rmnologin - ../init.d/rmnologin /etc/rc4.d/S99rmnologin - ../init.d/rmnologin /etc/rc5.d/S99rmnologin - ../init.d/rmnologin If you're missing some of these, the simplest way to fix it might be to just reinstall the sysvinit package like this: apt-get install --reinstall sysvinit Beyond that, if the script exists in /etc/init.d, but the links aren't there, you can manually install the links by using this command: update-rc.d rmnologin start 99 2 3 4 5 . The period at the end is part of the command. See 'man update-rc.d' for more information. Tom Jeremy Higgs wrote: Hi, I'm having some troubles with a Debian/PPC box running mostly testing (woody?) packages... After starting up, I have noticed that the /etc/nologin file is not removed, as it should be, and as a result, I cannot SSH or login with any user except root. Has anyone else encountered this? I'm not sure why it's happening, except that it started a couple of days ago... All of the services start up correctly, and the system seems to have switched to runlevel 2 and run all of the services there, but the /etc/nologin file still exists, even after a number of hours... Are there any configuration files which could have caused this? Thanks...
Re: Getting LILO right
The problem is that you are using the same kernel to boot all 4 installations. Each one of your 4 boot menu choices specifies 'image=/boot/vmlinuz' You have to specify the path to each kernel that you want to run for each installation in /etc/lilo.conf. There's a few ways to do that. For example, you could copy the other 3 kernels to your /boot directory on /dev/hda1, renaming them appropriately - so that you have something like this: # Mandrake stable image=/boot/vmlinuz label=ML7.2_stable root=/dev/hda1 read-only # Debian image=/boot/vmlinuz-from-hda5 label=Debian_stable root=/dev/hda5 read-only # Mandrake 8.0 beta image=/boot/vmlinuz-from-hda6 label=ML8.0_test root=/dev/hda6 read-only # Debian sandbox image=/boot/vmlinuz-from-hda7 label=Debian_test root=/dev/hda7 read-only Instead of copying the kernels, it's probably better to just mount each of the other 3 partitions from MH 7.2, and then specify the path to each of the other kernels in /etc/lilo.conf. Another approach would be to install a separate Lilo in each of the other 3 partition's boot sectors, and then use the Lilo in the MBR (installed from MH 7.2) to chain to the others. Your /etc/lilo.conf for MH 7.2 would look like this: # Mandrake stable image=/boot/vmlinuz label=ML7.2_stable root=/dev/hda1 read-only # Debian other=/dev/hda5 label=Debian_stable # Mandrake 8.0 beta other=/dev/hda6 label=ML8.0_test # Debian sandbox other=/dev/hda7 label=Debian_test For each of the other 3 installs, you would need to install a separate Lilo from that partition in the boot sector of that partition (specify 'boot=/dev/hda5' for Debian-stable etc.). Your boot sequence for the 4 installations would look like this: Mandrake stable: Lilo MBR - kernel /dev/hda1 Debian_stable:Lilo MBR - Lilo /dev/hda5 - kernel /dev/hda5 Mandrake 8.0: Lilo MBR - Lilo /dev/hda6 - kernel /dev/hda6 Debian sandbox: Lilo MBR - Lilo /dev/hda7 - kernel /dev/hda7 Tom Rick Commo wrote: Partitions: hda1 = Mandrake Linux 7.2 (installed first) hda5 = Debian potato (stable - don't play with it) hda6 = Mandrake 8.0 beta1 hda7 = Debian potato (sandbox - play here and then move to stable) Problem: During boot, on any Linux version except ML 7.2, there are dependency errors listed where the error message contains a reference to the kernel in ML 7.2. In order to get a clean boot I have to sue a floppy that was created when the OS in a partition was installed. I've read three O'Reilly books, the LILO HOW-TOs and a lot of posts and replies regarding LILO. In fact one of the O'Reilly books, Linux In A Nutshell, seems flat out wrong in their example. When I try to adapt my lilo.conf to look like theirs it produces LILO syntax errors. Does grub get around these problems? Can (and how do) you install it from binaries? What am I missing? Can anyone give me some pointers? My current lilo.conf file follows the signature. Thanks, -rick boot=/dev/hda map=/boot/map install=/boot/boot.b vga=normal default=ML7.2_stable keytable=/boot/us.klt lba32 prompt timeout=50 message=/boot/message menu-scheme=wb:bw:wb:bw # Mandrake stable image=/boot/vmlinuz label=ML7.2_stable root=/dev/hda1 read-only # Debian image=/boot/vmlinuz label=Debian_stable root=/dev/hda5 read-only # Mandrake 8.0 beta image=/boot/vmlinuz label=ML8.0_test root=/dev/hda6 read-only # Debian sandbox image=/boot/vmlinuz label=Debian_test root=/dev/hda7 read-only # image=/boot/vmlinuz label=failsafe root=/dev/hda1 append= failsafe read-only # other=/dev/fd0 label=floppy unsafe
Re: Tux Laptop Comment and Recommendation.
I have the model that was called the Obsidian when TuxTops sold it, and I believe the Emperor is essentially the same unit except it has updated graphics (like the Dell Inspiron 5000e). I got mine with 256 MB of RAM. I've been very happy with it. It's rugged, reliable, comfortable to use, and without any problems so far. The 15.1 screen is a pleasure, especially in 1400 x 1050. I got it with Debian preinstalled. They did a nice job with that, but I always like to do my own. So I kept the original install on there as a reference, but have shrunk down that partition and added my own Debian installation, plus Win98. I don't use a modem that often, but the Lucent winmodem works fine in Linux when I do use it. I'm using the Lucent ltmodem module which you can find some info on here: http://walbran.org/sean/linux/stodolsk/ I also have the Linksys Etherfast 10/100 + 56k Modem PC Card. Tom hammack wrote: QLITechnology picked up Tux Laptops. Here's what I am thinking about: Emperor (also know as a Dell Insipiron 5000), 15.1, SXGA+ 1400X1050, 128MB, 20GB HD, CD-ROM, 1.44 FD, and Lucent soft modem with Debian factory installed. I know the soft-modem rases a red flag, but QLI says that they will include an open source (new) kernal module that works flawlessly. Supposedly it was written by Lucent Technology. Comment and Recommendations appreciated! thanks John
Re: 2 simple questions
To change the login prompt message, you can edit the file /etc/issue. You will probably have to restart the login on each console for the change to take effect. For example you could log in, and then log out, and you will see the new message. Tom Brad Cramer wrote: I am not really new to linux (used Redhat for 3 years) but I am a recent Debian convert and I have a coulpe of simple questions. I am running Debian Woody and everything is up to date but I want to know how to change the type of system or version of Debian that shows up on a console login screen. Right now it says testing/unstable I looked at /etc/debian_version and it said the same thing there and I changed it to Woody but that didn't make any difference, any ideas? The other question may be a little more complicated. I am using gdm to login and I normaly run Enlightenment but I wanted to try out Gnome but when I selecect it from the gdm menu it starts gnome and kde together. I have replaced the /etc/gdm/Sessions/Gnome script with one that just has exec /usr/bin/gnome-session but that didn't help, if I start kde it works fine and it is a script that just has exec /usr/bin/startkde, any ideas on this one? Thanks Brad Cramer
Re: Choosing the Window Menager
You can use the following command as root... update-alternatives --config x-window-manager ...when you run it, it will look like this: [EMAIL PROTECTED]:~# update-alternatives --config x-window-manager There are 3 programs which provide `x-window-manager'. SelectionCommand --- 1/usr/bin/X11/fvwm95 *+2/usr/X11R6/bin/icewm 3/usr/X11R6/bin/wmaker Enter to keep the default[*], or type selection number: That's for my machine, but it will list your installed window managers, display the default, and allow you keep the current default or choose a new default. Tom Vittorio De Martino wrote: I installed Debian potato 2.2.r2 with X and Enlightenment and Wmaker. Upon startup X chooses the former while I'like like to start with the latter. Where can I tell X to start with Wmaker instead of Enlightenment?
Re: HELP! How do i config lilo?
You have to properly set up the Lilo configuration file /etc/lilo.conf, and then run the 'lilo' command to have the changes to /etc/lilo.conf take effect. You can probably figure it out easily enough by reading the Lilo documentation, and also this HOWTO: http://www.linuxdoc.org/HOWTO/mini/LILO.html If not, post the contents of /etc/lilo.conf and the output of this command: fdisk -l (lower case L, and run it as root) ...and I or someone here will have a look at it. Tom Dou Minggang wrote: There're two OS on my harddisk --Win98 SE2(chinese) and debian linux. But lilo can't load Win98! my E-mail:[EMAIL PROTECTED]
Re: Help! How to find ext2fs on disk
gpart is also in potato (stable). I think it's the same version that's in testing and unstable. Another utility that might help is the DOS-based Findext2, which you can get here: http://inet.uni2.dk/~svolaf/utilities.htm Tom David B. Harris wrote: To quote Christian Pernegger [EMAIL PROTECTED], # The file system must still be valid, save for the first superblock # perhaps - how can I find its beginning and end? I'd just like to get # the data out... Check out 'gpart'. I know it's apt-gettable from Debian unstable, and I'm sure a google/freshmeat search will turn up the homepage. David Barclay Harris, Clan Barclay Aut agere, aut mori. (Either action, or death.)
Re: Small Fonts in Netscape
There's a couple of HOWTOs on fonts that helped me. Both of them have a section on Netscape: http://www.linuxdoc.org/HOWTO/mini/FDU/index.html http://www.linuxdoc.org/HOWTO/Font-HOWTO.html Tom Joshua Kruck wrote: Hello, Does anyone have this same problem? I run my monitor at 1600x1200, so i know my text is going to be small. But some stuff is really tiny, i have always had this problem. Is there anything i can do/ fonts i forgot to install that would fix this? Thanks Joshua -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: possible move to unstable..
As I expected, several others have already filed bug reports on this problem. Tom Bob Hilliard wrote: Tom Pfeifer [EMAIL PROTECTED] writes: This is getting away from the thread's original subject, but the new lilo package that did make it into woody (21.6-2) *is* broken as far as I'm concerned. It replaces your /etc/lilo.conf with it's own (wrong) idea of what should be there, even if you cancel out of the configuration. That's very bad form. You should file a bug report against lilo in that case. Bob -- _ |_) _ |_ Robert D. Hilliard [EMAIL PROTECTED] |_) (_) |_) 1294 S.W. Seagull Way [EMAIL PROTECTED] Palm City, FL USA GPG Key ID: 390D6559 PGP Key ID: A8E40EB9
Re: possible move to unstable..
c) Upgrade to Woody(testing). Woody is the new in-between distribution, which is supposed to be more stable then Sid. For instance, the broken LILO package never made it into Woody. This is getting away from the thread's original subject, but the new lilo package that did make it into woody (21.6-2) *is* broken as far as I'm concerned. It replaces your /etc/lilo.conf with it's own (wrong) idea of what should be there, even if you cancel out of the configuration. That's very bad form. Here's my /etc/lilo.conf before upgrading to lilo 21.6-2: boot=/dev/hdc9 root=/dev/hdc9 install=/boot/boot-menu.b map=/boot/map lba32 prompt timeout=100 vga=5 delay=50 read-only verbose=2 default=linux2218.2 image=/boot/bzImage240.2 label=linux240.2 image=/boot/bzImage240.1 label=linux240.1 image =/boot/zImage2218.2 label=linux2218.2 And here's what I had afterwards: boot=/dev/hdc9 root=/dev/hdc9 compact install=/boot/boot.b delay=20 map=/boot/map append= read-only image=/vmlinuz label=Linux image=/vmlinuz.old label=old The only saving grace is that it does save your old file by renaming it. Time for a bug report, although I suspect this one is already reported. Tom David B. Harris wrote: To quote Marcial Zamora III [EMAIL PROTECTED], # hey all.. I know this mite stir up a great deal of debate, but its not my intention.. Im currently running potato, and thinking bout running unstable.. there are quite a few packages I would like to have in unstable, and I know ahead of time, to successfully install those packages, there are others in the same directory tree that I would need.. from wut I have seen in the entries in the mailing list so far, unstable is not really that *unstable*. The only real concern I think I would have is the move from Xfree86 3.3.6 to 4.0.2.. any of you guys have any input on this ? or any recommendations as to wut to do ahead of time, before I decided to go with a dist-upgrade ? to all who respond, I thank you in advance =) Well, there are a few things you can do; a) Add a deb-src entry in sources.list pointing to unstable, then 'apt-get source package that you want', then go into the newly created directory and(as root) 'dpkg-buildpackage -uc -b'. That'll give you a nice binary .deb built for your platform. This isn't guaranteed to work(since you're compiling a Sid package on a Potato machine), but it's always worked for me. b) Upgrade to Sid(unstable). It runs fine on my machine, but there are two things you should worry about: the upgrading process itself seems to be touchy - so you might run into trouble there. If you jump that hurdle though, you're probably set. The second thing is that you should be familiar with system recovery. For instance, a new LILO package was uploaded to Sid recently, and it made more than one machine unbootable. So, you should be able to restore things on your own. Also keep backups. :) Also, if something breaks, people are much less likely to sympathize with you, since you're running Sid(unstable), and you should know better ;) c) Upgrade to Woody(testing). Woody is the new in-between distribution, which is supposed to be more stable then Sid. For instance, the broken LILO package never made it into Woody. This is what I suggest to most people who ask about the different versions. Woody/testing is a nice compromise - you get relatively up-to-date packages, and your system isn't nearly as likely to die because of it. Currently, Woody is using XFree86 3.3.6, so if you upgrade to Woody, you won't need to worry about 4.0.2 yet. Hopefully, by the time 4.0.2 gets into Woody, a nicer setup program will exist(since the 3.3.6 and 4.0.2 config files are vastly different). Right now, there's 'xf86config', which is an admirable stop-gap measure, but it's not right for at least 60% or the users out there. David Barclay Harris, Clan Barclay Aut agere, aut mori. (Either action, or death.) --
Re: /proc/partitions blocks ?
Each block is 2 sectors, or 1024 bytes (1k) To convert #blocks to MB, just divide it by 1024. Example: 8001 blocks as shown in /proc/partitions would be 7.81 MB. Tom ktb wrote: I'm looking at the /proc/partitions file and it lists block sizes. I've been looking on the web, archives, docs on my system and can't find what the formula is for converting blocks to MBs. Does anyone know how to do this or where to find the info? Thanks, kent -- I'd really love ta wana help ya Flanders but... Homer Simpson
Re: bin86
That error seems to get just about everyone when compiling a kernel the first time. If you look back in the debian-user archives far enough, you'll find me asking about it. The base system is only meant to get enough of a running system so that you can then go ahead and install the rest. It should be kept that way. Tom Ken Weingold wrote: The debian.org site says that bin86 a complete 8086 assembler and loader which can make 32-bit code for the 386+ processors (under Linux it's used only to create the 16-bit bootsector and setup binaries). It is not installed in the initial Debian install. Both times I have done new installs of 2.2r2 and gone to rebuild a new kernel (from the source from kernel.org) the build has stopped with an error that it can't find as86. I install the bin86 package and run make again and it goes fine. Am I missing something else that should be there to build the kernel or is bin86 really needed? I am wondering which since if the second, bin86 should be installed with the base system. Thanks. -Ken -- [EMAIL PROTECTED]AIM: ScopusFest
Re: sharing internet between WINDOZE and LINUX
If it's an external modem, I can suggest looking into something like the Linksys BEFSR41, which is a 4-Port Cable/DSL Router: http://www.linksys.com/products/product.asp?prid=20grid=5 I'm using it now on my 3 machine home network to share my cable internet connection. It's easy to set up, and you get firewall protection in the bargain. Other vendors have similar products Tom Cameron Matheson wrote: Hey, My family's crappy windows computer has this beautiful DSL connection, which I have lusted after for many months. Anyway, I can't steal the modem or anything, so I was wondering, is their a way to share a window's internet with a linux box? Thanks, Cameron Matheson
Re: Going Debian: advice request
To answer one of your questions Once a stable version is released, it only gets updated (primarily) with security fixes. In other words, you won't see XFree 4.X, etc. in potato. So potato will never become woody, but rather woody will become frozen for testing, and then stable when it's released. As soon as woody goes frozen, a new unstable branch is started to pick up where woody left off. Tom Rodolfo Canet-Castello wrote: Hi all After long doubts and four years using Linux, I'm finally decided to use Debian as my distro and not change anymore. Would you kindly clear some things to me? I'm thinking of installing potato, since am really fed up of half-boiled distros (RH7, for instance), but I´d like to have some packages in more bleeding-edge versions. Any problem about that? Should I install woody instead if I intend to use non-stable packages? -After reading Debian docs, I don't get how updating works. Should I expect stable packages of gnome 1.2, XFree 4, etc.for potato or they're reserved for when woody becomes stable? In different words: through updating, does potato become woody, or potato doesn't change and it's woody what will change until stability? -How stable is unstable? I'm not running a server, should I go to woody directly? I know these are questions are very newby-like, but you don't know how different Debian sounds for a Red Hat/Mandrake guy. Thanks for all. * Dr. Rodolfo Canet-Castello Instituto Valenciano de Investigaciones Agrarias (IVIA) Dpto. Recursos Naturales Aptdo. oficial. 46113-Moncada (Valencia). ESPAÑA-SPAIN. Phone: 34-96-1391000 Fax: 34-96-1390240 Web page: http://www.ivia.es * Web page of Spanish Group of Soil Enzymology: http://www.ivia.es/soilenzymology/ *
Re: Which Navigator files for 4.75?
Installing the 'navigator' meta-package will cause the 4.76 version of Netscape Navigator to be installed if you do it using apt-get. Assuming you have /etc/apt/sources.list properly set up, you can just do this: apt-get update apt-get install navigator All dependencies will be downloaded and installed automatically. Here's the package information for navigator: Package: navigator Priority: optional Section: contrib/web Installed-Size: 7 Maintainer: Ryan Murray [EMAIL PROTECTED] Architecture: i386 Source: netscape4.base Version: 1:4.76-1 Depends: navigator-smotif-476, netscape-java-476, netscape-base-4 Conflicts: netscape-base-406, netscape-base-407, netscape-base-408, netscape-base-45, netscape-base-4 etscape-base-473, netscape-base-475 Filename: dists/potato/contrib/binary-i386/web/navigator_4.76-1.deb Size: 1050 MD5sum: 739e474e33939546753544a9909dac38 Description: Meta package that depends on other packages This package depends on the real netscape packages, so as to make things easier for people to install. meta-package: yes Tom Jonathan Gift wrote: Hi, I want to get hold of the last stand alone Netscape navigator and there's a great many files on debian, each requiring others. What do I need to get the stand alone Navigator. No email, news, etc. Thanks Jonathan -- Hey, I think I finally got the hang of i-
Exim - mail delivery on a LAN
Apologies in advance for a long post. I have a two machine home network using 192.168.1.X static addresses, both running Debian potato and using Exim as the MTA. Both machines on that network can reach the Internet through a hardware router/firewall (Linksys BEFSR41), and then a cable modem. The router has port forwarding capability, so I have incoming smtp (port 25) forwarded to one of the machines, and I can send and receive mail to/from that machine to/from anywhere on the Internet. To make that work, I use a dynamic dns service so that my Internet email machine has a fully qualified domain name that is Internet visible. Local mail delivery also works fine on both machines (user to user on each host). So far so good. What I can't figure out is how to configure Exim to send mail from one machine to the other on the LAN. And I suspect there is some basic fundamental of email/networking that I don't understand that is blocking the way. My home network setup is very simple: - I call the network 'home' (192.168.1.0) - each host obviously has it's own hostname - so I have newdebian.home and olddebian.home - and those names/addresses are in /etc/hosts on each machine - I don't run a local name server - I use my IPS's name servers - and those IP addresses are in /etc/resolv.conf. - other services such as telnet, ftp, ping work fine using hostnames But I can't get email to work between the two hosts. When I try, Exim just returns it to the same machine, with this message included: A message that you sent could not be delivered to one or more of its recipients. The following address(es) failed: [EMAIL PROTECTED]: unrouteable mail domain newdebian.home The problem based on the error message, is that Exim doesn't know about *.home hostnames. My question is: How do I get it to know about them? I have run eximconfig on both machines, choosing option #1 which is Internet machine. That sets up 2 default router entries in /etc/exim.config as shown at the end of this post. I understand that for non-local mail, a router has to be configured in /etc/exim.conf, which then hands it off to a transport, which I assume would be remote-smtp. Or no? I've been going through the Exim documentation, but it sorely lacks for some SFE (Simple F**king Examples) for those of us with simple needs. Any pointers in the right direction would be much appreciated, as would anyone who can straighten out any misunderstanding(s) I have that are obvious from reading this post BG. Thanks. Here's the routers section on both machines: ## # ROUTERS CONFIGURATION # #Specifies how remote addresses are handled # ## # ORDER DOES MATTER # # A remote address is passed to each in turn until it is accepted. # ## # Remote addresses are those with a domain that does not match any item # in the local_domains setting above. # This router routes to remote hosts over SMTP using a DNS lookup with # default options. lookuphost: driver = lookuphost transport = remote_smtp # This router routes to remote hosts over SMTP by explicit IP address, # given as a domain literal in the form [nnn.nnn.nnn.nnn]. The RFCs # require this facility, which is why it is enabled by default in Exim. # If you want to lock it out, set forbid_domain_literals in the main # configuration section above. literal: driver = ipliteral transport = remote_smtp end
Re: Exim - mail delivery on a LAN
OK, thanks Phil for all the information! I am pretty much stuck in the mud with this, so the detailed help is much appreciated. I won't be getting back to it until the weekend... As far as the name server, I think I'll be OK with that part of it (I've also noted Noah's post below). I had one running for a while out of curiosity, but then uninstalled it, not seeing a need for it. What I typed out above (below now) should be incredibly helpful :) It looks like it will be - again thanks! Tom Phil Brutsche wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 A long time ago, in a galaxy far, far way, someone said... What I can't figure out is how to configure Exim to send mail from one machine to the other on the LAN. And I suspect there is some basic fundamental of email/networking that I don't understand that is blocking the way. My home network setup is very simple: - I call the network 'home' (192.168.1.0) - each host obviously has it's own hostname - so I have newdebian.home and olddebian.home - and those names/addresses are in /etc/hosts on each machine - I don't run a local name server - I use my IPS's name servers - and those IP addresses are in /etc/resolv.conf. - other services such as telnet, ftp, ping work fine using hostnames But I can't get email to work between the two hosts. When I try, Exim just returns it to the same machine, with this message included: A message that you sent could not be delivered to one or more of its recipients. The following address(es) failed: [EMAIL PROTECTED]: unrouteable mail domain newdebian.home You need to get exim to know about the newdebian.home name. The problem based on the error message, is that Exim doesn't know about *.home hostnames. My question is: How do I get it to know about them? You need to run a private DNS server on one of your Linux systems. Both of your Linux systems needs to use your private DNS server for *all* name lookups. As me or on the mailing list if you need help setting that up. When delivering email, SMTP systems tend to use what's called the MX record for a certain DNS name (whether it's tux.creighton.edu or creighton.edu) to know what host should be handling that email. I have yet to find a SMTP agent that can use just the straight /etc/hosts file. I have run eximconfig on both machines, choosing option #1 which is Internet machine. That sets up 2 default router entries in /etc/exim.config as shown at the end of this post. I understand that for non-local mail, a router has to be configured in /etc/exim.conf, which then hands it off to a transport, which I assume would be remote-smtp. Or no? Close. This is what I do to my exim config at home to make this work (obviously the values you use will be different): 1) set local_domains to be the domains you want to route. I have local_domains = /etc/exim/local-domains; /etc/exim/local-domains is a file that contains: localhost kaitain.brutsche.com brutsche.com druid.obix.com kaitain.obix.com giedi.obix.com arrakis.obix.com fury.obix.com aeryn.obix.com 2) create transport definitions to define how to get mail to the destination. I have in the Transports configuration: druid_smtp: driver = smtp hosts = druid.brutsche.com giedi_smtp: driver = smtp hosts = giedi.brutsche.com arrakis_smtp: driver = smtp hosts = arrakis.brutsche.com fury_smtp: driver = smtp hosts = fury.brutsche.com aeryn_smtp: driver = smtp hosts = aeryn.brutsche.com 3) create directors to do the actual routing. I have in the Directors configuration: druid: driver = smartuser transport = druid_smtp domains = druid.obix.com no_more giedi: driver = smartuser transport = giedi_smtp domains = giedi.obix.com no_more arrakis: driver = smartuser transport = arrakis_smtp domains = arrakis.obix.com no_more fury: driver = smartuser transport = fury_smtp domains = fury.obix.com no_more aeryn: driver = smartuser transport = aeryn_smtp domains = aeryn.obix.com no_more I've been going through the Exim documentation, but it sorely lacks for some SFE (Simple F**king Examples) for those of us with simple needs. Tell me about it... It took me a week or two to figure out how to do just this much :) Any pointers in the right direction would be much appreciated, as would anyone who can straighten out any misunderstanding(s) I have that are obvious from reading this post BG. Thanks. What I typed out above should be incredibly
Re: New to Debian, boot problems
Booting Debian (or any Linux) from the 2nd drive with Lilo is not a problem. I'm booting from the 3rd drive. It should be just a matter of getting /etc/lilo.conf set up right, and then reinstalling Lilo by running the 'lilo' command as root. Here's a basic template for /etc/lilo.conf for what you want to do: boot=/dev/hda (install Lilo to MBR of master drive) install=/boot/boot.b map=/boot/map prompt (display Lilo prompt on boot) timeout=100(boot default after 10 seconds if no keybd input) default=debian (set default OS ) image=/path/to/your/kernel label=debian root=/dev/hdb? (your root partition such as /dev/hdb1) read-only(mount root read only until fsck runs - standard) other=/dev/hda?(location of your other OS such as /dev/hda1) label=legacy See 'man lilo' and /usr/share/doc/lilo/Manual.txt for more details on Lilo. Tom Willy Lee wrote: Hello all, I'm new to Debian, used to use RedHat. I installed Debian potato (CD from LSL) along with a new hard drive (installed as 2nd (slave) IDE) recently, and I made the mistake of placing all of Debian, including the root partition, on the 2nd drive. Now, unfortunately, LILO won't boot to the slave drive. I have to boot from the boot floppy I thankfully didn't skip making during the install. I would strongly prefer to be able to boot from the hard drive, using LILO to manage booting Debian and a legacy OS. I would prefer to not reinstall from the CDs, since I would rather not have to configure pnp, X, etc. again. The only other idea I have is to make an ext2 partition on hda, make it bootable, copy all the files that would be in a root partition over, then make lilo boot from there. I already have ext2 partitions on hda, left over from a RedHat install. My Debian install on hdb consists of /, /usr, and /home partitions. How workable does this sound? Has anyone else done something like this? Am I completely insane or missing something obvious? Yours in Debian, =wl -- Albert ``Willy'' Lee, Emacs user, game programmer They call me CRAZY - just because I DARE to DREAM of a RACE of SUPERHUMAN MONSTERS!
Re: install-mbr vs lilo
Essentially, you can use just Lilo by itself, or you can use both. If you could post contents of your /etc/lilo.conf, and a summary of your partitions (fdisk -l), it might be easier to see what the problem might be. Anyway, here's a quick comparison of the two as I understand them: Install-mbr only installs a master boot record, whose function is to: 1) Determine which partition to boot from (from user input or by default) 2) Call the boot code located in the first sector of the chosen boot partition, which then is responsible for actually booting the OS. BIOS == install-mbr in MBR == partition boot code == OS kernel In the case of Linux, that boot code in the first sector of the partition is usually Lilo, which is needed to boot the kernel. Install-mbr itself can not boot the Linux kernel - Lilo is needed for that. So if you use install-mbr, you also need Lilo installed in the partition's boot sector. In the case of NT, Win2k etc., they have their own specific boot code which they automatically install in the partition's boot sector. Lilo is much more versatile, and can install either a master boot record (boot=/dev/hda), or a partition boot record (boot=/dev/hdxx). If installed as a partition boot record, it needs something else in the MBR to call it - like install-mbr, or the standard MS mbr code, or some boot manager like System Commander. (could also be another copy of Lilo). BIOS == something in mbr == Lilo == Lilo menu choice Once you get to Lilo (whether in the MBR or in a partition boot sector), there are two fundamental ways it can boot an OS from there. 1) directly boot a Linux kernel as specified in image= ...Lilo == Linux kernel 2) call a partition boot sector as specified in other= ...Lilo == partition boot code == OS kernel There are almost endless variations of how Lilo can be configured. And actually, much of the Lilo boot code is contained in /boot/boot.b, which is called from the small amount of code that will fit in the boot sector. Install-mbr's code is completely contained in the MBR sector. Both can also be installed in a floppy boot sector. Hope some of this was useful for you Tom Kent West wrote: Note: Please let me know if this comes through as HTML (and accept my apologies) - I'm on a new email client that I'm unfamiliar with. Can anyone explain to me the difference between install-mbr and lilo? I've never really understood the Linux bootstrap process, and although I've read the man pages for these two apps I'm still unclear. History of Problem I'm Trying to Solve I recently discovered install-mbr when I did a Potato install on a new computer; I was VERY pleased with the way it worked because it allowed me to have a dual-boot with NT and Linux in (what's supposed to be only) an NT student lab at school (it's okay; I'm the new lab admin, and I'm experimenting before I openly start trying to introduce Debian to the lab). install-mbr has a very low-profile presence, so no one knows Debian is on the box unless they know to watch for the 3-second long display of the cryptic MBR prompt. Both OSes are on one 4GB drive; NT is onthe first 2GB partition of /dev/hda1, and Debian is spread across 5 or 6 partitions (/, usr, home, var, tmp, swap) on the second 2GB. However, when I tried a similar thing on a friend's computer with his knowledge and blessing, things went horribly wrong. His W2K is on /dev/hda (one partition); most of his data files are on a SCSI drive; and we were installing Debian 2.2 on his third drive /dev/hdb (2nd IDE drive), with 5 or 6 partitions. When it came to installing a master boot record, the options offered during the install didn't seem to quite fit what we needed, so we basically guessed, and the follow up reboot resulted in a bunch of repeating 1's and 0's. Booting off the Debian floppy that was created during the install allowed us to get back into Debian, where we experimented over several tries with lilo and install-mbr. We also tried running W2K's repair option to set the boot record back to Windows'. However, nothing worked. Eventually something (I suspect W2K's repair, but that's another story) totally hosed the W2K installation. So we reinstalled W2K. The MBR prompt still appears. It doesn't automatically boot into Windows, but by pressing A (Advanced), followed by 1 (first partition on the first drive?), W2K's boot handler appears and then W2K boots normally. Alternatively, at the MBR prompt, I can press A, followed by F to boot off the Debian floppy. So at this point, both OSes work properly, but I'm having to boot into Debian off of the floppy. I'm afraid to try lilo or install-mbr again without having a clearer understanding of the two apps. Any information beyond what's in the man pages would be greatly appreciated. Thanks!
Re: Install of VMware
I'd guess (maybe incorrectly) that you are running a newer version of the kernel than 2.2.12, because the latest release of VMWare for Linux (2.02, build 621) has precompiled modules for kernels up to 2.2.15 including 2.2.12. So if you are actually running 2.2.12, then VMware should have just used it's pre-compiled modules. The precompiled VMware modules should be located in: /usr/lib/vmware/modules/binary As the other message said, you can check your kernel version with 'uname -r'. Also, hopefully you are installing using the tar.gz file and not the rpm file. Many who have tried installing on Debian with the rpm (via alien) have had problems. The tar.gz install went very smoothly here on potato. I've recompiled the VMware modules a few times as I've upgraded to newer kernels. Tom John C. Plummer wrote: Hi, Found in the archives that others have loaded vmware on Debian 2.2 w/o too much difficulty. But I had one small problem trying with the install of the current release for Linux. It did not find any prebuilt vmnet modules that worked and wanted to build one. When it asked for the headers location I gave it /usr/src/kernel-headers-2.2.12. It erred with a message that there might be a slight inconsistency between the current kernel and the source headers. Its recommendation was to rebuild the kernel with those headers. However, rebuilding kernels is a little out of my league right now. Using apt-get update and upgrade and trying again did not change the situation. Any suggestions. Should I supply a different location? Should I download and supply a different library? Thanks in advance for your support. If you guys are ever near Johnstown, PA, the pizzas on us. jcp
Re: Install of VMware
Tom Pfeifer wrote: The precompiled VMware modules should be located in: /usr/lib/vmware/modules/binary Of course, they have to be located in /lib/modules/2.2.XX/misc at run time. The VMware installation should normally put them there during the install. Here's what you should see there: (only the last 3 are for VMware) [EMAIL PROTECTED]:~$ ls -l /lib/modules/2.2.17/misc/ total 212 -rw-r--r--1 root root 8500 Sep 10 07:45 lp.o -rw-r--r--1 root root13675 Sep 10 07:45 parport.o -rw-r--r--1 root root11304 Sep 10 07:45 parport_pc.o -rw-r--r--1 root root24028 Sep 10 07:45 serial.o -rw-r--r--1 root root78824 Sep 10 07:45 sunrpc.o -rw-r--r--1 root root26453 Sep 10 07:54 vmmon.o -rw-r--r--1 root root24397 Sep 10 07:54 vmnet.o -rw-r--r--1 root root 8446 Sep 10 07:55 vmppuser.o Tom
Re: hdparm
The package hwtools installs a script at /etc/init.d/hwtools, which is where I invoke hdparm from. I think the default script, when installed, has a commented out section for hdparm. Tom Jamie Raymond wrote: Hi, Where's the best place to put a call to hdparm so that it gets invoked upon booting? (would inserting it into an existing file in /etc/init.d be appropriate?) Thanks, Jamie
Re: Acroread not working
One way to get of the license agreementquit Acroread and go to your home directory and look in the file .acrorc for this line (it's at the end): *ShowUnixEula: false Just make that false, if it's true, and you're set. You have to do that once for each user of course. The OK button should show but Tom Matt Fulkerson wrote: Has anyone else had trouble with acroread? I've installed the Debian package on one potato i386 computer that works just fine. But on another, the pdf files are all garbled, even though xpdf can read them just fine. Also, on this same machine, I get the license agreement every time I run acroread, and there is no ok button to accept the agreement. The window has to be closed using the x-window menu for acroread to continue. I did originally install acrobat reader in /usr/local, but removed that installation due to the same puzzling behavior. Any ideas about what could be going wrong? Thanks.
Re: very simple lan question
The /etc/network/interfaces file is new starting with potato, while previous releases used /etc/init.d/network. Although /etc/network/interfaces would now be considered the preferred Debian way, I don't know of any reason why you can't continue to use the old method if you want. Of course if you try using /etc/network/interfaces, you'll want to disable or comment out the other file. Tom Patrick Dahiroc wrote: this is the first time i've looked at my /etc/network/interfaces file and everything is commented out. currently i configure my network interfaces from /etc/init.d/network. if i set my network from /etc/network/interfaces does this mean that i can remove /etc/init.d/network? what is the preferred way of configuring the network? On Sat, Aug 26, 2000 at 04:38:53PM -0700, Aaron Maxwell wrote: Hi, I have two boxes (one woody, one potato) with ethernet cards, connected by a RJ45 cable. I'd like to be able to ssh/sftp betwixt them. [I admit I don't grok networking much yet (that's partly why I'm doing this, to learn). I've mainly been reading the Net-HOWTO and the man pages for ifconfig, if(up|down), route, and references therein; let me know if there's another FM I should RT.] I've given the two boxes, 'leper-messiah' [1] and 'yomama', which I've given addresses 192.168.0.0 and 192.168.0.1 resp; and I've edited /etc/hosts on each box appropriately. The file 'leper-messiah:/etc/network/interfaces' contains the stanza iface eth0 inet static address 192.168.0.0 netmask 255.255.255.0 The file 'yomama:/etc/network/interfaces' contains this stanza iface eth0 inet static address 192.168.0.1 netmask 255.255.255.0 I've gotten the eth0 interface working fine (I think) on both. For example, on yomama, 'ifconfig eth0' yields yomama:~# ifconfig eth0 eth0 Link encap:Ethernet HWaddr 00:C0:F0:47:A9:A1 inet addr:192.168.0.1 Bcast:192.168.0.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:1 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:100 Interrupt:11 Base address:0xdc00 I've enabled the appropriate services in /etc/services on both machines, I'm pretty certain, so I don't believe that's the problem. I tried various manipulations of the routing table, but they didn't seem to help. I'm not sure what other info is useful, so please ask. Thanks in advance. Aaron
Re: VMware with potato - any issues?
Rick Macdonald wrote: I'm just about to try VMware on my potato system to run Win 95 or 98. Are there any problems to know about? ...RickM... If you have managed to get Quicken 2000 running under wine (I bow), you should have no problems getting VMware to run on Debian potato. You can install it exactly according to their instructions and it works fine. One note: there is a choice between an rpm install and a tar.gz install. I had no problems with the tar.gz, while I've seen where others have run into complications trying to install the rpm package on Debian via alien. Tom
Re: holly crap!
Jaye Inabnit ke6sls wrote: Help, PLEASE HELP I've done somethig very bad.. I did: rm * /var/spool/fax/outgoing I was user not root (little sigh), but I lost a lot of data.. Is there ANYWAY to recover all the lost files in /home/me ??? thanks . . . The Ext2fs Undeletion mini-HOWTO may be of some help. I've never tried file recovery on ext2fs myself. http://www.linuxdoc.org/HOWTO/mini/Ext2fs-Undeletion.html Tom
Re: disk partition using fips
Since you have Norton Utilities, be aware that the Image program that comes with it will typically keep a couple files at the end of a partition. These files will be in the root directory and have names like image.bak, image.idx, image.dat. If you have those they can be safely deleted - Image will regenerate them when you run it again. Also be aware that Image can be configured to run automatically at boot, so if you have that feature enabled, it will recreate those files the next time you boot. Another way that has worked for me is to run the Win98 Defrag program form Start - Run like this: defrag c: /p (assuming this is the c: drive) The /p should put all files at the beginning of the partition, leaving all free space in a conitguous block at the end. Tom \SDI \\\Semiconductor Instruments wrote: I would dearly like to repartition a drive on my systemto give me MORE spacefor linux. So I duely ran noton and defragged, which put all the stuff in the first 10% of the disk. But, looking on the map , the last sector had hidden files on it. So I turned on visualization in Win 98ofhidden file types.and system files- a total of 7 megs ! I realize that I can change all the file attributes somehow (I've yet to find the command under dos ), and then re-defrag , then re-attribute the files asa before. But it strikes me the more intelligent way to do things would be to discover from the fat or somehow else the ids of the files in the last sector. Is there no way of doing this ?? How can you read the fat ? I figure with a bit of math I can work out how to read the darned thing.
Re: 128 bit encryption netscape?
Bruce Stephens wrote: Tom Pfeifer [EMAIL PROTECTED] writes: Take a look at the News section at the fortify site here: http://www.fortify.net/intro.html This says that Fortify is on hold, since 128bit Netscape is available worldwide. I knew that already. What I was asking was why the Debian packages don't offer the 128bit version, even though the changelog implies that they do (or so it seems to me---am I misreading it?).. It means that (for non-US people) there's no apt-get way of getting a 128bit Netscape 4.73, whereas there is for 4.72. Presumably there's no change for US people? It's the same situation for all of us. The 4.73 communicator package doesn't get you 128 bit encryption, and requires the extra step of replacing the 56 bit binary with the 128 bit binary from the tar.gz installation. For what it's worth, that changelog is for the netscape-base-473 package. That package doesn't install any Netscape binaries: [EMAIL PROTECTED]:~# dpkg -L netscape-base-473 /. /usr /usr/share /usr/share/doc /usr/share/doc/netscape-base-473 /usr/share/doc/netscape-base-473/copyright.end-user /usr/share/doc/netscape-base-473/copyright.distributor.html /usr/share/doc/netscape-base-473/copyright /usr/share/doc/netscape-base-473/changelog.Debian.gz /usr/lib /usr/lib/netscape /usr/lib/netscape/473 /usr/lib/netscape/473/netscape I don't know if there are any plans to package the 128 bit version Tom
Re: Is Debian the last OS ?
Arthur H. Edwards wrote: The question was Why is Debian the last, rather than the first, distribution? To a large degree your response is the answer. People brand new to Linux eat kernels, they don't compile them. So, if you don't want it to be the last distribution, perhaps you shouldn't expect them to compile their own kernels! People brand new to Linux also don't know one kernel from the next. I can't see that as a deterrent. So, as usual, Debian has to know itself. It IS the last distribution. It requires more than a newbie level of sophistication. I learned Debian as, basically, a complete newbie to Unix/Linux. I think it's mostly a matter of visibility. Newbies are just not aware of Debian. It also has large rewards. That's for sure!! Tom
Re: Is Debian the last OS ?
Most newcomers to Linux will (understandably) start with a commercial distribution that they can find shrink wrapped on the shelves. That pretty much rules Debian out for them, but those who discover it later on tend to stick with it. Completely new to Linux/Unix, I started with Redhat 4.1, and then later Caldera, and didn't get too far with either one. I got them installed but was pretty much lost after that when it came to configuring them, installing software etc.. Finally I stumbled across a couple of posts about Debian that stirred my interest. I just went to the web site, started reading, downloaded a few files, and soon had the base system installed - this was the bo distribution. Contrary to most, I found Debian to be easier to learn. With the others, the whole system got installed right up front from the CD. But with Debian, I installed it piece by piece, package by package because I was downloading it over a modem. Dealing with it in smaller chunks I found myself leaning how to configure it, catching on to the package system etc., and soon was hooked for good. Tom Mark Suter wrote: Folks, How common is the Debian last practice, that is, try other distributions (including non-GNU/Linux) and then come to Debian to stay? Within Humbug[1], approximately 2/5 of the membership are now Debian users; however, only a few went straight to Debian. For me, Debian is the high point in most respects on a long road. In my work as a Systems Administrator I have used Solaris, Irix, Digital Unix, FreeBSD, OpenBSD and GNU/Linux. Within GNU/Linux, I've used MCC Interim Release, Yggdrasil, Slakware, Redhat and Debian. I still use all the non-GNU/Linux systems at work and they *do* have advantages, e.g. OpenBSD for security and crypto or Solaris for some serious 64 processor hardware; however, I believe that Debian last has allowed me to appreciate how good Debian GNU/Linux really is. Debian is improving all the time. Given the nature of the Debian distribution, I think that it is inevitable that Debian attract more first-time users. I believe that Debian will get there without needing to force it in that direction. For example, we Debian does auto-detection, it will be done *right* and this will be one step towards the first distro status. In any system that novices can use, the challenge is to scale to expert users. By aiming at the expert/developer end of the spectrum, Debian has avoided this very difficult problem. Yours sincerely, -- Mark John Suter | I know that you believe you understand [EMAIL PROTECTED] | what you think I said, but I am not sure GPG key id F2FEBB36 | you realise that what you heard is not Ph: +61 4 1126 2316 | what I meant. anonymous [1] http://www.humbug.org.au/ Part 1.2Type: application/pgp-signature
Re: 128 bit encryption netscape?
128 bit encryption is not available directly from installing Debian packages. There's a few options as far as getting the 128 bit encryption: 1) Install normally using the Debian package(s). This will install the 56 bit version. Then use the fortify packages (fortify and fortify-linux-x86) to install the 128 bit encryption. The fortify packages are in the non-US distribution, but it only works with versions up to and including 4.72. The Debian packages will install to /usr/lib/netscape. OR 2) Install by downloading the 128 bit version directly from Netscape. This will be in the form of a tar.gz file and after extracting the file to a setup directory, the included 'ns-install' script is run to install the program to /usr/local/netscape (by default). OR 3) If you want to install version 4.73 using Debian packages AND want 128 bit encryption, the fortify packages will not work for that version. What you do can in that case (or with any version) is to also install (temporarily) the 'direct from Netscape' tar.gz version just to get the 128 bit binary. You can then copy that binary over the 56 bit version installed by the Debian package. I just did this today on my potato box with Communicator 4.73. The binary copy was like this: cp /usr/local/netscape/netscape /usr/lib/netscape/473/communicator/communicator-smotif.real Tom Mathew Johnston wrote: is there a 128 bit encryption netscape package floating around? I cant find it in my packages list. Thanks :) Mat. -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null
Re: 128 bit encryption netscape?
Take a look at the News section at the fortify site here: http://www.fortify.net/intro.html Tom Bruce Stephens wrote: Tom Pfeifer [EMAIL PROTECTED] writes: 128 bit encryption is not available directly from installing Debian packages. There's a few options as far as getting the 128 bit encryption: Is there some reason for this? It seems at odds with the Debian changelog (see 4.73-17) URL:http://cgi.debian.org/cgi-bin/get-changelog?package=netscape-base-473, so obviously someone thought it would be in the package at some point. What went wrong?
Re: Using Partition Magic with Debian
Partition Magic v4 and v5 both work well as far as resizing, copying, moving Linux partitions. I've never had it do any harm to the ext2fs file system itself. However, when you use PM to resize/move a bootable partition that has Lilo installed in it's boot sector, be prepared to boot with a floppy (or with Loadlin) afterwards in order to reinstall Lilo. PM attempts to to 'fix' the Lilo boot sector to compensate for the resize/move operation - but often gets it wrong. PM will also make changes to your /etc/fstab file that it thinks are appropriate, and will sometimes get that wrong also. Tom [EMAIL PROTECTED] wrote: Has anyone used Partition Magic in order to resize partitions under Debian? The software claims to support resizing Linux EXT2 filesystems, etc, but will I trash my system if I do so? I used Norton Ghost to image my system from a 2.1 gig drive to an 8.4 gig drive and it's working great so far, but I have all this slack space I would like to assign to various partitions, /usr etc. So, has anyone done this sucessfully and/or have alternate methods that can be used to add slack space to existing partitions? Any suggestions would be appreiciated, Regards, Todd
Re: magicfilter trouble (was: apsfilter on Epson Stylus Color... Who can help?)
Andreas Hetzmannseder wrote: I have the SC 660, amd the magicfilter package works well with it. I would like to see your printcap entry. Mine looks like this: lp|esc600|Epson Stylus Color 600:\ :lp=/dev/lp1:sd=/var/spool/lpd/esc600:\ :sh:pw#80:pl#72:px#1440:mx#0:\ :if=/etc/magicfilter/stylus_color_720dpi-filter:\ :af=/var/log/lp-acct:lf=/var/log/lp-errs: But right now the printer does *nothing at all* - not even error messages. I have checked /dev/lp1, so this can't be the problem The SC 600 is well supported. Magicfilter has 3 filters for it: [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] Did you create the filters by yourself? I only found two corresponding driver entries: stylus_color_360dpi and stylus_color_720dpi (with magicfilter version 1.2-28). Please tell me, how you made it work, I'm really curious... Best regards, Andreas 1.2-28 is the slink version. I'm running potato and using magicfilter 1.2-39. I just used /usr/sbin/magicfilterconfig to set it up with no tweaking involved. There was a bug in the 720 dpi filter, but that has been fixed. Here's the (partial) 'dpkg -s output' for magicfilter 1.2-39: [EMAIL PROTECTED]:~# dpkg -s magicfilter Package: magicfilter Status: install ok installed Priority: optional Section: text Installed-Size: 452 Maintainer: David Frey [EMAIL PROTECTED] Version: 1.2-39 Depends: libc6 (= 2.1.2) Recommends: lpr | lprng, gs, enscript Suggests: dvips, pbmplus | netpbm, pnmtopng, libjpeg-progs | libjpeg-gif, libtiff-tools, psptools, recode, djtools, bzip2 Conflicts: apsfilter Conffiles: /etc/magicfilter/[EMAIL PROTECTED] a0c2f4b4679e30888484934a9687363c /etc/magicfilter/[EMAIL PROTECTED] 9df9ac128b5add4b825a1e57bc962ab3 /etc/magicfilter/[EMAIL PROTECTED] 3af72053af945a5194c62b02807628be /etc/magicfilter/[EMAIL PROTECTED] 059cd8e91aaf245fe59972ca2cc8dc65 /etc/magicfilter/[EMAIL PROTECTED] c170b1d25e691c10bbe5f336f7124e35 /etc/magicfilter/[EMAIL PROTECTED] 6b99d025645d38b074a3b0be447262b9 Tom
Re: /bin/kill : Where art thou?
Not sure which Debian version you're running, but in both potato and slink it should be at /bin/kill according to the output of 'dpkg -L'. In potato, /bin/kill is in the procps package, while in slink it's in bsdutils. In both potato and slink there is also a /usr/bin/skill, and it's in the procps package. for potato: [EMAIL PROTECTED]:~# dpkg -L procps /. /etc /etc/sysctl.conf /etc/init.d /etc/init.d/procps.sh /lib /lib/libproc.so.2.0.6 /sbin /sbin/sysctl /bin /bin/ps /bin/kill /usr /usr/bin /usr/bin/free /usr/bin/skill ... for slink: [EMAIL PROTECTED]:~# dpkg -L bsdutils /. /usr /usr/doc /usr/doc/bsdutils /usr/doc/bsdutils/copyright /usr/doc/bsdutils/README.script /usr/doc/bsdutils/changelog.Debian.gz /usr/bin /usr/bin/logger /usr/bin/renice /usr/bin/script /usr/bin/wall /usr/man /usr/man/man1 /usr/man/man1/script.1.gz /usr/man/man1/wall.1.gz /usr/man/man1/kill.1.gz /usr/man/man1/logger.1.gz /usr/man/man8 /usr/man/man8/renice.8.gz /bin /bin/kill Tom Eric G . Miller wrote: I seemed to have lost /bin/kill. Now, I have /usr/bin/kill, but poff (and possibily others) are looking for /bin/kill. I fixed poff, but I don't know what else might get broken due to the disappearance of /bin/kill. Anyway, I was wondering if anyone can shed some light on the movement of kill? I'd think I'd still want a /bin/kill in case /usr isn't mounted. The culprit seems to be bsdutils, but I'm not sure. Ciao,
Re: Debian 2.1 = Kernel problem
Someone can probably help you with that SCSI problem, but failing that, there's no need to buy Debian 2.2 (potato). In fact you probably can't yet anyway since it isn't quite released yet. What you could do instead is download just the handful of files needed to install the base potato system from your hard drive (or from floppies). That will get a bare bones Debian system up and running enough so you can establish an internet connection. From there you can install the rest over the net from within Debian using the apt-get and/or dselect tools. Here's the Debian 2.2 install intructions: http://www.debian.org/releases/frozen/i386/install Section 5 covers install methods, which will tell you what files you need to get started and where to find them: http://www.debian.org/releases/frozen/i386/ch-install-methods.en.html Tom Sven Meister wrote: Hallo Debians, I just received the Debian GNU/Linux 2.1 distribution. It consists of 5 CDs. The first one is the install-CD. On this first CD there is the kernel 2.0 and this kernel will be automaticly installed. But then I'll have the problem that my SCSI-Controller won't be detected. So I need to install the 2.2.x kernel dure the install process. But there's the problem with the first CD. And so my systen will never boot up, because it can't detect my SCSI-Controller. Shall I buy the Debain 2.2 distribution and if so, what is the main difference to the 2.1 one. Sorry if I sometimes ask simple questions, but I'm a newbie in those things. BTW: My SuSE distribution works, but I do not want to use it anymore. I think you all know why, don't you? Thanks to all debains!
Re: apsfilter on Epson Stylus Color... Who can help?
I would also suggest giving magicfilter a try if you don't resolve your
apsfilter problem. I have the SC 660, amd the magicfilter package works
well with it. The SC 600 is well supported. Magicfilter has 3 filters
for it:
[EMAIL PROTECTED]
[EMAIL PROTECTED]
[EMAIL PROTECTED]
Tom
Andreas Hetzmannseder wrote:
I've grown a long grey beard (no, not really :) ...) about the
following problem: Attempting to print a simple text file with
lpr filename on my Epson Stylus Color 600 produces a single line:
Unknown device: escp2
Then it prints the same sentence on new sheets of paper over and over
again, so that I have to remove the paper to stop the printer.
The standard printcap entry by apsfilter looks like this:
lp|lp2|escp2-a4-auto-mono|escp2 auto mono:\
:lp=/dev/lp1:\
:sd=/var/spool/lpd/escp2-a4-auto-mono:\
:lf=/var/spool/lpd/escp2-a4-auto-mono/log:\
:af=/var/spool/lpd/escp2-a4-auto-mono/acct:\
:if=/usr/lib/apsfilter/filter/aps-escp2-a4-auto-mono:\
:mx#0:\
:sh:
The corresponding logfile tells me something like this:
[Total: 1 page on 1 sheet]
/usr/lib/apsfilter/filter/aps-escp2-a4-auto-mono: line 111:
246 Broken pipe
$DECOMPRESS a2ps ${A2PS_OPTS}
247 Done(1) | eval $PRINT_PS
I made several troubleshooting checks:
1. I created a simple printcap entry, which worked just fine. It looked
like this:
lp:\
:lp=/dev/lp1:\
:sd=/var/spool/lpd/lp:\
:mx#0:\
:sh:
2. a2ps and rewindstdin seem to be correctly installed, although not in
/usr/lib/apsfilter (the base directory) as proposed, but in
/usr/lib/apsfilter/bin. To be sure, i copied the two files into the
base directory, but the problem remained.
3. Ghostscript (gs) is installed (as well as netpbm and two
jpeg-libraries: libjpeg62 and libjpegg6a). gs resides in the /usr/bin
directory, which is in the search path of GLOBAL.sh as required.
4. I even forced some debugging output, but I haven't learnt shell
scripting yet, so I don't know what to make of it ... If someone is
interested in this, I will post it.
Have I forgotten something? Did I choose the wrong printer driver
(escp2)? Do I need to install additional packages (like X, which I don't
have at present)? Who has experience in using apsfilter on an Epson?
Please, answer...
Re: How to make a boot disk?
The simplest way is to dd the kernel to the floppy disk, and then set the root device (partition). dd if=/path_to_your_kernel of=/dev/fd0 bs=512 rdev /dev/fd0 /dev/your_root_partition You can verify that the root device for the floppy disk kernel is set correctly by using this command: rdev /dev/fd0 You can also set video mode if you want. See 'man rdev' or 'man vidmode' Tom Marshal Wong wrote: Hey all, You would think that after 2 years of experience with Linux, I would know how to make a linux boot disk, but I don't. So how do I do it? :) I heard of dd the kernel onto disk, but aren't there certain variables that are on the kernel, like the root partition, that must be changed? Any help would be appreciated. Marshal
Re: LINUX ON FAT32
Fips 2.0 is also on the Debian ftp site here: ftp://ftp.debian.org/debian/tools/ Tom Alan wrote: Hi Vijay, Are you using fips v 2.0 (partitioning fat32 is new in this version). I've repartitioned a Win98 PC with fips recently - no problem. I picked up the source and binaries a wee while ago - can't remember the URL (reply to me directly and I can email them to you...).. Cheers, Alan - Original Message - From: Ron Rademaker [EMAIL PROTECTED] To: [EMAIL PROTECTED] Cc: debian-user@lists.debian.org Sent: Wednesday, July 19, 2000 2:58 PM Subject: Re: LINUX ON FAT32 Do you want to remove win98? If so, you can repartition your hd during the installation of Debian (uses cfdisk), in this process you remove the fat32 partition(s) and you can make ext2 and a swap partition, if you also want win98, you can also make a fat32 partition where you can install windows (you'll have to install win98 again, except if you got more then one partition already, in that case you can just remove one of those partitions and replace them by ext2), after that you can use lilo to set up multiboot. Hope this is of any help. Ron Rademaker On Tue, 18 Jul 2000 [EMAIL PROTECTED] wrote: Hi, I have win98 on FAT32. I want to partition the h/d with fips, but it is not allowing me since my pc is with FAT32. I want to load linux after paritioning. Thx. -Vijay.
Re: how do i get sound working?
Another thing that may help is to install the pciutils package (if you haven't already), and run the lspci command. That should give additional info on what Linux is recognizing as far as your sound card is concerned, as well as all your other PCI devices. I have an older version of the PCI64 card, and get this from 'lspci -v' 00:0a.0 Multimedia audio controller: Ensoniq ES1370 [AudioPCI] Subsystem: Unknown device 4942:4c4c Flags: bus master, slow devsel, latency 64, IRQ 9 I/O ports at 6800 As mentioned in the other post, PCI cards don't require you to specify I/O, IRQ etc. In the kernel configuration, you usually just need to enable sound support in general, and then select the correct driver for your card. Mine is ES1370, although yours is probably ES1371. I compiled my sound support directly into the kernel. The other option is to compile it as modules. As an example, here is the sound portion of my kernel config (kernel version 2.2.16): # Sound # CONFIG_SOUND=y # CONFIG_SOUND_CMPCI is not set CONFIG_SOUND_ES1370=y # CONFIG_SOUND_ES1370_JOYPORT_BOOT is not set # CONFIG_SOUND_ES1371 is not set # CONFIG_SOUND_MAESTRO is not set # CONFIG_SOUND_ESSSOLO1 is not set # CONFIG_SOUND_ICH is not set # CONFIG_SOUND_SONICVIBES is not set # CONFIG_SOUND_TRIDENT is not set # CONFIG_SOUND_MSNDCLAS is not set # CONFIG_SOUND_MSNDPIN is not set # CONFIG_SOUND_OSS is not set Tom Bob wrote: alright i've read the sound-how-to but it didn't help me. my sound card is a Creative Labs Audio PCI 64V. im not sure what sound driver i should be using or how to set the irq, I/o port, and DMA settings... running pnpdump does nothing.
Re: Question about partitioning
First of all, if you're installing Debian, I'd suggest going with version 2.2 (potato,frozen) instead of 2.1 (slink,stable). Potato is about to be released and is quite stable. Potato includes the new version of Lilo, so the 1024 cylinder issue is no longer a problem. I strongly suggest reading the Debian install intructions found at the link below. Those instructions include a good section on partitioning. http://www.debian.org/releases/frozen/i386/install Here's a few other points and suggestions that may help: 1) Linux uses it's own file system, so you will have to create Linux partitions for it. Linux partitions don't get drive letters assigned to them, and Win95 will not recognize them. 2) There is no need to remove Win95 in order to install Linux as long as you have enough room. You might be a little tight, but .75 GB should be enough room for a swap partition and a root partition big enough to hold a decent Linux installation. 3) If you don't need your D drive for anything, the most straight forward approach would be to delete that partition, and then use the newly created unpartitioned space to create Linux partitions. I would also suggest deleting the extended partition that contains drive D, and create your Linux partitions as primary partitions. Linux can run from extended/logical partitions, but primaries are generally simpler to deal with. I don't see a need for an extended partition on that small of a drive. That's a personal preference however. 4) You can use Win95's fdisk to delete drive D and the extended partition, and then create and format the Linux partitions during the Debian install process. In general, Linux requires a minimum of two partitions: The main (root) partition and a swap partition, although the swap partition, strictly speaking, is not required. Tom Ed Burke wrote: Hi Gang, I have reconsidered installing linux - now that I have all my ducks in a row. I had NT installed on an ex-corporate machine. So there were a lot of nifty programs but no meat behind them. I opted to discard this and install W 95 instead. I now have it installed on 1.25 Gb of a 2Gb disk. I figured I would install the linux on the remaining disk space. It says I have .98Gb of available space on drive D, drive C has W95. A slight aside here but W95 left me with only 100Mb out of 1.25Gb. Is that right? I'm wondering if I need to partition or can I just install right to the available drive D? there is one folder on D, and it is labled games, I could care less about these. So I presume I can over-write what ever is there. Or maybe I should format D so there is nothing on it. Ah ha, I just remembered the second ?, your documentation says that the OS needs to be loaded in the first 1024 cylinders. What does this mean if I have a split drive how do I know which is the first 1024 cylinders? It sounds as if I should format the entire hard drive, assign the linux partitions, then reinstall W95 when I'm done. Is any of this making sense? Thanks in advance ofr your help. Ed Burke
