Pages

Search

Changing the start end end date of the daylight saving time - Forums Linux

Changing the start end end date of the daylight saving time - Forums Linux

Changing the start end end date of the daylight saving time

Posted: 28 Feb 2006 03:12 AM PST

On Tue, 28 Feb 2006, in the Usenet newsgroup comp.os.linux.setup, in article
<com>, Nico Kadel-Garcia wrote:

"MOSHEMOSHE" <com> wrote:
 

Reboot - no. The few processes that may use $TZ would be restarted, but
most processes merely ask the kernel what time it is, and it handles
the time zone changes without fuss ASSUMING you set it up with the right
information to start with, and kept that information up to date. The
"current" timezone data is at ftp://elsie.nci.nih.gov/pub/tzdata2006b.tar.gz

-rw-r--r-- 1 8800 0 149555 Feb 20 15:08 tzdata2006b.tar.gz

A number of changes in Canada and Indiana, and relatively minor stuff in
Antarctica, Asia, the mid-East, and Brazil, but that's it. Your distribution
should have an updated timezone package which is more suited to your system.
 

Except that ntp data is in UTC, and it has no concept of local timezones.
The O/P asked the same question in comp.protocols.time.ntp and
comp.unix.admin under the handle "kavsha" <com>.
 

Why would there be a three hour jump? That infers that the system wasn't
configured right in the first place. If you are physically moving the
system across timezones, then keep the system on UTC.
 

Know the feeling. We keep all of our servers on UTC simply because they
can be accessed from a lot of places. Our workstations _generally_ stay
on local time, whatever that is.

Old guy

Ubuntu-Windows

Posted: 27 Feb 2006 08:37 PM PST

com a écrit : 

OK, you have four partitions :
windows
linux
linux swap
recovery
You will get more information about your partitions by typing Douglas
Mayne's commande :
# fdisk -l /dev/hda

Can you mount your windows partition to know if your windows system has
been altered ? You can do this by the command as root
# mkdir /mnt/windows
# mount -t ntfs /dev/hda1 /mnt/windows

and then

# ls /mnt/windows

and you will see the content of your windows partition if it hasn't be
altered.

Panels frame in kcontrol

Posted: 27 Feb 2006 07:12 AM PST


Bob Tennent wrote: 
 

For me here on Deb 3.1r1 (Sarge) using KDE - it's
Right click blank Panel area - choose Configure Panel >> Layout >>
Appearance
"Enable Icon Zooming" -- right alongside "Tool Tips" (KDE 3.3.2)
(I guess I should've known what you meant when you used the word
"huge"...lol) -- Admittedly, I didn't realize that one could configure
'those' panel options separately from the Desktop - I'm still finding
diff configuration options, buried all over in place, using
KDE...Fonts; for example comes to mind.(styles and sizes), especially
when using Konquerer as both a file manager and a web browser.
 

The only thing that comes to mind (besides corruption) is that the User
does not have the proper permissions to change/alter it. Look at it
when logged in as root. Possible ? I had issues while I was using xdm
as the DM, instead of kdm -- I experienced some funky stuff like what
you are - plus some (most) setting changes wouldn't stick.

FWIW - I just found yet *another* _Enable tooltips_ checkbox in;
K Control Center >> Appearnace and Themes >> Style

run a perl script during system boot

Posted: 27 Feb 2006 01:11 AM PST

On 2006-02-28, Chris F.A. Johnson <com> wrote: 

Just in case Chris doesn't get to it before I do, the octothorpe is #,
not $. Adding $ at the beginning of a line in rc.local may do some very
bizarre things. :)

--keith

--
san-francisco.ca.us
(try just my userid to email me)
AOLSFAQ=http://wombat.san-francisco.ca.us/cgi-bin/fom
see X- headers for PGP signature information

Kernel upgrade 2.4 -> 2.6, makes system very slow on laptop with 1GB of memory: BIOS caching bug

