Re: Future of gcc-3.4?
On Tuesday 29 March 2005 7:32pm, Theodore Kisner wrote: > > I have appended the message below. Thanks Theodore. > > > 3. The documentation should clearly state that the 'pure64' archive > > > is the 'official' one for the amd64 port which will be > > > integrated into the Debian archive after sarge is released. Should we even make new users aware of gcc-4.0 when making their initial decision to try AMD64? In other words, perhaps we should remove all references to the experimental branch in the AMD64 HOWTO, especially if I understand Andreas above to mean that the gcc-4.0 branch is a dead-end that will at some point in the distant future simply go away (or that the official branch will eventually catch up to gcc-4.0 and render it redundant)? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Future of gcc-3.4?
On Tuesday 29 March 2005 16:09, Ed Cogburn wrote: > Hi, > > What is the future plan for pure64 and gcc-3.4? What will the gcc-3.4 (now > almost gcc-4.0) archive eventually become? Will it always be an > experimental thing that never becomes "official", or will it eventually > become the official AMD64 port's Sid with pure64 becoming the Stable, or > what? I've never seen any reference that explains why those 2 different > archives exist and what their futures are. TIA. This has been discussed before on this list, but it seems that many messages that go out to the list do not actually get archived at http://lists.debian.org/debian-amd64/ I'm not sure why this is, but it has been happening for a while. For example, Andreas posted an explanation on 2005-02-21 about his intentions for the gcc-3.4 archive, but this mail never showed up in the archive. I believe that this type of archive failure is why many questions get repeated. Does anyone have any ideas why this is happening? I have appended the message below. -Ted > >On 05-Feb-21 17:48, Goswin von Brederlow wrote: > >> What happens to the gcc-3.4/gcc-4.0 repository is totaly undecided and > >> I leave that up to Andreas as he is doing all the work on it. > > > > My intention is to continue the gcc-3.4 archive until > > Debian officially switches to gcc-4.0 as its default compiler. > > > > However, this may take quite a long time and I think that to avoid > > confusion the following should be done: > > > > 1. The 'gcc-3.4' archive should be renamed to 'gcc4' to reflect its > > current state. > > > > 2. The documentation for the amd64 port should mark the 'gcc4' archive > > as an experimental archive. > > > > 3. The documentation should clearly state that the 'pure64' archive > > is the 'official' one for the amd64 port which will be > > integrated into the Debian archive after sarge is released. > > > > Hopefully, the name change from 'gcc-3.4' to 'gcc4' will not cause too > > much trouble for mirrors and current users. For some time the old name > > 'gcc-3.4' should be still available as a symlink to 'gcc4'. > > > > Regards > > Andreas Jochens -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Future of gcc-3.4?
Hi, What is the future plan for pure64 and gcc-3.4? What will the gcc-3.4 (now almost gcc-4.0) archive eventually become? Will it always be an experimental thing that never becomes "official", or will it eventually become the official AMD64 port's Sid with pure64 becoming the Stable, or what? I've never seen any reference that explains why those 2 different archives exist and what their futures are. TIA. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: List split?
On Tuesday 29 March 2005 4:38pm, John Goerzen wrote: > On Tue, Mar 29, 2005 at 01:18:34PM -0800, Ryan Lovett wrote: > > Now that debian-amd64 is successful enough that newbies have managed to > > get it working, could the list be split into something like -user and > > -devel? I'm more interested in the development of the port and not other > > (still important) issues like how to get GNOME/KDE/networking/etc. > > working on amd64 which have dominated the list of late. > > Shouldn't most of those go to the regular debian-user list? When Debian officially adopts us eventually, a d-u equivalent is where the user-level stuff should go, but right now d-u is pretty much useless because all the AMD64 users are on this list. :) Seriously though, d-u's traffic is so high, I long ago gave up on it, even when I was still running i386. I don't know what the "official position" is on this, but I would prefer Debian keep the AMD64 specific user mailing list (the developers OTOH, may *want* to integrate into the official d-d, I don't know), since the regular d-u is now a de-facto i386-specific list. AMD64 users will just be drowned out on that list, forcing most of us to use Subject headers to separate us, e.g. "Subject: [AMD64] xxx", at which point you have to ask, why bother? For a long while to come AMD64 users are going to have AMD64 specific issues/problems, so I believe we should keep our own specific user list for now. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: List split?
On Tue, Mar 29, 2005 at 01:18:34PM -0800, Ryan Lovett wrote: > Now that debian-amd64 is successful enough that newbies have managed to > get it working, could the list be split into something like -user and > -devel? I'm more interested in the development of the port and not other > (still important) issues like how to get GNOME/KDE/networking/etc. working > on amd64 which have dominated the list of late. Shouldn't most of those go to the regular debian-user list? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: pure64 semi-testing
Change that to: deb http://bach.hpc2n.umu.se/debian-pure64 testing main non-free contrib Ah, I see. Found the http://bach.hpc2n.umu.se/archive-structure.txt :-) Then I will still have a mix of sid/sarge, but I guess it will converge to sarge .. Thanks! /n -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: pure64 semi-testing
On Tue, Mar 29, 2005 at 11:22:36PM +0200, Niklas Ögren wrote: > > My sources.list: > deb http://bach.hpc2n.umu.se/pure64 testing main non-free contrib > deb-src http://bach.hpc2n.umu.se/pure64 testing main non-free contrib Change that to: deb http://bach.hpc2n.umu.se/debian-pure64 testing main non-free contrib Kurt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: pure64 semi-testing
there is already a sarge version of debian-amd64. Did you want something else? I thought they were more or less the same? At least when I tried to force my sid system to only look at sarge from the alioth-mirrors when running apt .. maybe I was doing that wrong. How to "freeze" a sid-system and change to sarge then? My sources.list: deb http://bach.hpc2n.umu.se/pure64 testing main non-free contrib deb-src http://bach.hpc2n.umu.se/pure64 testing main non-free contrib deb http://bach.hpc2n.umu.se/pure64 unstable main non-free contrib deb-src http://bach.hpc2n.umu.se/pure64 unstable main non-free contrib and preferences: Package: * Pin: release o=Debian-amd64,a=testing Pin-Priority: 650 Package: * Pin: release o=Debian-amd64,a=unstable Pin-Priority: 600 /n -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
List split?
Now that debian-amd64 is successful enough that newbies have managed to get it working, could the list be split into something like -user and -devel? I'm more interested in the development of the port and not other (still important) issues like how to get GNOME/KDE/networking/etc. working on amd64 which have dominated the list of late. Just my 2 cents, Ryan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: pure64 semi-testing
On Tue, Mar 29, 2005 at 08:34:14PM +0200, Niklas Ögren wrote: > >no. pure64 and the gcc-3.4 branches are entirely separate (and > >incompatible). > >I would recommend using the pure64 branch. The gcc-3.4/gcc4 is more like > >"experimental". You should not mix packages from these. > > For the pure64: > Am I the only one who would appreciate a system similar to the 32bit > Debian, where the unstable packages come into testing state if no > complaints after one week, and that's the point where "apt-get upgrade" > want to install them into my running system? If you use /debian-pure64 you can use testing/sarge. /pure64 only contains sid and sarge is a symlink to sid. Kurt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: pure64 semi-testing
there is already a sarge version of debian-amd64. Did you want something else? no need to CC me- I'm subscribed to the list. -Ted On Tuesday 29 March 2005 10:34, Niklas Ögren wrote: > Am I the only one who would appreciate a system similar to the 32bit > Debian, where the unstable packages come into testing state if no > complaints after one week, and that's the point where "apt-get upgrade" > want to install them into my running system?
pure64 semi-testing
no. pure64 and the gcc-3.4 branches are entirely separate (and incompatible). I would recommend using the pure64 branch. The gcc-3.4/gcc4 is more like "experimental". You should not mix packages from these. For the pure64: Am I the only one who would appreciate a system similar to the 32bit Debian, where the unstable packages come into testing state if no complaints after one week, and that's the point where "apt-get upgrade" want to install them into my running system? I know I'm running unstable (sid) on a production server, but I want to make it a little bit more safe somehow .. Maybe there is some kind of time-version pinning? Or can somebody help me setting up a mirror where I create a semi-testing distribution holding packages a week before releasing into the one my apt-get looks at? Or do I have to wait the > half year it will take to release sarge, and when our pure64 may become testing-like? Best Regards, Niklas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: kernel-image-2.6.11-amd64 packages
On Mon, Mar 28, 2005 at 07:46:48PM +0200, Jonas Meurer wrote: > sure, i did so. i used menuconfig, but that shouldn't matter. make menuconfig is not a substitute for make oldconfig. It does and should matter which you use first. You can use make menuconfig after using make oldconfig if you wish. make menuconfig is _only_ a substitute for make config. > still, the build failture happens. Len Sorensen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Another program for burning dvds
On Sat, Mar 26, 2005 at 07:53:42PM +0100, v0n0 wrote: > Lennart Sorensen wrote: > > >Well I burn DVDs like this: > >growisofs -Z /dev/hda -J -R /dirwithfiles > > > >-J and -R and /dirwithfiles are of course mkisofs options. > > > > > > > Really simple. But I got these errors: > > [EMAIL PROTECTED]:~$ growisofs -Z /dev/hda -J -R Filmati/master > Executing 'mkisofs -J -R Filmati/master | builtin_dd of=/dev/hda obs=32k > seek=0' > INFO: ISO-8859-15 character encoding detected by locale settings. >Assuming ISO-8859-15 encoded filenames on source filesystem, >use -input-charset to override. > /dev/hda: "Current Write Speed" is 4.1x1385KBps. > :-? the LUN appears to be stuck writing LBA=310h, retry in 141ms > :-? the LUN appears to be stuck writing LBA=310h, retry in 141ms > 0.23% done, estimate finish Wed Mar 23 04:31:36 2005 > 0.47% done, estimate finish Wed Mar 23 01:58:44 2005 > ... > 81.97% done, estimate finish Tue Mar 22 23:19:48 2005 > 82.20% done, estimate finish Tue Mar 22 23:19:48 2005 > 82.44% done, estimate finish Tue Mar 22 23:19:48 2005 > :-? the LUN appears to be stuck writing LBA=1af990h, retry in 141ms > 82.67% done, estimate finish Tue Mar 22 23:20:06 2005 > 82.90% done, estimate finish Tue Mar 22 23:20:05 2005 > 83.14% done, estimate finish Tue Mar 22 23:20:04 2005 > ... > 99.49% done, estimate finish Tue Mar 22 23:19:37 2005 > 99.72% done, estimate finish Tue Mar 22 23:19:37 2005 > 99.95% done, estimate finish Tue Mar 22 23:19:37 2005 > Total translation table size: 0 > Total rockridge attributes bytes: 1846 > Total directory bytes: 2048 > Path table size(bytes): 26 > Max brk space used 0 > 2141015 extents written (4181 MB) > builtin_dd: 2141024*2KB out @ average 3.3x1385KBps > /dev/hda: flushing cache > /dev/hda: closing track > /dev/hda: closing session > :-[ CLOSE SESSION failed with SK=2h/ASC=04h/ACQ=07h]: Resource > temporarily unavailable > > What do they mean? Thanks and regards I have never personally seen a message like that, so asking cdwrite mailing list (see lists.debian.org for the cdwrite list) would be better since that is where the authors of those programs hang out. Len Sorensen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
some issues with Gnome
Hi guys, I'm having some problems with gnome, and its librairies I think. To be honest, I don't really know what can be wrong as I can't find any clues in log files so I'll describe the symptoms: - gnome-session doesn't start anything. After logging in I get a blank screen, nothing else. - some gnome applications are very slow to launch, e.g. galeon, gedit, etc... - all my webbrowser based on mozilla freeze from time to time, and freeze all the time when I try to download a file. As I said, I can't find any clues in log files so I really have no idea of what is happening. I forgot to say, I'm running deb pure64, with the latest gnome packages. Hope you have some suggestions. Thanks a lot, Christophe Send instant messages to your online friends http://uk.messenger.yahoo.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: ASUS - K8N-E Deluxe Install Report (using /debian-installer/2005-03-24)
On Sun, Mar 27, 2005 at 03:19:02PM +0200, Remi Butaud wrote: > Debian-installer-version: > http://debian-amd64.alioth.debian.org/debian-installer/2005-03-24/monolithic/mini.iso > uname -a: Linux owl 2.6.8-10-amd64-k8 #1 Tue Mar 15 17:25:19 CET 2005 > x86_64 GNU/Linux > > Date: March - 27, 2005 > Method: netinstall from > ftp://mirror.switch.ch/mirror/debian-amd64/pure64 testing main contrib non-f > ree > and > http://debian-amd64.alioth.debian.org/pure64 testing main contrib non-free > (some packages were not available from the switch mirror or the > network was choppy) > > > Machine: Custom machine, Asus K8N-E Deluxe Motherboard > Processor: AMD64 3200+ > Memory: 2x512 MB Cordair Xmms > Root Device: IDE : /dev/hda1 (secondary devices on /dev/sda /dev/sdb : sata) > Root Size/partition table: > > # > proc/proc procdefaults0 0 > /dev/hda1 / ext3defaults,errors=remount-ro 0 1 > /dev/hda6 /home ext3defaults0 2 > /dev/hda7 /linux32ext3defaults0 2 > /dev/hda8 /windowsvfatdefaults0 2 > /dev/hda5 noneswapsw 0 0 > /dev/hdc/media/cdrom0 iso9660 ro,user,noauto 0 0 > /dev/hdd/media/cdrom1 iso9660 ro,user,noauto 0 0 > /dev/fd0/media/floppy0 autorw,user,noauto 0 0 > Note : the SATA disks are not mounted yet (WinXP) > (mount -t ntfs /dev/sda1 /xproot does the trick) > > Output of lspci and lspci -n: > lspci > :00:00.0 Host bridge: nVidia Corporation: Unknown device 00e1 (rev a1) > :00:01.0 ISA bridge: nVidia Corporation: Unknown device 00e0 (rev a2) > :00:01.1 SMBus: nVidia Corporation: Unknown device 00e4 (rev a1) > :00:02.0 USB Controller: nVidia Corporation: Unknown device 00e7 (rev a1) > :00:02.1 USB Controller: nVidia Corporation: Unknown device 00e7 (rev a1) > :00:02.2 USB Controller: nVidia Corporation: Unknown device 00e8 (rev a2) > :00:05.0 Bridge: nVidia Corporation: Unknown device 00df (rev a2) > :00:08.0 IDE interface: nVidia Corporation: Unknown device 00e5 (rev a2) > :00:0a.0 IDE interface: nVidia Corporation: Unknown device 00e3 (rev a2) > :00:0b.0 PCI bridge: nVidia Corporation: Unknown device 00e2 (rev a2) > :00:0e.0 PCI bridge: nVidia Corporation: Unknown device 00ed (rev a2) > :00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 NorthBridge > :00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 NorthBridge > :00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 NorthBridge > :00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 NorthBridge > :01:00.0 VGA compatible controller: ATI Technologies Inc Radeon > R350 [Radeon 9800 Pro] > :01:00.1 Display controller: ATI Technologies Inc Radeon R350 > [Radeon 9800 Pro] (Secondary) > :02:09.0 Multimedia audio controller: Creative Labs SB Audigy (rev 03) > :02:09.1 Input device controller: Creative Labs SB Audigy > MIDI/Game port (rev 03) > :02:09.2 FireWire (IEEE 1394): Creative Labs SB Audigy FireWire Port > :02:0b.0 FireWire (IEEE 1394): VIA Technologies, Inc. IEEE 1394 > Host Controller (rev 80) > :02:0c.0 RAID bus controller: Silicon Image, Inc. (formerly CMD > Technology Inc) SiI 3114 [SATALink/SATARaid] Serial ATA Controller > (rev 02) > > lspci -n > lspci -n > :00:00.0 0600: 10de:00e1 (rev a1) > :00:01.0 0601: 10de:00e0 (rev a2) > :00:01.1 0c05: 10de:00e4 (rev a1) > :00:02.0 0c03: 10de:00e7 (rev a1) > :00:02.1 0c03: 10de:00e7 (rev a1) > :00:02.2 0c03: 10de:00e8 (rev a2) > :00:05.0 0680: 10de:00df (rev a2) > :00:08.0 0101: 10de:00e5 (rev a2) > :00:0a.0 0101: 10de:00e3 (rev a2) > :00:0b.0 0604: 10de:00e2 (rev a2) > :00:0e.0 0604: 10de:00ed (rev a2) > :00:18.0 0600: 1022:1100 > :00:18.1 0600: 1022:1101 > :00:18.2 0600: 1022:1102 > :00:18.3 0600: 1022:1103 > :01:00.0 0300: 1002:4e48 > :01:00.1 0380: 1002:4e68 > :02:09.0 0401: 1102:0004 (rev 03) > :02:09.1 0980: 1102:7003 (rev 03) > :02:09.2 0c00: 1102:4001 > :02:0b.0 0c00: 1106:3044 (rev 80) > :02:0c.0 0104: 1095:3114 (rev 02) > > > > Base System Installation Checklist: > [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it > > Initial boot worked:[O] > Configure network HW: [E] > Config network: [O] > Detect CD: [O] > Load installer modules: [O] > Detect hard drives: [O] > Partition hard drives: [O] > Create file systems:[O] > Mount partitions: [O] > Install base system:[O] > Install boot loader:[O] > Reboot: [O] > > Comments/Problems: > > When detecting the network HW (embedded nForce 3 controler), I had > only 2 NIC detected, the two firewire ports (as eth0 and eth1). I had > to exit from the installer, execute a shell command: #modprobe > forcedeth > and then back
Re: usb wireless mouse stopped working
On Tue, Mar 29, 2005 at 08:55:13AM +0200, Alexandru Cabuz wrote: > Last night my wireless mouse batteries ran out, so I replaced them, > but now it wouldn't connect anymore. I am seeing the same behavior I > have seen in windows since the beginning. > > The wireless keyboard is seen no problem, but not the mouse. Both the > keyboard and the mouse use the same receiver, which is connected > directly using a USB bus. > > Up until now, every time I booted into windows (last time that > happened was about 6 months ago) I had to hook up my old wirebound > mouse, cos the wireless mouse wasn't recognized.Well, now I gotta do > the same thing in Linux. > > Anybody know what's going on? > > What package is responsible for this and how do I fix it? I tried > reloading the mousedev driver but that did nothing. What brand is it? In my experience, when you connect a logitech wireless receiver, the OS sees the mouse and keyboard right away, no matter if the mouse/keyboard currently is in range or not. After all just because you loose the signal for a moment shouldn't make the mouse or keyboard disconnect from the system and then reconnect. That would get annoying. Most likely the only thing necesary is the do the reconnect to the base of the device after changing batteries. Len Sorensen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
PHP4 works again (was Re: PHP4 causes apache to fail to start)
Hi Andreas, apt-get dist-upgrade upgraded php4 today and with this new version I am able to run php4 with apache again. Thanks! Per -- Per Bojsen <[EMAIL PROTECTED]> 7 Francis Road Billerica, MA 01821-3618 USA -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Notice: nvidia-kernel patches required.
The nvidia-* packages in sid/amd64 have a couple of small issues that I have discovered and would like to point out to everyone else for future reference. Firstly, it is imperitave that you upgrade to a 2.6.11+ kernel (whether a debian image or roll your own). Previous kernels have a bad implementation of change_page_attr. The complete text from nvidia is available here: ftp://download.nvidia.com/XFree86/Linux-x86_64/1.0-7167/README.txt Secondly, many users have reported bad performance under OpenGL applications (games). Not all games, but a good majority of them. I'm not certain what the cause is, directly, but nvidia has provided a patch. Actually, two patches. They are available here: http://www.nvnews.net/vbulletin/attachment.php?attachmentid=10788 and here: http://www.nvnews.net/vbulletin/attachment.php?attachmentid=10794 Since debian-amd64 has its own custom implementation of nvidia-kernel-source (and, as far as I know, you cannot simply install the NVIDIA-*pkg.run file) you'll have to apply the first patch to /usr/src/modules/nvidia-kernel/nv/os-agp.c and the second patch to /usr/src/modules/nvidia-kernel/nv/nv.c, after you have untarred the nvidia-kernel-source.tar.gz file that you have downloaded from apt-get. It would be best if we could have the maintainer patch these himself and move them back upstream. I have not yet contacted him myself because I'm uncertain as to whether these patches are universal (meaning perhaps they won't work for everyone or make matters worse for other folks). Regards, Zaq Rizer -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: fujitsu-siemens primergy rx300 s2
On Thu, Mar 24, 2005 at 12:43:56PM -0800, Larry Doolittle wrote: > Len Sorensen wrote - > > > Do [Broadcom] provide a driver that works without a firmware file? Do they > > include sources to any firmware files required? If not they can call it > > GPL all they want, but it still won't be GPL. They wouldn't be the only > > company to make that mistake (For example Sangoma's wanpipe drivers > > claim to be GPL but have binary only modules and firmware files in > > them). > > AFAICT, binary-only firmware is OK, if that blob is redistributable. > That's why hooks to allow user-space firmware loading were added, > it keeps those blobs out of the GPL-covered binary. Not everything on > a Debian CD has to be GPL. The firmware file is "merely aggregated". > > This is the situation with my Prism54 wireless card. Supplying the > firmware from the main CPU saves the manufacturer a few bucks and > square cm of board space for the PROM, makes firmware upgrades less > tricky. The only technical downside is the few milliseconds it takes > to schlep the bits onto the card. The legal issues arise if the > manufacturer fails to license the binary for redistribution, then > Debian etc. can't put it on the general-issue CD, and the end-user > has to cajole the file from the manufacturer before they can use the > hardware. > > Binary-only modules for the main CPU are, of course, deadly. I believe all my examples include binary only modules for the main CPU. If it is just a file to load into an fpga or other loadable device, then I don't personally have a problem with it, but some people do. Len Sorensen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Idea for structure of Apt-Get
Patrick Carlson wrote: Hello. I'm not sure if anyone has suggested something like this or not but I was thinking about the apt-get system and bittorrent today. What if the apt-get system was redesigned so that users could download updates and upgrades from other users? This way they would trickle out to people, slowly at first, but then more and more people would have the update and thus more people could get it faster. I know Faster than what? Today's system is very fast: One user (maintainer) uploads a new version and everybody have instant access to it as soon as they do the "apt-get upgrade". No "slow trickle at first." there would probably be a lot of security issues involved but then maybe people wouldn't have to worry about setting up .deb mirrors and trying to get the latest upgrades. Just a thought. If it's a bad one, let me know. :) Oh, you're worried about the internet slowing as everybody upgrade and downloads the same stuff? There is a much better solution to this, and it is called "caching proxies". Many an ISP have a caching proxy already, that caches both ftp and http which is the protocols usually used by apt over the net. Caching proxies have two big advantages over changing apt: * Nothing have to be done to apt at all! * Proxies also cache other things than debian packages. Helge Hafting -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: usb wireless mouse stopped working
Alex writes: Hello, Last night my wireless mouse batteries ran out, so I replaced them, but now it wouldn't connect anymore. I am seeing the same behavior I have seen in windows since the beginning. The wireless keyboard is seen no problem, but not the mouse. Both the keyboard and the mouse use the same receiver, which is connected directly using a USB bus. Up until now, every time I booted into windows (last time that happened was about 6 months ago) I had to hook up my old wirebound mouse, cos the wireless mouse wasn't recognized.Well, now I gotta do the same thing in Linux. Anybody know what's going on? What package is responsible for this and how do I fix it? I tried reloading the mousedev driver but that did nothing. Thanks. Alex. Hi, I now have my USB trackball plugged into a USB2PS2 adapter. :-| The USB is a part of the 'hotplug' and probably the udev name style. Try: /etc/init.d/hotplug restart Try: lsusb Look in /proc/bus/usb Look in /etc/hotplug for the config files. There are probably more kernel modules I can't remember. Good Luck [EMAIL PROTECTED] -- AMD Athlon64 @2.4Ghz Corsair TwinX1024-3200XL @480Mhz DDR ASUS A8V Deluxe ASUS Radeon A9250Ge/Td/256 Creative SB Live WD Raptor SATA Maxtor PATA IBM/Okidata Color PostScript3 Lexmark Mono PostScript2 Debian GNU/Linux debian-amd64/pure64 sid Kernel 2.6.11 XFree86 4.3.0.1 Xorg X11R6.8.2 1.5 Mb DSL -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: usb wireless mouse stopped working
On Tue, Mar 29, 2005 at 08:55:13AM +0200, Alexandru Cabuz wrote: > Last night my wireless mouse batteries ran out, so I replaced them, > but now it wouldn't connect anymore. I am seeing the same behavior I > have seen in windows since the beginning. This isn't a OS related problem. It is a pairing problem, under mouse and on radio receiver there is a small button to pair device, follow the instruction of device (logitech is: press both button [device+receiver] and wait few second that LEd blink). When battery ran out the mouse probably forget who is its receiver :) Regards Sythos -- Sythos - http://www.sythos.net () ASCII Ribbon Campaign - against html/rtf/vCard in mail /\- against M$ attachments -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
MSI K8N Neo Platinum Installation Report & GRUB/LILO troubles
Hi, Only this weekend did I have the chance to try again and install debian on my computer. It didn't went very well, as I kept having errors from time to time while reading from burned install isos (It also happened last time). I thought they were related to my particular reader (DVD NEC 3520A), but it kept happening once I switched to an older one. I had to try several times so I could install anything. > Huam. At the time of installing, I used P-ATA disks. S-ATA is working > here, but I installed a newer kernel somewhen. I burned a Ubuntu iso (that detects my disks), and went on to install debian chrooting. > >installed me the base system. So far so good (kind of :P ). My main > >(unsolved) problems began when I tried to to install GRUB. > > > > > Yeees. I've had that troubles too. grub-install and "setup" from the > grub shell does mostly a segfault. > Booting with grub worked at my side, but with a scrambled boot-screen. > I used a normal (IA32) grub install to get a working grub installation. Is it possible to install a IA32 compiled grub in my debian-64 disk using apt-get? I did tried to install Ubuntu on my other disk just for grub, but because of the read errors it ended failing everytime. During this week, I'll try to install i386 Knoppix, to see if I can finally get a working grub! Thanks for the replies, -- Ricardo Diz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
