Pages

Search

Screensaver password - Forums Linux

Screensaver password - Forums Linux

Screensaver password

Posted: 11 Jul 2006 10:24 AM PDT

Maurice Batey wrote:
 

Look a little harder. Try:
YaST->User Management->Expert Options->Login Settings

--
Larry Bristol --- The Double Luck
http://www.doubleluck.com

Problem: no parallel in /dev

Posted: 10 Jul 2006 03:47 PM PDT

Unruh napisal(a): 

It's ridiculous, when in dmesg I have parport0 and in /dev I do not,
but that's the truth.

dvdrw kmsg mouse ram15 sda3 tty0 tty22
tty36 tty5 tty63 vcs5
... fb log mptctl ram2 sda5 tty1 tty23
tty37 tty50 tty7 vcs6
..udev fb0 loop null ram3 sda6 tty10 tty24
tty38 tty51 tty8 vcs7
adsp fbsplash loop0 nvram ram4 sda7 tty11 tty25
tty39 tty52 tty9 vcsa
audio fd loop1 port ram5 sda8 tty12 tty26
tty4 tty53 ttyS0 vcsa1
bus fd0 loop2 psaux ram6 sequencer tty13 tty27
tty40 tty54 ttyS1 vcsa12
cdrom floppy loop3 ptmx ram7 sequencer2 tty14 tty28
tty41 tty55 ttyS2 vcsa2
cdrom1 full loop4 pts ram8 shm tty15 tty29
tty42 tty56 ttyS3 vcsa3
cdrw gpmctl loop5 ram0 ram9 snd tty16 tty3
tty43 tty57 urandom vcsa4
console hda loop6 ram1 random sound tty17 tty30
tty44 tty58 vcs vcsa5
core hdb loop7 ram10 rd stderr tty18 tty31
tty45 tty59 vcs1 vcsa6
disk hpet mapper ram11 rtc stdin tty19 tty32
tty46 tty6 vcs12 vcsa7
dri initctl mem ram12 sda stdout tty2 tty33
tty47 tty60 vcs2 zero
dsp input misc ram13 sda1 tts tty20 tty34
tty48 tty61 vcs3
dvd kmem mixer ram14 sda2 tty tty21 tty35
tty49 tty62 vcs4

This is my /dev, sorry for lack of text formatting.

GRUB problems

Posted: 10 Jul 2006 10:12 AM PDT

Everything is golden now. For about a day, GRUB was booting to the
grub> prompt and then I had to tell it to boot with the kernel. After
figuring out that grub was looking in the wrong place for the grub.conf
file, I was able to correct the issues entirely. We now have a
physical server free for use in other tasks. Thanks everyone for the
help!

unresolved symbols and other problems

Posted: 10 Jul 2006 06:17 AM PDT

chuckcar wrote: 
Well I don't have time to do any of this just now as I have to catch a boat to the
mainland and will be away for 1 week but just to put you in the picture :

Initially I did not compile the kernel so I did not cause the problem by doing so.

This was the problem from a fresh install with no attempt to alter anything.

The mouse did not work for either kernel until I ran xorgconfig a few times and eventually
chose PS/2 for the mouse type. Then it worked with the 2.4.29 kernel.
Thanks,
Norm

How can I configure custom memory size for video?

Posted: 09 Jul 2006 01:30 PM PDT

Nico Kadel-Garcia wrote: 

Actually these are two excellent suggestions. It turns out I had
already
cached some other (old, but not quite as bad) video cards in my parts
bin
intending that some day I would try swapping one of them in. Too bad I
didn't write THAT in my system administration notes!

So I swapped in a board with 8MB already on it (which was more than
the old card had), and can get a halfway decent screen resolution.
I did have to edit xorg.conf anyway, but "man xorg.conf" is quite
adequate for editing color depths and video modes. So much easier
than trying to make the old video card do what it was never designed
for.

By the way, I also looked at my XF86Config file from my Fedora Core 2
installation, but I'm not sure I'd now recommend what I found there.

Oddly, system-config-display still shows only 640x480 and 800x600
modes, although the display actually is 1024x768 at this moment
(verified by a screen capture). But that problem can wait.

David Karr