Posted: 26 Feb 2006 07:06 PM PST

> Now for my system, I need them as they are. If I turn off the 

I guess if you have more than 4 Gigs of RAM in your system my comments
are not really useful... They are also irrelevant if your bios does not
have that caching bug i mentioned...

best,

mark

linux 2.6.5.1 [fedora core 2] custom build kernel reload

Posted: 25 Feb 2006 12:10 PM PST

Hi Lenard,

Thanks for the reply.
I tried the steps you mentioned but it still hangs when Grub loads
kernel [Uncompressing].
So I was curious whether it is because of processor type.

Processor type shows Pentium III in the bios, but the linux running on
machine shows
I686 now which option should I choose during the config. Is this the
cause for m/c hang.

Thanks,
Vinod.

sftp syantax to copy file from box A to box B

Posted: 25 Feb 2006 05:38 AM PST

On 25 Feb 2006 05:38:55 -0800, anymouse wrote: 

Next login to sftp try
help
 

So, you want to
get filename_here
 

No. Go back to
man sftp
and read the INTERACTIVE COMMANDS section.
 

Once you are logged in ls should work.
 

Check the INTERACTIVE COMMANDS for get/put/mget/mput
 

Hmmm, guessing, boxb does not know the node.domain.boxa
Try using sftp anymouse@boxa_ip_address_here
Then after entering anymouse's password on boxa

get pine-4.64-1.i386.rpm
bye

Intel PRO / Wireless 2200 BG listed as ethernet

Posted: 25 Feb 2006 02:11 AM PST

> Wireless IS ethernet.

Yes, of course, you're right. Sorry for the confusion, I meant a
hard-wired ethernet cable.

DosBox mouse cursor vanishes (Debian Etch)

Posted: 25 Feb 2006 01:12 AM PST

com wrote:
 

Yeah, I've tried to register twice, but it's not sending me the
confirmation emails. There seems to be plenty of activity, so maybe
it'll get sorted soon.
 

Hmmm. If it's so ancient, why does nobody release a newer version? Even
a public beta would make it into Debian Testing and be installable as a
regular package.

Still, might try the CVS thing.

CC

Linux Mandrake> VNC server settings?

Posted: 24 Feb 2006 04:54 AM PST

CBFalconer wrote: 

Because the people who have been in his newsgroups a while have killfiled
him.

2.4.30 & 2.4.32 kernel comple error

Posted: 23 Feb 2006 09:25 PM PST

Harmon Seaver wrote:
 

Ahh, it's a 486 *laptop*. Definitely time to stuff the hard drive in another
box and do the install there, using i386 software instead of i686 software.
Do you really need this old beater to stay alive, or would it be easier to
upgrade your way out of the difficulties?

Ubuntu & Partitions - Confused !!

Posted: 23 Feb 2006 12:55 PM PST


Douglas Mayne wrote: 

hi;

FWIW;
start menu | run DISKMGMT.msc

(or: for one level higher)

start menu | run COMPMGMT.msc

just trying to help shorten those l-o-n-g nasty directions to get to a
silly GUI applet :-)
(basically, on 2000 and XPoop - should be the same - though XPoop Pro
has many more choices).
 

Linux experts needed

Posted: 23 Feb 2006 11:35 AM PST


<com> wrote in message
news:googlegroups.com... 

Why would we replace Usenet and Google Groups with yet another advertising
driven website, especially written by someone who multi-posts and doesn't
know how to write URL's in email? And especially when the "top questions"
are distribution dependent and answered extensively on this newsgroup?

vsftpd setup question

Posted: 22 Feb 2006 11:31 PM PST

On Thu, 23 Feb 2006 08:31:50 +0100, Frank wrote:
 

Is /bin/false listed in /etc/shells ?

--
-Menno.

firefox onto zipslack

Posted: 22 Feb 2006 06:08 PM PST

Buzzard schrieb:
 

Maybe dillo is an intermediate solution.

