XFree86 3.2A?
Robert Nicholson writes: > I've heard that the acceleration is worth it. Particularly on my Tecra. > > So are the .deb's available for 3.2A? No. Debian only includes software for which source is available; the XFree86 betas are binary only releases. If you are only interested in the acceleration then you should be able to install the appropriate XFree86-3.2A server binary either on top of your current binary or in /usr/local/bin. If you install it in /usr/local/bin then remember to change the first line of /etc/X11/Xserver to point to the correct place. Steve Early -- 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?
[EMAIL PROTECTED] writes: > 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: In this particular case it's a bug in the gwm package; it depends on xlib when it should have depended on elf-x11r6lib. If you remove it before upgrading, the upgrade should work. You may find that there are other packages with a similar bug. You can tell which package it is that is getting in the way; dpkg tells you here: > > 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 > === Once you have upgraded the X packages you can re-install the buggy packages using the --force-depends option. Steve Early -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]
Re: Odd X message
Guy Maor writes: > Add this to your XF86Config file: > > Section "Modules" > Load "pex5.so" > Load "xie.so" > EndSection Alternatively, if you don't use PEX and XIE then don't add the Load lines. Save yourself a bit of memory... Steve Early -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]
xdm -- Second X Session
[EMAIL PROTECTED] writes: > 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" How about something like 'X :1 -query machinename' where machinename is the name of your machine. Incidentally, you can control who is allowed to start the X server by editing the first line of the /etc/X11/Xserver file. The '-query' option tells the server to send an XDMCP 'query' message to the xdm on the specified machine, asking that xdm to manage the display. If you want to start an X session on another machine you can use the same command. Alternatively you can get xdm to start two servers by adding another line to /etc/X11/xdm/Xservers. You will need to specify that the second server is display :1, and you will probably also need to tell the servers explicitly which VT to start on; there is a known race condition when two servers start simultaneously. Steve Early -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]
What Debian packages do I need to grab to upgared to Xfree 3.2
Stan Brown writes: > Could someone give me a complete list of the Debian packages neededto > upgradeto XFree 3.2 ? Filenames and md5sums: -rw-r--r-- 1 root root 2027180 Nov 10 05:23 xbase_3.2-0_i386.deb -rw-r--r-- 1 root root 14588186 Nov 10 05:36 xbooks_3.2-0_all.deb -rw-r--r-- 1 root root 393680 Nov 10 05:23 xext_3.2-0_i386.deb -rw-r--r-- 1 root root 1632024 Nov 10 05:25 xfnt100_3.2-0_all.deb -rw-r--r-- 1 root root 1355422 Nov 10 05:25 xfnt75_3.2-0_all.deb -rw-r--r-- 1 root root 266374 Nov 10 05:25 xfntbase_3.2-0_all.deb -rw-r--r-- 1 root root 3070500 Nov 10 05:25 xfntbig_3.2-0_all.deb -rw-r--r-- 1 root root 499664 Nov 10 05:26 xfntcyr_3.2-0_all.deb -rw-r--r-- 1 root root12424 Nov 10 05:25 xfntpex_3.2-0_all.deb -rw-r--r-- 1 root root 1128244 Nov 10 05:26 xfntscl_3.2-0_all.deb -rw-r--r-- 1 root root 529024 Nov 10 05:23 xlib6-dev_3.2-0_i386.deb -rw-rw-r-- 1 root root 688698 Nov 10 05:24 xlib6_3.2-0_i386.deb -rw-r--r-- 1 root root 883298 Nov 10 05:37 xmanpages_3.2-0_all.deb -rw-r--r-- 1 root root 776276 Nov 10 05:24 xnest_3.2-0_i386.deb -rw-r--r-- 1 root root 610288 Nov 10 05:18 xserver-8514_3.2-0_i386.deb -rw-r--r-- 1 root root 683642 Nov 10 05:18 xserver-agx_3.2-0_i386.deb -rw-r--r-- 1 root root 670786 Nov 10 05:19 xserver-mach32_3.2-0_i386.deb -rw-r--r-- 1 root root 713696 Nov 10 05:19 xserver-mach64_3.2-0_i386.deb -rw-r--r-- 1 root root 614174 Nov 10 05:19 xserver-mach8_3.2-0_i386.deb -rw-r--r-- 1 root root 649426 Nov 10 05:19 xserver-mono_3.2-0_i386.deb -rw-r--r-- 1 root root 689422 Nov 10 05:20 xserver-p9000_3.2-0_i386.deb -rw-r--r-- 1 root root 862832 Nov 10 05:20 xserver-s3_3.2-0_i386.deb -rw-r--r-- 1 root root 765344 Nov 10 05:20 xserver-s3v_3.2-0_i386.deb -rw-r--r-- 1 root root 935350 Nov 10 05:21 xserver-svga_3.2-0_i386.deb -rw-r--r-- 1 root root 1106326 Nov 10 05:21 xserver-vga16_3.2-0_i386.deb -rw-r--r-- 1 root root 624070 Nov 10 05:21 xserver-w32_3.2-0_i386.deb -rw-r--r-- 1 root root 804134 Nov 10 05:25 xslib_3.2-0_i386.deb 938f2dacc8240c2566e5a3f0e3083ad8 xbase_3.2-0_i386.deb 349ca1638db1a682074e413072d2e07b xbooks_3.2-0_all.deb a5f6d9cf4a737bffcf648403fbab88af xext_3.2-0_i386.deb 845865b2cbf5ccda82165807dbc80a25 xfnt100_3.2-0_all.deb e452e392ca772c77541a5bca0fb5db5f xfnt75_3.2-0_all.deb a47774de33c80c4286eccd8943e3425b xfntbase_3.2-0_all.deb 7d8750b21519c7dcd1122f5f62d7f77b xfntbig_3.2-0_all.deb 7e9da326eb1e14914c1e4e9a71a1eca2 xfntcyr_3.2-0_all.deb 42dfea1e12f2b37bceefbc0ebd7e3145 xfntpex_3.2-0_all.deb ad078b63c86d2e34e07f15a2c0199fa9 xfntscl_3.2-0_all.deb ab19341d565f6297cd698030754ccdfe xlib6-dev_3.2-0_i386.deb a05a89cc3226117efd17d04620acefa0 xlib6_3.2-0_i386.deb d8f768f95b9835bb2dea9872715f6941 xmanpages_3.2-0_all.deb d0b2579a7536e05e53428f771c5db566 xnest_3.2-0_i386.deb 1241e7614db9d10fd957c4d470b878a0 xserver-8514_3.2-0_i386.deb 6434ffcc7f612dbacff3cae7b997f9b2 xserver-agx_3.2-0_i386.deb 554dd62afc9efad269ce0c156f52b7d1 xserver-mach32_3.2-0_i386.deb 24e5dc0b2cae4962426d60f1f1926e36 xserver-mach64_3.2-0_i386.deb 09daac8b38c35e03ae63fd7f1d79d827 xserver-mach8_3.2-0_i386.deb 140396e617e8f5066afb610cf6d7077b xserver-mono_3.2-0_i386.deb 39e5125b3c6016f0037f75896739fe8a xserver-p9000_3.2-0_i386.deb f0328d8a7e52448c33c07b775cb02776 xserver-s3_3.2-0_i386.deb dd467f26399ebc8935326bd6cfd5dc11 xserver-s3v_3.2-0_i386.deb 18163afb25c1137c6613411cf14e2bc4 xserver-svga_3.2-0_i386.deb 3126d4744a3680ada2e52548d3e29704 xserver-vga16_3.2-0_i386.deb 305dd922d9ee682bf780666c47fd5ffb xserver-w32_3.2-0_i386.deb 9ff55f1a7b4bc4dc9fc7e8f48d760d81 xslib_3.2-0_i386.deb I haven't released the 3.2 version of xcontrib yet. That will probably happen next weekend. > I have compiled it and run it on my Debian machine, and it is a big win > for my S3 card, but I would like to keep dpkgs database up to date on > the state of my machine. I grabe everything in unstable/boinary/x11 > that had a 3.2 in the filename, and this appears to not be the complete > set. What do you seem to be missing? If your file transfer went alright, my guess is that you have some old, incorrect packages on your system that depend on 'xlib' rather than 'elf-x11r6lib'; this will prevent you from installing the new 'xlib6' package. If this is the case, upgrade or remove the packages that depend on xlib before installing the new X packages. Steve Early -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]
X is painful
[no-longer CCed to debian-devel because this isn't a developer issue really] Bill Bumgarner writes: > > I have to vent. > > I cannot believe that after HOW MANY years of development, X windows is > still such a completely inconsistent and painful user interface. Ah. The X Window System is not a user interface. It is a standard by which applications can drive displays and input devices. It provides mechanism, not policy. It is possible to build very nice user interfaces on top of X. The system used by secretaries where I work, for example, is built using X. All of the applications in this system, including the window manager, come from one vendor (Xerox in this case, I believe). > Maybe I'm just spoiled by years of NEXTSTEP-- but, damnit, NEXTSTEP really > is the most well-inntegrated user inrface *ever* built. Seriously. NextStep provides policy as well as mechanism. I agree, it is extremely nice. Creating a user interface under X that is as good as NextStep is just a matter of getting every X application author to agree to adhere to the same policy. I wish you luck. Steve Early -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]
XFree86 3.2 Initial Reports
Bill Bumgarner writes: > 1) XF86Setup doesn't provide for resolutions beyond 1280x1024 [though it > does a nice job of ensuring that the server chooses the HIGHEST available > resolution]. Resolutions beyond 1280x1024 are not yet a common case. I suspect that most people using higher resolutions will want to tailor them for their monitors anyway. You ought to be able to do this using xvidtune. If you can come up with a patch to make XF86Setup provide higher resolutions, unidiffs are gratefully accepted... > 2) There is no option to automatically start the server using other than > an 8 bit mode. While the configuration information is correctly created > for 15, 16, 24, and 32 bpp modes, one must edit /etc/X11/xdm/Xservers by > hand and add '-bpp 16' [or whatever]. I suppose I _could_ add a prompt for this in the postinst scripts. On the other hand, editing configuration files is not difficult. > The default background used under XDM is disgusting-- it is pretty much > gurantees to cause aliasing on any monitor at higher resolutions... > whoever decided that that particularly multi-pixel carpet-like pattern > should be the X standard should be shot. It makes a really good test pattern, though. When you're setting up your monitor it's ideal. A solid background for the login screen is probably desirable. As you mention in your other message, it could be achieved with a line in /etc/X11/config and a section in the Xsetup file. I'm quite reluctant to edit these files without good cause, though, because whenever I do it makes dpkg scream about conffiles to all the people who have customised them. "If it isn't broken, don't fix it" etc. > We really ought to add a more pleasant default background color for user's > and for the xdm window. As well, we should customize the login panel to > provide a more pleasant and attractive debianized experience. One of the good things, in my opinion, about Debian is that it provides packages that are set up sensibly with 'normal' defaults. I don't want to start doing anything fancy just to look pretty; other distributions have tried this, and it occasionally causes confusion and problems. It's more a philisophical issue than a technical one, really - people should be able to configure their systems however they like, without having to undo all sorts of distribution-specific gunk first. Steve Early -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]
Re: problems with X
In article <[EMAIL PROTECTED]> you write: >I have installed Debian 1.1.9 and xbase, xlib, xserver-svga, and fvwm >packages. I chose during xbase to use xdm to start x.. and during boot-up >I see the message "starting xdm".. however typing "xdm" at a root prompt >doesn't do anything. I tried xinit and got the following output: If you use xdm to start an X server, then the server should start automatically when you boot. If it doesn't then there's something wrong. You shouldn't have to type 'xdm' at any prompt. >TRANS(SocketUNIXConnect) () can't connect: errno = 111 >giving up. >xinit: Connection refused (errno 111): unable to connect to X server >xinit: No such process (errno 3): Server error. This is the clue. For some reason, the X server is unable to create the Unix-domain socket to listen for local connections. This could be because you don't have Unix-domain sockets in your kernel (I don't know whether this is a configuration option anymore) or because there is something up with the /tmp/.X11-unix directory. Try deleting /tmp/.X11-unix (and everything under it) and starting the server. Steve Early -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]
Re: X authorization
In article <[EMAIL PROTECTED]> you write: >How is the X authorization set up in Debian? > >I am running xdm and I discovered that only the login user can >start an X window. The 'MIT-MAGIC-COOKIE' authentication method is being used; only X clients with access to the appropriate 'cookie' (an automatically generated password) can connect to the server. I suggest you read the Xsecurity manpage in the xmanpages package for more information. The xauth and Xserver manpages are also relevant. >There are 2 situations when I cannot start a >X window: >(1) when I try to start a window after 'su' to root. I discovered this >can be fixed if I do 'xhost +mymachinename'. How to this automatically? >A line in Xaccess or some /etc/X11/X???.hosts file? You should set up a script to be run by root to copy the cookie from the user's .Xauthority file to root's .Xauthority. >(2) after establishing a PPP connection to my service provider and >changing my hostname (I have only a dynamic IP address from my ISP). >Here I suppose there is nothing I can do except do xhost from my ip-up >script after fixing (1). What is your DISPLAY variable being set to? If it's hostname:0.0 (or similar) then the connection from the X client to the server will be made by TCP using the cookie listed for TCP. If it's just :0.0 then the connection will be made using a Unix-domain socket, and the cookie listed for that connection method. (The cookie will have the same value, just a different name). If all you're worried about is getting X clients on your local machine to start up on your own display, I'd recommend having DISPLAY set to :0.0, so changes in hostname or IP address won't matter. Steve Early
Re: X-window keys
On Fri, 14 Jun 1996, Max Hyre wrote: >Martin Alonso Soto Jacome's <[EMAIL PROTECTED]> answer got to > me first: > > > Well, that's exactly what xdm is intended for. xdm tries to keep an > > xserver running permanently, so that you can always login to the system > > using a nice graphical login prompt dialog box. > > ``Oh'', he said in a quiet voice. (I've just started using X under > Linux, and hadn't grasped the differences between startx and xdm.) > >At the time I was tweaking the ModeLines to get the display size > best suited to the screen, and thus was starting and killing X > constantly. Next time, I'll just use startx, and save myself some > hassle. You can also leave xdm running in the background, and start the server manually whenever you want to use X. Remove the line :0 local /usr/X11R6/bin/X from the /etc/X11/xdm/Xservers file, and xdm won't start an X server automatically. You can then use a command like X -query localhost ...to start an X server when you need one. If it's present, it might also be an idea to remove the line xdm-start-server from /etc/X11/config, as if it's present then the X configuration scripts will add the line back to /etc/X11/xdm/Xservers next time you configure or update the X packages. Replace it with no-xdm-start-server, and you shouldn't ever be prompted about xdm starting a server again. Steve Early [EMAIL PROTECTED]
Re: .xinitrc
On Wed, 12 Jun 1996, David M. Cooke wrote: > I ran into this. Reading /etc/X11/Xsession told me enough to > fix it. > > Edit /etc/X11/config and add the following lines: > allow-user-resources > allow-user-modmap > allow-user-xsession > > I think this should be concidered a bug. These lines should > already be present and the sysadmin can remove one or more of > them in very unusual cases where that might be desired. Yes, I consider it to be a bug. I haven't worked out exactly which interaction between the package configuration scripts makes /etc/X11/config be created without these lines, but I'm going to skip the problem by writing a little utility to make the scripts properly idempotent. Expect new X packages in a few days. Steve Early [EMAIL PROTECTED]
Re: xdm problem
On Wed, 12 Jun 1996, Zachary DeAquila wrote: > I can't seem to log in through xdm into my newly upgraded from .93 to 1.1 > system. I log in, the screen freaks out as it swaps video modes to > the correct one that I'm running (or is it restarting the X server? > whatever) and then... it comes back to the xdm prompt. I can log in > fine if I do a ctrl-alt-F4 and get back to the text prompt, and > if I kill xdm, I can do a startx just fine... > > I'm running kernel 1.2.13, xserver_svga, and fvwm2, using config files > that worked fine under .93r6. Are you sure that, when you updated the xbase package you EITHER kept all the old config files OR installed all the new ones? A mix will probably not work. Look for errors in ~/.xsession-errors and /var/log/xdm-errors. If you can't get it working yourself, mail the contents of these files to me and I'll have a look. Check that your ~/.xsession file is executable as well - this might have worked before if it wasn't, but won't now. Steve Early [EMAIL PROTECTED]
Re: security hole in X????
On Tue, 4 Jun 1996, Carlos Carvalho wrote: > The problem is that, with telnet, windows started on the remote > machine open without problems in the local display, even without > giving a xhost on the local machine. Is this correct? It only > happens if you are the same user on both machines. How are you starting the X session? Are you using xdm, or something like startx? Are you sure that you aren't doing an 'xhost +' anywhere in your startup scripts? Steve Early [EMAIL PROTECTED]
Re: installation
On Mon, 20 May 1996, Steven Boothe wrote: > Here's the copy that followed the result of inserting my > root disk at the prompt: > > "RAMDISK 1474560 starting 0x0024 > insert root > VFS: Disk change detected on device 210 > RAM disk trying oldstyle RAM image > RAM disk trying oldstyle RAM image > insert Debian GNU/Linux Root Disk and press enter" > > When I do this I get this message: > > "[MS-DOS FS Rel. 12,FAT > 12,check=n,conv=b,vid=0,gid=0,umask=022,bmap] > [me=0x6c,cs=1248,#f=m,fs=40358,f1=27462,ds,8448,de=29807,dat > a=10320,se=26207,ts=-808993323,ls=133641] > transaction block size=512 > HPFS: hpfs_read_super: not HPFS > kernel panic: VFS:Unable to mount root fs on 0:0200" It looks like you have copied the root_floppy.gz file to an MSDOS format disk, rather than simply putting it at the start of the disk. Please see the FLOPPIES.readme file for instructions. Steve Early [EMAIL PROTECTED]
Re: regular (aka bsd) compress distribution?
On Mon, 20 May 1996, Yves Arrouye wrote: > Is it impossible to distribute a real compress program? I know there > may be problems with an LZW patent, but I don't know how they relate > to the distribution of a compress program for say personal use. > If this is possible I'll make a package for it. If we do have a compress package, it must go in non-free. > If this is really impossible, would it be at least possible for the > gzip package *not* to provide a compress link (uncompress is okay > because gzip correctly uncompresses compress'ed files)? It is really > confusing to be able to run the compress command deep in an app. building > hierarchy and to see some time after that (in my case) the fonts file > that have been compressed by this compressed cannot be understood by X > (starting with mkfontdir). The gzip package should not provide a compress link. I asked the maintainer to remove the link some time ago, and he did - it seems to have crept back in though. I will submit a bug report. I need a real 'compress' for font file compression too. I suppose I haven't noticed the bad gzip package because I put a real compress in /usr/local/bin, and it's ahead of /usr/bin on my PATH. Steve Early [EMAIL PROTECTED]
Re: Imake problems.
On Mon, 20 May 1996, Dale Scheetz wrote: > I have tried to use imake on several packages recently. If I try xmkmf I > get something like: > > imake -DUseInstalled -I/usr/X11R6/lib/X11/config > Imakefile.c:3: Imake.tmpl: No such file or directory > imake: Exit code 33. Stop. > > Anyone know what's missing? You are missing the development package, xdevel. This package is necessary to compile X clients. It contains the configuration files for imake and the header files that go in /usr/X11R6/include. Steve Early [EMAIL PROTECTED]
Re: X and ELF/a.out
On Mon, 20 May 1996, Scott Barker wrote: > I've noticed that, so far, I can virtually indiscriminately mix and match ELF > and a.out on a partially updated debian system. I'm now wanting to upgrade > X. Will I still be able to use a.out and ELF binaries under X? Yes. The xcompat package contains the old a.out shared libraries. Steve Early [EMAIL PROTECTED]
Re: dselect complaints
On Sun, 19 May 1996, William S. Gribble wrote: > Ian Jackson wrote: > > I'm not interested in hearing any more complaints or even extensive > > suggestions for improvement, unless the person complaining is > > volunteering to do the work on a new interface. > > If you don't want feedback about the tools, might I suggest that you > give up their maintenance to someone who does? Dselect as it exists > is nothing more or less than a working prototype of the tool it needs > to be. I believe you have missed the point. Ian knows that the dselect user interface is not what it should be, and has received extensive suggestions for improvements. He doesn't have time to work on these suggestions at the moment, so sending him more suggestions is not a terribly useful thing to do. It isn't a matter of ego, or a belief that the user interface is good. It's just time. > What needs to happen, in my opinion: > > 1. Make the release of debian-1.1 public, when outstanding bugs are fixed. >Emphasize alternatives to dselect in the documentation. Make it >clear that dselect is still a working prototype rather than a finished >product. Provide script(s) to handle several common initial-installation >scenarios, with instructions about how to use dpkg to install more or >remove unwanted packages. I believe this is sensible - dpkg should be better documented anyway. > 2. Open a period of discussion to draft a new specification for dselect, >using the lessons learned from the current version as a starting point. > 3. Rewrite dselect to meet the new specification. Who is going to do this? There have been many separate suggestions for package management user interfaces, but so far nobody has made any move towards implementing them. I think that the only way we're going to find out what the best interface is is to implement them all (at least partially) and see which work. This doesn't all have to be done by the same person. Steve Early [EMAIL PROTECTED]
X font server instructions
On Fri, 17 May 1996, Olaf Erb wrote: > Loading emacs freezes X11 completely for > about 5 seconds, with a.out everything slowed down during emacs-startup, too, > but not like now. That's the price we pay for new features.. Maybe the new version of emacs is requesting more fonts? The X server doesn't multi-task while rendering fonts. If this is a problem, you should consider setting up a font server. I suppose I should write some instructions on how to enable the font server in Debian. It's actually quite easy: (assuming you're using a recent version of xbase and have all the font packages installed) Add the line 'start-xfs' to /etc/X11/config Run '/etc/init.d/xfs start' Edit your /etc/X11/XF86Config file to include the line: FontPath"tcp/localhost:7100" in the 'Files' section. Kill and restart your X server. ...although font rendering will still take time, the X server will not hang while it is happening. Steve Early [EMAIL PROTECTED]
Re: X Windows
On Thu, 16 May 1996, Carlos Carvalho wrote: > Stephen Early ([EMAIL PROTECTED]) wrote on 16 May 1996 12:45: > >> e.g. have xdm login screens on vc 3,4,5,6 > >Yes, it's possible. Bear in mind that it will be necessary to run an X > >server for each VC, which will take a lot of memory. > > Isn't there a problem with the lock file? No. The lock files exist to stop you running two servers with the same display number on the same machine. When you run multiple servers, you give them different display numbers. Steve Early [EMAIL PROTECTED]
Re: X Windows
On Thu, 16 May 1996, Dale Scheetz wrote: > > /etc/init.d/xdm stop > > > When I run the script it seems to run ok, produces no output, and returns > the prompt. However, killing fvwm2 still produces a new login screen (even > when you do it several times). 'ps a' still shows no xdm process. I see - it only tries to stop xdm if it is set up to start it at boot time. I'll change that in the next xbase, if I remember. As a matter of interest, what does this do: start-stop-daemon --stop --verbose --exec /usr/bin/X11/xdm Steve Early [EMAIL PROTECTED]
Re: X Windows
On Thu, 16 May 1996, Dale Scheetz wrote: > OK, so, I used xdm to start X and things work fine. When I exit fvwm2 I > get a login prompt. Now, I want to shut down the server. > > A. I can find no xdm process either with ps a or top. Is it hiding? No, it should be there. You should be able to kill it using the /etc/init.d/xdm script: /etc/init.d/xdm stop Steve Early [EMAIL PROTECTED]
Re: X Windows
On Thu, 16 May 1996, Craig Sanders wrote: > i don't use xdm at the moment, just startx. > > Is it possible to get xdm to put a login prompt on more than one vc? > > e.g. have xdm login screens on vc 3,4,5,6 > > so i can login on vc3 but let other people share my machine in X windows > without having to log out...just press ctrl-alt-F4 to switch to another X > login screen. Yes, it's possible. Bear in mind that it will be necessary to run an X server for each VC, which will take a lot of memory. Technically you can do it by adding extra lines to /etc/X11/xdm/Xservers. The default line says: :0 local /usr/X11R6/bin/X You can add more lines, of the form: :1 local /usr/X11R6/bin/X :1 :2 local /usr/X11R6/bin/X :2 etc. There may be a race condition involved in starting lots of X servers simultaneously - I haven't checked yet. If this turns out to be the case, you may be better off starting xdm without any X servers, and then starting up the X servers at a later point in the boot sequence. You can tell an X server to ask xdm for a login window using the -query command line option. For instance, to start an X server with display number 1: /usr/X11R6/bin/X :1 -query hostname If you have set up your XF86Config file correctly, and your graphics card supports it, you can have X servers with different colour depths running as well. For instance: /usr/X11R6/bin/X :3 -bpp 16 -query hostname ...would try to start up a 16bpp X server on display number 3. NB display numbers are NOT VC numbers; when you start an X server it will grab the first free VT. For more details, see the Xserver(1x) manpage. Steve Early [EMAIL PROTECTED]
Re: X Windows
On Wed, 15 May 1996, Dale Scheetz wrote: > When I try xdm as a user (with the server up and running via root) I get > told: > Only root wants to use xdm > Have I got some permissions wrong? Or have I just missunderstood...again. You have misunderstood. When it is set up correctly, xdm can be started as part of the boot process. It will start an X server and provide a login window. If you don't want it to be started automatically, you can still configure it and start it from a root shell. By 'configured' I really mean that there should be a line in /etc/X11/xdm/Xservers to start your local X server. It should look like: :0 local /usr/X11R6/bin/X You should be prompted about this when you install the X packages. If you aren't, you've probably said either Yes or No to it in the past. If you are using the latest version of the X packages, see /etc/X11/config in conjunction with /usr/doc/X11/debian.README If you want to run xdm, but don't want it to run an X server, you can remove that line from /etc/X11/xdm/Xservers (and set the no-xdm-start-server option in /etc/X11/config). You can then start an X server and get a login window with a command like: /usr/X11R6/bin/X -query hostname ...where hostname is your machine's name. Steve Early [EMAIL PROTECTED]
Re: X Windows
On Mon, 13 May 1996, Dale Scheetz wrote: > I am somewhat put off by the hodge podge of packages in the x11 section. I > know I need: > xserver_x I chose xserver_svga > xlib > xbase > xfntbase > xmanpages > fvwm2 Actually you don't need the xmanpages package; it contains the manpages to do with X development. Manpages for the standard X clients are included in the xbase package. > Is there anything else I need for a minimal X installation? How do I tell > (asside from examining dependencies and description fields) which of the > other packages in this section are desirable, necessary, objectionable, > etc... > I'd love some pointers on what's left as well. The minimum local X installation is xlib, xbase, xfntbase and an X server package. You're likely to want xcontrib as well; it contains some very useful clients. The reason that X is split up into so many packages is that it's so _big_ and there are so many different things it can be used for. For instance, sometimes people want to set up a large machine as a server, and lock it away in a room. This machine will have a minimal display card, and will not run an X server locally. It might have all the fonts installed, and could run a font server. Other machines could then be set up with only the X server package; they would read fonts from the font server, and the clients would all run on the main server. Steve Early [EMAIL PROTECTED]
Re: xconsole for 1.1?
In article <[EMAIL PROTECTED]> you write: >[EMAIL PROTECTED]:[~] >dpkg -S xconsole >xbase: /usr/X11R6/bin/xconsole >xbase: /usr/X11R6/man/man1/xconsole.1x > >Hope that answers your question... That's the unstable xbase. It is, of course, in the stable xbase as well. Steve Early [EMAIL PROTECTED]
Re: 1.1 X setup default: bs/del don't work with motif apps.
On Fri, 10 May 1996, Martin Konold wrote: > I did a ln -s /usr/X11R6 /usr/X386 > in order to get the motif application netscape running. > This way it will find the > /usr/X11R6/lib/X11/XKeysymDB > for wihich netscape looks at > /usr/X386/lib/X11/XKeysymDB > > May the debian team will include this symlink in the xbase package No, this symlink won't be included in the xbase package. It is a nasty hack. Instead, the Netscape installation should arrange for environment variables to make Netscape look in the right place for its files. Steve Early [EMAIL PROTECTED]
Re: xconsole
> when I start X through xdm, I get a nice xconsole that displays all kind > of messages. When I start xconsole by hand from an X-session (or from my > .xsession-file), I don't get them. How do I get them anyway? Messages from syslogd to xconsole are sent through the named pipe /dev/xconsole. You can make xconsole read from this pipe by using the -file option. Steve Early [EMAIL PROTECTED]
Re: 1.1 fresh installation report
On Tue, 7 May 1996, Yves Arrouye wrote: > - Xconsole is still not anywhere. You mean the xconsole program, or the named pipe in /dev? I think that /dev/xconsole should be managed by the syslogd package, as the default syslogd configuration refers to it. > - Having chosen my X server and answered all X config. questions, I > still have XF86_NONE (or NOTHING?) in the Xserver file. I don't know how this happens - I've never seen that problem before. > - Having installed xdm, the xdm/Xservers file is not updated with an > entry for my local server, though the comments in this file indicate > it should be done by the installation program. I knew about that problem, and I've fixed it in the latest xbase, version 3.1.2-9. Steve Early [EMAIL PROTECTED] PS your return mail address seems to be incorrect; you'll probably only receive this message via the mailing list.
Re: xbase doesn't setup the server
On Thu, 2 May 1996, Carlos Carvalho wrote: > I upgraded X to ELF from .99R6, and after going through xbase, xfnt*, > xlib and some clients, xdm didn't start the server. I had to > re-decipher all the mess of xdm which I obviously had forgotten :-( This is fixed in xbase-3.1.2-9, uploaded today. > I also have a suggestion about fonts: I thought I had installed all > the xfnt*, but I had forgotten xfntbase... This means that the server > stops when it doesn't find the font "fixed". Considering that I had > those fonts in the previous installation and that something removed > them, so it wasn't my fault, I think it'd be nice to have a dependency > for xfntbase either in xserver or xfnt^base* (in zsh notation), or > another suitable place. No, a dependency is not the right thing to do; it is quite possible to run the X server without any fonts being installed. The idea of having non-base font packages depend on the base package is interesting, and I'll consider it for the future. It'll probably be reduced in strength to a "Recommends" line, though. Steve Early [EMAIL PROTECTED]
Re: xdm config after install
On Mon, 6 May 1996, Douglas Bates wrote: > When xbase was being installed I thought I responded that I wanted xdm > to be started at boot time. Now I can see that after a reboot an xdm > process is running but no X-server is started on the default display. It's a known bug in the current X packages; they don't put the appropriate line in /etc/X11/xdm/Xservers. Add the following line to this file and things should work: :0 local /usr/X11R6/bin/X > If I try to configure xbase again I get [...] You can't configure a package that's already configured. > I can run an X server as root by using startx. I cannot run it as a > regular user; presumably because of permission problems. You can change who is allowed to run an X server by editing /etc/X11/Xserver; there are three choices: RootOnly, Console and Anybody. > I would welcome suggestions on what to reconfigure so the X server > starts up at boot time. If adding the line to /etc/X11/xdm/Xserver doesn't work, try adding the line 'start-xdm' to /etc/X11/config. If there's a line there saying 'no-start-xdm' then remove it. This controls whether xdm is started at all. If /etc/X11/config doesn't exist then you have an old version of the X packages. I've answered the question about /etc/X11/xdm/Xservers about five times now, and each time the answer has been posted to debian-user. Please would people check through the most recent messages before posting questions, as some questions really are frequently asked. I'll release a fixed set of X packages soon (as soon as I've finished my dissertation - there's a deadline soon). Steve Early [EMAIL PROTECTED]
Re: installing debian1.1 in a free partition
On Thu, 2 May 1996, Francisco Avelino da Silva wrote: > * The X configuration: hh. I run X well when I try startx xinit or > xdm with fvwm. When I used openwin upon xdm was more complicated, but with > some effort now it works (at home I have a new atlantis-intel > motherboard with a AtiMach64 CT chip that ONLY works with the last > XMach64 3.12D server; after the normal installation of debian on a > clean partition I substituted only the XF86_M64 file in the /usr/X11R6/bin > directory). Substituting the server (or putting the new one in /usr/local/bin) is the right thing to do, until the next version of XFree86 is released officially. Could you describe the problems you had with openwin, and what you did to make it work? Steve Early [EMAIL PROTECTED]
Re: upgrading from 0.93R6 to 1.1 beta
On Thu, 2 May 1996, James D. Freels wrote: > Can I install v 1.1 over the existing v 0.93R6 installation as a usual > package (or whole sets of packages) upgrade? I could not find > instructions on how to do that. Yes, you can. Two sets of instructions have been posted to debian-user recently describing how to do this; one describes a method using dselect, and the other provides a script to upgrade the base packages. Further upgrades can then be made with dselect. Steve Early [EMAIL PROTECTED]
Re: problem upgrade to 1.1
On Thu, 2 May 1996, gli wrote: > Then I joyfully upgraded the rest of the system. I upgraded the X11 from > the unstable tree, after I fetched all the packages that I need such as > xbase, xserver-mach32, etc, and install it, also using dselect and > dpkg-ftp, but I got some error messages at the end. Could you possibly send me the error messages? There is one known problem in the current X packages; the server is not added to /etc/X11/xdm/Xservers. /etc/X11/Xserver should be set up correctly. I'm going to release fixed packages after I've finished my dissertation. > 1) configure the required files by hand. I need to read some related > documents before I can make sure everything is ok. I will learn more. If /etc/X11/Xserver and /etc/X11/xdm/Xservers are the only problem, it's probably best to set them up by hand. Once you've done this, re-run the configuration scripts for the packages (using dpkg --configure --pending) and things should work. You should put the following two lines in /etc/X11/Xserver: /usr/X11R6/bin/XF86_Mach32 Console You should add the following line to the end of /etc/X11/xdm/Xservers: :0 local /usr/X11R6/bin/X > 2) Un-select the packages and remove the configure files using dselect, > then re-select the packages again and hope it will be configured correctly > this time. I have not try this way, what happen if I have the same > result? Or some magic in Debian system. That should work, apart from the known bug with putting the line in /etc/X11/xdm/Xservers. > 3) Start all over again. Directly install 1.1 from scratch. You don't need to do that. > I would prefer, something along the line of the second method above, to > fix my Debian system. Because I have other packages install as well, they > were not configured correctly during the installation also. For example > the sendmail keeps dumping out error message on my first console. Other > packages complain about sendmail is not configured yet. The gpm 1.0 is > not working correctly, it was working in the older package. And zgv > cannot run, it cannot find libvga.so.1. The modules was in not good > order, cannot use insmod, etc. You can find out which packages are unpacked but not configured by using dpkg --audit. You can use dpkg -s packagename for any installed or unpacked package to find out what it depends on, and then install the required packages manually. Alternatively dselect is supposed to do the right thing, but I always find that using dpkg directly is easiest and fastest. Steve Early [EMAIL PROTECTED]
