Exactly the point. Why else would said 'lawyer'
be so concerned about the fact the archive
contains the spam? Someone wants it removed
because it is potentially damaging to them.
They want the evidence destroyed before it can
be used against them in court. So, if the 'lawyer'
wants to provide legal copyright ownership details, fine, but then
the legal copyright holder could be sued before the evidence is destoyed. Since said 'lawyer' would
want to avoid this, said 'lawyer' will disappear.
Rich can just call the bluff here, and see if
said 'lawyer' responds.
Most likely in this case
'lawyer' == spammer == copyright holder.
Tell the 'lawyer' that you need definitive
proof of the identity of the original author,
and that said 'author' must personally claim
copyright infrigement.
If the original spammer want to claim authorship
of the original spam, fine. Otherwise, I'll bet
you never hear from said 'lawyer' again.
One more point to add. Retailers make or break
their fiscal year (usually ends Jan 31st), based
upon their sales between Black Friday and Jan 31st. At this point in time, things are not looking good for the retailers, so keeping
their pricing strategies under wraps makes
a lot of sense. At the same time, it is also
paranoid on the retailers part, because they
do have time to adjust their prices before
Jan 31st to increase sales. Bottom line, it
probably won't make much difference in the U.S.
due to the state of the economy. All of the
retailers will likely lose money this fiscal
year anyway.
I'm seriously thinking about installing gentoo
on a 486, 16MB, and just for grins,
do it via floppy and dial-up. As long as the
phone line stays up while I need it, I imagine
I can get Gentoo installed in about one month.
Your comparison of Apache and Mozilla is flawed.
Mozilla development has to put up with pressure from
the AOL marketroids.
Kinda dependent upon who is the client
and who is the server, eh?
Get the latest source from here.
As non-root user, create if needed
mkdir ~user/src
cd src
cp ~/tmp/linux.2.5.44.tar.gz.
gunzip -d linux-2.5.44.tar.gz
tar -xvf linux-2.5.44.tar
mv linux-2.5.44 linux-2.5.44-xxx#
# use a unique xxx# (example: yih1 for Your Initials Here 1)
# If you do another build for 2.5.44, then use yih2, etc
cd linux-2.5.44-yih1
# edit the Makefile, and on the 4th line make it
# appear as: EXTRA_VERSION = -yih1
# if you have a.config from a prior build then
cp ~user/src/linux-2.4.18/.config.
# I used 2.4.18 as an example. If you've never
# built a kernel before, you may have a.config
# in/usr/src/linux but it will likely be a
# very full one that will build stuff you don't need
# if you have an old.config
make oldconfig
# that will add new CONFIG_* items that are needed
# note that you'll have to Return your way through
# that to add the new items in a disabled state
# next, whether you had an old.config or not, run
make menuconfig
# go through this from top to bottom.
# it can be confusing at first, but at a
# minimum, get your processor type correct
# Use the help function
# one item you definitely want to enable is
# your IDE or SCSI stuff obviously.
# sorry, I can't provide more guidelines here
# it all depends upon your hardware. You may end
# up with unusable kernels until you get it correct
# which can be very frustrating indeed.
# but once you have a working.config, you'll
# always be able to use that as a base for future builds.
# continuing, still as non-root 'user'
nohup nice make dep clean bzImage modules &
# wait until it's done. I monitor the build via
tail -f nohup.out
# assuming the build is clean[1]
su # no dash, you want to be root but in the 'user' environment
# a pwd here should be ~user/src/linux-2.5.44-yih1
cp arch/i386/boot/bzImage/boot/2.5.44-yih1
# substitute i386 as needed for your platform
cp System.map/boot/System.map-yih1
make modules_install
# edit your/etc/lilo.conf and add a new boot item, and run lilo
# if you use grub, do the grub stuff
# make sure you keep your current kernel boot item in case the new kernel craps out
reboot
note that you don't build the kernel as root,
nor do you put it into/usr/src/linux.
Only the install of the kernel is done as root.
All of the above allows you to keep multiple
kernel trees, and allows you to manage them properly.
[1] - if the build is not clean, try turning
stuff OFF in make menuconfig
Anything new of course may cause compilation failures
I hope that helps, that was all of the top of my head. I'm sure others can point out extra items
to consider.
If the data is not critical or can be easily re-created,
then a filesystem will suffice. But if the data
is critical to the business, and/or not easily
be re-created, the data should go into a real DB that
is Managed Properly(tm).
You don't explain how GPL would remove competition.
Unless you mean that it removes the possibility
that a large corporation could squeeze out it's
competitors.
Otherwise, having the code released under GPL
would encourage enhancements by various parties,
that would/could result in more competitive products. No one entity can out-market their
version of the code with a large war chest.
Their version of said software will have it's
fate decided by the quality of the software.
The Unitied States of America was formed on
the basis of freedom. It is necessary that
the principle of freedom be given to the
software that the U.S. creates with taxpayer
money.
Slashdot Mirror
3 years is equal to 5 years for small values of 5.
So...
XP really does mean eXtra Pain.
The description of this problem sure sounds like Windows behaviour.
Yep. I run two kernel compiles simultaneously to warm up the room.
Most likely in this case 'lawyer' == spammer == copyright holder.
Tell the 'lawyer' that you need definitive proof of the identity of the original author, and that said 'author' must personally claim copyright infrigement. If the original spammer want to claim authorship of the original spam, fine. Otherwise, I'll bet you never hear from said 'lawyer' again.
Fire them now before it's too late.
Then LART the idiot who hired them.
Failure to stop this sickness while
you can will result in major pains later.
There is no silver bullet, never will be.
Logic requires careful thought, and careful thought requires time.
No. HTH. HAND. YIHBT.
One more point to add. Retailers make or break their fiscal year (usually ends Jan 31st), based upon their sales between Black Friday and Jan 31st. At this point in time, things are not looking good for the retailers, so keeping their pricing strategies under wraps makes a lot of sense. At the same time, it is also paranoid on the retailers part, because they do have time to adjust their prices before Jan 31st to increase sales. Bottom line, it probably won't make much difference in the U.S. due to the state of the economy. All of the retailers will likely lose money this fiscal year anyway.
You obviously have never installed Gentoo from stage1.
The process leaves you with plenty of time for other activities.
I'm seriously thinking about installing gentoo on a 486, 16MB, and just for grins, do it via floppy and dial-up. As long as the phone line stays up while I need it, I imagine I can get Gentoo installed in about one month.
Backup twice.
Two cents from (another) old admin.
Are you implying that doing a right-click on a banner ad and selecting 'Block Images from this Server' does not work?
I can see the commercial now, featuring Steve Balmer.
Perhaps the web page in question is intentionally broken in order to avoid overloading the staff.
Your comparison of Apache and Mozilla is flawed.
Mozilla development has to put up with pressure from the AOL marketroids.
Kinda dependent upon who is the client and who is the server, eh?
Get the latest source from here. . .config from a prior build then . .config /usr/src/linux but it will likely be a .config .config or not, run .config, you'll /boot/2.5.44-yih1 /boot/System.map-yih1 /etc/lilo.conf and add a new boot item, and run lilo
As non-root user, create if needed
mkdir ~user/src
cd src
cp ~/tmp/linux.2.5.44.tar.gz
gunzip -d linux-2.5.44.tar.gz
tar -xvf linux-2.5.44.tar
mv linux-2.5.44 linux-2.5.44-xxx#
# use a unique xxx# (example: yih1 for Your Initials Here 1)
# If you do another build for 2.5.44, then use yih2, etc
cd linux-2.5.44-yih1
# edit the Makefile, and on the 4th line make it
# appear as: EXTRA_VERSION = -yih1
# if you have a
cp ~user/src/linux-2.4.18/.config
# I used 2.4.18 as an example. If you've never
# built a kernel before, you may have a
# in
# very full one that will build stuff you don't need
# if you have an old
make oldconfig
# that will add new CONFIG_* items that are needed
# note that you'll have to Return your way through
# that to add the new items in a disabled state
# next, whether you had an old
make menuconfig
# go through this from top to bottom.
# it can be confusing at first, but at a
# minimum, get your processor type correct
# Use the help function
# one item you definitely want to enable is
# your IDE or SCSI stuff obviously.
# sorry, I can't provide more guidelines here
# it all depends upon your hardware. You may end
# up with unusable kernels until you get it correct
# which can be very frustrating indeed.
# but once you have a working
# always be able to use that as a base for future builds.
# continuing, still as non-root 'user'
nohup nice make dep clean bzImage modules &
# wait until it's done. I monitor the build via
tail -f nohup.out
# assuming the build is clean[1]
su # no dash, you want to be root but in the 'user' environment
# a pwd here should be ~user/src/linux-2.5.44-yih1
cp arch/i386/boot/bzImage
# substitute i386 as needed for your platform
cp System.map
make modules_install
# edit your
# if you use grub, do the grub stuff
# make sure you keep your current kernel boot item in case the new kernel craps out
reboot
note that you don't build the kernel as root, nor do you put it into /usr/src/linux.
Only the install of the kernel is done as root.
All of the above allows you to keep multiple kernel trees, and allows you to manage them properly.
[1] - if the build is not clean, try turning stuff OFF in make menuconfig
Anything new of course may cause compilation failures
I hope that helps, that was all of the top of my head. I'm sure others can point out extra items to consider.
You can follow what's going one without filling up your inbox here.
If the data is not critical or can be easily re-created, then a filesystem will suffice.
But if the data is critical to the business, and/or not easily be re-created,
the data should go into a real DB that is Managed Properly(tm).
No, I have white and blue Ethernet cables also.
Perhaps that is why the Cable Company hires contractors to do the installs.
Unless you mean that it removes the possibility that a large corporation could squeeze out it's competitors.
Otherwise, having the code released under GPL would encourage enhancements by various parties, that would/could result in more competitive products. No one entity can out-market their version of the code with a large war chest. Their version of said software will have it's fate decided by the quality of the software.
The Unitied States of America was formed on the basis of freedom. It is necessary that the principle of freedom be given to the software that the U.S. creates with taxpayer money.
...is not to play.
Well sure. They knew he was going to delete all of his e-mail when he got back. Therefore, they have to deliver the trojan the old-fashioned way.