---<(kaimartin)>---
--
Kai-Martin Knaak
http://lilalaser.dyndns.org/blog

Grub boots from command line but not menu

Posted: 22 Feb 2006 05:46 PM PST

On Sat, 25 Feb 2006 21:43:58 -0800, iforone wrote:
 

That's a nice variant, kind of like, "read the _fine_ manual."
WAG and SWAG:
http://www.ceri.com/q_v6n5q4.htm
 
Note: Try again with post. My adjacent response was incomplete. There is
some sort of "hair trigger" on pan's send button ;-)

Note: comment inline.

I did some testing, with results which confirm your experience. Grub
could read all of the known filesystems on the disc as soon as stage2 was
loaded. The results of my tests show that if grub menu is displayed, then
it doesn't require anything else to read the filesystems for which it has
been compiled. Also, it doesn't appear to reload stage2 when root
is issued within a grub menu.lst stanza. It appears that stage2 is the
superset of all the filesystems it knows how to read, established when
stage2 is compiled. As you thought, grub proved to be even more flexible
than I had guessed. But it was also more limited with chainloader than I
thought.

More Information

I could not duplicate the experience of the OP. grub would not
"forget" how to load a filesystem once stage2 is loaded. I tested
grub, version 0.97. The only error I could generate was if stage2
could not be loaded at all. That is, if I removed stage2 from the
grub directory, "grub error 15" is reported. I also found some problems
with grub installed at the partition are detailed below.

Specific Test Information

Several tests were performed separately using separate filesystems and
modes of operation. I tested ext2, XFS, JFS, and ReiserFS with Grub being
loaded directly from a hard disk and from a CD-R with the grub loader. I
used my project, a Slackware-based LiveCD as the base platform for
testing:
http://www.xmission.com/~ddmayne2/10.2-live/

I was using a VMWare virtual machine as the "hardware" platform.

1. A Basic boot test: this is what grub should do as a minimum.
Grub is installed on the partition, so that the loader can be setup:

# grub
grub> root (hd0,4)
grub> setup (hd0)
grub> quit

All of my tests were successful, with the exception of JFS.

Again, at this point grub can read all of the other partition types that
it knows about without extra help. Therefore, commands like these succeed
(either from menu.lst or the boot shell):

grub> kernel (hd0,4)/boot/vmlinuz ro root=/dev/hda5

grub> kernel (hd0,5)/boot/vmlinuz ro root=/dev/hda5

Weird result with JFS

JFS/Grub would hang before showing the menu when loaded directly from the
hard disk. But, this is strange, when booting from CD-R, and using
chainloader from the boot shell (as shown below) works fine- the menu
loads, and bootup proceeds normally:

grub> root (hd0)
grub> chainloader +1
grub> boot

This error could have been due to a mistake I made, but I tried it
twice with the same results.

2. Tests with chainloader. (And a big word of caution.)

Some of the ways I had envisioned the chainloader command do not work.
For example, it is possible to link to a Windows NTFS partition with this
syntax:

grub> rootnoverify (hd0,0)
grub> makeactive
grub> chainloader +1
grub> boot

I didn't test the above example, nor chainloading to lilo on the
partition. Chainloading to lilo may be tested at a later date.

This syntax also works with a GNU/Linux partitions which are
formatted using _ext2_. This assumes grub has been setup properly at the
target partition, using syntax similar to this:

grub> root (hd0,4)
grub> setup (hd0,4)

Then, from the grub boot shell, issue these command:

grub> rootnoverify (hd0,4)
grub> chainloader +1
grub> boot

This causes grub's menu to be displayed, at least with ext2.

Other filesystems

