Pages

Search

Can new Mandriva install co-exist in GRUB with Suse? - Forums Linux

Can new Mandriva install co-exist in GRUB with Suse? - Forums Linux

Can new Mandriva install co-exist in GRUB with Suse?

Posted: 28 Mar 2007 09:01 PM PDT

On Thu, 29 Mar 2007 11:29:02 +0100, David Bolt wrote:
 
 

Not according to OP.

GRUB has menu.lst under /boot. For Suse, its entry is
title Suse
root (hd0,0)
kernel /vmlinuz root=/dev/sda11 vga=795 etc.

with the new GRUB entry as follows
title Mandrive 2007
root (hd0,0)
kernel /vmlinuz /root=dev/sda16 vag=795 etc.

Both call for "root (hd0,0)" and "kernel /vmlinuz", which means they both
use the same kernel. Having different / partitions means one or the other
will have a mismatch with /lib/modules, and also kernel sources in
/usr/src/linux, which won't help a bit with Nvidia or ATI driver
compilation.
 
 

Who misread the partition used for Mandriva?
 

Actually, I use the same boot partition for a number of OS installs. I
just never mount it. I have kernel entries;

kernel (hd0,0)/suse10.0/vmlinuz root=...
kernel (hd0,0)/suse10.1/vmlinuz root=...
kernel (hd0,0)/man2007/vmlinuz root=...

with corresponding initrd entries in my menu.lst stanzas. Each OS has a
directory with its name on it that contains the kernel, initrd,
System.map, etc. that goes with that OS.
 

My mind always does that. ;)

--
imotgm
"Lost? Lost? I've never been lost... Been a tad confused for a
month or two, but never lost."

unsatisfied Linux lover

Posted: 28 Mar 2007 11:45 AM PDT

The Natural Philosopher wrote:
 

Your DOS? Stick it in your ass.

FREE Linux Shell Provider

Posted: 27 Mar 2007 02:32 PM PDT

On Tue, 27 Mar 2007 19:02:52 -0400, Chris M <edu> wrote:
 

*.mine.nu is a freebie domain from dyndns.org

Grant.
--
http://bugsplatter.mine.nu/

lirc 0.8.1 won't configure

Posted: 25 Mar 2007 04:53 PM PDT

On Mar 26, 9:19 pm, "Jim" <com> wrote: 
Forget about Old Debian 3.1r5 and install new Debian/Etch 4.0

You find it at http://www.debian.org/devel/debian-installer/

It has lit 0.8.0 packed for Debian/Etch
 

Is this realy all messages you get?

What does lirc README tell you what other programming libraries is
needed to program this?
 

I would install Debian/Etch 4.0 and not old Debian/Sarge 3.1

/Jackson

Boot log

Posted: 25 Mar 2007 06:57 AM PDT

I wrote: 

Old guy writes: 

BOOTLOGD(8) Linux System Administrator's Manual BOOTLOGD(8)

NAME
bootlogd - record boot messages

SYNOPSIS
/sbin/bootlogd [-c] [-d] [-r] [-s] [-v] [ -l logfile ] [ -p pidfile ]

DESCRIPTION

Bootlogd runs in the background and copies all strings sent to the
/dev/console device to a logfile. If the logfile is not accessible,
the messages will be kept in memory until it is.

OPTIONS
-d Do not fork and run in the background.

-c Attempt to write to the logfile even if it does not yet exist.
Without this option, bootlogd will wait for the logfile to
appear before attempting to write to it. This behavior
prevents bootlogd from creating logfiles under mount points.

-r If there is an existing logfile called logfile rename it to
logfile~ unless logfile~ already exists.

-s Ensure that the data is written to the file after each line by
calling fdatasync(3). This will slow down a fsck(8) process
running in parallel.

-v Show version.

-l logfile
Log to this logfile. The default is /var/log/boot.

-p pidfile
Put process-id in this file. The default is no pidfile.

BUGS

Bootlogd works by redirecting the console output from the console
device. (Consequently bootlogd requires PTY support in the kernel
configuration.) It copies that output to the real console device
and to a log file. There is no standard way of ascertaining the
real console device if you have a new-style /dev/console device
(major 5, minor 1) so bootlogd parses the kernel command line
looking for console=... lines and deduces the real console device
from that. If that syntax is ever changed by the kernel, or a
console type is used that bootlogd does not know about then bootlogd
will not work.

AUTHOR
Miquel van Smoorenburg, nl

SEE ALSO
dmesg(8), fdatasync(3).

Jul 21, 2003 BOOTLOGD(8)

--
John Hasler
gt.org
Dancing Horse Hill
Elmwood, WI USA

What did aptitude fail to do when it installed telnetd?

Posted: 24 Mar 2007 02:39 PM PDT

In comp.os.linux.networking Jim <com> wrote: 

Ok, lets check some file ownerships and permissions:

ls -l /usr/sbin/in*

-rwxr-xr-x 1 root root 22720 2006-02-07 02:21 inetd
-rwxr-xr-x 1 root root 35940 2005-10-09 17:24 in.telnetd

ls -l /usr/lib/telnetlogin

-rwsr-xr-- 1 root telnetd 6032 2005-10-09 17:24 /usr/lib/telnetlogin

Note: suid
 

Check that they also exist in shadow and gshadow.

grep "telnet" /etc/services

telnet 23/tcp
telnet 23/udp

cat /etc/hosts.allow

ALL: 127.0.0.1

Is inetd running as root?

ps -ef|grep "inetd"
root 21241 1 0 Feb26 ? 00:00:34 /usr/sbin/inetd

Try adding "-a none" to telnet command in inetd.

Try running the telnetd and -D debugging options. I believe that you can use
sudo to run an user telnetd.

