Linux-Misc Digest #564, Volume #27 Sun, 8 Apr 01 20:13:04 EDT
Contents:
DRI Drivers with XFree86-4.0.2 (Reto Wigger)
Re: very misc, diskette geometry, etc apples and trs80s. ("xinodabeano")
Re: Two frustrating Samba problems... (Michael Perry)
Re: Support for LCD Monitors? (Michael Meissner)
Please help with Samba printer share (Arctic Storm)
Re: kernel upgrade - yikes!! (tech2kjason)
Re: KDE 2.1 or Gnome 1.4? (Bob Hauck)
Re: Two frustrating Samba problems... (Dances With Crows)
----------------------------------------------------------------------------
From: Reto Wigger <[EMAIL PROTECTED]>
Subject: DRI Drivers with XFree86-4.0.2
Date: Mon, 9 Apr 2001 23:44:14 +0200
Hi
To play Quake3Arena on my linux machine i installed the DRI-Drivers
from sourceforge (rage128-20010404-i386-Linux.tar.gz)
In my PC is a
ATI Xpert 2000 Pro,32MB, AGP4x SD-RAM, Rage 128 VR
plugged.
So the drivers sould match to my card.
I have:
SuSE Linux 7.1
XFree86-4.0.2
Kernel 2.4.2
My /etc/X11/XF86Config:
Section "Module"
Load "dbe"
SubSection "extmod"
Option "omit xfree86-dga"
EndSubSection
Load "extmod"
Load "type1"
Load "freetype"
Load "glx"
Load "dri"
EndSection
Section "DRI"
Mode 0666
EndSection
Section "Files"
RgbPath "/usr/X11R6/lib/X11/rgb"
FontPath "/usr/X11R6/lib/X11/fonts/local/"
FontPath "/usr/X11R6/lib/X11/fonts/misc/"
FontPath "/usr/X11R6/lib/X11/fonts/75dpi/:unscaled"
FontPath "/usr/X11R6/lib/X11/fonts/100dpi/:unscaled"
FontPath "/usr/X11R6/lib/X11/fonts/Type1/"
FontPath "/usr/X11R6/lib/X11/fonts/Speedo/"
FontPath "/usr/X11R6/lib/X11/fonts/75dpi/"
FontPath "/usr/X11R6/lib/X11/fonts/100dpi/"
ModulePath "/usr/X11R6/lib/modules/"
EndSection
#Input Devices wie Maus, Tastatur......
Sectiontion "Device"
Identifier "Standard VGA"
VendorName "Unknown"
BoardName "Unknown"
Driver "vga"
EndSection
Section "Device"
Identifier "ati"
Driver "ati"
#VideoRam 32768
EndSection
.......
# End of /etc/X11/XF86Config
My X Server crashes with these messages:
Module Loader present
(==) Log file: "/var/log/XFree86.0.log", Time: Sun Apr 8 17:19:26 2001
(==) Using config file: "/etc/X11/XF86Config"
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (??) unknown.
(==) ServerLayout "Simple Layout"
(**) |-->Screen "Screen 1" (0)
(**) | |-->Monitor "vs"
(**) | |-->Device "ati"
(**) |-->Input Device "Mouse1"
(**) |-->Input Device "Keyboard1"
(**) XKB: rules: "xfree86"
(**) XKB: model: "pc105"
(**) XKB: layout: "de_CH"
(**) FontPath set to
"/usr/X11R6/lib/X11/fonts/local/,/usr/X11R6/lib/X11/fonts
misc,/usr/X11R6/lib/X11/fonts/75dpi/:unscaled,/usr/
X11R6/lib/X11/fonts/100dpi/:unscaled,/usr/X11R6/lib/
X11/fonts/Type1/,/usr/X11R6/lib/X11/fonts/Speedo/,/usr/
X11R6/lib/X11/fonts/75dpi/,/usr/X11R6/lib/X11/fonts/100dpi/"
(**) RgbPath set to "/usr/X11R6/lib/X11/rgb"
(**) ModulePath set to "/usr/X11R6/lib/modules/"
(--) using VT number 7
(II) Loading /usr/X11R6/lib/modules/fonts/libbitmap.a
(II) Module bitmap: vendor="The XFree86 Project"
compiled for 4.0.2, module version = 1.0.0
(II) Loading /usr/X11R6/lib/modules/libpcidata.a
(II) Module pcidata: vendor="The XFree86 Project"
compiled for 4.0.2, module version = 0.1.0
(II) Loading /usr/X11R6/lib/modules/libscanpci.a
(II) Module scanpci: vendor="The XFree86 Project"
compiled for 4.0.2, module version = 0.1.0
(II) Unloading /usr/X11R6/lib/modules/libscanpci.a
(--) PCI:*(1:0:0) ATI Rage 128 Pro PF rev 0, Mem @ 0xe0000000/26,
0xdf000000/14, I/O @ 0xd800/8
(II) Loading /usr/X11R6/lib/modules/extensions/libdbe.a
(II) Module dbe: vendor="The XFree86 Project"
compiled for 4.0.2, module version = 1.0.0
(II) Loading /usr/X11R6/lib/modules/extensions/libextmod.a
(II) Module extmod: vendor="The XFree86 Project"
compiled for 4.0.2, module version = 1.0.0
(II) Loading /usr/X11R6/lib/modules/fonts/libtype1.a
(II) Module type1: vendor="The XFree86 Project"
compiled for 4.0.2, module version = 1.0.0
(II) Loading /usr/X11R6/lib/modules/fonts/libfreetype.a
(II) Module freetype: vendor="The XFree86 Project"
compiled for 4.0.2, module version = 1.1.8
(II) Loading /usr/X11R6/lib/modules/extensions/libglx.a
(II) Module glx: vendor="The XFree86 Project"
compiled for 2.49.119Ey, module version = 1.0.0
(II) Loading /usr/X11R6/lib/modules/extensions/libGLcore.a
(II) Module GLcore: vendor="The XFree86 Project"
compiled for 2.49.119Ey, module version = 1.0.0
(II) Loading /usr/X11R6/lib/modules/extensions/libdri.a
(II) Module dri: vendor="The XFree86 Project"
compiled for 2.49.119Ey, module version = 1.0.0
(II) Loading /usr/X11R6/lib/modules/linux/libdrm.a
(II) Module drm: vendor="The XFree86 Project"
compiled for 2.49.119Ey, module version = 1.0.0
(II) Loading /usr/X11R6/lib/modules/drivers/ati_drv.o
(II) Module ati: vendor="The XFree86 Project"
compiled for 2.49.119Ey, module version = 6.2.5
(II) Loading /usr/X11R6/lib/modules/input/mouse_drv.o
(II) Module mouse: vendor="The XFree86 Project"
compiled for 4.0.2, module version = 1.0.0
(II) ATI: ATI driver (version 6.2.5) for chipsets: ati, ativga
(II) R128: Driver for ATI Rage 128 chipsets: ATI Rage 128 RE (PCI),
ATI Rage 128 RF (AGP), ATI Rage 128 RG (AGP), ATI Rage 128 RK (PCI),
ATI Rage 128 RL (AGP), ATI Rage 128 Pro PD (PCI),
ATI Rage 128 Pro PF (AGP), ATI Rage 128 Mobility LE (PCI),
ATI Rage 128 Mobility LF (AGP), ATI Rage 128 Mobility MF (AGP),
ATI Rage 128 Mobility ML (AGP)
(II) RADEON: Driver for ATI Radeon chipsets: ATI Radeon QD (AGP),
ATI Radeon QE (AGP), ATI Radeon QF (AGP), ATI Radeon QG (AGP)
(--) Assigning device section with no busID to primary device
(--) Chipset ATI Rage 128 Pro PF (AGP) found
(II) Loading /usr/X11R6/lib/modules/drivers/r128_drv.o
(II) Module r128: vendor="The XFree86 Project"
compiled for 2.49.119Ey, module version = 4.0.1
(II) Loading /usr/X11R6/lib/modules/libvgahw.a
(II) Module vgahw: vendor="The XFree86 Project"
compiled for 4.0.2, module version = 0.1.0
(II) R128(0): PCI bus 1 card 0 func 0
(**) R128(0): Depth 16, (--) framebuffer bpp 16
(II) R128(0): Pixel depth = 16 bits stored in 2 bytes (16 bpp pixmaps)
(==) R128(0): Default visual is TrueColor
(==) R128(0): RGB weight 565
(II) R128(0): Using 6 bits per RGB (8 bit DAC)
(II) Loading /usr/X11R6/lib/modules/linux/libint10.a
(II) Module int10: vendor="The XFree86 Project"
compiled for 4.0.2, module version = 1.0.0
(II) R128(0): initializing int10
(II) R128(0): Primary V_BIOS segment is: 0xc000
(--) R128(0): Chipset: "ATI Rage 128 Pro PF (AGP)" (ChipID = 0x5046)
(--) R128(0): Linear framebuffer at 0xe0000000
(--) R128(0): MMIO registers at 0xdf000000
(--) R128(0): BIOS at 0xdffe0000
(--) R128(0): VideoRAM: 32768 kByte (64-bit SDR SGRAM 1:1)
(II) R128(0): PLL parameters: rf=2950 rd=65 min=12500 max=40000; xclk=12000
(II) Loading /usr/X11R6/lib/modules/libddc.a
(II) Module ddc: vendor="The XFree86 Project"
compiled for 4.0.2, module version = 1.0.0
(II) Loading /usr/X11R6/lib/modules/libvbe.a
(II) Module vbe: vendor="The XFree86 Project"
compiled for 4.0.2, module version = 1.0.0
(II) R128(0): VESA BIOS detected
(II) R128(0): VESA VBE DDC supported
(II) R128(0): Manufacturer: ___ Model: ffff Serial#: 4294967295
(II) R128(0): Year: 2245 Week: 255
(II) R128(0): EDID Version: 255.255
(II) R128(0): Digital Display Input
(II) R128(0): Max H-Image Size [cm]: horiz.: 255 vert.: 255
(II) R128(0): Gamma: 3.55
(II) R128(0): DPMS capabilities: StandBy Suspend Off
(II) R128(0): Default color space is primary color space
(II) R128(0): First detailed timing is preferred mode
(II) R128(0): GTF timings supported
(II) R128(0): redX: 0.632 redY: 0.335 greenX: 0.296 greenY: 0.593
(II) R128(0): blueX: 0.143 blueY: 0.065 whiteX: 0.280 whiteY: 0.311
(II) R128(0): Supported VESA Video Modes:
(II) R128(0): 720x400@70Hz
(II) R128(0): 640x480@60Hz
(II) R128(0): 640x480@75Hz
(II) R128(0): 800x600@75Hz
(II) R128(0): 1024x768@60Hz
(II) R128(0): 1024x768@75Hz
(II) R128(0): Manufacturer's mask: 0
(II) R128(0): Supported Future Video Modes:
(II) R128(0): #0: hsize: 1280 vsize 1024 refresh: 60 vid: 32897
(II) R128(0): #1: hsize: 1024 vsize 768 refresh: 85 vid: 22881
(II) R128(0): #2: hsize: 800 vsize 600 refresh: 85 vid: 22853
(II) R128(0): #3: hsize: 640 vsize 480 refresh: 85 vid: 22833
(--) R128(0): unexpected EDID version 255 revision 255
(==) R128(0): Using gamma correction (1.0, 1.0, 1.0)
(II) R128(0): vs: Using hsync range of 30.00-70.00 kHz
(II) R128(0): vs: Using vrefresh range of 50.00-120.00 Hz
(II) R128(0): Clock range: 12.50 to 400.00 MHz
(WW) R128(0): Default mode "1280x960" deleted (hsync out of range)
(WW) R128(0): Default mode "1280x1024" deleted (hsync out of range)
(WW) R128(0): Default mode "1280x1024" deleted (hsync out of range)
(WW) R128(0): Default mode "1600x1200" deleted (hsync out of range)
(WW) R128(0): Default mode "1600x1200" deleted (hsync out of range)
(WW) R128(0): Default mode "1600x1200" deleted (hsync out of range)
(WW) R128(0): Default mode "1600x1200" deleted (hsync out of range)
(WW) R128(0): Default mode "1600x1200" deleted (hsync out of range)
(WW) R128(0): Default mode "1792x1344" deleted (hsync out of range)
(WW) R128(0): Default mode "1792x1344" deleted (hsync out of range)
(WW) R128(0): Default mode "1856x1392" deleted (hsync out of range)
(WW) R128(0): Default mode "1856x1392" deleted (hsync out of range)
(WW) R128(0): Default mode "1920x1440" deleted (hsync out of range)
(WW) R128(0): Default mode "1920x1440" deleted (hsync out of range)
(--) R128(0): Virtual size is 1024x768 (pitch 1024)
(**) R128(0): Default mode "1024x768": 94.5 MHz, 68.7 kHz, 85.0 Hz
(--) R128(0): Display dimensions: (255, 255) cm
(--) R128(0): DPI set to (10, 7)
(II) Loading /usr/X11R6/lib/modules/libfb.a
(II) Module fb: vendor="The XFree86 Project"
compiled for 4.0.2, module version = 1.0.0
(II) Loading /usr/X11R6/lib/modules/libramdac.a
(II) Module ramdac: vendor="The XFree86 Project"
compiled for 4.0.2, module version = 0.1.0
(II) Loading /usr/X11R6/lib/modules/libxaa.a
(II) Module xaa: vendor="The XFree86 Project"
compiled for 4.0.2, module version = 1.0.0
Symbol xf86EnablePciBusMaster from module
/usr/X11R6/lib/modules/drivers/r128_drv.o is unresolved!
(==) R128(0): Write-combining range (0xe0000000,0x2000000)
(II) R128(0): [drm] created "r128" driver at busid "PCI:1:0:0"
(II) R128(0): [drm] added 4096 byte SAREA at 0xc5a52000
(II) R128(0): [drm] mapped SAREA 0xc5a52000 to 0x40017000
(II) R128(0): [drm] framebuffer handle = 0xe0000000
(II) R128(0): [drm] added 1 reserved context for kernel
(II) R128(0): [agp] Mode 0x1f000201 [AGP 0x1106/0x0305; Card 0x1002/0x5046]
(II) R128(0): [agp] 8192 kB allocated with handle 0xc817b000
(II) R128(0): [agp] ring handle = 0xe4000000
(II) R128(0): [agp] Ring mapped at 0x42211000
(II) R128(0): [agp] ring read ptr handle = 0xe4101000
(II) R128(0): [agp] Ring read ptr mapped at 0x40018000
(II) R128(0): [agp] vertex/indirect buffers handle = 0xe4102000
(II) R128(0): [agp] Vertex/indirect buffers mapped at 0x42312000
(II) R128(0): [agp] AGP texture map handle = 0xe4302000
(II) R128(0): [agp] AGP Texture map mapped at 0x42512000
This should not happen!
An unresolved function was called!
X connection to :0.0 broken (explicit kill or server shutdown).
Who can help me?
--
Warum durch ein Fenster gucken, wenn die T�r schon offen steht?
have a lot of fun
rewi
------------------------------
From: "xinodabeano" <[EMAIL PROTECTED]>
Subject: Re: very misc, diskette geometry, etc apples and trs80s.
Date: Sun, 8 Apr 2001 19:19:55 -0500
"xinodabeano" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]...
> Where can I find more info on how diskettes drives work, what formats
> various
> os's use to write their filesystems, and possibilities on writing code to
> read from disks created under trsDos, appleDos, and CP/m? Can a late model
> PC drive even read these disks, or does the layout of sectors, tracks, etc
> rule that out?
>
> I've searched via google, but have not been able to turn up anything very
> useful--to me anyway.
>
> Thanks for any info/pointers.
>
Were there any sparc or other hardware that is supported by linux that
has/had 5 1/2 drives besides the pc?
------------------------------
From: [EMAIL PROTECTED] (Michael Perry)
Subject: Re: Two frustrating Samba problems...
Date: Sun, 08 Apr 2001 23:22:19 -0000
On 08 Apr 2001 22:38:49 GMT, Hiawatha Bray <[EMAIL PROTECTED]> wrote:
> First, how do I get my Windows box to see the files on my Linux machine?
> When I go to Network Neighborhood, I see the Linux computer, but when I
> click on the Icon for it, I get an Action Cancelled window. When I run net
> view in a DOS window, I get an Error 53 saying the computer can't find the
> machine. But when I do a generic net view command, to show all the boxes
> connected, the Linux box pops right up. I don 't get this. Do I need to
> set up shares for the Linux drives? If so, how?
>
> My other question: How do I see the Windows shares on the Linux box?
> What's the Linux equivalent of Network Neighborhood? Thanks.
>
>
>
Check out how you are mounting home directories in the smb.conf file. Also
how do you have security setup? Are you doing user level security and
creating smbpasswds for each user? ARe passwords encypted?
Here is how I do this:
1) create a home share using the default ones that most distributions
include in the smb.conf file. I want to write to the shared directories so
I change the file and directory permissions.
2) add a user using the smbpasswd utility. Become root and do "smbpasswd -a
username". It will prompt for a password. Now enter one and remember it!
3) go the win98 box. Create a new user on it with the same username and
password you just entered on the linux box. You probably will have to
reboot. But before you do ensure that your workgroup is workgroup on both
the linux and windows box. I understand that samba will reread the smb.conf
file but I always stop and restart smb as the root user by doing a
/etc/init.d/smb restart.
4) Create more shares as you need and remember to always read on
www.samba.org for clues on using smb.conf files. They have a very good
section on modifying and using the smb.conf file. You can mount cd drives,
zip drives, jaz drives, etc using the preexec and postexec commands along
with a share.
I share homes, zip drive, a projects share, etc on my linux box. ON my 98
box, I get a printer from the linux system, access to my zip drive, my linux
cd drive, etc. Important thing here is to digest and understand what goes
on in a smb.conf file. Best place for that is www.samba.org.
--
Michael Perry
[EMAIL PROTECTED]
===================
------------------------------
Crossposted-To: alt.uu.comp.os.linux.questions,comp.os.linux.hardware,uk.comp.os.linux
Subject: Re: Support for LCD Monitors?
From: Michael Meissner <[EMAIL PROTECTED]>
Date: 08 Apr 2001 19:30:02 -0400
"Robert Hardy" <[EMAIL PROTECTED]> writes:
> Not knowing so much about Linux etc. I am wondering if I will have problems
> using a LCD monitor (precisely the Proview BM568 or the TAXAN Crystalvision
> 680) - I am just putting together a system and will want to run some
> distribution of Linux (no preference as yet). Will I need drivers and such -
> since I know that they supply Win9* etc drivers with the product (not sure
> what they do), but they don't have any Linux drivers for download from their
> sites.
IMHO, it might be best to get a LCD monitor that has both analog and digitial
inputs, which raises the price somewhat. That way, even if you can't get the
digital controls to work, you can hook it up as a normal monitor. For digital
controls, your choices are:
G400 with flat panel support addon (not G450)
G200 with flat panel support addon + DVI adapter
ATI Radeon VE
ATI Radeon All-in-Wonder with DVI output
ASUS 7100 with DVI output
VisonTek GeForce2 with DVI output
For the Matrox cards, you have to order the digital flat panel addon directly
from Matrox. The G200 uses an earlier connector, so you will also need an
adapter to the current DVI connector. Note, my motherboard (ASUS P2B-DS) seems
to disable the flat panel support in both the G400 and the G200. You can get a
Matrox binary, non-GPL driver for X that supports the flat panel, and 2.4 frame
buffer code for the G400 has support for 'dfp' (though since my motherboard
doesn't support it, I can't say if it works).
The Radeon VE supports DVI flat panels with the vesa framebuffer support, but
there is no X support at the present time. Given ATI claims to work with the
Xfree86 developers, it is probably just a matter on months until it is
supported. Until then, constructing an X server that uses the framebuffer
might work.
The Xfree86 sources mention that that the All in Wonder flat panel support is
disabled at the current time. XIG (commercial X server, $99) does claim
support the All In Wonder flat panel.
The digital output of the two GeForce2 cards is not supported in the current
Xfree86 sources, but you can get a binary, non-GPL driver from nVidia that
claims support. I haven't tried these cards yet.
--
Michael Meissner, Red Hat, Inc. (GCC group)
PMB 198, 174 Littleton Road #3, Westford, Massachusetts 01886, USA
Work: [EMAIL PROTECTED] phone: +1 978-486-9304
Non-work: [EMAIL PROTECTED] fax: +1 978-692-4482
------------------------------
From: Arctic Storm <[EMAIL PROTECTED]>
Subject: Please help with Samba printer share
Date: Sun, 08 Apr 2001 23:30:39 GMT
I have a network between RedHat 7 and Win2K.
The printer and internet are connected to the RedHat 7 system.
I'm able to establish internet sharing and disk sharing; the Win2K computer
can read/write to the Linux hard drive. However, I cannot print to the
printer from Win2K. When I try to print a test page from the properties
window, I get the following error.
"Test page failed to print. ... Unable to create a print job."
What kind of things can I do to trouble shoot?
Below is the smb.conf file.
[global]
workgroup = WORKGROUP
server string = SambaServer
printing = BSD
printcap name = /etc/printcap
load printers = yes
lock directory = /var/lock/samba
share modes = yes
interfaces = 127.0.0.1/24 192.168.1.1/24 192.168.2.1/24
bind interfaces only = yes
null passwords = yes
encrypt passwords = yes
wins support = yes
case sensitive = no
[printers]
comment = All Printers
path = /var/spool/lpd/lp
browseable = no
guest ok = yes
printable = yes
public = yes
writable = no
printing = BSD
create mode = 0700
print command = /usr/bin/lpr -r -h -P%p %s
guest ok = yes
null passwords = yes
[ljet]
comment = Okidata Okipage 6e (HP LaserJet 4 compatible)
path = /var/spool/ldp/lp
guest ok = yes
printer name = lp
printing = BSD
writable = yes
public = yes
printable = yes
guest ok = yes
null passwords = yes
print command = /usr/bin/lpr -r -h -P%p %s
[vfat]
comment = Windows Partition Drives
path = /mnt/vfat
browseable = yes
read only = no
guest ok = yes
[homes]
comment = Home Directories
path = /home
browseable = yes
read only = no
guest ok = yes
------------------------------
From: tech2kjason <[EMAIL PROTECTED]>
Crossposted-To: redhat.kernel.general,linux.redhat.install,comp.os.linux.setup
Subject: Re: kernel upgrade - yikes!!
Date: Sun, 08 Apr 2001 18:36:32 -0500
On Sun, 8 Apr 2001 15:13:45 -0700, "ekkis" <[EMAIL PROTECTED]> wrote:
>"tech2kjason" <[EMAIL PROTECTED]> wrote in message
>news:[EMAIL PROTECTED]...
>> On Fri, 6 Apr 2001 23:58:02 -0700, "ekkis" <[EMAIL PROTECTED]> wrote:
>>
>> >ran up2date on RH7 and was confused by the "excluded" list... it upgraded
>my
>> >kernel rpms to 2.2.17... after rebooting the box I have no network!
>troulbe
>> >is uname says I'm still on 2.2.16 but the modules directory under
>/usr/lib
>> >says 17 and there's no 16... yikes!
>> >
>> >can anyone suggest what I can do, especially given that I have no access
>to
>> >the net since the NICs won't come up?
>> >
>> >1k tia - erick
>> >
>>
>> I always wondered why RH advised users not to use up2date to upgrade
>> kernel packages... now I know...
>>
>> This issue can be resolved in one of two ways:
>>
>> 1 ) manually reinstall the updated kernel packages yourself:
>>
>> or
>>
>> 2) follow these steps...
>>
>> cd /boot
>> ls -al
>> verify that the System.map-2.2.17, kernel.h-2.2.17,
>> module-info-2.2.17, and vmlinuz-2.2.17 are present and/or linked
>> properly from System.map, kernel.h, module-info, and vmlinuz
>>
>> with ls -al you should see something like...
>> ...
>> kernel.h --> kernel.h-2.2.17
>> module-info --> module-info-2.2.17
>> System.map --> System.map-2.2.17
>> vmlinuz --> vmlinuz-2.2.17
>> ....
>> kernel.h-2.2.17
>> module-info-2.2.17
>> System.map-2.2.17
>> vmlinuz-2.2.17
>> ....
>>
>>
>> if /boot looks okay, it's time to visit lilo.conf inside /etc.
>> cd /etc
>>
>> use your favorite editor to verify the lilo.conf file, to make sure
>> that the "image=/boot/vmlinuz-2.2.17" is pointing to the right kernel.
>>
>> in my case, that section looks like this:
>> ....
>> "image=/boot/vmlinuz-2.4.3"
>> label=linux
>> read-only
>> root=/dev/hdc9
>>
>> other=/dev/hda1
>> label=win98
>>
>> Just remember that if you make any changes lilo.conf, to type lilo at
>> the prompt, so that it initializes it's pointers for the next reboot.
>
>thanks for replying. nfortunately option 1 was not available since up2date
>cleaned up after itself so I don't have the RPMs and I can't get them as my
>NICs don't work with the system as is... so I followed option 2:
>
>when I get a listing from /boot I notice that while:
>
>System.map -> System.map-2.2.17-14
>module-info -> module-info-2.2.17-14
>vmlinuz -> vmlinuz-2.2.17-14
>
>and
>
>System.map-2.2.17-14
>module-info-2.2.17-14
>vmlinuz-2.2.17-14
>
>exist, there is no kernel.h-2.2.17-14 and kernel.h is a normal file (dated
>before the upgrade (as are boot.b, chain.b message and os2_d.b) instead of
>being a link.
>
>also I notice that initrd.2.2.16-22.img exists (and doesn't seem to belong
>to any package) and there is no 2.2.17-14 version...
>
>also, the contents of my lilo.conf:
>
>boot=/dev/hda
>map=/boot/map
>install=/boot/boot.b
>prompt
>timeout=50
>message=/boot/message
>linear
>default=linux
>
>image=/boot/vmlinuz-2.2.16-22
> label=linux
> initrd=/boot/initrd-2.2.16-22.img
> read-only
> root=/dev/hda1
>
>what next then? can I change the image without having a new initrd?
>
>1k thx - e
>
As a precaution, add the following lines to your lilo.conf below the
default = linux
image=/boot/vmlinuz-2.2.17-14
label=linux2217 <--- ( any label you wish )
read-only
root=/dev/hda1
save lilo.conf
In /boot, create an empty file called kernel.h-2.2.17-14
rm kernel.h ( the link ) then create a link to the new kernel.h file
ln -s kernel-2.2.17-14 kernel.h
the contents of the kernel.h file is generated automatically during
the boot process, all we're doing here is saving is the original, and
making preparations for the new kernel to write to it's own, unique
kernel.h.
Once that is done, run lilo and reboot... At the lilo prompt, select
the new kernel/label and everything should seem as though it was all a
bad dream.... when you're comfortable with everything under the new
kernel you can go back and remove the old 2.2.16 image references from
lilo.conf. For the time being, leave the other files in /boot alone.
Good luck,
Jason L. [EMAIL PROTECTED]
------------------------------
From: [EMAIL PROTECTED] (Bob Hauck)
Subject: Re: KDE 2.1 or Gnome 1.4?
Reply-To: bobh = haucks dot org
Date: Sun, 08 Apr 2001 23:43:48 GMT
On Sun, 8 Apr 2001 20:39:56 +0200, controller <[EMAIL PROTECTED]> wrote:
>> I'm happy with KDE 2.1.1. It is very polished, fast enough (although
>> not as fast as blackbox), and the wife and kids use it happily.
> do you know by any chance which 'part' of KDE makes it slower? is it the K
> window manager?
It is my impression, not having done much testing, that kwin is a bit
slower than blackbox. The reason I think this is that KDE seems a tiny
bit faster with blackbox, even with all the desktop geegaws loaded. It
is not a huge difference, but noticeable sometimes, like on ancient
hardware or when using VNC.
The full KDE desktop with panel, root window icons, drag&drop support,
multimedia support, etc, also takes a lot more memory than a simple wm,
which makes a difference on lower-memory systems like my laptop (P-120
with 48 MB).
> currently I'm toying with the idea of installing windowmaker
> and adding the KDE panel to it....would that make sense in your opinion?
It oughta work. Works with blackbox, except that KDE doesn't recognize
the blackbox virtual desktops.
My current preference is to use the stock KDE setup by default except
for my old systems which run blackbox.
--
-| Bob Hauck
-| To Whom You Are Speaking
-| http://www.haucks.org/
------------------------------
From: [EMAIL PROTECTED] (Dances With Crows)
Crossposted-To: comp.os.linux.setup
Subject: Re: Two frustrating Samba problems...
Reply-To: [EMAIL PROTECTED]
Date: 09 Apr 2001 00:00:20 GMT
[nonexistent NGs removed]
On 08 Apr 2001 22:38:49 GMT, Hiawatha Bray staggered into the Black Sun
and said:
>First, how do I get my Windows box to see the files on my Linux
>machine? When I go to Network Neighborhood, I see the Linux computer,
>but when I click on the Icon for it, I get an Action Cancelled window.
>When I run net view in a DOS window, I get an Error 53 saying the
>computer can't find the machine. But when I do a generic net view
>command, to show all the boxes connected, the Linux box pops right up.
>I don 't get this. Do I need to set up shares for the Linux drives?
>If so, how?
Read the Samba documentation, or use Swat to set up shared directories.
A typical share looks like this within the smb.conf file:
[share]
comment = Linux share
path = /path/to/directory
writeable = yes
guest ok = yes
create mode = 775
Once you've edited smb.conf to your liking, killall -HUP smbd .
>My other question: How do I see the Windows shares on the Linux box?
>What's the Linux equivalent of Network Neighborhood? Thanks.
"smbclient -L $HOST" should display a list of the services on HOST. KDE
2.0 has something that is supposed to work like Nyetwork Neighborhood,
but it doesn't work AFAICT. The "map network drive" function in Doze is
not available to normal users under Linux; only root can mount SMB
filesystems *unless* /etc/fstab is correctly set up and the user doing
the mount owns the mountpoint.
For example, if there were a machine called BORG and a shared directory
on BORG called WIBBLE, /etc/fstab could contain:
//BORG/WIBBLE /mnt/wibble smbfs noauto,user,workgroup=WORKGROUP 0 0
and theoretically any user could mount this filesystem. However, if
user bob tries to mount this filesystem, smbmnt(8) checks /mnt/wibble to
see if bob owns the directory. If bob doesn't, then smbmnt exits with a
misleading error message.
I *think* the KDE Samba client gets around this mess by using smbclient
as the back end, but like I said before, I haven't been able to get it
to work right.
--
Matt G|There is no Darkness in Eternity/But only Light too dim for us to see
Brainbench MVP for Linux Admin / Workin' in a code mine, hittin' Ctrl-Alt
http://www.brainbench.com / Workin' in a code mine, whoops!
=============================/ I hit a seg fault....
------------------------------
** FOR YOUR REFERENCE **
The service address, to which questions about the list itself and requests
to be added to or deleted from it should be directed, is:
Internet: [EMAIL PROTECTED]
You can send mail to the entire list by posting to comp.os.linux.misc.
Linux may be obtained via one of these FTP sites:
ftp.funet.fi pub/Linux
tsx-11.mit.edu pub/linux
sunsite.unc.edu pub/Linux
End of Linux-Misc Digest
******************************