But, this procedure _does not_ work with the more complex journaled
filesystems, XFS, JFS, ReiserFS. In fact, if the "setup" commands are
issued on an XFS partition, the partition is destroyed. Grub reports no
errors when installing on XFS, but the partition will fail to mount.
Also, grub "setup" on ReiserFS report an error. To emphasize, this is the
case where grub is installed on the partition, not loading through the
MBR. That generally works- as shown in my test 1 (above.) When I checked
grub's documentation, it reports that it can be installed on the
partitions using FFS (?) or ReiserFS:
http://www.gnu.org/software/grub/manual/html_node/Bootstrap-tricks.html#Bootstrap-tricks

That is not what I see in reality with ReiserFS, however. Perhaps,
grub is not intended to be installed on the partition (BPB) of advanced
filesystems. The least it could do is to "do no harm." It should really
identify XFS, and refuse to modify the BPB. But for consistency sake, it
should be possible to install the loader this way.

Conclusion

Test, don't assume something works by extrapolation. The failure of XFS
and grub really surprised me.

I took some screenshots of my tests. Perhaps, I'll try to organize and
post them.

imotgm, thanks for your input. Your "reported working" experience was
helpful for me to investigate further and to learn more about grub.

--
Douglas Mayne

Changing root filesystem from CD to USB drive

Posted: 22 Feb 2006 03:24 PM PST

On Wed, 22 Feb 2006 17:02:12 -0800, dmly.usa wrote:
 
I thought I did, but maybe we're having trouble communicating. Please,
reread my last post and see if you can tell where we went separate
directions.

Is anything installed on the USB disc now? If not, is part of your plan
to use it as the root filesystem for a the GNU/Linux distribution of your
choice?

BTW, you need to improve your posting style. Apparently, you are
posting from google groups, and their default setting does not include any
context of the thread. This is bad form. Remember, this is Usenet not
Google Groups.

--
Douglas Mayne

Setting up a Directory that group of people could get to

Posted: 22 Feb 2006 04:52 AM PST

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

co.uk wrote: 

You'd chmod the directory to prevent outsiders (users other than the
owning group) from gaining access to the contents of the directory. You
may also want to remove write access to the group to prevent
unauthorized deletion of files in the directory.

You'd have to chmod all the files in the directory as well, to prevent
write access to each file.

HTH

- --

Lew Pitcher, IT Specialist, Corporate Technology Solutions,
Enterprise Technology Solutions, TD Bank Financial Group