online linux man page

Posted: 08 Jul 2006 07:20 PM PDT

iforone wrote:
 

Before I said "it does not work" I said "Unless I have
missed something".

--

Dan C. Gets caught apparently Plagiarizing:
Message ID: <sierrandays.org>
Yeah, this is the type critical of me!

WinXP dual boot with non-defragmented disk?

Posted: 08 Jul 2006 02:52 PM PDT


chuckcar wrote: 
 
 

No I'm not...and I made very clear the differences in my earlier posts.

Have you looked at the Diskeeper documentation atleast ??

Also note;
NTFS can be installed many ways -- and if the person doing the install
uses;

A: an image of a previous install (ghost type app/utility)
B: installed using the NTFS utils "oFormat" and the like...

There's the chance that the Boot sector (and various other Meta-Data
files (IIRC; $BITMAP, $MFT, etc)) can be stored "anywhere" on the HDD
(laced throughout). This is a likely occurence anyway, but even more-so
if one used a PXE type setup (option B above). Certain blocks of data
may become 'locked' and broken up into pieces. But, either way, the
swapfile can always be forced to the outer-most blocks.

I am no NTFS guru-type, and I could be mistaken about certain explicit
details.

YMMV

Regards

Cut down Linux (Debian)

Posted: 07 Jul 2006 03:05 PM PDT

 

Thanks for the heads up!

Mark.

ubuntu installation + stupidity cost me data

Posted: 07 Jul 2006 12:33 PM PDT

com wrote in
news:googlegroups.com:
 

First thing to try is doing and fdisk/mbr and then booting to linux with
a cd to see what partitions are there and try mounting them. You then
might try to copy any important data to a linux partition and go from
there. Beyond that, you'd have to check the correlation between the fats
and the files themselves to see what's scrawed. If you don't know what
that means, don't do it and stop there maybe try doing a scandisk
*without* fixxing errors just so you see what and where they are copying
all it tells you down.

--
(setq (chuck nil) car(chuck) )

Sometimes eth0 & eth1 swap in Fedora

Posted: 06 Jul 2006 01:53 PM PDT

Allen Kistler wrote:
 

Coming late into this thread I would like to add this to the discussion.
If it is not relevant the please disregard.


7.4.3.7. Device naming order changes randomly after rebooting

This is due to the fact that Udev, by design, handles uevents and loads
modules in parallel, and thus in an unpredictable order. This will never
be “fixed”. You should not rely upon the kernel device names being stable.
Instead, create your own rules that make symlinks with stable names based
on some stable attributes of the device, such as a serial number or the
output of various *_id utilities installed by Udev. See also the network
interface renaming example in Section 7.12, “Configuring the network
Script”.

7.12.1. Creating stable names for network interfaces

Instructions in this section are optional if you have only one network
card.
With Udev and modular network drivers, the network interface numbering is
not persistent across reboots by default, because the drivers are loaded in
parallel and, thus, in random order. For example, on a computer having two
network cards made by Intel and Realtek, the network card manufactured by
Intel may become eth0 and the Realtek card becomes eth1. In some cases,
after a reboot the cards get renumbered the other way around. To avoid
this, create Udev rules that assign stable names to network cards based on
their MAC addresses.
First, find out the MAC addresses of your network cards:
grep -H . /sys/class/net/*/address

For each network card (but not for the loopback interface), invent a
descriptive name, such as “realtek”, and create Udev rules similar to the
following:
cat > /etc/udev/rules.d/26-network.rules << "EOF"
ACTION=="add", SUBSYSTEM=="net", SYSFS{address}=="52:54:00:12:34:56",
NAME="realtek"
ACTION=="add", SUBSYSTEM=="net", SYSFS{address}=="00:a0:c9:78:9a:bc",
NAME="intel"
EOF

These rules will always rename the network cards to “realtek” and “intel”,
independently of the original numbering provided by the kernel. Use these
names instead of “eth0” in the network interface configuration files
created below.
Note
Persistent names must be different from the default network interface names
assigned by the kernel.



--
Dancin' in the ruins tonight
mail: echo ee.pbz | perl -pe 'y/a-z/n-za-m/'
Tayo'y Mga Pinoy