Re: debian2.2r4 and MatroxMillenniumG450
FYI, debian-release is not a list for helping users. Try debian-user or debian-devel. Also, since almost all your problems relate to X11, there's a Debian X11 mail list too, see URL:http://lists.debian.org/. I'll answer anyhow. Lars-Eric Gustavsson [EMAIL PROTECTED] writes: After these really annoying Debian sessions my suggestions are: 1. Fix the supposed bugs in the anXious mouse etc selections part, and try to autodetect more things, please The X configure has radically changed for the upcoming Woody release, using something called dexconf. anXious is dead. 2. IMPORTANT!!: If the XF86Config file plus the X server don't function together with the hardware, either go back to a rather safe video mode (as the one already used in the XF86Setup program ! ), and/or let the user do this by pressing Esc if he doesn't see a good picture after some seconds Dunno about this one. I think dexconf picks conservative defaults. 3. Write some good information for the poor Millennium G450 users (am I the only one to have met these problems ??), maybe also suggest an XF86Config file that could be tried, and tuned ... Sounds like something for the XFree86 folks more than us. The upcoming Debian 3.0 release, btw, uses XFree86 4.1.x. 4. Put all your possible efforts on enabling the 4.0 version of XFree86 into your Debian system (which would solve the Matrox problems, too, I guess ) Already done, see above. -- ...Adam Di Carlo..[EMAIL PROTECTED]...URL:http://www.onshored.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: potato installs and the aftermath
brian r [EMAIL PROTECTED] writes: First, once I have Debian running I really like it. Especially the apt-get solution for upgrading. However, I have installed Debian on 3 different workstations and 1 file server and the process was very different each time. How so? From the point of choosing which device driver modules I want to getting everything working. Why? One time I choose the simple method for choosing packages and then it didn't give me a choice but just installed a minimal set and quit--e.g., no man command or pages! The easy method is called 'tasksel'. You can run it even after installing (as root). You are probably going to 'tasksel', but not picking any packages. That is the only reason why it might behave in the way you desribe. Take the time to learn how to select and deselect packages. My problem is cdrom won't read audio cd's but I can mount data cds. Ask on debian-user list, this is not an install question. -- ...Adam Di Carlo..[EMAIL PROTECTED]...URL:http://www.onshored.com/
Re: how to use BTS for install disks
Rogério Brito [EMAIL PROTECTED] writes: Yes, exactly that bug. The problem is that the modules are not present in the /target/lib/modules/2.2.19/pcmcia directory (in fact, there is no pcmcia directory). I had been bitten by this bug and I saw at least one more person report it to debian-boot (which I now subscribe). I haven't seen any comments regarding the fix, though. Fixed, but we have other problems now, to wit, the cardmgr stuff which is packed off to the drivers disk isn't showing up like it should... To make *my* matters worse, my card (a vanilla Realted-8139 based PCMCIA card, whose manufacturer has not even included its name on the package) is not supported with the standard pcmcia-cs package. On the other hand, recompiling a new 2.4.9 stock kernel with in-kernel PCMCIA support and enabling the 8193too module seems to work fine. I guess that since 8139-based cards are so common, it would be good if the boot-floppies included support for them out of the box (Red Hat 7.1 does, althought I didn't see what solution they have adopted). [...] And I have already offered my help to the boot floppies team. :-) You're offering to the wrong group. You would have to work out a way so that the 2.2.X kernels and the pcmcia-cs and pcmcia-modules carry support for this device. This probably means working through kernel patches or pcmcia-cs patches. In either case, you must work with the kernel maintainer and/or pcmcia-cs maintainer. I would suggest working out patches and filing Important bugs against the relevant packages. -- ...Adam Di Carlo..[EMAIL PROTECTED]...URL:http://www.onshored.com/
Re: DocBook - db2pdf and db2ps problems
[resending, I had bad mail configuration which killed my outbound mail] Henning Hansen [EMAIL PROTECTED] writes: I tried the debian-user list, but my question was probably too sgml specific, so I repost it here: Ok, I'm crossposting reply. I'm a newcomer to Debian and Linux in general, and my current job is limited to prepare documentation using docbook on Debian. I do have some problems, and when I try to search information about docbook, I end up with RedHat specific advice. Are the following problems with db2pdf and db2ps due to my Debian installation, and does anyone know what to do about it: - Graphics, especially for PDF output: I have been adviced to use the PNG graphics format, but my version of the docbook tools (probably jadetex) does not know .png. OK, I can do without PNG, but worse is that I cannot find a way to include graphics in PDF files at all. PDF is also not known as a graphics format, and other formats don't work. I think you are pointing out that docbook doesn't recognize PDF as a graphics notation. This is true and is a known bug in Docbook. You can work around this by putting this in your document preamble: !DOCTYPE ... [ !-- docbook itself should include this -- !ENTITY % local.notation.class | PDF !NOTATION PDF SYSTEM PDF ] - Font problem, Postscript and PDF: I needed to include the 'µ' (micron) letter in my text, and this makes db2pdf and db2ps (dvips to be more exact) ask for a font file called lbmr.pfb. It's not there, and while the letter will be left out in the PDF output, the Postscript file contains no text at all because of this. Ah. This is bug#39711 and is fixed in a rejected upload of JadeTeX. I'll re-upload it, but you'll have to force [EMAIL PROTECTED] to fail. I think it runs by default in tetex even though the actual pfb files are non-free and not included. Would it be possible to send me a *small* docbook SGML file that has these characters? I'd like to follow up with this -- I think there's a tetex bug here that it's enabling the lucidabr font package by default. - BeginPage tag: The beginpage tag does not seem to work at all, it's supposed to induce a pageshift in printed output. I have seen no mention of these problems anywhere, so I wonder if it works for everybody else, or am i the only person to actually prepare documentation for printout using docbook on Debian? Again, provide a sample file, and I can check it. May be a docbook-stylesheets (DSSSL) bug. If somebody can commment on the state of docbook on Debian in general (not specific to my problems above), this will also be of interest. We're actively working right now on compliance with a new packaging format. I've been doing a lot of work on JadeTeX and OpenJade. Apparently, with the woody packages, table output in particular is much much better for the TeX backends. We're also actively working on providing an XSL toolchain, but that still has a while to go. -- .Adam Di [EMAIL PROTECTED]URL:http://www.onShore.com/
Re: Debian installation screens (cont)
Paulo Henrique Baptista de Oliveira [EMAIL PROTECTED] writes:
There is also a make mirror command. But I'm not a developer.
It doens't matter, configure it to use the anonymous rsync ('config'
file).
I have a mirror here but I need to know what dirs are necessary to
compile the boot-floppies.
Too difficult to explain -- please read the fine documentation and
run make mirror instead.
--
.Adam Di [EMAIL PROTECTED]URL:http://www.onShore.com/
Re: Installing Debian on a Mega Raid Controller help!!
Miller, Jim [EMAIL PROTECTED] writes: I am trying to install Debian 2.2 Rev2 on a megaraid controller from AMI. The default kernel freezes when the megaraid driver loads. Try using the 'compact' kernel instead. I have installed 2.4.0 onto the Rescue floppy. The problem I have is anytime the installer tries to mount a drive it returns a permission denied error. The funny thing is if I enter a shell the mount was successful. No idea. We don't support 2.4 kernels on Potato boot-floppies. -- .Adam Di [EMAIL PROTECTED]URL:http://www.onShore.com/
Re: Debian 2.2: download stops during apt-get update
[EMAIL PROTECTED] (Jeff Kelm) writes: I originally sent this to debian-user, but got no response. Perhaps this is the more appropriate list. Well, no, not really, but I'll give it a shot. I am in the process of trying to upgrade my computers to 2.2. My workstation was running 2.0 and my server was running 1.3. When I upgraded my workstation, I started having network problems. Downloading files seems to frequently stop after 1-5 minutes. The network is still up, pinging the source still works. Other connections (e.g., http) still are running. There is just no download occurring! Sometimes everything works great. My slrnpull cron job hasn't worked since the upgrade because it aborts after downloading one group and part way through the next group with the error ***Connection to news.concentric.net lost. Performing shutdown.. Kinda sounds like a kernel issue or a hardware issue. I don't think it's a Debian issue. I thought there might be some problem with the server (acting as my Internet gateway) running 1.3, and since I needed to install a larger hard drive anyway, I did a clean install of 2.2 on the server. Everything goes great until I get to the point of downloading the rest of the system using ftp and apt-get. When I try to do apt-get update the same downloading problem occurs and apt-get times out without getting the full packages listing. I've been using Linux for a couple years now, but I'm no expert. Usually the Debian installs and upgrades work without any big problems. I'm not sure how to go about troubleshooting this one. The log files don't show anything curious. I've checked the archives of this mailing list, but haven't found any mention of a similar problem. So it must be something I'm not doing correctly. Both machines are using 486 processors. They use different network cards (NE2000 and HP J2405A). Ouch. Are you sure you don't have any network flakiness? The cables are good? It sounds to me like a hardware issue. Perhaps you have BaseIO or IRQ conflicts or something since they are rather old machines. Perhaps this happened on both machines as you upgraded the kernel? I really would point to either the physical network or the i386 hardware somehow. Try pulling out other cards, check your bios settings and stuff in proc. Make sure you don't have any IRQ conflicts or anything. Maybe try compiling a kernel just including the drivers you need... -- .Adam Di [EMAIL PROTECTED]URL:http://www.onShore.com/
Re: updated mount packages for Potato
S.Salman Ahmed [EMAIL PROTECTED] writes: FG == Fred Gray [EMAIL PROTECTED] writes: FG Hi, The recent Debian 2.2r2 release shipped with the FG 2.2.18pre21 kernel, which includes significant changes to the FG Network File System (NFS) code. Unfortunately, it did not come FG with a version of mount that is needed to support these FG changes. FG I was going to ask when 2.2r2 was about to be released. That question is answered. Next question: where is the list of changes/bug-fixes/security fixes for 2.2r2 ? see the links on http://www.debian.org/releases/stable/ Has anything major changed in the boot-floppies ? Not really, just bugfixes. See Changelog below. -- .Adam Di [EMAIL PROTECTED]URL:http://www.onShore.com/ boot-floppies (2.2.20) stable; urgency=low * Herbert Xu [EMAIL PROTECTED]: - alpha: Use kernel 2.2.18pre21. -- Herbert Xu [EMAIL PROTECTED] Sat, 25 Nov 2000 15:14:45 +1100 boot-floppies (2.2.19) stable; urgency=low * PowerPC fixes: - Update kernel version to 2.2.18pre21 - Fix the miBoot command line options not to try to force atyfb (should fix color issues on some mach64 cards) - Create /dev/nvram on the root disk - Add nvsetenv and ofpath, as well as fixing the paths for yaboot - No longer include System.map on the HFS (powermac) boot floppy (there isn't enough room with the new kernels) - en/dbootstrap.sgml updates from Ethan Benson to match the new ybin - Bail out earlier in the boot floppy creation process if we can't do it on this architecture - Make CHRP rescue.bin be DOS formatted. Perhaps the same thing needs done to PReP - can PReP even boot FAT images? - Populate /dev/input in the base tarball - adbmouse and friends no longer work with the new kernels. * Build with packages from proposed-updates: - ncurses 5.0-6.0potato1 - modutils 2.3.11-13.1 - dpkg 1.6.15.2 (sparc only) - kernel 2.2.18pre21 / pcmcia 3.1.22-0.1* (all relevant flavors) -- Daniel Jacobowitz [EMAIL PROTECTED] Wed, 22 Nov 2000 11:57:38 -0500 boot-floppies (2.2.18) stable; urgency=low * build with Debian 2.2r1 plus updates (closes: Bug#77459) * Adam Di Carlo: - i386 and sparc use kernel 2.2.18pre21 (closes: Bug#77425) - Makefiles: clean is a bit cleaner - release.sh (i386): also put kernel configs in TOP/flavor (hey, it's a small file); don't leave stranded release/kernel-config file, put it in the bf-common tarball - rootdisk.sh: add pcd0 device mknod (closes: Bug#74322), which MAKEDEV doesn't know about; add gscd and cm206cd devices; remove some hacks on device creation due to bugs fixed in MAKEDEV - dbootstrap: quiet bootarg makes more things shut up; disable the check for root filesystem being on extended partition while LILO is going on the MBR, because LILO supports this now (closes: Bug#64823); add new fullscreen_execlog utility function - debian/control: add Build-Depends and Build-Depends-Indep (closes: Bug#70387); remove required package from depends - documentation: fix links to dselect-beginner (closes: Bug#72870); add a section in the first chapter talking about where to get Debian (closes: Bug#71532); other corrections (closes: Bug#70871); fix linux history link (closes: Bug#76408); enable Polish and Russian documentation now that newer debiandoc-sgml is in Potato; give example TFTP file name on SPARC (closes: Bug#40775); mention problems with booting from IPX (closes: Bug#49172); when reporting bugs on i386, you must report the flavor * Josip Rodin: - documentation: update non-US package numbers * Eric VanBuggenhaut: French updates * Marcin Owsiany [EMAIL PROTECTED]: - Polish updates - documentation/doc-check script added to help translators stay up-to-date - LANGUAGE_CHOOSER integration (closes: Bug#31865) detailed descriptions follow NOTE: i18n integration is not quite complete, but it is very very close; it has specifically been kept out of the mainline version due to some bugs which are expected to be fixed shortly - moved bf-utf from its module to utilities, modified relevant files accordingly - Makefile: added conditional build time depends on libpng2-dev and libpopt-dev - rootdisk.sh: uses LANGUAGE_CHOOSER for compact and idepci i386 flavors, in which case it: uses more blocks, adds fb0 ptyp ptyq ptyr ptys devices, includes a font for bterm, includes a wrapper 'udbootstrap' and modifies inittab accordingly, includes libutf8_plug.so, bterm, all messages files, lc-enabled dbootstrap removed redundand '$' from awk invocations - utilities/bogl/Makefile: added bterm's font reduction to build process - utilitise/dbootstrap/Makefile: added rules necessary for creation of 'dbootstrap-lc
Re: none
Jasper Spit [EMAIL PROTECTED] writes: Hi, Trying to install Debian 2.2 on my new system which has the main hard drive connected to a Promise Ultra 100 connector. Problem ofcourse is that when I boot from the Debian CD, the promise controller and hard drive are not detected. So I created a boot disk with the 2.2.17 kernel and the Promise patches applied. This works, I can boot with the boot disk, and I see that the controller and harddisk are detected (hde, lol !), BUT, now I want to proceed installing from the debian CD. So how can I get my system to boot from the bootdisk I created, and then proceed with the normal setup from the Debian binary #1 CD ? I tried stuff like root=/dev/hdc in the /etc/lilo.conf on the disk, but that didn't work. I think I need to load /install/root.bin on the CD, but how ? I would suggest you make floppies based on the images provided on the cd, simply replacing the kernel on the rescue disk. You'll probably get module errors but that's not a deal-breaker for installation. -- .Adam Di [EMAIL PROTECTED]URL:http://www.onShore.com/
Re: install trouble: stuck at select tasks
Joey Hess [EMAIL PROTECTED] writes: This documentation seems thoroughly out of date, debian 2.1-era. Indeed it is. Sorry. -- .Adam Di [EMAIL PROTECTED]URL:http://www.onShore.com/
Re: Potato install fails to load ROOT image
Stuart Ballard [EMAIL PROTECTED] writes: Sorry to reply to myself, but I've come to the conclusion after further testing that my floppy drive is 100% busted and I'm not going to be able to do anything useful off it. I also can't (practically) replace it. I do have a fully functioning RedHat 5.2 installation on the machine and a fast network connection, but it's one big partition plus swap. Is there any way I can get debian onto this puppy? CD? Install from DOS? Those would be easiest. But I'll assume those won't work. I'm thinking of things along the lines of # cd / # mkdir redhat # mv * redhat # /redhat/usr/bin/tar zxvf redhat/base_2.2.tar.gz Ouch. Do you have a free partition to play with? YOu only need, uh, 150MB or so. But then... - How do I get a kernel? Install from harddisk option, is documented. The problem is going to be starting the system. I don't know what to say about this. Hmm. It might be possible to gunzip and loop mount root.bin and then chroot into it, invoking the busybox init. Never tried it though. - How do I make the system bootable (is LILO in the default install?) Yup, sure. [Possible answer: mv /redhat/boot /boot, and just boot off the old kernel - how much else would have to be preserved, though?] doesn't much matter... - How do I get into the installation system? (presumably base_2.2 doesn't extract to a fully functional distribution, or we wouldn't have an installation program at all...) See above. Note that due to the aforementioned fast network connection, there is no problem getting stuff onto this machine, and it already has linux on an ext2 filesystem, so it should be among the easier cases of this kind of installation. On the other hand, the absence of a working floppy is going to make life hard. Yeah, that's why non-sucky arches like powerpc/sparc etc have openfirmware and better support for fully network installation. One *possible* workaround would be that, since the floppy drive is more temperamental than 100% broken, I might be able to get the rescue floppy, at least, to boot. If I can do this, I can of course enter rescue mode and mount my existing / partition as root, but (at least according to the installation guide) you can't install from a partition onto the same partition. Or, again, if you have disk space to play with, make a little dos partition, then boot from a dos disk and run the loadlin option... What I'm trying to say is, Er, help? Good luck! -- .Adam Di [EMAIL PROTECTED]URL:http://www.onShore.com/
some comments about the potato installation system
I'm putting in a few comments here since the Installation Manual is still so out of date. BTW, we are correcting this in an ongoing fashion; newer versions of the manual are being updated for boot-floppies 2.2.17, but can also be found at http://www.debian.org/releases/potato/ . Be aware that we are still finding and fixing problems in the Potato boot-floppies. The woody effort has branched off under the guidance of Joey Hess; there is another little group including me who are still working on the Potato documentation and bug fixes. (Thanks especially to Joey aka Martin Schulze who is doing a marvellous job going through the bug list.) First off, there are some new boot arguments that aren't well documented which might be very useful to folks. On i386, press f7.txt to see them. Notable is the 'quiet' option, which suppresses a lot of confirmation messages (are you sure? type stuff) as well as trying to go ahead and do the right thing when it seems right rather than asking. This is helpful if you are doing a lot of installations but aren't quite ready for an auto-installer. Another notable option is 'debug', which is good if you are reporting a bug against boot-floppies. This creates extra logging to tty3, which can also be found in /var/log/messages during installation, or /var/log/installer.log after installation. If you are submitting a bug report, it's always appreciated to have the installer.log file. If you are in the midst of installing and have no network or base system yet, one way to copy it over is to tar it to a floppy. Finally, if you are in i386, I really suggest you start off with the 'compact' flavor of disks (images-1.44/compact) on SCSI machines, or 'idepci' (images-1.44/idepci) on IDE machines. These include kernels which are much more reasonable on modern systems than the compatable with everything standard kernel, and only have one driver disk a piece (downside is no sound modules). Anyhow, have fun out there and be sure to report problems as bugs against boot-floppies (or kernel problems as bugs against whatever kernel-image-* package the disk set you have uses). We are listening. -- .Adam Di [EMAIL PROTECTED]URL:http://www.onShore.com/
Re: Mass install / Autoinstall (Was: Re: Debian vs Red Hat??? I need info.)
I would agree most of the proposed solutions are quick hacks. The fact is, we won't be natively supporting bulk installation until Woody. And even that is in question. As I understand it, the proposed Woody install system is debconf based; moreover, debconf can have different backends for receiving configuration info, for instance, an LDAP backend, or a backend that munges an XML file from a web server. Yes, vapor vapor vapor but that's the right way to do it if you ask me. Hopefully debconf will be _de rigeur_ for any package requiring configuration info at pkg install time in Woody, so what we would have is really a general solution rather than just a partial or hack solution. -- .Adam Di [EMAIL PROTECTED]URL:http://www.onShore.com/
Re: Potato boot problems
Christopher DeMarco [EMAIL PROTECTED] writes: I'm using the current disk set of potato boot/root disks (build 2.2.13, 5/5/2000) and the 3-disk set of drivers (May 5 2000). I install the drivers from the disks before doing anything else, assuming that this will allow me to do a http or ftp install. This seems to go alright, but when I try to configure the modules (so as to install my network card) I get a whole lot of ugly messages (they look like sed is barfing) and the list of network drivers is blank. What architecture are you? For a proper bug report, we need actual error messages. You should be able to run things manually or else 1. What's wrong? Probably a bug in boot-floppies, or, rather, modconf. 2. How can I do a network install of potato? If you are on i386, try the idepci or compact flavors. They *may* include support for your network devices. Alternatively, you may be able to 'modprobe' your required modules by hand on tty2. -- .Adam Di [EMAIL PROTECTED]URL:http://www.onShore.com/
Re: Promise Ultra 66
[EMAIL PROTECTED] (Karl M. Hegbloom) writes: The bootfloppies for Slink don't handle UDMA66. You need to use bootfloppies with a kernel on them that's patched for UDMA66 support (using the IDE patches from ftp.kernel.org:/pub/linux/kernel/people/hedrick/). I'm not sure if potato's bootfloppies (will) support UDMA66. Oh, so _that_ is what the ide kernel is for. I wish the long description in the package would at least describe what it's for... Should we create another flavor ide? Yes -- tausq is working on a no-scsi flavor and the ide flavor. We already have the kernel and pcmcia modules in potato for the ide patch flavor. Randolph had a good name for it... I think maybe the name was -idepatch or -udma66. So hopefully we will have this ready soon. -- .Adam Di [EMAIL PROTECTED]URL:http://www.onShore.com/
Re: Booting problem with AMD Athlon
Alain Birtz [EMAIL PROTECTED] writes: I recently bought Debian 2.1 and I tried to install it on my brand new PC. However I was not capable to make it to the installer. When I start from the CD-ROM, I see the boot: prompt, I hit return and then it starts loading stuff, like a normal boot does. However, when it arrives at the line NCR53c406a: no available ports found it hangs there. The cursors waits at the beginning of the next line. Generally, it is the *next* message (the one that doesn't appear) which is the trouble-maker. Some people told me that, because of my Athlon processor, I should try boot floppies with potato. True. I made the floppies and was able to boot from the rescue floppy. It asked me for the root disk and I put it in. It loads the the ramdisk, free some memory, then freezes. here is the log: VFS: Insert root floppy disk to be loaded into RAM disk and press ENTER RAMDISK: Compressed image found at block 0 VFS: Mounted root (ext2 filesystem) readonly. Freeing unused kernel memory: 140k freed _ hangs here Very strange! Here is the list of my hardware: AMD Athlon 550 Mgz 1 IDE hard-disk: 13 gig 128 meg of RAM Nothing SCSI FUJITSU motherboard (AMI BIOS ) Sceptre Monitor 17 inch (VGA comptible) S3 Trio3D/2X cheap graphic card Ethernet card: StarTech Do you have any idea of what could be wrong? Not offhand. We will be uploading a new potato boot-floppies (2.2.5) soon, which is 2.2.14 based. Maybe that will fare better. If not, we'll file a bug against the kernel, that is, file a bug against kernel-image-2.2.14. -- .Adam Di [EMAIL PROTECTED]URL:http://www.onShore.com/
Re: initial boot problem, help request
Floyd Rodgers [EMAIL PROTECTED] writes: trying to initial load slink stable version sparc2 via floppies results in these messages. fatal error: cannot read file system error: bad or malformed address fatal error: cannot read file system fatal error: cannot read file system Please ask on debian-sparc. 2g disk set to address 1. Any ideas? No 'fraid not. Is there any place in Dallas to buy a CD version? No clue. Have you seen the registered distributors on the web site? -- .Adam Di [EMAIL PROTECTED]URL:http://www.onShore.com/
Re: Bootdisk for ThinkPad
Dale, can you try just booting with the rescue disk at http://www.debian.org/~aph/boot-floppies/2.1.12-19991209/ ? Let me know if this doesn't work... -- .Adam Di [EMAIL PROTECTED]URL:http://www.onShore.com/
Re: Bootdisk for ThinkPad
Gunnar Evermann [EMAIL PROTECTED] writes: I've made the same experience with a TP 365XD. Can you try booting from the set at http://www.debian.org/~aph/boot-floppies/2.1.12-19991209/ please? -- .Adam Di [EMAIL PROTECTED]URL:http://www.onShore.com/
Re: A Problem with jadetex
There were quite a few problems with the slink packages of jadetex; it might be easier to upgrade to the relevant potato package. No, the slink version should work fine on a slink system. Mario, can you give me some more details on your system? Assuming you are running standard slink tetex and slink jadetex, all should be well (I use it a lot still). The only reason I can think of for your problems would be if you were using a potato tetex and a slink jadetex, since in potato, tetex moved stuff from /usr/lib/texmf to /usr/share/texmf. After you install jadetex, you should be able to do kpsewhich jadetex.fmt and get a valid response. Can you? -- .Adam Di [EMAIL PROTECTED]URL:http://www.onShore.com/
Re: Booting problems!
[EMAIL PROTECTED] writes: Nathan Duehr wrote: Make sure you try the Tecra disk images I've read it and tried it. But thats a 'no go' Any other suggestions.? If I recall, your problem is that you cannot get past 'loading root.bin' -- or was it 'loading linux'. I would suggest checking the BIOS settings. Make sure processor cache, shadow ram, and all that jazz is turned off. Try a few things. Try removing unneccesary cards. Read the install manual -- it talks about this. This is on a laptop, right? Thinkpad 770? Or was that someone else? If none of that helps, could you fill out a complete report as a bug report against boot-floppies? Include full hardware info and what you see on your screen and all the different stuff you tried. Really sorry for the inconvenience! -- .Adam Di [EMAIL PROTECTED]URL:http://www.onShore.com/
Re: How to do it? [Xserver]
I think your problem is that you need to 'chmod 0666 /dev/fb?'. This is a known bug in the slink Xsun X window system servers. -- .Adam Di [EMAIL PROTECTED]URL:http://www.onShore.com/
Re: Booting problems!
[EMAIL PROTECTED] writes: thank you for reading this message. The first boot for installation of debian 2.1 fails. After 'Loading linux ..' nothing happens, the machine hangs. Generally this means a bad floppy. There are other boot methods also, such as CD-ROM or loadlin from a DOS partition. Soon, TFTP for i386 also. -- .Adam Di [EMAIL PROTECTED]URL:http://www.onShore.com/
Re: Problems installing with Promise Uttra33 (hde hdg)
John Beimler [EMAIL PROTECTED] writes: I switched over to the 2nd virtual console and noticed there are no devices for hde or hdg, so I am guessing this is the problem. I am hoping someone has a quick fix for me. I would like to leave the setup the way it is, the HD controller that is on the motherboard is really flaky. Can't you just bring up the shell in tty2 and mknod these devices? Sorry, I know this is just a workaround ... this is a bug in the boot-floppies that we fixed in mid-April, however, we never made a post-2.1.9 release... Enrique? Feel like burning a boot-floppies 2.1.11 for slink? -- .Adam Di [EMAIL PROTECTED]URL:http://www.onShore.com/
Re: Kernel patches needed for running Informix Dynamic Server Linux Edition
F. Fernandez [EMAIL PROTECTED] writes: I'd like to know where can I find the patches to recompile the kernel 2.0.36 and/or 2.2.x so that the system supports more open files. [...]They also say that the 2.2.5 that comes with RH6.0 already has been patched to work with Informix and Oracle. Are those patches available in Debian? If not, anyone knows where to find them? Pretty much any linux kernel works with Debian. We provide images to get people started but you don't have to run a stock Debian kernel image to run Debian. By no means. In some cases, we provid kernel patch packages to solve problems, generally, patches required for certain architectures. I guess, basically, we just don't feel the need to provide this functionality by default, since most people don't need it, and if you do need it, tweaking the kernel and patching is so easy there's no reason to provide a package. I suggest you just . get the kernel-source package, or download sources from kernel.org or whereever you like to get kernel sources . ferret out the proper kernel patch for whatever kernel you are running (I think it's just a tweak to an include file), then . use kernel-package to compile a new kernel Voila. -- .Adam Di [EMAIL PROTECTED]URL:http://www.onShore.com/
Re: Netscape strange errors
Quoting Adam Di Carlo Do you have the motifnls package installed? You may need to set your XNLSPATH environment variable to /usr/X11R6/lib/X11/nls in order for some Motif applications to work. Paulo == Paulo Henrique Baptista de Oliveira [EMAIL PROTECTED] writes: Paulo Oh. I dont have motifnls installed. I dont know what to do Paulo now!! Try installing the motifnls package. If it's still a problem, try setting the XNLSPATH as indicated above. Thanks. -- .Adam Di [EMAIL PROTECTED]URL:http://www.onShore.com/
Re: Newbie question on dselect
[EMAIL PROTECTED] (Rick Tan) writes: I just successfully installed slink 2.1 on a sparc machine. When I attempted to use dselect to install some other packages off the net, I ran into the following problem. Get http://http.us.debian.org stable/contrib Packages Get http://http.non-us.debian.org stable/non-US Packages Error http://http.us.debian.org stable/contrib Packages Couldn't lookup host http.us.debian.org Error http://http.non-us.debian.org stable/non-US Packages Couldn't lookup host http.non-us.debian.org I believe the errors in the above has to do with the fact that the machine is behind a firewall. Um, no, the errors are because it can't resolve the host names. You have to have a working DNS configuration (man resolv.conf). Alternatively, try IP numbers but I'm not sure if that will work or not. How do set the proxy server information in the system. What program or tool is available for this? Well, this depends on your backend. I deduce you are using apt. In that case, set the 'http_proxy' variable. I do: export http_proxy=http://burrito:3128/ dselect -- .Adam Di [EMAIL PROTECTED]URL:http://www.onShore.com/
slashdot poll
Debian seems to be taking a beating on the recent /. poll of distributions. Have you all voted? .Adam Di [EMAIL PROTECTED]URL:http://www.onShore.com/
Re: Debian goes big business?
On 19 Jan 1999 16:55:29 -0600, John Hasler [EMAIL PROTECTED] said: Shawn writes: I am all for a for-profit business forming as a value-added seller of Debian products. Such a business could focus on pre-installations, packaging and marketing, and user support. Exactly! This is just the sort of company I would love to participate in. I have cross-posted this to debian-devel. onShore, Inc., my company, (not yet listed on the consultants page -- too busy with work and Slink right now) sells bundled GNU/Debian systems, including hardware and support. We are resellers for most major manufacturers. We're basically a consulting company (business to business), not an ISP or box pusher. We also do a lot of open-source development and the like. FWIW, I'm actually starting a push right now to offer bundled Debian/Sparc boxes, since we're also Sun resellers, and since the Sparc architecture has a lower TCO and scales better than x86. We operate out of Chicago and NYC (312 850-5200 and 212 254-0063). -- .Adam Di [EMAIL PROTECTED]URL:http://www.onShore.com/
Re: pkgsel
With respect to pkgsel, I thought our ultimate idea (not really for slink) was to provide actual empty 'metapackages', which are just normal packages with a whole slew of dependancies and a little README/Changelog/etc in /usr/doc/metapkgname . Is this the plan? I'll try to be sure and document how to exploit the existing pkgsel stuff. Anyone volunteering text snippets for the Installation Manual would be appreciated. -- .Adam Di [EMAIL PROTECTED]URL:http://www.onShore.com/
Re: pkgsel
Brandon == Brandon Mitchell [EMAIL PROTECTED] writes: With respect to pkgsel, I thought our ultimate idea (not really for slink) was to provide actual empty 'metapackages', which are just normal packages with a whole slew of dependancies and a little README/Changelog/etc in /usr/doc/metapkgname . Is this the plan? How about another thought on how to do it. Do a dpkg --get-selections. Then compare what is currently installed to the groups of packages that have been defined. You then show the user if all, some, or none of the group is currently installed. The user then has the choice to change the group to all or none. Finally save the changes (will dpkg --set-selections remove things?), maybe even offer to run apt-get. Um, if we adopt *my* metapackage scheme, we already *have* all these benefit (i.e., in dselect) with no code needing to be written. Furthermore, we can deliver updates to the metapackages in the archive, just as we do any other package. -- .Adam Di [EMAIL PROTECTED]URL:http://www.onShore.com/
