On 04/13/2011 07:52 PM, Przemek Klosowski wrote:
On Wed, Apr 13, 2011 at 12:52 AM, Rafael Skodlarra...@linwin.com wrote:
/boot was added because of crappy BIOS that was not able to handle
cylinders beyond 1024 years ago. That's not needed anymore and makes no
sense either. What good is it
hahahahaha:
http://tldp.org/LDP/Linux-Filesystem-Hierarchy/html/foreward.html
So guess which distributions are not even LINUX. Nevermind Unix.
Regards to all of you, let me go back to hybernation. (and Debian)
Jan de Kruyf.
On Wed, Apr 13, 2011 at 9:26 AM, Erik Christiansen
On 04/14/2011 02:32 AM, Rafael Skodlar wrote:
Not true. You do not need /boot to boot any of multiple OSes installed
on the same system. Grub or LILO for that matter handled that just fine.
It was the BIOS limitation that required to have boot stuff under the
cylinder number 1024. Even that
On Thu, Apr 14, 2011 at 09:31:56AM +0200, Jan de Kruyf wrote:
hahahahaha:
http://tldp.org/LDP/Linux-Filesystem-Hierarchy/html/foreward.html
The guff from freedesktop.org still looks like an April fool's joke to
me, because once another partition is mounted as /usr, then the kernel
isn't goung
because once another partition is mounted as /usr, then the kernel
isn't . . . .
This is probably where the rub is. They have perceived some desperate need
to do things in / for user space while the machine has not even mounted the
partitions.
Smells of windoze thinking. Look ma no brain. And it
On Thu, Apr 14, 2011 at 01:42:32PM +0200, Jan de Kruyf wrote:
because once another partition is mounted as /usr, then the kernel
isn't . . . .
This is probably where the rub is. They have perceived some desperate need
to do things in / for user space while the machine has not even mounted
On 4/14/11, Rafael Skodlar ra...@linwin.com wrote:
On 04/13/2011 07:52 PM, Przemek Klosowski wrote:
On Wed, Apr 13, 2011 at 12:52 AM, Rafael Skodlarra...@linwin.com wrote:
/boot was added because of crappy BIOS that was not able to handle
cylinders beyond 1024 years ago. That's not needed
On 04/14/2011 09:43 AM, Przemek Klosowski wrote:
On 4/14/11, Rafael Skodlarra...@linwin.com wrote:
On 04/13/2011 07:52 PM, Przemek Klosowski wrote:
On Wed, Apr 13, 2011 at 12:52 AM, Rafael Skodlarra...@linwin.com wrote:
/boot was added because of crappy BIOS that was not able to handle
On Tue, Apr 12, 2011 at 02:36:14PM -0400, gene heskett wrote:
I had a link forwarded to me today, which may have a bearing on some
problems I am having with an unrelated linux install.
http://freedesktop.org/wiki/Software/systemd/separate-usr-is-broken
Sure looks scary, but decidedly dufus.
On 04/12/2011 02:36 PM, gene heskett wrote:
I had a link forwarded to me today, which may have a bearing on some
problems I am having with an unrelated linux install.
http://freedesktop.org/wiki/Software/systemd/separate-usr-is-broken
My emc install isn't broken in this manner as /usr is on
On 04/12/2011 03:49 PM, gene heskett wrote:
I suppose technically it is possible to create a /usr directory on the
root partition and populate it with a core collection of programs so
they are available early in booting and then merge the rest of /usr from
another partition later on, but
On 04/12/2011 04:09 PM, Igor Chudov wrote:
I used Linux since 1995. I do not personally see the point of having /usr
mounted separately.
Igor
Years ago, way back when Gene was a young feller, the /usr partition was
(and still is actually, though on some systems /usr/local competes with
this
On 04/12/2011 05:55 PM, Igor Chudov wrote:
The way I see it, /usr is for files given by the distribution, and
/usr/local is for local stuff that was compiled locally. This is how I
always perceived it. But I see your point also.
i
That's one way of looking at it, however, that's not the way
On 04/12/2011 09:17 PM, Jon Elson wrote:
Igor Chudov wrote:
I used Linux since 1995. I do not personally see the point of having /usr
mounted separately.
The idea, I think, is that the /boot file system, and maybe the /root
file system, also, are nearly static.
A static file system is a lot
On 04/13/2011 12:52 AM, Rafael Skodlar wrote:
My Linux experience only goes back to Feb 1994 when it was more than a
toy. If I remember my Slackware from Linux Systems Labs 49 floppy disks
correctly, it acted like most Unix systems of the day with multiple
partitions for this or that.
For a
On Wednesday, April 13, 2011 07:20:57 AM Mark Wendt did opine:
On 04/12/2011 02:36 PM, gene heskett wrote:
I had a link forwarded to me today, which may have a bearing on some
problems I am having with an unrelated linux install.
On 04/13/2011 07:24 AM, gene heskett wrote:
I get a boatload of errors when I run that command too, however, /usr is
in the root partition.
So do I on the shop/emc machine, Mark, so I suspect that command example
needs more fine tuning.
It may be that those errors show up for hardware not
On Wednesday, April 13, 2011 07:24:51 AM Mark Wendt did opine:
On 04/12/2011 03:49 PM, gene heskett wrote:
I suppose technically it is possible to create a /usr directory on
the root partition and populate it with a core collection of
programs so they are available early in booting and
On Wednesday, April 13, 2011 07:40:57 AM Mark Wendt did opine:
On 04/13/2011 07:24 AM, gene heskett wrote:
I get a boatload of errors when I run that command too, however, /usr
is in the root partition.
So do I on the shop/emc machine, Mark, so I suspect that command
example needs
On 04/13/2011 07:36 AM, gene heskett wrote:
On Wednesday, April 13, 2011 07:24:51 AM Mark Wendt did opine:
In the crashes before, / went read-only because something blew the
partition table away. /var was on /, so no logs. I had to re-install.
2 weeks later, same story, re-install something
On 04/13/2011 07:44 AM, gene heskett wrote:
What happens when you do a poweroff from the command line?
On the shop box, a graceful shutdown, but no poweroff. Reboots work too,
and quite snappy too.
I can start a ping to shop, log into it, sudo reboot, and miss less than 40
pings.
Yeah, I
On Wednesday, April 13, 2011 08:00:31 AM Mark Wendt did opine:
On 04/13/2011 07:36 AM, gene heskett wrote:
On Wednesday, April 13, 2011 07:24:51 AM Mark Wendt did opine:
In the crashes before, / went read-only because something blew the
partition table away. /var was on /, so no logs. I
On Wednesday, April 13, 2011 08:07:11 AM Mark Wendt did opine:
On 04/13/2011 07:44 AM, gene heskett wrote:
What happens when you do a poweroff from the command line?
On the shop box, a graceful shutdown, but no poweroff. Reboots work
too, and quite snappy too.
I can start a ping
On 04/13/2011 08:06 AM, gene heskett wrote:
I'm making a SWAG there might be an issue with your swap partition,
rather than umounting /var. If the shutdown is hanging on the Turning
off swap it's probably not getting to the the umount on the /var
partition. Try creating a new swap partition
On Wednesday, April 13, 2011 10:59:44 AM Mark Wendt did opine:
On 04/13/2011 08:10 AM, gene heskett wrote:
On Wednesday, April 13, 2011 08:07:11 AM Mark Wendt did opine:
On 04/13/2011 07:44 AM, gene heskett wrote:
What happens when you do a poweroff from the command line?
On the shop
Mark Wendt wrote:
The /boot dir holds the Linux boot images and remains static only as
long as you don't upgrade your version of the system. The /root
partition only remains static if you don't su or log in as root (that's
it's home dir...) If your /usr partition gets corrupted, at least
On 04/13/2011 12:03 PM, Jon Elson wrote:
Mark Wendt wrote:
The /boot dir holds the Linux boot images and remains static only as
long as you don't upgrade your version of the system. The /root
partition only remains static if you don't su or log in as root (that's
it's home dir...) If your
On Wed, Apr 13, 2011 at 12:52 AM, Rafael Skodlar ra...@linwin.com wrote:
/boot was added because of crappy BIOS that was not able to handle
cylinders beyond 1024 years ago. That's not needed anymore and makes no
sense either. What good is it booting kernel from /boot and then fail to
access
I had a link forwarded to me today, which may have a bearing on some
problems I am having with an unrelated linux install.
http://freedesktop.org/wiki/Software/systemd/separate-usr-is-broken
My emc install isn't broken in this manner as /usr is on /, but it still
throws 31 errors using that
On 4/12/2011 2:36 PM, gene heskett wrote:
I had a link forwarded to me today, which may have a bearing on some
problems I am having with an unrelated linux install.
http://freedesktop.org/wiki/Software/systemd/separate-usr-is-broken
My emc install isn't broken in this manner as /usr is on /,
On Tuesday, April 12, 2011 03:35:10 PM Kent A. Reed did opine:
On 4/12/2011 2:36 PM, gene heskett wrote:
I had a link forwarded to me today, which may have a bearing on some
problems I am having with an unrelated linux install.
I used Linux since 1995. I do not personally see the point of having /usr
mounted separately.
Igor
On Tue, Apr 12, 2011 at 2:49 PM, gene heskett ghesk...@wdtv.com wrote:
On Tuesday, April 12, 2011 03:35:10 PM Kent A. Reed did opine:
On 4/12/2011 2:36 PM, gene heskett wrote:
I had a link
On 4/12/2011 4:09 PM, Igor Chudov wrote:
I used Linux since 1995. I do not personally see the point of having /usr
mounted separately.
Igor
Igor:
Some of us came to Linux with prior experience using Unix. To quote a
footnote from the Wikipedia article on the Filesystem Hierarchy Standard
On Tue, Apr 12, 2011 at 3:44 PM, Kent A. Reed knbr...@erols.com wrote:
On 4/12/2011 4:09 PM, Igor Chudov wrote:
I used Linux since 1995. I do not personally see the point of having /usr
mounted separately.
Igor
Igor:
Some of us came to Linux with prior experience using Unix. To quote
34 matches
Mail list logo
