Re: Somethings Serious Amiss with JDK?
On Tue, 7 Jan 1997, Lawrence Chim wrote: ugs wrote: 2) When I forced the issue, I got an error similar to the one Joey Hess reported earlier with 1.0.2.2: Whenever I try to run any of the java stuff, like appletviewer, javac, etc, I get this error: [EMAIL PROTECTED] ~/prog/old/javajavac DragItem.java java was not found in /usr/lib/jdk/i586/bin/java easy, as it said it cannot find /usr/lib/jdk/i586/bin/java. you can cd to /usr/lib/jdk/i586/bin, then type ln -s java-jdk java. it is a bug still in 1.0.2-3, hope it fixes in 1.0.2-4 That does the trick. Thanks alot! Paul Serice -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]
Somethings Serious Amiss with JDK?
1) From my tribulations with JDK, I do believe jdk-common and jdk-static depend on each other. Thus, neither can be installed. 2) When I forced the issue, I got an error similar to the one Joey Hess reported earlier with 1.0.2.2: Whenever I try to run any of the java stuff, like appletviewer, javac, etc, I get this error: [EMAIL PROTECTED] ~/prog/old/javajavac DragItem.java java was not found in /usr/lib/jdk/i586/bin/java Sincerely Paul Serice -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]
Re: How do people on this list backup stuff?
Before I tell you what I do to make a perfect and bootable copy of your current Linux setup, let me tell you how I have my hard drives configured. the problem with this is that if you backup errors or a program upgrade that you later decided that you didn't want you can't get to the previous backups because you just overwrote them with the new backup. Absolutely, it is a problem. That's why I keep a second proven but older backup drive. Doesn't solve all the problems, but it will provide an excellent base from which to start repairs. also, it is better to put backups on removable media so that it is possible to move them offsite. and that doesn't mean that you are stuck with tape drives either -- i use a Jaz drive. Yeap. I have a great fear of fire. That's why I put the second drive in a fire proof box. Paul Serice -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]
Re: How do people on this list backup stuff?
I am curious to find out how people back stuff? Specifically I am interested in finding out whether it is necessary to use a tape system or is it also possible to use another hardrive. Afterall, it would appear a hardrive is cheaper than a *quality* tape system? Before I tell you what I do to make a perfect and bootable copy of your current Linux setup, let me tell you how I have my hard drives configured. For my everyday setup, I go into the BIOS setup program and turn off all IDE support and boot from a SCSI hard drive using /dev/sda6. I keep my backup on the IDE hard drive /dev/hda. Thus, to boot my backup, all I have to do is go into the BIOS setup program and enable IDE support. When IDE is enabled, the computer will boot from /dev/hda. Thus, if my Linux partition ever crashes, I don't have to boot a stripped down version of Linux from floppy. Instead, I get the full blown version in the state it was in at the time of the last backup. The trick is to get your current Linux setup (hereinafter known as /dev/sda6) over to your backup partition (hereinafter know as /dev/hda1) and then to make it bootable. Be extra careful with the make it bootable partion of what follows because it entails installing LILO which, if done improperly, can have very serious ramifications. BACKUP TO HARD DRIVE mini-HOWTO (Paul Serice, copyright 1997, use at your own risk, and analogize for your setup!) 1) Format your backup partition: mke2fs /dev/hda1 (Of course, if your backup partition is other than hda1, then use it instead. Needless to say, this step is irreversible so get it right.) 2) Mount the newly formatted partition: mount -t ext2 /dev/hda1 /mnt 3) I'm not sure if this next step is necessary, but delete the lost+found directory on the newly formatted partition. a) cd /mnt b) rm -r lost+found 4) Make an exact copy of your Linux setup and put it on your backup partition: a) cd / b) find / -xdev -print | cpio -pdam /mnt NOTE: I found this method in _Unix Unleashed_. I think it is superior to using tar and gzip. 5) Make your backup bootable: a) Edit /mnt/etc/fstab (*not* /etc/fstab). This file tells Linux which partition you want to use as your root partition. You need to let Linux know you'll be booting to /dev/hda1 as your root partition instead of to /dev/sda6. To accomplish this, you just delete the /dev/sda6 and replace it with /dev/hda1 leaving the rest of that line like you found it. b) Edit /mnt/etc/lilo.conf (*not* /etc/lilo.conf). Near the top of this file find and edit (or create) the lines that say boot=/dev/sda6 and root=/dev/sda6. The first line tells lilo where to install itself (in this case lilo installs itself into the extended partion /dev/sda6. The second line tells lilo that the root partition will be /dev/sda6. On my system, I boot the backup straight from the Master Boot Record. Thus, I edit the boot= parameter to read boot=/dev/hda. Because the root is /dev/hda1, the root= parameter becomes root=/dev/hda1. Analogize as necessary. c) Now, tell lilo to install itself. At this point, you should understand something about lilo. If you are installing lilo for /dev/hda1, it needs to have /dev/hda1 mounted as the root partition. Thus, if you just type lilo, lilo will read /etc/lilo.conf and see your original Linux setup instead of your Linux backup. If you run lilo with the -r parameter, lilo will temporarily switch the root partition to the one you specify. To do this, type lilo -r /mnt. NOTE: Because using lilo can be destructive I suggest you first run lilo using lilo -r /mnt -v -v -v -t. This will run lilo and show you what it will do without making any changes to your system. 6) To restore from your backup, just boot to /dev/hda1 and use it as your original. IMPORTANT: It's a good idea to have a floppy which will let you boot directly to your root Linux partition when your MBR gets futzed. (I use this diskette to boot my original Linux partition so that I may back it up because, once the IDE hard drive is on-line, the BIOS will try to boot my backup skipping the normal bootup procedure of reading the MBR on the SCSI.) To create this diskette, if your kernel is /vmlinuz then 1) fdformat /dev/fd0H1440 to low-level format a floppy. (See man fdformat and man mknod to create /dev/fd0H1440 if you don't have this device already.) Good Luck Paul Serice -- This message was delayed because the list mail delivery agent was down.
Re: Virtual Terminals Greater Than tty8.
What was the command line for your mknod for each one? mknod tty9 c 4 9 mknod tty10 c 4 10 mknod tty11 c 4 11 etc. Paul -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]
What's the trick with X 3.2?
I've looked through the dependencies and I think xlib6 should be installed first. Turns out there is something called xlib that is blocking an easy upgrade. I get the following few errors: dpkg: considering removing xlib in favour of xlib6 ... dpkg: no, cannot remove xlib (--auto-deconfigure will help): gwm depends on xlib (= 3.1.2-4) xlib is to be removed. dpkg: regarding xlib6_3.2-1.deb containing xlib6: xlib6 conflicts with elf-x11r6lib xlib provides elf-x11r6lib and is installed. dpkg: error processing xlib6_3.2-1.deb (--install): conflicting packages - not installing xlib6 Errors were encountered while processing: xlib6_3.2-1.deb === I don't know much about dpkg. I've tried using dpkg -purge --force-depends xlib followed by the same install above. I was able to install xlib6 this way but nothing worked. So, how do I get over this first hump? Thanks Paul -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]
Re: Virtual Terminals Greater Than tty8.
On Wed, 27 Nov 1996, Adam Heath wrote: I just did mknod to create tty9 through tty12. Everything seems to be working fine, but I thought I would just check to make sure those vt's weren't disabled for a reason. You can even go to tty24! To switch, hit LEFT ALT-(F1 - F12) for the first 12, RIGHT ALT-(F1-F12) for the upper 12. I have two dos sessions started automatically on tty23 and tty24 for a DOS based BBS telnet. I've always wondered what the right alt was for. Thanks Paul -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]
Virtual Terminals Greater Than tty8.
I just did mknod to create tty9 through tty12. Everything seems to be working fine, but I thought I would just check to make sure those vt's weren't disabled for a reason. Thanks Paul -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]
Re: xdm -- Second X Session
On Mon, 25 Nov 1996, Joey Hess wrote: Edit /etc/X11/xdm/Xservers. Here's mine: :1 local /usr/X11R6/bin/X vt8 -bpp 16 :1.0 :0 local /usr/X11R6/bin/X vt7 This starts up 2 xdms, one at 16bpp and the other at 256 colors. The vt7 and vt8 are important -- without them, the 2 xdm's fight with each other when they are starting up and do weird things to my video card. Thanks a million! Worked like a charm. Paul -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]
xdm -- Second X Session
Can someone clue me in or point me in the right direction on have xdm start up a second X session on startup. I did manage to change no-start-xdm to start-xdm in /etc/X11/config, and that change now causes xdm to manage one session nicely. So far, I've only been able to manually get a second X session going for root (doesn't seem to work for a normal user :( ) by using the following command line: startx -- /usr/X11R6/bin/XF86_Mach64 :1 But other than this, I have had no success at running simultaneous X servers. Could someone who's trodden this path before pass down some wisdom from the ages? Thanks Paul -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]
Re: cleaning up kernel source
On Wed, 6 Nov 1996, Lars Wirzenius wrote: David Morris: do I want to leave something hanging around /usr/src/linux? Except possibly the documentation, no. Debian distributes the header files as part of the libc5 package. So that's what's been going on. What I've been doing is following the instructions in /usr/src/linux/README and creating pointers in /usr/include to the kernel source tree (right now for 2.0.24). Which way is better? Thanks Paul Serice -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]
When on the updates?
I'm fairly new to debian. I see on the debian-changes mailing list where some security upgrades have been released. I've check the debian ftp server for about a week now and the upgrades don't appear there. Am I checking in the right place? If so, about how long is it between the time an upgrade is announced on debian-changes and the time it is ftp-able? Paul Serice -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]
