On Wednesday 03 July 2002 03:38, Michael wrote:
> I tried to visit this site.
> The result upset me so much i sent them this.
I sent the letter below, and I encourage everyone on the list to send a
Subject: Create a Real Web Site Please
From: Bryan S. Tyson <bryantyson(a)earthlink.net>
When attempting to view your site using Konqueror 2.2.1 and Mozilla
0.9.4, both Linux web browsers, I was curtly informed that my browser
is "incompatible." Your site, sir, is what is "incompatible." Stick
with established standards and real html, not Microsoft proprietary
Powered by SuSE Linux 7.3 Professional
KDE 2.2.1 KMail 1.3.1
This is a Microsoft-free computer
Bryan S. Tyson
We have an winNT server and need to auto mount a shared folder as if it were a
windose mapped drive Z: on SuSE8
Could someone please explain how to do this and how to make sure it is set-up
for every user everytime the system is booted.
New to Linux
Reading some mails on the GIMP mail list, I ran across the procedure
to install some more fonts for not only Gimp, but the system and
StarOffice to use also. Well, I installed the fonts, went to the
shell and issued the command xset fp+ <font directory> and then the
rehash command and all fonts are there! Ok, that went well, but each
time I restart the system, I have to do it all over again? Is there
a way to make it permanent and read the new fonts like it does the
ones the system installs or is that a no-no?
end of line
xset fp+ <new font directory>
xset fp rehash
---KMail 1.2--- SuSE Linux v7.2---
Registered Linux User #225206
/tracerb(a)sprintmail.com/ *Magic Page Products*
*Team Amiga* http://home.sprintmail.com/~tracerb
I don't remember seeing this problem on the list.
KMail print on screen is clear and most letters are
separated. When I print out a mail, some letters,
particularly the "t", the "si" and the "sk" combinations
are scrunched together with adjoining letters.
I am printing to an HP 2200D laserjet. The
typeface on screen (and on paper) is a
sans-serif font. Even on screen, it is slightly
scrunched in spots. "ri" and "ti" and "tt" and "th" are
too close together.
While attempting to stop a video playing on Macro Media Flash Player 7,
I managed to lock out everything. I could not move the mouse cursor,
the arrow keys and the rest of the kb didn't work, ctl-alt-del did nothing.
None of the function keys did anything. (The video was something downloaded
from the 'net via Firefox.) I wound up pulling the big switch, as us hams
like to say. Is there anything else I could have done?
I'm trying to put Linux to practical use, and this is the first time I've seen
10.0 crash, so it's good, but not fool-proof. (If something can be broken,
this fool will break it!)
I have a fileserver running SuSE 8.0 with 2 IDE Drives and a
SCSI RAID (RAID5). The system boots up to one of the IDE drives,
and the SCSI RAID drive runs as a mounted filesystem (/dev/md0).
(all filesystems are REISERFS).
The SCSI RAID drive has crashed (won't boot up), and I need to
recover it (repair it, through some utility).
The software does not seem to want to mount the disks, even though
the SCSI BIOS (Adaptec) recognizes the disks, and they are listed as
I tried to repair the disk(s) (with reiserfsck), but it produced an
reiserfs_open: bread failed reading block 2
reiserfs_open: bread failed reading block 16
reiserfs_open: neither new nor old reiserfs form found on /dev/md0
The literature suggested that this error message is hardware related
(either a disk is physically damaged, or maybe the RAID isn't
recognized), but again, the disks are recognized (and therefore,
so is the SCSI Card).
I tried to boot up with SuSE CD 1 in Recovery mode, but not sure
what to do there (i.e., after the root prompt - just run reiserfsck?).
Literature suggests there are plenty of tools to handle disk recovery,
and especially RAID support, I can't find reference to them
The installation of the RAID was trivial (using the YAST2
partitioning GUI window on startup), and yet recovery seems to be a
mystery. This can't be right.
Does anyone know where there are "decent" and "usable" recovery tools?
OR ... does anyone know what "specifically" to do in this case? Can
I re-partition without formatting, and recover the existing data?
Any help is appreciated - I'm sure I'm missing something "obvious", but
can't find "obviously" what to do in the literature, docs, etc.
School of Engineering and Applied Science
University of California, Los Angeles
El 2003-07-09 a las 13:37, C Hamel escribió:
(You forgot to post to the list)
> I am afraid I don't even know how to ask a question, at this point, but I'll
> make an attempt: Exactly where should this ntp thing be called to set the
> clock ...or(/and) by what process?
It is a very proper question :-)
Well, it depends. There are two ways. If your computer is up all the time,
and has a permanent network connection, you can use the ntpd daemon, which
polls a set of servers about once a minute, and _very_ slowly adjusts the
system clock; it can even note the systematic error or drift, and take
that in to account to discipline the system clock.
There are many options available for the daemon: see full doc in:
Or, you may have a temporary network connection, like I do; I will explain
this in some detail.
We can adjust the clock to "internet" time, once, sometime after we
connect to internet. This, apparently, can be done with the daemon, using
some option I don't fully understand. Or we can use ntpdate - a program
which is to disappear some time in the future, but that I use, and SuSE
uses as well in its own script.
For this, we can simply call "/etc/init.d/xntpd ntptimeset" - and assume
that when "ntpdate" finally disappears SuSE will adjust the script
Of course, /etc/ntp.conf has to be configured; at least, it must have a
list of servers:
This is sufficient for "xntpd ntptimeset" to work; just leave the rest of
the config at the default values. If you want to use the daemon, then I'm
not the person to ask :-)
Ok, so when is the appropriate time to make this time adjust? Well,
ideally, during system boot-up, after network connection is established.
This is done properly by the service xntpd, if enabled. The SuSE script
"/etc/init.d/xntpd start" does first a clock set using ntpdate, if the
variable XNTPD_INITIAL_NTPDATE is set to "AUTO". Then, it starts the
daemon to keep time synchronized.
And, if our network connection is not permanent? Then, the script
"/etc/ppp/poll.tcpip", which is called from "/etc/ppp/ip-up", will adjust
the clock first thing: assuming we have some servers configured, it will
be done every time we connect to internet with the modem. I do it
differently, only once every five times, and I also update the hwclock.
The danger of this method is that the clock might suddenly go forward or
backward a bit (seconds or hours, it depends): not very nice on a *nix
system, but we can not avoid it.
More details to be aware of: what happens to the hardware or CMOS clock?
Well, the script "/etc/init.d/boot.clock" (read it, it is documented) does
this sequence of things (using the command "hwclock") before starting
- Create if it doesn't exist, the file "/etc/adjtime"
- Adjust hardware clock (CMOS) for known drift during the time the
computer has been off; this depends on the previous file to work.
- Copy CMOS clock (hardware) to system time (CPU and OS maintained).
After this, the system goes fully up, and maybe, the clock is adjusted
from the internet or by hand (danger!). But (and this is very different
than windows) the CPU maintained clock has to be copied back to the CMOS,
because the kernel doesn't do it. SuSE does it in the script
"/etc/init.d/halt" that copies system time to hardware time just before
power off. Me, I prefer to do it just after I adjust to network time,
inside "ip-up.local", like this:
More things to be aware of: a common mistake is manually adjusting the
system clock from kde control center (for example), and not updating the
hwclock at the same time: the drift adjust algorithm of hwclock thinks
that the CMOS clock is fast or slow by the same amount you adjusted the
clock, and the next boot it will adjust the time by several hours... The
solution is to delete "/etc/adjtime" and call "/sbin/hwclock --systohc"
just then (documented on the SuSE sdb).
Well, this has been enough chatter on my part; let's hope I didn't make
many mistakes :-)
I am converting one of our Domino servers fro NT4 to SuSE 8.2.
Is there any way to add a secondary IP to the network card? I used to have
such a setup for the current NT box and eve tried this config with
Mandrake but thi sdoes not seem to be possible with YAST2.
Any idea anybody?
I'dd like to know what the following files in the directory /boot are about.
Can anyone give me a clue or point me to some documentation?
Thanks in advance,
This email is confidential and intended solely for the use of
the individual to whom it is adressed. Any views or opinions
presented are solely those of the author and do do not
necessarily represent those of the Azlan Holdings bv and/or
subsidairy. If you are not the intended recipient, be advised
that you have received this email in error and that any use,
dissemination, forwarding, printing or copying of this email
is strictly prohibited
If you have received this email in error please notify
Azlan Holdings MIS Helpdesk by telephone on
+31 (0) 79 3443200.
To unsubscribe send e-mail to suse-linux-e-unsubscribe(a)suse.com
For additional commands send e-mail to suse-linux-e-help(a)suse.com
Also check the FAQ at http://www.suse.com/support/faq
We received a copy of 9.1 today at work and I have installed this on three
machines with dissapointing results.
The first machine was an IBM Thinkpad R40 with a Centino 1600 CPU. This
machine worked fine and the performance was great.
The second and third machines were unusable, KDE takes serveral minutes to
start, attempting to start YAST for instance will take about a minute for the
SU box to appear and then another minute for YAST to load. I get similar
results for all applications I have tried, in all instances the system
performs like a P100 with very little RAM.
The machines that run slowly are both Athlon XP based machines, one being an
Athlon XP 2400 with 1GB of DDR RAM on an ECS Elite motherboard.
The second machine is an XP2000 with 512MB of PC3200 RAM on a PCChips
I have applied all the updates with no effect.
Any ideas would be appreciated, I've had to switch back to 9.0 as the whole
9.1 experience is unuseable has anybody got any ideas?
Registered Linux user number 330730
Internet SIP Phone: 1-747-244-2699