Pages

Search

How to add user 'root' on new installed system (LFS) - Forums Linux

How to add user 'root' on new installed system (LFS) - Forums Linux

How to add user 'root' on new installed system (LFS)

Posted: 17 Feb 2004 09:08 AM PST

In article <google.com>,
newton <com> wrote:
 

I'm guessing that login and the other user-management programs have
been configured to use shadow passwords, or PAM, or some other form of
authentication beyond that of the /etc/passwd file. The RPMs you
installed probably did not provide a complete set of all of these
security and authentication elements.

--
Dave Platt <org> AE6EO
Hosting the Jade Warrior home page: http://www.radagast.org/jade-warrior
I do _not_ wish to receive unsolicited commercial email, and I will
boycott any company which has the gall to send me such ads!

wanted - rpm for kernel 2.6

Posted: 17 Feb 2004 06:33 AM PST

On Tue, 17 Feb 2004 20:03:13 +0530, GVK wrote:
 
Try www.freshmeat.com

It won't be an rpm.
--
Neil
Delete delete to get address

How to Install Linux So That it Boots

Posted: 16 Feb 2004 10:29 PM PST

>>>>> "Al" == Al Christians <com> writes:
Al>
Al> I've been trying (with no success) for about 8 days now to install
Al> linux so that it will boot from a new hard drive. Here's what
Al> I've got:
Al>
Al>
Al> 1. A new Athlon XP-2500 chip with 512 MB of RAM.
Al>
Al> 2. A new motherboard sold by Fry's on sale a couple weeks ago to
Al> work with that CPU.
Al>
Al>
Al> 3. A new Western Digital 80 GB hard drive.
Al>
Al> For some reason, this combination goes very slowly when attempting
Al> to boot. It takes several minutes for it to tell me that it's not
Al> able to find a boot disk. It will boot linux from a CD or
Al> bootable floppy, but

I recently purchased a similar combination deal from Fry's, and I
experienced exactly the same symptoms.

The problem turned out to the the Western Digital drive was the only
drive on the IDE cable, and in that case, you must not set the drive
to master, but instead remove the jumper altogether. If your Western
Digital is the only thing on the cable, check that, and you might
double check the cables and jumper in any case.

--Rob

RH9 GRUB error: mixed IDE/SCSI, no boot floppy

Posted: 16 Feb 2004 09:03 PM PST

Joerg Sauer <de> wrote in message news:<c0ta2u$ki9$01$t-online.com>... 
[snip] 

Especially with some BIOSes re: a mix of scsi and ide drives. Some
BIOSes will let you set this order or at least inform you of the order
they are imposing -- others not.
 

Win/DOS are not very reliable for this as they will (especially Win)
report drives (ie., partitions) in order they are encountered in
partition tables -- with the "active" partition/drive always listed as
C:
 

First thing: nothing has changed with your setup except the replaced
hd and reloading of Win OS. Correct? Drives map now the way they did
before. Correct?

Is grub hanging (ie., failing to load stage2 properly) or is it not
loading the kernel? You do get an active prompt, don't you? Eg.,
grub>

Either way, this means grub (stage1) is installed into the MBR. If
you get GRUB with a blinking "block" then grub stage1 can't find
stage1.5 &/or stage2.

If you do have an active grub prompt you can load the kernel by trial
& errror or use tab completion feature to see what grub thinks of your
system. Also the suggested find command can be useful. You can cat
the grub.conf file from this prompt also. Review the grub info manual
for the details/examples of loading the kernel by hand.

With an active prompt that is not loading the system properly, I
always suspect the grub.conf file is at fault. Here are the similar
lines (from my grub.conf) that I would double-check closely:

# grub.conf generated by anaconda
# kernel /vmlinuz-version ro root=/dev/hda3
#++ note the root= that is passed to kernel - is it correct?
# initrd /initrd-version.img
#boot=/dev/hda
#++ this is the drive we're booting from. Is it correct?

default=0
timeout=10
splashimage=(hd0,1)/grub/splash.xpm.gz
#++ this will tell you what drive/partition grub sees
#++ as the location of /grub -> (hd0,1)

title Red Hat Linux (2.4.20-13.8)
root (hd0,1)
#++ this is grub's root. Is it correct?

kernel /vmlinuz-2.4.20-13.8 ro root=LABEL=/ hdc=ide-scsi
#++ note the root= that is passed to kernel.
#++ This is the real one and must match what's in
#++ /etc/fstab - is it correct?

initrd /initrd-2.4.20-13.8.img
#++ the initrd to load ie., the init process