(Opinions expressed here are my own, not my employer's)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFD/Hb0agVFX4UWr64RAhCRAKDE0v3ViT53gyl0Gc4a3rc5iDpzdQC fZhU8
AU0LwQuqIuFfDILRyAWdOUg=
=nrPF
-----END PGP SIGNATURE-----

Yum package conflict: yum-2.4.1-1.fc4 and medley-package-config-102-1.rhfc4.at

Posted: 21 Feb 2006 06:08 PM PST

Ron Albright wrote: 

This is actually not necessarily evil: bugzilla, for example, has a big
stack of Perl dependencies that are quite harmless to the rest of your
system.
 

A small one. But for the "fedora-release" package, the related dependencies
should be minor, and even if you break the dependencies on that one it's not
evil. And this "rpm -Uvh --oldpkgs" trick will let you revert packages one
or two at a time, or in small sets of related packages.
 

Etc. Brother, you need a local mirror to deal with all of this: It should be
possible to write a small script to go through the list of "extra" packages,
and install them from a local mirror. Just make sure to be careful with
packages that have i386 and i686 versions.

Here is my tool for building a local mirror, which may help:

#!/bin/sh
#
#
#

progname=`basename $0`
LOCKDIR=/var/run/rsync
LOCKFILE=$LOCKDIR/${progname}.pid

RSYNC="rsync"
RSYNC="$RSYNC -aH"
RSYNC="$RSYNC -v"
RSYNC="$RSYNC --delete-after"
#RSYNC="$RSYNC --delete-excluded"
#RSYNC="$RSYNC --bwlimit=50"

if [ $# -gt 1 ]; then
echo "Usage: $0 [ --dry-run ]"
exit 1
elif [ $# -eq 1 ]; then
if [ "$1" = "--dry-run" ]; then
RSYNC="$RSYNC --dry-run"
else
echo "Usage: $0 [ --dry-run ]"
exit 1
fi
else
if [ -f $LOCKFILE ]; then
# Stolen from /etc/init.d/functions, check for lockfile
read line < $LOCKFILE
for p in $line ; do
[ -z "${p//[0-9]/}" -a -d "proc$p" ] && \
pid="$pid $p" && \
echo "$progname is already running, exiting" && \
exit 1
done
echo "Flushing old lockfile $LOCKFILE"
/bin/rm -f $LOCKFILE
echo $$ > $LOCKFILE || exit 1
fi
echo $$ > $LOCKFILE || exit 1
trap "/bin/rm -f $LOCKFILE" EXIT
fi

MIRRORDIR=/y/linux/fedora/core
if [ ! -d $MIRRORDIR/. ]; then
echo "$MIRRORDIR/. is not a directory, exiting"
exit 1
fi

#RSYNCHOST="rsync://mirror.hiwaay.net/fedora-linux-core"
#RSYNCHOST="rsync://fedora.server4you.net/fedora"
#RSYNCHOST="rsync://linux.nssl.noaa.gov/fedora/core"
RSYNCHOST="rsync://mirror.mcs.anl.gov/fedora-linux-core"
RSYNCHOST="rsync://mirror.hiwaay.net/fedora-linux-core"

#RSYNCDIRS="$RSYNCDIRS 2/i386/os/"
#RSYNCDIRS="$RSYNCDIRS 3/i386/os/"
#RSYNCDIRS="$RSYNCDIRS 4/i386/os/"
#RSYNCDIRS="$RSYNCDIRS updates/"
RSYNCDIRS="$RSYNCDIRS ./"

#EXCLUDEARGS="$EXCLUDEARGS --exclude=SRPMS"
#EXCLUDEARGS="$EXCLUDEARGS --exclude=iso"

EXCLUDEARGS="$EXCLUDEARGS --exclude=ppc"
EXCLUDEARGS="$EXCLUDEARGS --exclude=x86_64"
EXCLUDEARGS="$EXCLUDEARGS --exclude=debug"

EXCLUDEARGS="$EXCLUDEARGS --exclude=1"
#EXCLUDEARGS="$EXCLUDEARGS --exclude=2"
#EXCLUDEARGS="$EXCLUDEARGS --exclude=3"
#EXCLUDEARGS="$EXCLUDEARGS --exclude=4"

EXCLUDEARGS="$EXCLUDEARGS --exclude=testing"
# test is downloaded in rsync-fedora-test.sh
EXCLUDEARGS="$EXCLUDEARGS --exclude=test"
EXCLUDEARGS="$EXCLUDEARGS --exclude=development"

EXCLUDEARGS="$EXCLUDEARGS --exclude=FC2-i386-DVD.iso"
#EXCLUDEARGS="$EXCLUDEARGS --exclude=FC2-i386-disc1.iso"
#EXCLUDEARGS="$EXCLUDEARGS --exclude=FC2-i386-disc2.iso"
#EXCLUDEARGS="$EXCLUDEARGS --exclude=FC2-i386-disc3.iso"
#EXCLUDEARGS="$EXCLUDEARGS --exclude=FC2-i386-disc4.iso"
EXCLUDEARGS="$EXCLUDEARGS --exclude=FC2-i386-SRPMS-disc1.iso"
EXCLUDEARGS="$EXCLUDEARGS --exclude=FC2-i386-SRPMS-disc2.iso"
EXCLUDEARGS="$EXCLUDEARGS --exclude=FC2-i386-SRPMS-disc3.iso"
EXCLUDEARGS="$EXCLUDEARGS --exclude=FC2-i386-SRPMS-disc4.iso"

EXCLUDEARGS="$EXCLUDEARGS --exclude=FC3-i386-DVD.iso"
#EXCLUDEARGS="$EXCLUDEARGS --exclude=FC3-i386-disc1.iso"
#EXCLUDEARGS="$EXCLUDEARGS --exclude=FC3-i386-disc2.iso"
#EXCLUDEARGS="$EXCLUDEARGS --exclude=FC3-i386-disc3.iso"
#EXCLUDEARGS="$EXCLUDEARGS --exclude=FC3-i386-disc4.iso"
EXCLUDEARGS="$EXCLUDEARGS --exclude=FC3-i386-SRPMS-disc1.iso"
EXCLUDEARGS="$EXCLUDEARGS --exclude=FC3-i386-SRPMS-disc2.iso"
EXCLUDEARGS="$EXCLUDEARGS --exclude=FC3-i386-SRPMS-disc3.iso"
EXCLUDEARGS="$EXCLUDEARGS --exclude=FC3-i386-SRPMS-disc4.iso"

#EXCLUDEARGS="$EXCLUDEARGS --exclude=FC4-i386-DVD.iso"
#EXCLUDEARGS="$EXCLUDEARGS --exclude=FC4-i386-disc1.iso"
#EXCLUDEARGS="$EXCLUDEARGS --exclude=FC4-i386-disc2.iso"
#EXCLUDEARGS="$EXCLUDEARGS --exclude=FC4-i386-disc3.iso"
#EXCLUDEARGS="$EXCLUDEARGS --exclude=FC4-i386-disc4.iso"
EXCLUDEARGS="$EXCLUDEARGS --exclude=FC4-i386-SRPMS-disc1.iso"
EXCLUDEARGS="$EXCLUDEARGS --exclude=FC4-i386-SRPMS-disc2.iso"
EXCLUDEARGS="$EXCLUDEARGS --exclude=FC4-i386-SRPMS-disc3.iso"
EXCLUDEARGS="$EXCLUDEARGS --exclude=FC4-i386-SRPMS-disc4.iso"

for rsyncdir in $RSYNCDIRS; do
echo "Getting $RSYNCHOST/$rsyncdir"
$RSYNC $EXCLUDEARGS $RSYNCHOST/$rsyncdir $MIRRORDIR/$rsyncdir
done

Setting up Ftp on Linux server

Posted: 21 Feb 2006 01:17 PM PST

Thanks everyone! I have used ssh and winscp.

How to include - in the source RPM - all the files listed in %files ?

Posted: 20 Feb 2006 11:32 PM PST

Thanks Laurenz
Bye,
Ron.

HP Tape Driver

Posted: 20 Feb 2006 11:08 PM PST

In article <P%yKf.2412$news.pas.earthlink.net>,
Levi Gruber <net> wrote:
:Does anyone know where I might find a linux driver for an HP SureStore
:DAT24(internal)? Model number is C1537A. I looked on DriverGuide.com, but no
:luck. It seems it is too old for HP to still be providing support.

Just connect the drive to your SCSI adapter. Linux will recognize it
as a generic SCSI tape drive. You'll want to have the "mt-st" package
installed to provide a command-line interface for tape positioning,
rewinding, etc.

--
Bob Nichols AT comcast.net I am "RNichols42"

logging into root of remote machine

Posted: 20 Feb 2006 09:19 PM PST

> You should log in as a regular user and su or sudo to root.

He has a good point. That is a security risk, logging in to a machine
as root remotely. Unless, this system is on a secure local network. Are
you still having trouble? Is there anything we can help with?

Slackware Server ISP change

Posted: 19 Feb 2006 11:27 PM PST

Yes. Thank you to all, i managed to fix it, and now it works perfectly.

I never said it was a Linux problem, it was my problem that i did not
know linux.

Anyway thanx everybody!!!

Problem setting up dual boot Suse10/WinXP

Posted: 19 Feb 2006 10:16 PM PST

On Mon, 20 Feb 2006 11:29:02 +0000, imotgm wrote:
 

That did the trick. Thank you very much.