There may be some issues with PAM modules, but I don't know much about these.

Regards,

Mark.

--
Mark Hobley
393 Quinton Road West
QUINTON
Birmingham
B32 1QE

Telephone: (0121) 247 1596
International: 0044 121 247 1596

Email: markhobley at hotpop dot donottypethisbit com

http://markhobley.yi.org/

HOWTO: turn one linux PC into multple stations for kiosk

Posted: 24 Mar 2007 05:50 AM PDT



com wrote:
 

Did you check out Lew Pitcher's post or my post? These both seem to be
exactly what you want. One for free and one for a fee.

bootable floppy for Debian-on-USB

Posted: 22 Mar 2007 07:48 AM PDT

On Mon, 26 Mar 2007 14:30:05 -0700, orange wrote:
 
OT: I see you are posting from Google. The default settings do not follow
the etiquette guidelines for this newsgroup. For example, it is good
etiquette to quote some context in replies, not to top post, etc.

On topic: I assume there are bootdisks available for Debian, and all of
its derivatives. Ubuntu is one popular derivative. I don't know enough
about what you are asking to offer any more specific advice.

One "circularity" that I have noticed about setting up GNU/Linux is that
it often requires a running Linux. This is a classic "Catch 22,"
if you are already having trouble booting GNU/Linux at all. IIRC, help
with bootstrap is the topic of this thread. Have you found a way around
that obstacle? If you have never setup before, then I think it
would be easiest to follow the standard setup procedure.I don't know
which distributions will "magically" setup to flash as a working target.
The dramatic size increase in flash make it an attractive target to
encapsulate a GNU/Linux environment, including the bootloader, etc. As my
"slackware on stick" post shows, making the adaptation is not too
difficult, at least when using Slackware.

Going Off-topic: I run Slackware, not Debian. Some of the specifics of
startup are distribution dependant; such as, making an initrd. An initrd
is often required when dealing with USB devices because most generic
kernels include USB support through kernel modules. See my previous
referenced link earlier in this thread for an example.

I have two "startup environments" which are Slackware based. The
techniques used in those environments can probably be adapted to any
GNU/Linux, but I prefer Slackware.

1. 10.2-live
http://www.xmission.com/~ddmayne2/10.2-live
2. erf-dm
http://www.xmission.com/~ddmayne2/erf-dm

I also have two generic boot images which can help boot in some
circumstances (again, I make no claim to applicability to your
situation):

1. generic grub bootable CD
http://groups.google.com/group/comp.os.linux.setup/msg/602040b59e1eac50
2. SBM bootable floppy image
http://groups.google.com/group/comp.os.linux.setup/msg/e56c561db0f77fa9

--
Douglas Mayne

hi...iam a student from nit warangal india plz help me in linux encrypted file system project...

Posted: 21 Mar 2007 12:59 PM PDT

On Tue, 27 Mar 2007 08:09:51 +0200, Matthias Fassl wrote:
<snip> 
<snip> 
<snip> 
Cryptographic features have gone through quite a bit of evolution.
Hopefully, they will settle down now with the built in support provided by
device mapper (see below.) I never used the CFS in the article you
referenced, but I did use cryptoloop, and now device mapper.

Device Mapper: The 2.6.x kernel supports encryption via device mapper's
dmcrypt module. Device mapper replaces cryptoloop. The OP may want to use
a more up to date distribution with support for the 2.6.x kernel. In
addition to kernel support, you probably want the tool crypsetup from the
luks project. Other than that, you can add a fast and transparent
cryptographic "pipeline stage" just above the hardware device level. The
example below is an overview of how it works, AIUI:

Suppose /dev/hda7 is available and you would like to encrypt its future
contents. I will use the XFS on top of device mapper, because it is a
journaled filesystem with a good reputation.

To illustrate:
/dev/hda7 -> real partition
/dev/mapper/hda7 -> dmcypt encryption associated with /dev/hda7

Use cryptsetup to make the association:
# cryptsetup -h plain -c aes256 create hda7 /dev/hda7

Format the encrypted device:
# mkfs.xfs /dev/mapper/hda7

Mount it;
# mount /dev/mapper/hda7 /mnt/hda7

Now, when you write to the object mounted, this occurs:

file write -> mount (/mnt/hda7) -> filesystem layer -> encryption via
dmcrypt -> physical write from device (/dev/hda7)

And when you read from the object mounted, this occurs

file read <- mount (/mnt/hda7) <- filesystem layer <- decryption via
dmcrypt <- physical read from device (/dev/hda7)

This article has some good examples:
http://linuxgazette.net/114/kapil.html

Follow along and practice with some of the examples. Use caution if
working as the root user and directly with partitions, or use a disposable
system for practice sessions.

--
Douglas Mayne

Ubuntu video failure on LiveCD boot/install - 6.06LTS, 6.10 and Feisty Faun

Posted: 20 Mar 2007 11:41 PM PDT

Resolved by looking at what video card Knoppix deteced, copying the
xorg file onto a USB memory drive, rebooting Ubuntu, dropping into
text mode, and adding in to the virtual filesystem the xorg file. Fawn
now finds the right driver, and all's well.

Video Adapter Driver problem w/ FC6

Posted: 15 Mar 2007 12:49 PM PDT

Richard Vaughn <com> wrote: 

What happens if you remove the 800x600 and smaller screen sizes, leaving only
1024x768 in the "Screen" sections of the XF86Config file?

Does this give you a higher resolution?

Regards,

Mark.

--
Mark Hobley
393 Quinton Road West
QUINTON
Birmingham
B32 1QE

Telephone: (0121) 247 1596
International: 0044 121 247 1596

Email: markhobley at hotpop dot donottypethisbit com

http://markhobley.yi.org/