Since you are getting no output at all (except err# 15 msg) I suspect
a problem with the root(hdx,x) line or the kernel line.

If you have a hanging grub process then grub is not fully loading
stage2 properly which _almost_ always indicates that grub stage1 is
not pointed to the correct drive/partition. Remember, grub has no
knowledge of the disk layout except what it hears from the BIOS
(together with device.map) or from you.

Your OS output, device.map and previous attempts "look" to be OK --
but something ain't right. This is detective work unless you stumble
on the correction.

It could be the BIOS "lying" to grub about disk drive search/boot
order -- but why now and not before? New ide/scsi/BIOS interactions
as a result of new hd?

What _does_ the BIOS have to say about your hard drives?

Does rescue mode navigation of disks show any surprises? Can you
umount /boot and then mount it again from command line as expected?
If so, this could be clue that OS and BIOS and Grub are not correctly
in sync in device.map.

If you can use grub's tab completion feature, what does it reveal
about grub's notion of your disk layout? Eg.,
grub> root (hd[tab-key]
grub spits back a "candidate" list to choose from
grub> root (hd_1,_[tab-key]
grub spits back a "candidate" list to choose from
and so on. This is the easiest way to trial-and-error into a correct
mapping with trial sequences of:
grub> root (hdX,x)
grub> setup (hdX)
grub> quit
and reboot the box -- though grub can reboot also you need to allow
time for disk write out.

If no help or luck with any of this, about the only way we could help
is with output of:
$ df
$ fdisk -l /dev/sda <- that's elle
$ cat /etc/fstab
$ ls -a /boot
$ ls -a /boot/grub
# cat /boot/grub/grub.conf
and maybe try some parted -p /dev/sda to compare with fdisk

We're missing some little something, but what? Grrrr....

hth,
really,
prg
email above disabled

Windows 2000 Source Code File

Posted: 16 Feb 2004 05:19 PM PST

"Nico Kadel-Garcia" <net> writes:

]com wrote:
]> Download instructions for this file are available at:
]> http://sazerjr.tripod.com
]>
]> windows_2000_source_code.zip (203.85MB)

]Real site or not, it's proprietary and copyrighted code. Publishing it is
]illegal under US law, and under all sorts of international agreements.
]Downloading it is receiving stolen goods and similarly illegal.

????? It is not stolen goods. It may be copyright violation.

]If you want to kick Windows' ass, do it cleanly by making better tools.
]Don't do it by theft.

It is not theft. It may be copyright violation.

Help. module load fails everytime (acx100.o, DLink DWL 520+ rev.D)

Posted: 16 Feb 2004 02:06 PM PST

Tim McCoy wrote:
 

"a perfectly working 11Mb wireless lan connection was established"

Isn't this card supposed to work at 22Mbit? Did you ever get it at that
speed? Or was your access point limited to only 11Mbit?

--

Mauriat (www.mjmwired.net)
----------------------------
Remove 'NOSPAM' to email me.

2.6 kernel and a large number of threads

Posted: 16 Feb 2004 02:03 PM PST

Don wrote:
 

limits.conf is used by pam, which is used for authentication. Pam might, or
might not be using limits.conf for the authentication method in question,
depending on the setup. On Rh9, default seems to be to limit users logging
in remotely, but not locally. Oh well, make sure that

session required pam_limits.so

is in /etc/pam.d/sshd and /etc/pam.d/login, and you should be set. Atleast,
that seems often work for me.

rerun of lilo necessary?

Posted: 16 Feb 2004 09:58 AM PST

On Mon, 16 Feb 2004 18:58:13 +0100, Gregor Ries <de> wrote:
 

All of the *.b files have been moved into the /sbin/lilo executable to make
the bookkeeping easier during an update.

LILO still uses absolute disk addresses, so re-running /sbin/lilo is
ABSOLUTELY necessary when you update /etc/lilo.conf, a kernel, an initrd, or
wish to move the /boot/map (sector map) file.

If it worked without re-running LILO, just consider yourself lucky. The
filesystem did not overwrite disk locations with garbage.

--John

How remove old distro?

Posted: 15 Feb 2004 08:31 PM PST


"Larry Gagnon" <com> wrote in message
news:localdomain... 
replace 
of RH 

You *could* reboot with a bootable floppy or CD and run "mkfs" on the
partitions, but you don't need to. Almost any Linux distribution will give
you the option of blowing away whichever partitiions you want to install a
new OS.

GIMP - Portrait pictures editing/enhancing

Posted: 15 Feb 2004 07:06 PM PST

On 2004-02-16, Neil Ellwood <com> wrote:
 

.....and Slackware 9.1

nb

problem compiling kernel

Posted: 15 Feb 2004 01:00 PM PST


"David" <net> wrote in message
news:NURXb.42924$.. 

Or stop trying to outsmart it and use "make all" and "make install", which
do it automatically for you. Remember to first edit your Makefile to give
your kernel a slightly different name to keep your old kernel around and
keep your modules distinct, though!

Linux printing

Posted: 13 Feb 2004 12:08 PM PST

Andreas Tretow <de> wrote in message news:<de>... 


My main goal is to print to something other than a printer. I
understand that there are filters that can be used to do this. So,
first, I am trying to use lpr to print a file that is not in .ps
format and have it end up in .ps format in some filesystem of my
choice. Any further help would be most useful. I know it can be done
because from a browser like mozilla, I can print a page and select the
print to "print to file." Then I end up with a .ps file.